News is something you didn't know - Charles Arthur, The Independent
THE LONG-AWAITED and much-delayed update to Windows XP, Service Pack 3, is giving owners of machines with AMD hardware headaches aplenty it seems.
The problems, which first arose just one day after the push, have been causing lots of noise on Microsoft support sites and angry user bogs.
One user reported, "I just installed Windows XP SP3 and after completing the processes and when the system reboots, the system cannot proceed to load the Windows. It just displays the flash screen of Windows then after it reboots again."
Angry users have also reported that, after the installation, it is not even possible to boot in safe mode, usually the last resort before setting up a repeated forehead/screen interface.
Jesper Johansson, a former program manager for security policy at Microsoft and a well respected bogger on such things has provided some pointers as to where the problem might lie.
According to Johansson, there appears to be two separate problems. One affects only AMD-equipped PCs sold by Hewlett-Packard. "The problem is that HP, apparently along with other OEMs, deploys the same image to Intel-based computers that they do to AMD-based computers," said Johansson.
"Because the image for both Intel and AMD is the same all have the intelppm.sys driver installed and running. That driver provides power management on Intel-based computers. On an AMD-based computer, amdk8.sys provides the same functionality. "
There's a whole bunch of other info and some useful fixes for those of you stuck in the dreaded loop of death over on Jesper's Bog. ยต
installed sp3 on 3 amd machines (one an acer laptop) - and no problems. thanks.
HP uses the wrong drivers !?! nice, my next PC will certainly be a HP ;-) I wonder what would happen if they put an AMD driver on a intel CPU. :)
"been causing lots of noise on Microsoft support sites and angry user bogs." I cant see it from the Toilets point of view ?
People in my office scoffed at me for deciding to wait at least several months before installing this SP due to concerns about crashes and compatibility. And I laugh and I laugh.
No problem installing SP/3 (direct update from MS Updates site) for an older Foxconn nForce 4 Ultra board with an Opteron 150 cpu. It's unclear just how many "updates" were posted to the system since I had already gone through the tedious process of adding most known updates just prior to SP/3 release.
Last night i installed SP3 on a old Athlon XP 1800+ and no problems so far...
loaded sp3 on my amd machines, no problems.
Apparently auto/win/MS update are blowing up. No surprise as installing service packs from those methods is always a stupid idea anyway. Has anyone tested it using a local install? (I don't have any AMD boxes. I haven't had problems with anything so far.) Always Download the full SP file... the 300+ MB thing. Run the file with the Extract switch to save an Unpacked copy of it. (/Extract:C:\SP3) Copy EVERYTHING in the I386 directory to a CD so you have it for future screw-ups. Run the Update.exe in the Update folder (CD or Hard drive) to start the installer. For more convenience, make an Autorun.inf for the CD with this in it... [Autorun] open=update\update.exe This is the fastest way to deal with multiple machines. It's also faster than auto/win/ms update by a huge amount and if far less likely to crash since you won't even be able to extract from a corrupt download.
I've been installing sp3 on computers for 3 months now, because it speeds up the critical updats from microsoft. AMD AND INTEL. The only time I had a problem was with Media Center OS. Can't remember which cpu. Just remember it was Media Center. Was able to get in safe mode and turn back.
Any user who buys a big box PC from any manufacturer and doesn't format / reinstall with a clean version of windows to rid themselves of all the bloatware and crapware deserves what they get when things like this happen...
Funny, I have several AMD machines running here, none of them giving any problems at all. They are: Mobile Sempron -> fine 2x Opteron 270 -> fine Athlon 4200X2 -> fine Sempron LE-1150 -> fine Done the same om many client machines, brand and clones, no problems either. But all machines have uptodate drivers and stable BIOS (not the latest or Vista BIOS!)
Installed SP3 on my HP 6715b laptop earlier today and i have had no problems.
I have a Toshiba note A45-S120, after SP3 install and restart my 3G modem gone, I remove them, but nothing change. As a matter in fact there is more than that about SP3 that MS not tell us.
I downloaded the 'network install' SP3 package and installed it on my AMD system with no issues - 690G chipset, Athlon 64 x2 5000+ BE, 4GB of DDR2-800. I haven't had any issues thus far.
I've installed XP SP3 on seven of my XP Pro SP2 AMD 3200 xp socket A machines. Only one very minor problem with D-Link wireless utilities. I know....I'm way behind the times. But I do love being a relic of my past. 100% installed perfectly with no problems other than the one above. In fact, they boot a bit faster I feel. I'm no M$ supporter, but I do believe in giving credit where credit is due. And in my experience, the overwhelming reason for most computer problems I rectify are because of operator error/ignorance/laziness/experimentation and etc. Oh frelling well.....
MS put deliberate bugs in the PUBLIC release of SP3 to crash random machines. It's a way of forcing people into VISTA. The BETA SP3 releases available to developpers only are stable on AMD!
Have installed SP3 on four brand-new workstations in the last two day and they started just fine. Had to re-register the WUPS2.DLL file in order to finish the remaining updates though. Looks like the main problem wasn't caused by Microsoft, but by HP. Microsoft not to blame? Gotta be a first time for everything, I guess... Thus far it at least seems smoother than the SP2 rollout.
PIII-1GHz - XP/SP3 successfully installed. Dual AthlonMP + SATA RAID Dell/CERC 2610SA (Adaptec) - endless reboots. System reboots without BSOD right after preloadeded some drivers. Some speculate that unsigned drivers for SATA aren't recogbized with SP3. But my SATA drivers are signed...
SP3 borked my P4 2.4gig Gigabyte mobo system. None of the posted 'fixes' works. I'd consider SP3 as 'unproven'. YMMV. You have been warned.
This was right-on-time ... thanks! Have a Compaq branded AMD machine and used the run "sc config intelppm start = disabled" routine in the SafeMode and everything is fine!
Perhaps SP4 could just be a Ubuntu image!
Have installed SP3 on four brand-new workstations in the last two day and they started just fine. Had to re-register the WUPS2.DLL file in order to finish the remaining updates though. Looks like the main problem wasn't caused by Microsoft, but by HP. Microsoft not to blame? Gotta be a first time for everything, I guess... Thus far it at least seems smoother than the SP2 rollout.
If you have an AMD system that is in the reboort loop, just boot into safe mode and rename intelppm.sys.
there are still people using AMD out there... fnarrrr
Slipstreamed SP3 into my Win XP Pro CD which is 6 years old and no problems here and it's a AMD 939 3800 X2 with 1GB DDR RAM nforce 4 motherboard.
I can't believe how many people that only reads the headline of the article and then jump to the comments-page and writes whatever. The article actually says that it's AMD machines combined with the HP brand, so NO the fate of a toshiba AMD machine or your own home-assembled thing will not be of any interest!
Yup, I think it is finally time to hammer the nails in the coffin for the eight year old O.S.
Baloney! I beta tested SP3 and have nothing but improvement in the overall operation of my computer.
been using SP3 for months now on both an AMD and Intel machine with no problems......installed the new release last night and still no problems.....I guess some people shouldnt be allowed to do anything but surf the net and use e-mail........to many thing they are Computer Wizards today...I laugh when they screw things up and pay me to fix it.....:)
Got mine off technet. it worked pretty well for like a week and a half and it would endlessly reboot and randomly work. Almost rmaed the board too
While technically yes it's AMD machines affected, the title should point out it's ONLY some machines from specific companies! The title hints at bad programming by Microsoft is to blame, or AMD is not processing the data correctly. It says absolutely nothing about HP and the fun guys who decided to use Intel drivers on AMD systems. Guess I'm going to install network card drivers for my sound card and blame Maxtor about the resulting problems since I have a Maxtor hard drive...
If i were Charlie i would say that 'BAN XP SP3'!!!! - because it crashes on DAAMIT machines!!! and he will continue as far as cursing microsoft because of conspiracy with vista, nvidia and intel...
Running Window MCE - updated and it shut down and eliminated all the media center functions execept the extender. No ehshell, ehreciever. Running a HP a1640n with everything current except the video driver (12/07 ver) since it considers the newest g965 ones not incorrect.
I guess everybody here knows this is nothing new. Right? I have been a proponent of AMD power for years, but ultimate stabilty was *never* completely there. Since the Intel Core 2 series, it has basically been a no contest. Is this really news to some of you guys ??????.
So the INQ, headed by Charlie (the DAAMIT SALESMAN) wanted to illustrate a conspiracy that MS favors intel over ati and that nvidia is also behind these silly SP3 staibility issues... ... and that Hector is the innocent all so divine victim here. WOW INQ! WAKE UP!
I just installed Ubuntu on a machine that the user installed SP3 on. His machine would not complete the boot process after installing SP3. To tell the truth, I think that his Windows version was pirated but I'm not sure. I installed Ubuntu 8.04, and didn't even tell him it's not Windows. It's been a full day now, and so far no complaints. He was already using Firefox but I was expecting to hear complaints about Open Office. No complaints yet, but it is still early.
After sp3 went on i get constant crashing using IE/win update. It wont load at all infact.. just crashes the machine. FF works fine mind a8n-sli premium 4800+ wont be putting it on any of my other machines untill i can get this one sorted
hathaw, Damn! You're right! Why didn't I see that???
I didn't write:Deliberate Bugs MS put deliberate bugs in the PUBLIC release of SP3 to crash random machines. It's a way of forcing people into VISTA. The BETA SP3 releases available to developpers only are stable on AMD! posted by : hathaw, 09 May 2008 Yet it is NOT Random, microsoft picked its own advanced Ultimate mainboard, First real OK Platform M2A-VM & corrupted it thru any SP3 XP added to it, Bam, NO More XP. Maybe F8 & SAFE will work, yet its typical of that mainboards many flaws: thus NO Ultimate OEM ethier. Sells to both TOP O/S, Works in Neither. Thomas Drashek
SP3 seem to have problems in the following two situations: 1)running an HP prebuild system with and AMD processor. 2) Running an AMD System with the Asus A8N-SLI series of motherboards. so please stop commenting on the other systems that work fine - when they infact are not affected by this problem
Happened to my Non HP Conroe rig too, couldnt get to the login screen, just kept looping. :(. If i was in america i would sut Microsoft for releasing an unworthy product and mental stress caused by data loss and having to set the whole thing up again.
I have 2 AMD machies One of the had no problem. The other a Compaq Persario Had this problem. It went into safemode ok and I was able to uninstall. Does anyone know if there is a fix yet?
AMD 4600+ X2, 2GB, 6800GT - upgrade to SP3 all OK. Upgraded via M$ website.
you guys are almost all idiots. obviously microsoft would never release and update that's screws up all amd machines. this is obviously HPs fault. ethier you guys just read the title or you don't understand what your reading. on the other hand though, i'd really like to know which moron at HP decided to install Intel drivers and AMD machines...
I just installed it to my AMD X2 pc with and Abit Nforce 4 X16 No problem at all I guess this problem happens in specific hardware and not in all AMD machines...
My personal PC is also an AMD machine that has developed the nasty habit of freezing up at the splash screen. After a hard reboot, it will go ahead & start normally (if anything involving Microsoft can be called "normal")
I had the same problem with intel celeron machine.
I've got a homebuilt Asus A8N SLI-Deluxe rig & i isolated the problem to the mouse being plugged into the usb at boot up. Simply remove whilst booting up & then plug in once up & running. Apparently keeping a flash pen inserted into a usb port whilst booting up will work aswell. I've simply uninstalled SP3 till this gets sorted !
I have an old XP1800+ laptop, sold by Compaq, pre-HP takeover, that had SPzero on it when I bought it (Presario 916US). I upgraded via WUS to SP1, then SP2 3-4 years ago. Haven't "upgraded" to SP3 yet (let someone else discover any Nasties FIRST! Just ran a "search" and found "intelppm.sys" in the system32 drivers. I suspect that either MORE vendors used a common Intel/AMD image or that Microsoft itself inserts the file during one of their WUS sessions. BTW, this "ancient" machine (w/ 768MB of RAM) runs WinXP SP2 just fine, and it will NEVAH be "upgraded" to Vista (probably can't get drivers for the mobo and integrated video, anyway).
In our consulting business, we have had several computers from clients with this problem, recently. They had their updates on auto, and they were slammed at 3am by the SP3 install that put their computer into the "Loop of Death." We even had one user that took matters into their own hands erased all their data by using the factory default restore partition from HP. That user is not happy to say the least. They did not have a recent backup. The big problem with this one is "safe mode" usually does not work. That's why we had to get involved by booting with an OS CD to fix. Most users don't have an OS CD because they aren't hardly sold with computers anymore. Our firm works on Linux, Mac, and Windows. We put the blame on this issue on Microsoft. Encouraging users to have updates on auto, and then not thoroughly testing those updates like SP3. Users turn off auto updates. Set your computer to notify you of new updates, and then you pick and choose which you wish to install. Before installing do a quick Google, Yahoo or such to see who and how many are having problems before downloading and installing any updates not just Microsoft's updates. Writing this and knowing the Microsoft lovers will blast us saying we're anti-Microsoft. The fact is we encourage Microsoft products but not their auto-updates; that's the first thing we turn off when a computer enters our shop.
Fine machine until installing SP3 - it gives Windows splas screen and then hangs with a black screen.
I am have a terrible time after trying to install SP3 onto my Intel-based machine. Exactly the problems talked about with AMD is happening for me ... I get to the windows splash screen then the PC reboots and the whole process goes round in circles. This is completely ridiculous.
At first, sorry for my english. I have asus X50N F5 notebook. I have SP2 and no problems i found. Realy good performance in video coding, editing ant etc. When i decided to test SP3, but... No reboot problem, just everything gone VERY SLOW. Video coding went about 30-40% slower.
I got hit by this SP3 fiasco july 4 because of auto update. If you go to the ms support website they list lots of standard pre update requirements, like turn off antivirus and firewall applications. But auto update doesnt follow this procedure, so on my system with macafee, zone alarm and norton tilities running the auto install failed, leaving a partial set of files and changing the winver.exe value to indicate that sp3 was in. But it didnt have an entry in the add / remove software list due to the corrupt install. 3 issues happened at that time. 1 on bootup I could not get online, server not found. called my dsl provider n found out that zonealarm needed to be deleted n reinstall the updared program to deal with sp3 change in internet protocol. .2 Random system crashes every 3 to 6 hours. I tried to determine the cause several ways but finally just googled sp3 crashes n saw lots of sites listing these problems. even windows has a sp3 crash issues page, so I tried their advice . remove sp3 in controll panel, but since it did not have an entry there it would not uninstall. Tried spuninst.exe but it failed because it could not find some files and so did not uninstall anything. I called ms support and after 3 days of 3 hours each day they got to the option of last resort, REINSTALL WINDOWS FROM OS CD.. That was the only thing that worked, and now I have my auto update set to notify but dont install anything. During the hours of hunting down settings and reboot cycles I asked the last tech if there were known issues with software like my zonealarm which had to be updated to function under the new os patch. His answer was yes they had an inhouse list but it has not been released yet since they were still adding up the affected programs. I was able to confirm that mcafee and symantic programs needed to be updated to handle new protocols, The advice in above post of not automaticly accepting updates for a few weeks would be wise.Then google that updates name to find out what the actual fallout is.
Installed SP3 yesterday on Dell precision M65 (Centrino duo according to the label). Afterwards machine would not boot in any mode giving error messages relating to trying to write to protected memory. Dell (MS?) system restore would not let me enter an admin password longer than 8 char so could not restore to prior to update. Had to create Acronis boot disk on an old machine (two CD writers would not work) so eventually created a boot USB stick. Restored from Acronis image backup and am now working again. Thank you Acronis. No more MS updates for me, I do not have the time to mess around sorting out other mistakes. Description of SP3 says it brings together a series of previous updates and a few minor changes, hardly something which you would expect to cause such major problems.
This was happening to me too so I tried something seemingly random. I switched the RAM sticks around into different slots and voila! Its up and working. Hope this helps. Cheers!