Beta
×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

XP SP3 Crashes Some AMD Machines

kdawson posted more than 6 years ago | from the workarounds-emerge dept.

Windows 267

Stony Stevenson alerts us to new information on the XP SP3-induced crashes that we discussed a few days back. Jesper Johansson, a former program manager for security policy at Microsoft, is maintaining an ongoing log and support site for users affected by any of several problems triggered by XP3. Machines using AMD hardware, particularly HP desktops, seem to have several modes of failure; others affect Intel machines.

cancel ×

267 comments

Sorry! There are no comments related to the filter you selected.

Typical Microsoft (4, Funny)

mrbluze (1034940) | more than 6 years ago | (#23373852)

I suppose now we have to wait until "Windows XP Service Pack 3" Service Pack 1 comes out before it becomes usable.

Re:Typical Microsoft (1)

DanWS6 (1248650) | more than 6 years ago | (#23373892)

I've been using SP3 RC for a few months now without any problems. It's weird to see so many other people having issues.

Re:Typical Microsoft (-1, Troll)

Anonymous Coward | more than 6 years ago | (#23374650)

I've been using SP3 RC for a few months now without any problems.

Great. Another Winshill who can't understand that they are not the whole world.

Re:Typical Microsoft (1, Insightful)

Anonymous Coward | more than 6 years ago | (#23373964)

typical slashdot; post anything about ms that crashes but i still don't see where slashdot covered how feisty fawn fucked hp tablet owners even though there are several sites that cover the issue. i guess linux failures just aren't newsworthy?

Re:Typical Microsoft (5, Funny)

mrbluze (1034940) | more than 6 years ago | (#23373978)

i still don't see where slashdot covered how feisty fawn fucked hp tablet owners
That wasn't a bug, that was a feature!

Re:Typical Microsoft (5, Funny)

truthsearch (249536) | more than 6 years ago | (#23374002)

Wow, you're right. With the Linux HP tablet market being about the same size as the Windows desktop + laptop market I'm surprised it didn't get more press.

Re:Typical Microsoft (1)

willyhill (965620) | more than 6 years ago | (#23374200)

With the Linux HP tablet market being about the same size as the Windows desktop + laptop market I'm surprised it didn't get more press.

With the size of the Windows desktop market I'm surprised that this gets so much press.

But we all know why these stories are run here, don't we.

Re:Typical Microsoft (0)

Anonymous Coward | more than 6 years ago | (#23374460)

There's a simple explanation. [slashdot.org]

Re:Typical Microsoft (1)

pallmall1 (882819) | more than 6 years ago | (#23374624)

...i still don't see where slashdot covered how feisty fawn fucked hp tablet owners...
What image of feisty fawn did HP pre-install on the tablet?

Re:Typical Microsoft (0, Troll)

Dana W (1281070) | more than 6 years ago | (#23374736)

Oh no? you are one of the ten people who bought a tablet PC? Wow, sucks to be you. Least Ubuntu updates fix things, not break them.

Re:Typical Microsoft (-1, Troll)

Anonymous Coward | more than 6 years ago | (#23374028)

WINDOWS VISTA LOL

Re:Typical Microsoft (3, Funny)

timberwolf753 (1064802) | more than 6 years ago | (#23374402)

Windows Vista another name for "You been Rick Rolled Bitch"

Re:Typical Microsoft (2, Insightful)

Anonymous Coward | more than 6 years ago | (#23374330)

This is why I always wait at least a few months to apply a new service pack. I don't feel like being Microsoft's beta tester. ;)

Frist Pr0st (-1, Troll)

Anonymous Coward | more than 6 years ago | (#23373856)

Frist Pr0st !!!!!!!!!!!!!!

Mahahahahahhahahaaaaaaaaaaaaaaaaaaaaaaaaaaaa !!!

Man I hate Windows

Re:Frist Pr0st (5, Funny)

Anonymous Coward | more than 6 years ago | (#23373914)

Bah, you beat me to it. I was trying to get it, but I have SP3 installed on my computer and it crashed >.

Re:Frist Pr0st (3, Funny)

flyingfsck (986395) | more than 6 years ago | (#23374678)

First Vista Post!

Uhh, hello? Anybody still there?

Ulterior motive (4, Funny)

Facetious (710885) | more than 6 years ago | (#23373872)

You see, SP3 is actually a tool to make users believe they should upgrade to Vista. Relax, I'm just being Facetious.

Re:Ulterior motive (3, Insightful)

wizardforce (1005805) | more than 6 years ago | (#23373946)

yeah, not so much upgrade to Vista as try to keep those on XP from fleeing Windows like rats on a sinking ship.

Re:Ulterior motive (2, Insightful)

CSMatt (1175471) | more than 6 years ago | (#23373970)

Seems like these crashes would be doing the opposite.

Re:Ulterior motive (3, Insightful)

wizardforce (1005805) | more than 6 years ago | (#23374158)

my point was that SP3 was supposed to try to retain current windows users in the face of vista's failure to impress. SP3 instead seems to be driving people away at least until/if it gets fixed.

There is only one problem with this theory (5, Insightful)

zappepcs (820751) | more than 6 years ago | (#23374448)

Quite simply, if MS wanted to keep customers they would create a product with zero problems (or as close as they can get) and push it out at a VERY competitive price. That is how the marketplace is supposed to work. When your namebrand is trashed, you have to compete extra hard. MS seems unwilling to do this, or at least has failed to show that they are trying to do so.

That might just be bad business decisions on their part, but whether it was malicious or stupidity does not matter. In either case the end result is that MS loses more customers. Nobody wanted to hear that MS was losing or soon to be dead a year ago when predictions were rife, but here it is, in your face. MS is consistently failing to either impress or produce quality product. The dragon^H^H^H^H^Hcathedral is near death... is it time for the penny market to celebrate?

Not on your life, it will be time to celebrate when the dried bones of the dragon are used up as party favors. Until then, it is time to keep competing aggressively, and nothing short of that will do. Competition, not patents, drives innovation. Innovation will bring us secure computing at home. A kind of secure that behaves friendly to the end user.

Now, am I bashing MS for pleasure? No, it is because MS products are in their deathbed and nothing short of a complete restart will get them out of it. It does not appear that MS will do that. There is nothing in current or near future activity that shows MS will do anything different from what got them in the death bed to start with. The beast is dieing. There is nothing more to say.

Call that a troll if you will, but the truth hurts sometimes. Do I want it to die? NO! Emphatically NO!!!! Without competition, quality dies. Would I like to see MS slide into a comfortable second place? Yes.... and the reasons are simple, just ask any Linux fanboi for them.

SP3 failed utterly in the face of the current market that MS faces. There is NO excuse for that in business. If you believe the art of war extends to business, MS deserves to be beheaded ungracefully. That is how business goes, so don't bother telling me that I'm a troll.

Re:Ulterior motive (1)

doomy (7461) | more than 6 years ago | (#23374398)

I thought DirectX 10 was supposed to do this.

Re:Ulterior motive (5, Funny)

WaroDaBeast (1211048) | more than 6 years ago | (#23374612)

No, no, and no again. SP3 is meant to prepare XP users to an unstable environment.

Only one crash (1)

jupiterssj4 (801031) | more than 6 years ago | (#23373888)

Only had one problem on my Acer Laptop (TravelMate 8210) with SP3, it forgot that I had a wireless card, restarted and been fine since then (almost a week) so I'd say no problems for me

Re:Only one crash (4, Funny)

Whiney Mac Fanboy (963289) | more than 6 years ago | (#23373926)

Only had one problem on my Acer Laptop (TravelMate 8210) with SP3, it forgot that I had a wireless card, restarted and been fine since then (almost a week) so I'd say no problems for me

Wow! Your anecdote (in which you don't even mention if you're using intel or AMD) has totally changed my mind about the reliability of SP3!

Re:Only one crash (2)

jupiterssj4 (801031) | more than 6 years ago | (#23373998)

It's an Intel T7400, I was hoping that people would look it up, highest end when I bought it last year

Re:Only one crash (5, Funny)

BlueCollarCamel (884092) | more than 6 years ago | (#23374000)

My machine works fine with SP3, not a single problem. How's two anecdotes for ya, bitch?

Re:Only one crash (5, Funny)

PacoCheezdom (615361) | more than 6 years ago | (#23374058)

Re:Only one crash (1)

BlueCollarCamel (884092) | more than 6 years ago | (#23374228)

My post was a reference to that... I guess I should have linked it as well.

Re:Only one crash (-1, Flamebait)

Anonymous Coward | more than 6 years ago | (#23374250)

And yet a couple stories posted to the bastion of unbiased reporting that is slashdot was all that was required to set your mind in the first place. Have you even tried SP3?

Didn't think so. Hypocrite.

Re:Only one crash (2, Insightful)

i.of.the.storm (907783) | more than 6 years ago | (#23374286)

Similarly, these anecdotes about SP3 crashing computers have totally changed my mind about the reliability of SP3. It works both ways...

Re:Only one crash (0)

Anonymous Coward | more than 6 years ago | (#23374422)

Wow! You don't trust some random user! That must be a sure sign of SP3 breakage!

Hey, wait a minute! (4, Insightful)

M1rth (790840) | more than 6 years ago | (#23373920)

Headline singles out AMD machines, body indicates that AMD and Intel are equally affected by various modes of crash. Sounds like someone's trying to drum down AMD stock or something... nah, we'd never have a processor partisan writing for Slash would we?

Re:Hey, wait a minute! (1)

mrbluze (1034940) | more than 6 years ago | (#23373944)

Headline singles out AMD machines, body indicates that AMD and Intel are equally affected by various modes of crash. Sounds like someone's trying to drum down AMD stock or something... nah, we'd never have a processor partisan writing for Slash would we?
Possibly, but how many people with enough money are going to take this seriously? Suspecting stock options bought around the blowing up of the twin towers is fair enough, but trying to make a buck on the stocks via Slashdot is a it obtuse, don't you think?

Re:Hey, wait a minute! (1)

mrbluze (1034940) | more than 6 years ago | (#23373960)

Actually this sounds more like Microsoft deliberately trying to drum down their stock prices. Are they planning a share buy-back or something?

Re:Hey, wait a minute! (3, Funny)

that this is not und (1026860) | more than 6 years ago | (#23374688)

Maybe they're trying to drive the price of their stock down in hopes that Yahoo will be able to afford to buy them.

Re:Hey, wait a minute! (5, Informative)

TheSHAD0W (258774) | more than 6 years ago | (#23373962)

Apparently it's mostly AMD machines that had some Intel-specific drivers installed.

Easiest way to fix the problem, before installing SP3, open a CMD window, and type "sc config intelppm start= disabled".

Re:Hey, wait a minute! (1)

Joe The Dragon (967727) | more than 6 years ago | (#23374014)

and stop buying oem systems and build your own or do a clean install with out all the oem crap / bloat.

Re:Hey, wait a minute! (0)

Anonymous Coward | more than 6 years ago | (#23374172)

and stop buying oem systems and build your own or do a clean install with out all the oem crap / bloat.

Spoken like a true idiot. I built a half-dozen or so machines until I started to place a higher value on my time...happens when you have kids and a stressful job. Don't like HP desktops? Then try a different vendor or buy a machine targeted towards the business sector (not as much stuff pre-installed).

Re:Hey, wait a minute! (1)

BlueCollarCamel (884092) | more than 6 years ago | (#23374296)

Because everyone knows how, has the time or will to do so, right?

Re:Hey, wait a minute! (2, Interesting)

westlake (615356) | more than 6 years ago | (#23374590)

and stop buying oem systems and build your own or do a clean install with out all the oem crap / bloat.

That won't solve the problem when some obscure motherboard driver or hardware failure sends your system into a tail spin.

I'll take the odds that the most difficult problems to diagnose are with the custom builds. The video card that has worked loose from its slot. The driver that hasn't been updated since August 2001.

Re:Hey, wait a minute! (5, Funny)

Anonymous Coward | more than 6 years ago | (#23374566)

You see, that's why Windows will never be ready for the desktop: Until you get rid of all that command line gibberish, I'll never be able to install it on my grandmother's computer.

Rename the topic to say INTEL drivers on AMD systm (5, Informative)

Joe The Dragon (967727) | more than 6 years ago | (#23373940)

Rename the topic to say INTEL drivers on HP AMD systems is the cause.
The topic you have makes AMD look bad.

Why is HP useing the same basic image for there amd and intel systems?

What other driver bloat is in OEM systems?

Is INTEL coding there drivers to mess up AMD systems?

AMD legal should take a look at this.

I have SP3 running on my AMD right now and it's works 100%

Re:Rename the topic to say INTEL drivers on AMD sy (2, Insightful)

Dencrypt (1068608) | more than 6 years ago | (#23374032)

It's all in the eye of the beholder. To me, the topic says: "M$ can't make software for other architectures than intel." or; "M$ can't make software. Period." Hopefully people read a lot more than just topics though.

Re:Rename the topic to say INTEL drivers on AMD sy (4, Insightful)

Anonymous Coward | more than 6 years ago | (#23374178)

Yeah because it's definitively Microsoft's fault that HP is packing Intel drivers on their AMD machines. Typical baseless Microsoft Hatred.

Re:Rename the topic to say INTEL drivers on AMD sy (4, Interesting)

Khyber (864651) | more than 6 years ago | (#23374048)

HP should NOT be using the same image for their Intel and AMD-based systems. There's always one for the Intel systems and one for AMD systems of each type (So, a DV2000 laptop has two generic system images, one for Intel-based and one for AMD-based. It's almost ALWAYS been this way.)

By the way, this appears to be Microsoft's problem, since HP maintains and is responsible for their own recovery images (all customized for each model and revision of laptop) and their own drivers.

Re:Rename the topic to say INTEL drivers on AMD sy (1)

hairyfeet (841228) | more than 6 years ago | (#23374774)

What gets me is these folks are smart enough to hear about SP3, find and download SP3, and yet they aren't smart enough to make a disc image before they install a giant service pack that could bone their system? It isn't like there aren't several [excelcia.org] free [easeus.com] alternatives [partitionlogic.org.uk] to choose from, as well as a trial of Acronis [acronis.com] which I use.


Why anyone would risk the royal PITA of having their machine completely boned and having to spend hours or even days restoring everything to its original state when a simple disc image could restore it back to health in a few minutes is beyond me. Maybe it's because I've spent so many years fixing Windows boxes in repair shops, but the thought of actually sitting at home for all that time trying to fix a boned Windows install just doesn't cut it for me. So I have an image of each machine in my family with a clean install for when I need to clear the "bitrot", and I keep a monthly image made of each machine on a portable drive in case anything breaks and I need to just send it back a few weeks. But that is my 02c on the subject,YMMV

Re:Rename the topic to say INTEL drivers on AMD sy (2, Informative)

Korin43 (881732) | more than 6 years ago | (#23374804)

Why bother? It's just as fast to reinstall Windows (and you can do it on the same partition, so all you lose are a few settings).

Re:Rename the topic to say INTEL drivers on AMD sy (2, Informative)

i.of.the.storm (907783) | more than 6 years ago | (#23374268)

Yeah, sensationalism as usual, I've got SP3 running perfectly on an AMD and an Intel system, both with no problems and the same as they were with SP2.

BAD_POOL_POINTER, HID problem, standyby problem (5, Informative)

PerfectSmurf (882935) | more than 6 years ago | (#23373948)

I installed SP3 Sunday and three problems immediately cropped up that I haven't seen in the years since I first installed XP. First is a stop, BAD_POOL_POINTER 0x00000019 (0x00000020,0x8a231120, 0x8a231158, 0x1a070000). Second is a problem with the HID service not starting. Third is that PaintShop Pro (V7) now cancels all attempt to enter standby mode. Sigh...

Lovely. (2, Informative)

Mr. Ksoft (975875) | more than 6 years ago | (#23373950)

I'm on both an AMD machine and an HP desktop. Good thing I chose to wait a few months before SP3ing myself. (As for my friend, he didn't and now I'm the one laughing)

Re:Lovely. (1, Interesting)

Anonymous Coward | more than 6 years ago | (#23374578)

You're a fucking shithead, asshole.

well duh (1)

ILuvRamen (1026668) | more than 6 years ago | (#23373956)

Who wrote this article? If you combine the headline and the last setence is basically says "SP3 screwes up some AMD and Intel systems." Gee, you think? Totally biased against AMD if you ask me. You don't just kinda mention "oh yeah, it breaks some intel ones too" at the very end after making it sound like AMD has some huge problem.

I smell a rat (0)

kurt555gs (309278) | more than 6 years ago | (#23373966)

Let's see , is there any where else where M$ and Intel conspired to damage anything? OLPC maybe? EEPC?

Nahh these are good companies beyond reproach.

Right......

No it doesn't (1)

Fat Wang (1230914) | more than 6 years ago | (#23373974)

SP3 does NOT cause any crashes whatsoever. And I do not work for Microsoft.

Re:No it doesn't (0, Redundant)

chunk08 (1229574) | more than 6 years ago | (#23374050)

Care to back up your assertions with evidence?

Wintel Conspiracy (4, Interesting)

chunk08 (1229574) | more than 6 years ago | (#23373982)

Too bad my submission from monday didn't make it, it would have made for some interesting conspiracy theories. AMD and Intel have made the briefs in their anti-trust case public (With heavy censorship^Wediting). One of AMD's contentions is that Intel's compiler is actually written to reduce speed and stability of programs it compiles when said programs are run on AMD processors.

<conspiracy>Maybe Microsoft has a deal with Intel to do the same with SP3 (and other Windows versions/SPs?) or they use Intel's compiler.</conspiracy>

Worth considering.

Re:Wintel Conspiracy (4, Insightful)

Joe The Dragon (967727) | more than 6 years ago | (#23374078)

more like intel payed HP to put there drivers on to all systems in way that MS says they do not support. HP needs to step up and pay for peoples down time and the cost of having a tech come out and fix it. This may even need to come down to a class action law suit.

make the head line say HP systems useing a unsupported by MS driver setup / image load crash under SP3.

Re:Wintel Conspiracy (5, Informative)

harryjohnston (1118069) | more than 6 years ago | (#23374214)

It may also be worth pointing out that (according to TFA) folks had this exact same issue when service pack 2 came out, so it isn't as if HP's configuration wasn't already known to cause problems.

Re:Wintel Conspiracy (1)

flnca (1022891) | more than 6 years ago | (#23374772)

One of AMD's contentions is that Intel's compiler is actually written to reduce speed and stability of programs it compiles when said programs are run on AMD processors.
That's fairly normal because Intel and AMD don't sit on tables to consolidate their chip architectures and optimization strategies! ;)

Assembly programmers know that AMD and Intel chips have a lot of different concepts. Even within the same product range, architecture changes and hence, optimization strategies. This is annoying to assembly programmers, because they have to optimize their code for every CPU there is.

A compiler can address optimization only when the CPU type is known. But that would mean compiling the program when it's on the user's computer. Instead, most programmers that use optimizers don't set the CPU type at all, which leaves the compiler to choose a default value, which nowadays might be a Pentium Pro level CPU (which would be ages old). If the programmer chooses to optimize for a particular CPU, say, Pentium 4, then the program will naturally run slower on AMD processors, because optimization strategies don't match.

Virtual machines like the JVM or the CLR can do a better job of optimization, because they know the user's CPU type.

Ancedote time... (4, Funny)

SanityInAnarchy (655584) | more than 6 years ago | (#23373984)

I imaged my whole Windows partition, in preparation for the horrible instability that would be SP3. I then took a deep breath, and started the download, figuring it would take several hours.

It went reasonably quickly, had exactly one reboot (which brought me fully up to date; no "critical updates" after that), and then ran solidly while I played Portal for another five or six hours.

I was almost disappointed.

It was an Intel machine, though.

Re:Ancedote time... (2, Interesting)

whoever57 (658626) | more than 6 years ago | (#23374258)

And your point is?

Really: no-one has suggested that all machines have this problem after SP3 is installed, so one anecdote of a machine that does not suffer any problems is pointless.

Re:Ancedote time... (1)

ceoyoyo (59147) | more than 6 years ago | (#23374776)

His point is that Microsoft updates, formerly a source of great excitement, seem to be becoming disappointingly boring. Just like those OTHER OSes.

Seems now it's not enough just to run Windows, you have to buy an HP as well.

Re:Ancedote time... (1)

SanityInAnarchy (655584) | more than 6 years ago | (#23374790)

I didn't have a point.

I got modded "funny" anyway. Cool!

Limited impact (5, Funny)

Mostly a lurker (634878) | more than 6 years ago | (#23373988)

As I understand it, this only impacts Windows XP users who are running computers with AMD or Intel processors. There is no evidence of SP3 introducing problems on XP machines with alternative architectures.

Re:Limited impact (3, Funny)

Aranykai (1053846) | more than 6 years ago | (#23374036)

Yeah, Im running sp3 on my RISC system with no problems whatsoever.

Thats what all you fanboy AMD and Intel people deserve.

Re:Limited impact (2, Interesting)

chunk08 (1229574) | more than 6 years ago | (#23374042)

Who actually runs Windows XP on "alternative architectures." I am genuinely interested. If I could run a PowerPC PC, I would.

Re:Limited impact (2, Funny)

calebt3 (1098475) | more than 6 years ago | (#23374138)

Your sarcasm detector is broken.

Re:Limited impact (2, Funny)

Anonymous Coward | more than 6 years ago | (#23374198)

Probably because he installed SP3 on it :P

Re:Limited impact (2, Funny)

jamesh (87723) | more than 6 years ago | (#23374530)

Someone must have uttered the phrase "A sarcasm detector? Now there's a really useful invention!".

Re:Limited impact (1)

SiegeTank (582725) | more than 6 years ago | (#23374088)

Limited impact in the same post as XP machines with alternate architectures. Just lucky not too many people use x86 & IA-64 :)

Re:Limited impact (2, Informative)

Khyber (864651) | more than 6 years ago | (#23374092)

Just how many "alternative architectures" does XP run on? Last I checked, none. I think Microsoft's multi-architecture support for their main operating systems died after NT4 (along with support for DEC's Alpha) and they went x86. Looking at Microsoft's support page [microsoft.com] , they say Pentium or compatible processor, so that means x86 only.

Re:Alpha (1, Insightful)

Anonymous Coward | more than 6 years ago | (#23374272)

NT4 ran on Alpha, PowerPC, and SPARC, among others, but it wasn't written by their in-house staff. They hired some away from DEC to write it for them.

Re:Limited impact (0)

Anonymous Coward | more than 6 years ago | (#23374274)

Wooooosh

Re:Limited impact (0, Redundant)

onefriedrice (1171917) | more than 6 years ago | (#23374378)

Woosh!

Re:Limited impact (2, Interesting)

afidel (530433) | more than 6 years ago | (#23374540)

Windows 2000 had Alpha support up until RTM. Windows 2003 and XP supports x64 and 2003 supports Itanium. The NT codebase is actually fairly portable and there are internal MS projects around running it on various architectures just to make sure they could move with the market if there was ever a huge move off x86/x64 (as unlikely as that is).

Re:Limited impact (3, Informative)

ShadowFalls (991965) | more than 6 years ago | (#23374410)

My Via C3 system is running fantastic with XP SP3. Take that AMD and Intel!

What is the purpose of a service pack? (2, Interesting)

sweet_petunias_full_ (1091547) | more than 6 years ago | (#23374060)

Isn't the original purpose of a service pack to add reliability, rather than take it away?

One would think that by SP3 there would only the most minor bugs left to close, but instead giant new ones are opened. Machines that become unbootable? That's pre-alpha quality stuff.

Something is badly broken with their methodology... no wonder they were trying to do a people grab at Yahoo, the higher ups are probably pulling their hair out by now trying to figure out how to fix their organizational problem and maybe they thought a new project built on BSD (but independent from Apple code) with entirely new staff would bail them out.

misleading headline (4, Insightful)

timmarhy (659436) | more than 6 years ago | (#23374174)

wow what a porker. sp3 crashes AMD based systems, then when you read on it's intel drivers installed on AMD systems that causes the problems.

not exactly a cut and dry SP3 problem and certainly not an AMD or INTEL issue at all.

people who write this crap need to all be thrown in a cage and be made to rip each other apart.

Re:misleading headline (0)

Anonymous Coward | more than 6 years ago | (#23374438)

Yeah it's an SP3 problem. If you have, say, an Intel power management driver on your AMD machine, or AMD on an Intel machine, the driver shouldn't crash your system; it should realize the hardware is non-matching and not run. In fact I see no reason it shouldn't be possible to support both. You know, with any Linux distro, you can support AMD *and* Intel processors with a single image...

Re:misleading headline (2, Funny)

jamesh (87723) | more than 6 years ago | (#23374542)

people who write this crap need to all be thrown in a cage and be made to rip each other apart.

<chant>Two journalists enter. One journalist leaves.</chant>

Actually I'd like to see that as a form of conflict resolution for almost all arguments on slashdot.

endless rebooting is not at all related to SP3 per (2, Funny)

stox (131684) | more than 6 years ago | (#23374176)

"SP3 causes the computer to crash during boot, and Windows XP, by default, is set up to automatically reboot when it crashes. That is why you end up in the endless rebooting scenario."

Nope, no relation at all. After all, crashing is perfectly normal.

Im waiting.. (5, Funny)

rossdee (243626) | more than 6 years ago | (#23374206)

I'm waiting for Service Pack 3.11

Re:Im waiting.. (2, Funny)

flyingfsck (986395) | more than 6 years ago | (#23374664)

...but that would only be for XP Workgroups, what about Domain users?

Re:Im waiting.. (3, Funny)

MilesAttacca (1016569) | more than 6 years ago | (#23374690)

I actually found Windows 3.11 to be a very usable operating system. Namely, because if it froze, I could CTRL+ALT+DEL, the system would actually reboot, and then it would be usable again.

OK so far (2, Informative)

willow (19698) | more than 6 years ago | (#23374212)

One data point. Asus M2N-SLI Deluxe w/ 1502 BIOS version and an AMD 64 X2 4600+ is OK so far.

Re:OK so far (1)

freedom_india (780002) | more than 6 years ago | (#23374282)

True. I downloaded the first patch manually. (one which used to crash MS Retail Mgmt System).
It works fine on my M2N-E-SLI with AMD 64 X2 4300+.

Microsoft: (4, Funny)

Weaselmancer (533834) | more than 6 years ago | (#23374224)

The World is our Beta Tester.

Re:Microsoft: (1)

BlueCollarCamel (884092) | more than 6 years ago | (#23374314)

No amount of in-house testing can compare to real-world use.

Re:Microsoft: (1)

westlake (615356) | more than 6 years ago | (#23374514)

The World is our Beta Tester.

Well of course it is.

There is no standard Windows system.

HP's custom OEM image installed an Intel system file on AMD PCs. Not exactly recommended practice.

Blue screen after first reboot... (4, Informative)

Trollificus (253741) | more than 6 years ago | (#23374254)

I got hit by this bug when the patch went live last week on Windowsupdate. As the article states, the solution in was to disable intelppm.sys from safemode. It's a lot quicker if you do it using autoruns [microsoft.com] . It's too bad this article wasn't posted last week. It would have saved me a lot of trouble shooting time.

Re:Blue screen after first reboot... (2, Insightful)

biobogonics (513416) | more than 6 years ago | (#23374344)

I got hit by this bug when the patch went live last week on Windowsupdate. As the article states, the solution in was to disable intelppm.sys from safemode. It's a lot quicker if you do it using autoruns. It's too bad this article wasn't posted last week. It would have saved me a lot of trouble shooting time.

This bit me today as I manually went though Windows Update on one of my office's machines, an older Compaq Presario with an AMD processor. Not knowing about the simple 1 line of instructions that would disable the intelppm.sys driver, I went through multiple re-boots and finally backwards using system restore. Finally downloaded 300+ MB of the XPSP3 installer (I have several other machines to update as well) and ran it after applying the patch. No real trouble after that.

I can't really blame MS for this. I can't blame HP that much either. The machine was near the bottom of the Compaq/HP line. It was purchased to allow our (former) receptionist to perform her duties and little more.

Compared to Vista SP1... (2, Interesting)

shutdown -p now (807394) | more than 6 years ago | (#23374266)

All in all, it still seems to be faring much better than Vista SP1. For what it's worth, the latter is still disabled on Windows Update for one of my PCs (because of "incompatible hardware or drivers").

address bar is removed though (1)

daveb (4522) | more than 6 years ago | (#23374334)

SP3 works fine for me but it removed my address bar from the taskbar. MS claim somewhere its a compliance thing but that's totally BS as vista has the address bar and the address bar in SP2 will load the default browser (ie firefox).

There are work arounds and third party patches - but this is just annoying.

What we should really be asking is (-1, Flamebait)

Zorque (894011) | more than 6 years ago | (#23374534)

Why is anyone still using AMD?

Re:What we should really be asking is (0)

Anonymous Coward | more than 6 years ago | (#23374606)

You should be flogged.

HP SP2 problems too (2, Informative)

cojsl (694820) | more than 6 years ago | (#23374570)

I recall some HP machines had serious problems (driver related?) with installing XP2 too.

No Problems (0)

Anonymous Coward | more than 6 years ago | (#23374692)

Installed SP3 on an intel-based machine, no problems at all.

Stop code 0x0000007E is not a new problem (5, Informative)

fragMasterFlash (989911) | more than 6 years ago | (#23374800)

Anyone who build Windows XP images that are rolled out onto both AMD and Intel machines should have long ago learned about the stop code 0x0000007E perils that come from the intelppm driver. The root of all evil here is that processors are not plug and play devices as far as XP is concerned and their associated drivers are hardcoded to start at boot time. Why the hell Microsoft has not taken the time to update intelppm.sys to check for a GenuineIntel x86 Family XX Model YY Stepping ZZ ID before touching HW specific registers is a mystery to me (I hope the conspiricy theorists amongst you will regale me with much food for thought).
Load More Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>