System Keeps Rebooting after Installing Windows Service Pack 3
I just installed Windows XP SP3 and after completing the processes and when the system reboots, the system cannot proceeds to load the Windows. It just displays the Flash Screen of windows then after it reboots again. I've tried to start Windows thru Safe Mode but then I cannot enter the Safe Mode because the system reboots. Can anybody help me with my problem? Thank you.
Answers
This problem only happens if you install an outdated version of pre-release SP3. That latest version of SP3 RC2 Refresh (build 5508) does not have this problem. Nor will the final version next week (build 5512).
See http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3163197&SiteID=17 for recovery instructions.
All Replies
This problem only happens if you install an outdated version of pre-release SP3. That latest version of SP3 RC2 Refresh (build 5508) does not have this problem. Nor will the final version next week (build 5512).
See http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3163197&SiteID=17 for recovery instructions.
Not true
I downloaded the official relaese today, I got a continual reboot cycle with no error message. The gdi32.dll fix (above) worked though.
That's ok at least you have SP3, I'm still on SP2 & my computer restarts after I shut it down. In addition it no longer has the stand by option. It wasn't like that before I formatted it.
Hmm, I downloaded SP3 from Windows Update this afternoon, after 5 hours of reboots, blue screens, I had to actually go to Vista to get my computer sorted. Then I read this was a RC version, but not from Windows Update did I read this .....
Kinda irresponsible to drop a major update as a RC and not say anything in the title. Would have saved me hours of work today.
Rather unfortunate that people are claiming the reboot issue was fixed and yet we had this issue. Wonder why that is ? I can't fix the issue either, thanks to HP there is no media to get a recovery console happening. And I don't understand why this would be something "I" should have to fix ....
Rene, this is with the final RELEASE version you got today??
Yours still says it's an RC version?
Rene S wrote: Hmm, I downloaded SP3 from Windows Update this afternoon, after 5 hours of reboots, blue screens, I had to actually go to Vista to get my computer sorted. Then I read this was a RC version, but not from Windows Update did I read this .....
Kinda irresponsible to drop a major update as a RC and not say anything in the title. Would have saved me hours of work today.
Rather unfortunate that people are claiming the reboot issue was fixed and yet we had this issue. Wonder why that is ? I can't fix the issue either, thanks to HP there is no media to get a recovery console happening. And I don't understand why this would be something "I" should have to fix ....
- BTW, replacing the gdi32.dll DOES NOT fix this issue on all PC's! I tried that so called "fixed" and it ruined my PC and made it totally bootless! This is on 3311. The only way I could get it to boot was put the previous SP3 version of gdi32.dll back in the system32 folder in DOS.
I, too downloaded SP3 today (May 7 about 11pm) from MS update - so I have the 'new and improved' version, right?
* Downloaded and installed and worked fine on my Laptop (XP HOME).
* Downloaded and installed and worked fine on a new PC system I just built (system has only win XP MEDIA installed - nothing else).
HOWEVER -
* Went to my PC (XP PRO), and SP 3 downloaded, installed and went to re-start and now hangs > bringing up 'windows did not start successfully .. .."
Last known good = doesn't work.
Tried Recovery console, it didn't like any of my PW, so i yanked out the drive and manually replaced the gdi32.dll from the above referenced PC and re-installed to my PC.
No progress - same thing, it just keeps re-booting after 23 seconds or so. Tried booting to safe and command prompt to no effect.
Any ideas? What a bummer! I just happened to stop by the update site for the malicious download and it prompted me with the SP3 download. The best laid plans .. .. ..
This is ridiculous. Well done MS. They screw around with RMS and delay the release because of that even though so few use it, yet they ignore the most serious issue of all of not being able to start your freakin' computer!
- Well, II downloaded it when first released last week and installed on my work laptop as a test and on our 2 Windows laptops at home, all without issue.
However, when I installed it on my dads PC over the weekend, I got continual reboots, however I was able to get into safe mode and uninstall SP3, so it would appear there are a number of potential issues that can cause this.
Sadly I didn't note the error code, my Dad needed his PC back as soon as possible. One thing is for certain though, this will not be going on my music production laptop until I am certain that it will work (Or I can borrow Ghost from work and ensure I have a working backup!). I just wanted to add that my laptop [XP home] (successful SP3 install) and my PC [XP PRO] (unsuccessful install) are both running zone alarm and current subscriptions of Norton 2005. The newly built XP MEDIA machine I built for my sister has zone alarm and current subscription Norton 2008 [but has no installed software other then the OS].
Of course, my now non-working PC is my workhorse
I have the same problem I install the sp 3 on may 7 and my pc just not boot up. I had to restore the original configuration. I try again. and same issue. Another fine example of Microsoft quality. For my work I have to use Windows if not I would have a Mac.
How do you restore the original config? I noted that SP3 made a restore point, but i don't know how to point it there. The option to 'use the last known good config' option on start up results in no changes to the continuous boot re-cycling.
Of course, perhaps it's a moot point, as the PW's I entered on the recovery console XP does not like. <sigh>
indycar_89 wrote: How do you restore the original config? I noted that SP3 made a restore point, but i don't know how to point it there. The option to 'use the last known good config' option on start up results in no changes to the continuous boot re-cycling.
Of course, perhaps it's a moot point, as the PW's I entered on the recovery console XP does not like. <sigh>
If you can get in to safe mode, go to control panel, add/remove programs and remove Service Pack 3, otherwise you will have to try the method described here.Thanks Mal7921. This issue is not responding to the GDI32.dll fix that has worked on older SP3 versions. I have already replaced the GDI32.dll by removing the drive and installing it as a slave and manually replaced the GDI32.dll from a barebones machine that is running SP3 [the GDI32.dill came from the win/sys/etc file from the drive in question, not the barebones sys file]. To no avail. Nothing changed.
I think others are getting an error message, we don't seem to be getting an error message, it just keeps coming up the 'failed to start on last attempt' screen. None of the options will work from there, however. (safe mode, command prompt, boot normally, etc.)
I did find this article about how to un-install SP3 from Recovery Console (so far, I have not been able to get into RC - none of the passwords have worked - but I'll keep trying), but not sure if I should attempt this or wait to see if a MSFT tech has any ideas. http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2934347&SiteID=17
Hi,
For everyone facing the endless reboot issue, we would need to have some more information.
1. System configuration
2. Does safe mode boot succeed?
3. Can you try to boot with automatic restart disabled (press F8 before the OS selection screen) and share the result? Any messages displayed on the screen etc.
4. System event viewer logs (from safe mode) and/or contents of %windir%\minidump.
Please share any/all of this information at shashank<dot>bansal<at>microsoft<dot>com
Thanks
Shashank
indycar_89 wrote: How do you restore the original config? I noted that SP3 made a restore point, but i don't know how to point it there. The option to 'use the last known good config' option on start up results in no changes to the continuous boot re-cycling.
Of course, perhaps it's a moot point, as the PW's I entered on the recovery console XP does not like. <sigh>
"Last known good configuration that worked" or something like that. You should be seeing it automatically when it won't boot, it's in that safe mode options screen. Or you can get to it by pressing the F5 key repeatedly while booting. But, that never worked for me!
indycar_89 wrote: Thanks Mal7921. This issue is not responding to the GDI32.dll fix that has worked on older SP3 versions. I have already replaced the GDI32.dll by removing the drive and installing it as a slave and manually replaced the GDI32.dll from a barebones machine that is running SP3 [the GDI32.dill came from the win/sys/etc file from the drive in question, not the barebones sys file]. To no avail. Nothing changed.
I think others are getting an error message, we don't seem to be getting an error message, it just keeps coming up the 'failed to start on last attempt' screen. None of the options will work from there, however. (safe mode, command prompt, boot normally, etc.)
I did find this article about how to un-install SP3 from Recovery Console (so far, I have not been able to get into RC - none of the passwords have worked - but I'll keep trying), but not sure if I should attempt this or wait to see if a MSFT tech has any ideas. http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2934347&SiteID=17
Was your PC set up with factory installation disks or pre-built from the factory? It may be that there is no admin password if that is the case, and if that is not the case, have a look for P.I.N.G. (Partimage Is Not Ghost), which is an imaging program similar to Ghost, one of the options it comes with is an option to blank the local admin password on a machine, though I have not used this myself other than for imaging PC's.Clint D. wrote: indycar_89 wrote: How do you restore the original config? I noted that SP3 made a restore point, but i don't know how to point it there. The option to 'use the last known good config' option on start up results in no changes to the continuous boot re-cycling.
Of course, perhaps it's a moot point, as the PW's I entered on the recovery console XP does not like. <sigh>
"Last known good configuration that worked" or something like that. You should be seeing it automatically when it won't boot, it's in that safe mode options screen. Or you can get to it by pressing the F5 key repeatedly while booting. But, that never worked for me!
Last known good configuration never worked for me, and I have yet to hear of it working for anyone.
Many can not even get in to safe mode, though I did manage that and that was the only way I could remove SP3.Shashank Bansal [MSFT] wrote: Hi,
For everyone facing the endless reboot issue, we would need to have some more information.
1. System configuration
2. Does safe mode boot succeed?
3. Can you try to boot with automatic restart disabled (press F8 before the OS selection screen) and share the result? Any messages displayed on the screen etc.
4. System event viewer logs (from safe mode) and/or contents of %windir%\minidump.
Please share any/all of this information at shashank<dot>bansal<at>microsoft<dot>com
Thanks
Shashank
Hi, thanks for replying. I'm not getting any error message. So there are no minidump files or Event Viewer entries. All appears to be normal, and the very instant the black XP logo screen starts to "fade in", it stops and reboots, then stops at that menu where it says "Windows didn't load on previous attempt" and it gives you those options like safe mode, safe mode with networking, last known good configuration, etc. Regardless of what is chosen there, nothing works. That black XP logo screen never loads, it's like if it were an animation, only the very first frame of the "animation" loads where the first frame is dark and low contrast so-to-speak.
Sometimes it will boot into safe mode, sometimes it won't. After about 10 tries, it just suddenly finally loads!
I state again, that the method of replacing the gdi32.dll file ruined my PC and the only way I could fix it was to put the previous file back in the system32 directory in DOS.
I'm not sure what you mean by "System configuration", do you mean the hardware that's being used?
Thanks.
This machine is one I have built. Upgraded to XP pro from win 2Kpro, so I have the origional MS XP PRO disk. Long ago and far away was the install, and I have tried all the usual suspects as far as PW's are concerned. blank, etc. Might be a case sensitive issue?
I''m hoping that since I can access the drive in question from a bare-bones machine, I can just rename/remove and insert whatever file I need to and then put the drive back into the original machine.
My last known good never worked either, but I've also never been able to get it to boot to safe-mode.
I also have no mini dump log or file.
** I did** do the GDI.dll change, with no effect. I guess I'll check to make sure the two .dlls are in fact different files. But I'm not sure which GDI.dll this present version of SP3 is using - but i DO NOT think this is the same issue, because we are not getting any error messages.
Nice to know I'm not the only one out here looking for a life vest! (I do have a Acronis backup, but its pretty dated)
On this thread, it seems to me that people are confusing different possible reasons for a reboot cycle. The first thing to sort out is what particular reason is your PC rebooting for - and the first thing to do is stop the automatic reboot, so that you can view the BSOD and read off the error message from the BSOD.
So people who are getting "Windows did not start properly" need to set the option not to reboot after error, and allow the BSOD to display, note down all the error details and messages, and post them here.
The poster who mnetioned he had an HP system is probably experiencing the issue with AMD processors: the fix for this has been posted on other threads and is a simple registry fix when booted in Safe Mode.
The fix involving gdi32.dll is specifically only for the C0000139 BSOD, and it will not work for anything else.
RDHW -
Thanks. Here is the info I have shared with Msoft.
after stoppin auto restart - on stop, blue screen:
"Problem was detected ans windows has been shut down to protect your computer from damage.The BIOS in this system is not fully ACPI compliant . ~info about updating~if unable to update bios or if most recent is installed, you can turn off ACPI mode during text setup. Press F7 when prompted to install storage drivers (I have not been prompted to do this) Windows will silently disable ACPI and allow you to continue with installation"STOP: 0x000000A5 (0x0000002, 0x86De2928, 0xE1012a70, 0x86d4EE10>I have not done this procedure<I am using AMD, but the SP3 has worked on both my laptop and barebonses system, both w/ AMD.my config: AMD Athlon 64x2 dual core 2000Mhz 1024 ramMB= ASUS A8N32-SLI amibios v 1303 7/13/06Microsoft is working on this and they have this info and a few logs I have sent.I don't think I can do the AMD fix as booting into safe mode won't work. Unless I can access the registry with the boot drive as a slave on another machine?Sounds like I also need to revert back to the origional GDI.dll I renamed this morning from one of the other threads.- indycar_89, your error information is very different from what others have been posting about, and it is nothing to do with gdi32.dll, so do not interfere with that file. The obvious question is: can you try updating the BIOS on your motherboard to the latest available version? Try the ASUS web site for motherboard BIOS updates.
Thanks Robin. I'll check ~ I'm pretty sure I have the lastest and greatest. I think somehow some boot drivers got jacked or something.
Way to go, Microsoft, releasing the pile of dung, called SP3, that hoses your system so bad even Safe Mode isn't working! Props to your QA guys, they certainly have done their job. *sarcasm*
indycar_89 wrote: The BIOS in this system is not fully ACPI compliant . ~info about updating~if unable to update bios or if most recent is installed, you can turn off ACPI mode during text setup. Press F7 when prompted to install storage drivers (I have not been prompted to do this) Windows will silently disable ACPI and allow you to continue with installation"I just unchecked the box that RDHW mentioned, so we'll see if I'm getting a BSOD somewhere, but I don't think I am or I would see it. I can sit and watch it and I never see any BSOD.My mobo is also an Asus (P4C800-E Deluxe), but it IS ACPI compliant, it's set that way in the BIOS.Be careful about flashing to new Asus BIOS versions. They suck. They remove features that previous BIOS versions had! In my case, v1015 removed UDMA 6! So I'm using 1014 so my ATA133 and SATA drives will be UDMA 6.What happened to "Shashank Bansal [MSFT]"?Hey Clint - I'm about to cash in my chips for the night. I'm sure my board is ACPI compliant. There is one higher version of bios, but its a beta and like you say - who knows. I'm pretty certain it's a driver issue. I did also download a ACPI driver, but i have no way (that I know of) to find out what ACPI driver is already on the hard drive. Nor do I know how to install this driver without the OS.
I think I'll wait for Shashank to get back to me > he is working on this issue.
- When you go into the Device Manager, under "Computer", do you see "ACPI......PC"? On mine I see "ACPI Multiprocessor PC", ("multiprocessor" because it's a HyperThreaded P4 which shows as dual CPU's). If you see this, then it should be safe to say it's ACPI. Of course if you can't get into it to see it...........never mind.
As for the gdi32.dll issue: that file shows as 278k in my system32 folder (3311). If I unpack the SP3 file that I downloaded, gdi32.dl_ is only 133k in size. Apparently even after the download is unpacked, the files are still "compressed" in some way. ?But when I unpack the newest SP3 5512 download, gdi32.dl_ on it is 134k. So apparently the files are indeed different in that 'compressed' state or whatever it is. What it ends up being after final 5512 of SP3 is installed, I can't say. Does anyone know?
indycar_89 wrote: I did also download a ACPI driver, but i have no way (that I know of) to find out what ACPI driver is already on the hard drive. Nor do I know how to install this driver without the OS.
See if you can unzip or unpack that ACPI driver file and look for any .ini or .inf files. I always get those confused and I can NEVER remember which is which! But you want to find the one that is the driver setup info file type. If you find it, then search the HD for that file or similar file name to see if it's installed. It may be in Windows, System32, or if it's the inf type file in the windows/inf folder. If the HD is not hooked up to another PC, you can do a 'dir' in DOS to list what's in each folder to find it. Time-consuming.
Hello everyone,
I am having exactly the same problem, I also have an ASUS A8N32-SLI, I have tried with the BIOS 1405, but, it do the same. I have found a temporal solution that works for me:
I have a 2GB USB pen drive, I plugged it before power up the computer, and then, the OS boots up perfectly. It doesn't matter the contents of the pen drive. It's only needs to be detected by the BIOS during the boot-up. It works also if you add another hard drive like SLAVE or in other controller.
My computer is totally stable. I have SP3 installed since 1st of May, with this problem resolved by this way.
I don't know why this resolve the issue for my, I only know that works for me.
My Computer specs:
AMD X2 4800+
ASUS A8N32-SLI Deluxe
4 modules KHX3200A/512 Kingston HyperX
RAID 0 - 2 x Hitachi Deskstar T7K250
Pioneer DVR-A09
2 x XFX 6800GT 256MB SLIed
Us Robotics 805417a WiFi.
I have tried with a completely fresh install (XP-SP2 OEM), and inmediately applied the SP3 (without installing any software or drivers). It has exactly the same effect. BSOD error 0x000000A5.
I think that the people from MS must talk with ASUS people.
Regards
P.D.: Please if somebody try to follow my steps and work for him, please share it with te community and post it.
I thought you may be on to something when I saw that.... "I have found a temporal solution that works for me", (BTW, I think you mean "temporary").
But, unfortunately not. I have a 2nd HD hooked up and that doesn't help. One SATA main and one IDE for storage and backup. I also have a USB and FireWire HD, and a USB flash card reader (and conventional floppy drive combo) that's seen by the BIOS as USB mass storage. So, this didn't work for me, but at least it worked for you. The question now, is, why did it work.
However.....my main HD is not on a Native controller (it's on the Promise) and the IDE HD is on a Native Intel IDE controller. Perhaps "it's seeing this as only one HD". And, the FW and USB HD's are not on when I boot. But even if they were they would not be seen during the boot process. What exactly do you mean by "detected by the BIOS during the boot-up"? Do you have to see something during POST regarding the external drives or 2nd HD, or do you mean the BIOS just needs to know they are there while booting? But again there's my flash card reader which should fill your requirement. It too is not seen during POST, but is always seen in the BIOS.
rgg071178 wrote: I have tried with a completely fresh install (XP-SP2 OEM), and inmediately applied the SP3 (without installing any software or drivers). It has exactly the same effect. BSOD error 0x000000A5.
Now I'm confused, I thought you said you found a fix, a way around this, but above you said it's exactly the same effect. So are you still getting the rebooting issues or did the addition of your USB device get rid of the rebooting issue?
Yes, sorry the correct word is temporary.
The clean fresh installation was a test. I was looking for installed software or drivers, which could interfere with SP3. Those test were unsuccessful.
I have an USB card reader too. The BIOS during POST detects it as USB MASS STORAGE, but with it doesn't work. It only works with a pen drive. My BIOS during POST detects the devices in this sequence:
Processor installed
Memory count
s-ata devices
p-ata devices
usb devices
NVIDIA RAID BIOS
RAID VOLUME
and finally boot the OS.
Once the OS begins to load, just in the exact point that the reboot happens, I can see the led of the pen drive blinking. This point is when the WINDOWS XP screen is fading in.
If you are telling that have an intel native HDD controller, your problem could be from a different kind.
I'm going to try this tonight with some USB flash drives and see what happens.
My mobo has both the Native Intel (2) SATA and (2) IDE controllers, plus an IDE and (2) SATA controllers from Promise.
I am getting the neverending rebooting issue as well. I downloaded SP3 from the update website last night and went to restart, and got to "How do you want to start Windows", tried all options, and they all reboot my computer.
I tried numerous things last night like, doing a chkdsk -r from recovery console, also tried a fixboot, a Windows repair, and a fixmbr, but nothing worked. I eventually reformatted and everything came up fine after new fresh install with SP2. I then loaded in my motherboard drivers, video drivers, mouse driver, and loaded anti-virus, then tried to update to SP3 again. After second update to SP3, it did same thing as before.
Shashank:
1. My system configuration is:
Asus A8N32 SLI Deluxe -skt939
Athlon 64 3700 @ 2.72 GHz < stable too, everyday running speed for 2 years
2GB of Corsair XMS DDR500
2 x EVGA 7900GT Superclocked in SLI
Seagate SATA2 250GB
Plextor dual layer DVD burner
Razor Copperhead mouse
Kaspersky Internet Security 7
Also all of my drivers are WHQL certified.
2. Safe mode does not work.
As far as your number 3 goes, I'm not following. It seems like what your asking for and others have mentioned is that there is a blue screen with STOP code on it, that I just don't see. If this is the case how do I get to see this blue screen?
Any ideas anybody? It appears that there are a few other people with very similar Asus board in this thread as well.- Hi everyone,
I tried the workaround suggested by rgg071178 and it worked fine for me. The only information that was missing in his post is that you have to keep the memory stick everytime that you boot the computer. If you take it off, it comes back to the endless loop.
My computer configuration is
AMD X2 3500+ASUS A8N32-SLI Deluxe
2x Corsair TWINX 1024Mb
Seagate 250GB SATA HD 7200
GeForce 7600 GT Gainward Bliss PCX 256Mb (PCI-E) DT SilentFX
I was getting this error message:
The BIOS in this system is not fully ACPI compliant . ~info about updating~if unable to update bios or if most recent is installed, you can turn off ACPI mode during text setup. Press F7 when prompted to install storage drivers (I have not been prompted to do this) Windows will silently disable ACPI and allow you to continue with installation"STOP: 0x000000A5 (0x0000002, 0x86De2928, 0xE1012a70, 0x86d4EE10
and I tried both solutions without any success
1) Replacing the C:\Windows\System32\gdi32.dll with the C:\Windows\ServicePackFiles\i386\gdi32.dll
2) Renaming the intelppm.sys to intelppm.old in C:\Windows\System32\Drivers
The only workaround was to boot with me memory stick inserted (I have a 1Gb Kingston).
I downloaded the SP3 from the Microsoft Update website and I am using an original copy of Windows.I also have the latest BIOS version from Asus.
I hope this information will help other as much as helped me. I flipped on my external USB hard drive, and that did stop the never ending boot - however, the system is now stalled at the "WIN XP please wait ...." screen. Been hung there about 15mins now. Gonna let it hand some more, just in case it's actually doing something. I do get flashing drive light, but still it hangs.
Fragem - if you press F8 during start up, you will get more boot options, and one of those will be to disable the auto -reboot. then the screen will freeze and provide some info ~ yours I'm assuming will say something like mine does (posted above) [before this stall issue]
dave
I am making more tests, and the unique solution for me is a pen drive (USB FLASH DRIVE, nor an external HD) or a new internal HD connected to the SATA or PATA controllers.
I don't have any idea of, why this works.
I hope that this post will be very useful for more people with our problem and the MS tech guys look it for a solution.
Best Regards
***UPDATE****
Since the system was hanging at the win xp please wait screen (not the normal winxp screen) I rebooted with the USB external drive turned off - and the constant re-booting started again. Then I put in a thumb USB drive into a front USB port - and still the continued re-booting. Then I powered back on the USB external drive (which is connected to a USB port in the REAR) and the system booted all the way and is now running!!
I have an appointment I need to attend to, so I am not able to do any more tests till later, but wanted to post this.
Dave
indycar_89 wrote: I flipped on my external USB hard drive, and that did stop the never ending boot - however, the system is now stalled at the "WIN XP please wait ...." screen. Been hung there about 15mins now. Gonna let it hand some more, just in case it's actually doing something. I do get flashing drive light, but still it hangs.
Fragem - if you press F8 during start up, you will get more boot options, and one of those will be to disable the auto -reboot. then the screen will freeze and provide some info ~ yours I'm assuming will say something like mine does (posted above) [before this stall issue]
dave
Thanks indycar_89. I've entered safe mode by doing F8 plenty of times before, I've just never seen it listed before, but after doing it here at work just now, I see the option. Its apart of that middle chunk of 5 options that I've never had to use so I've always overlooked them.
I'll give the USB flash drive suggestion from rgg a try tonight.
I'll post back with my STOP code tonight. Microsoft please find a permenant fix.
I've heard of a couple of reasons why this occurs. One is some kind of problem with gdi32.dll that I do not know much about yet. The other is an issue with the Intel power management driver starting on an AMD system for some reason. A fellow MVP named Bill Castner told me about a work-around which I documented here:
See if that workd for you. It shoudl primarily be a problem with OEM deployed systems, so if this actually is your problem with a custom built system, I'd like to know about it.
My system was custom built by me. My copy of Windows is an OEM copy that I purchased from either Newegg or ZipZoomFly.
That's what bothers me. There is a solution to the GDI32 problem posted here:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
Here is what you do:
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
See if that works for you. If it doesn't, please try the intelppm solution. If the intelppm solution works for you I think we have a different level of problems and I'd like to hear about it.
Same situation:
1. Machine: HP Pavillion a1657c / AMD Athlon 64x2 Dual Core Processor 4600 / 2Gig Ram / Nvidia GeForce 7500 LE Video Card
2. Safe mode boot successful (that is how I am writting this post)
3. Will try
4. Will capture and load.
THIS IS NOT THE PROBLEM!! Don't change your GDI.dll
That solution was for a pre-release. This problem is different. We have continually re-booting systems.
(Yes i tried the GDI change - its not the problem here)
I also have a custom built machine.
Wachuko, that's almost exactly the same machine I had. I am guessing you are running HP's pre-installed XP image? If so, you have the intelppm.sys problem that I detailed in the blog post.
Indycar_89: from what I have heard, the GDI problem was not fixed in the released version. I have not seen that problem personally though, so I can't vouch for it.
If you have an AMD system, try the intelppm.sys fix. Is there any other information you can give us? Do you have a STOP error code or, better still, a minidump? I did not get one with mine, but I have heard others get it.
Jesper Johansson wrote: Wachuko, that's almost exactly the same machine I had. I am guessing you are running HP's pre-installed XP image? If so, you have the intelppm.sys problem that I detailed in the blog post.
HP XP image, correct. Do you mind providing the link to the blog? I can't seem to find it. Thank you!
Yep. HP XP image. Here is the blog post:
Jesper Johansson wrote: Yep. HP XP image. Here is the blog post:
Jesper,
Spot on!! That did it. Thank you!
- I just downloaded the package from Microsoft a few minutes ago. You are telling me they are releasing an out of date version? Why is it offered? Now that I have vented, what is a fix? I get the reboot circle, too. I cannot get into any version of "Safe Mode" and the system recovery disk promises to wipe out all data. I even put in an install CD to see if it would go to "Repair". No such luck. I understand now that IE7 is part of the problem because of some changes. That was not an obvious thing that it needed to be uninstalled. If it had been modified to such a point that WIN will not boot, what willl it do when I go to other interactive sites (like colllege courses) that require it? Any experience there?
- Does anyone notice that this is only happening to AMD? I have 5 computers. The pentiums had no problem, but all three AMDs did...
imfoster wrote: Does anyone notice that this is only happening to AMD? I have 5 computers. The pentiums had no problem, but all three AMDs did... Check the fix Jesper gave me. Worked for both of my AMD machines that were having problems. Easy to do.
I'm back into Windows normally, the idea that rgg had about plugging in a USB flash drive worked. After plugging in a flash drive my computer booted normally.
My error code that I received was going on about my BIOS not being ACPI compliant.
Stop code: 0x000000A5
This error code is different than the one for the gdi32.dll error, and is also different than the one for produced by the intelppm.
I did a search on my machine and it does have the intelppm.sys file on it, I guess that could still be the problem.
A few things for a couple of the questions posted here. Some of these have been covered in previous posts on this thread.
1) AMD Both my AMD laptop (compaq) and another AMD bare-bones system of mine installed SP3 without issue. Of course, all are running different boards, processors and chips. My system that had/has problems is a duel core on a ASUS A8N SLI deluxe MB. ( the system is posted up there somewhere)
2) the SP3 on windows update is the most current, and according to MOST folks, the gdi.dll problem has been resolved with the version posted on MSFT Update. As for me, the first thing I tried was the gdi.dll fix, had no effect. Switched back to the GDI.dll that came with the SP3 update.
3) Many posters have found that hooking up a USB pen drive, thumb drive or hard drive has worked for them. Even attaching a SATA or ATA drive has been said to work as well.
For me, (as supplied by another poster above) my system responded when I turned on my USB back-up hard drive (its been there al along, butnot powered up) and rebooted. My system the hung on the sp3 win xp please wait screen. I turned off the USB external and put in a thumb USB in a FRONT USB port and rebooted - and the system went back to auto re-booting. I then turned back on the USB hard drive that's hooked up to a port on the BACK, and presto! Windows finished booting and works flawlessly.
I have not had time to mess anymore with it, so I don't know if I turn off the USB drive if the problem reoccurs or not. Will play with it some more later tonight- but I have spent too much time on this already.
4) I did ot have a mini dump log. I did/do have a few logs - one is a install log and the other is something like didi (?) that the Microsoft tech asked for. His email is listed on the 2nd page of this thread. I can give those to you if you like - i'm not at home now so I'm not sure even what the files were called that I sent.
5) I have not looked at the thread posted just above that has a solution yet, so I have not tried that. Again, I'm behind on some stuff now so when I get time .. ..
Dave
- Yes. My error code was the same. ACPI etc.
Dave/Indycar_89
Sounds to me like there are at least two different problems here.
First, some systems crash with a 0x000000A5 error, indicating that the computer is not ACPI compliant. This appears to happen at the reboot during the installation, if I understand it correctly. This issue seems to affect primarily AMD-based computers with a standard OS image. The fix is to plug in some kind of external storage device and reboot the computer.
Second, AMD-based computers running an OEM image (notably HP, but possibly others) go into an endless reboot cycle after the service pack is installed. Most, if not all, do not show a STOP error code at all, and nothing is logged in the event log. The reason is that the OEM deployed both the power management driver for Intel and the one for AMD into the image, which for some reason triggers this behavior after a service pack installation. The fix is to boot into safe mode and disable the intelppm driver.
Does that summarize what we have seen in this thread? Is there anything else going on here? Does anyone have anything else they can confirm is happening? I'm trying to concisely collate the issues others are seeing because I know some folks from the SP3 product team at Microsoft are looking at this thread.
There does not appear to be a single person on this thread that have had any success with the gdi32.dll fix. That seems to indicate that this particular issue has gone away.
Just to add to this, I tried Jesper's idea to disable the intelppm, but that had no effect. I tried it from safe typed what Jesper provided into the run box, rebooted and I'm still stuck in a booting loop. I also tried this from recovery console and from there it was telling me that it could not find the file.
Rick, do you have an AMD-based computer with an OEM image? Putting it a bit simpler, do you have an HP computer, probably a Pavillion, with a product number starting with 'a'? If so, try this:
If that does not fit you and you are getting a 0x000000A5 error on the blue screen, try booting the computer with a USB flash drive attached.
If you need help figuring out how to do this, ping me from the blog.
BTW, this is NOT caused by an out of data package, nor does it have anything to do with IE 7.
- Fragem, you seem to have the other problem, the ACPI one. Can you give me some details on your computer? Is it also AMD-based?
Jesper, the stop error 0x000000A5 does not automatically show itself, the only way to see it is to boot up and act like you were going into safe mode, but instead of choosing safe mode or normal you choose "Disable auto restart upon error" (something like that), once you enter in there then you see the blue screen with the stop code. Also this problem like the second one you mentioned does do a continuous reboot cycle that is only fixable by plugging in removeable storage.
Sorry to reiterate some of what you already said, I just wanted to clarify it seeing as myself and indy_car89 are having the exact same issue.
Jesper Johansson wrote: Fragem, you seem to have the other problem, the ACPI one. Can you give me some details on your computer? Is it also AMD-based? Yes it is.
Here are my pc's components:
Asus A8N32 SLI Deluxe -skt939
Athlon 64 3700 @ 2.72 GHz < stable too, everyday running speed for 2 years
2GB of Corsair XMS DDR500
2 x EVGA 7900GT Superclocked in SLI
Seagate SATA2 250GB
Plextor dual layer DVD burner
Razor Copperhead mouse
Kaspersky Internet Security 7
Also all of my drivers are WHQL certified.
Jasper - I think both issues are the same. Many posters have not hit F8 and then selected 'disable auto re-boot', and so they have not seen an error message. My understanding is that everyone has had the endless reboot cycle on this thread - but i may have missed something. I think the non-error posts are from folks who have not turned off auto re-boot, so they don't see an error message.
I could be wrong!
I think there are actually two completely different issues. What's more, the ACPI problem seems related to the Asus A8N32 SLI Deluxe motherboard. Everyone on this thread that has had the ACPI problem seems to be on that motherboard. The manifestation of both is the same, however, with the endless reboot cycle, but the cause is different.
I updated the blog post too as a way to make it easier to discover.
Jesper - First of all, my apologies for referring you to as 'Jasper'.
Secondly, I believe you're correct. Sorry I missed it. Read your blog, nice.
Thanks for your efforts to keep thing straight!
- I have this rebooting problem... but I'm on an INtel Celeron D 346! ANyone know why o.O?
No worries on the name man. Trust me, I'm used to it. :-)
I just wish this could have bene caught ahead of time.
Dudeman, I presume you installed the final release of the service pack? Did you try setting the "Disable automatic restart on system failure" setting and get an error code? That would help tremendously. Post back when you have one.So I tried that below and not only did it not work for me, this time I got the first BSOD. That could be because someone suggested (either in this thread or another "rebooting issue" thread) to disable the automatic restarting after a BSOD, and did that yesterday. Naturally, nothing was written to the minidump folder so it was useless! This was the BSOD, the infamous IRQL_NOT_LESS_OR_EQUAL and:
0x0000000A (0xF779FC54, 0x000000FF, 0x00000000, 0x804FB806)
As anyone can guess, again naturally, I'm the only person on the planet with a 0x804FB806 parameter because a search for it finds nothing!
So another apparently useless BSOD due to no memory dump! No, it's not hardware because this is a new mobo, new HD, and new memory! Plus the memory passes all tests in the MS WMD (Windows Memory Diagnostics) program and newest MemTest86+.
Clint D. wrote: I'm going to try this tonight with some USB flash drives and see what happens.
My mobo has both the Native Intel (2) SATA and (2) IDE controllers, plus an IDE and (2) SATA controllers from Promise.
I found a solution.
Restart your computer and press F8. Then, on my computer, you can choose which device to boot from. Choose HD. Thats all.
indycar_89 wrote: Fragem - if you press F8 during start up, you will get more boot options, and one of those will be to disable the auto -reboot. then the screen will freeze and provide some info ~ yours I'm assuming will say something like mine does (posted above) [before this stall issue]
dave
That only works on certain mobo's. Pressing F8 when I boot only gives me a boot menu that selects different boot devices.
rgg071178 wrote: I am making more tests, and the unique solution for me is a pen drive (USB FLASH DRIVE, nor an external HD) or a new internal HD connected to the SATA or PATA controllers.
I don't have any idea of, why this works.
I hope that this post will be very useful for more people with our problem and the MS tech guys look it for a solution.
Best Regards
Your "nor"'s and "or's" are a bit confusing.
Thanks.
Jesper Johansson wrote: I've heard of a couple of reasons why this occurs. One is some kind of problem with gdi32.dll that I do not know much about yet. The other is an issue with the Intel power management driver starting on an AMD system for some reason. A fellow MVP named Bill Castner told me about a work-around which I documented here:
See if that workd for you. It shoudl primarily be a problem with OEM deployed systems, so if this actually is your problem with a custom built system, I'd like to know about it.
For the record, replacing gdi32.dll on my PC only made things worse! It would never boot at all. And, I'm not using an AMD CPU, it's a Socket 478 P4 Northwood. Power management, and all those type of options are off in my BIOS.
Jesper Johansson wrote: I've heard of a couple of reasons why this occurs. One is some kind of problem with gdi32.dll that I do not know much about yet. The other is an issue with the Intel power management driver starting on an AMD system for some reason. A fellow MVP named Bill Castner told me about a work-around which I documented here:
See if that workd for you. It shoudl primarily be a problem with OEM deployed systems, so if this actually is your problem with a custom built system, I'd like to know about it.
Sorry I forgot to mention mine is a custom built PC, it's not any name brand PC. And like others I've seen so far mention this, it's an Asus mobo! But as I just stated in my last post, P4 and not AMD.
Jesper Johansson wrote: That's what bothers me. There is a solution to the GDI32 problem posted here:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3151626&SiteID=17
Here is what you do:
1. boot from a Windows CD and go for the repair option.
2. Copy gdi32.dll from c:\windows\servicepackfiles\i386\gdi32.dll to c:\windows\system32\gdi32.dll. (Do keep a backup copy of the old gdi32.dll in c:\windows\system32 directory)
3. Reboot normally
See if that works for you. If it doesn't, please try the intelppm solution. If the intelppm solution works for you I think we have a different level of problems and I'd like to hear about it.
Sorry but I'm not sure what the "intelppm solution" is. I have several intelppm files on my PC: one in the system32/drivers folder; SP uninstall; ServicePackfiles/i386; symbols/sys; and two in "reinstallbackups...." folders.
Again, mine is a custom built PC and P4, not HP or OEM or AMD.
imfoster wrote: Does anyone notice that this is only happening to AMD? I have 5 computers. The pentiums had no problem, but all three AMDs did... I don't mean to be repetitive, but some may only be watching for replies to their posts, so I'll state again my PC is not an AMD but a P4.
Rick, I'm using IE6 not IE7.
Fragem, the USB flash drive method did not work for me. That is very strange that is working for some. For all of you that has had success with that method, look in your BIOS and see if you have anything about "Legacy USB Devices" or similar and how is it set. Asus for one, has a problem when Legacy USB devices is enabled. It's disabled on mine. Also check to see if you all have only 480mbps USB 2.0 enabled, or also have USB 1.1 full speed enabled. The only option I have for that is USB 2.0 enabled or disabled. FTR, my mobo is an Asus P4C800-E Deluxe.
Master500 wrote: I found a solution.
Restart your computer and press F8. Then, on my computer, you can choose which device to boot from. Choose HD. Thats all.
But we are all booting from the HD anyway, correct? Do you mean set the main HD as the first boot device, and not floppy or CDROM as first with HD second?
Currently I have boot order: floppy, cd, hd. I used floppy to update bios.
Updating bios didn't help.
If I boot the computer it will check my empty floppy and cd and then try to boot from HD, and start looping with BSOD.
When I press F8 and choose to boot from HD it works, I don't remember if that dialog changes the boot order, I think it's only chooses what to boot from.
- Hmmm. When I can restart again I'll try this. I usually have the HD as the first boot device, but I just haven't changed it back from the CD being first.
Clint:
Sorry for my bad typing. I meant "not". An external HDD doesn't work for me, it only works with an USB FLASH DRIVE (pen drive), or adding a new internal s-ata or p-ata HDD attached to any of the onboard controllers.
I have enabled the Legacy USB, USB 2.0 Hi Speed and USB 1.1 Full Speed.
I supose that this temporary fixing is only valid if you have a 0x000000A5 ACPI error.
Regards
rgg071178 wrote: Clint:
Sorry for my bad typing. I meant "not". An external HDD doesn't work for me, it only works with an USB FLASH DRIVE (pen drive), or adding a new internal s-ata or p-ata HDD attached to any of the onboard controllers.
I have enabled the Legacy USB, USB 2.0 Hi Speed and USB 1.1 Full Speed.
I supose that this temporary fixing is only valid if you have a 0x000000A5 ACPI error.
Regards
Ok. I have a second storage HD attached internally to the PRI IDE connector, so that didn't work for me. On that BSOD I mentioned that I got after disabling restart, the first parameter
was a 0x0A error, nothing mentioned about ACPI. I'm going to check my ACPI area in the BIOS again, I believe there was another similar option below it. I'll also try the external USB HD method "on", and I'll leave the USB flash drive attached. It could be that the USB flash drive didn't work because it has never been hooked up yet on SP3, maybe it needs to be first seen for a first time for it to work thereafter.
Well I restarted with the flash drive still connected and I got that same BSOD again I mentioned here in the 6th post from the bottom: http://forums.microsoft.com/technet/showpost.aspx?postid=3315878&siteid=17&mode=1&sb=0&d=1&at=7&ft=11&tf=0&pageid=4 (Why aren't posts here numbered and how can we link to a specific post? I updated the info in that post with the correct 0x000000FF parameter).
So that method definitely doesn't work for me. Next time I restart I'll turn on the external USB HD.
That ACPI area in my BIOS is:
ACPI 2.0 support..........[Enabled]
ACPI APIC support.......[Enabled]
BIOS-->AML ACPI table....[freakin' forgot what was here!!
]
FYI if anyone doesn't know, ACPI is related to the "MPS" option in the BIOS which is "Multi-Processor Support". MPS is a deprecated precursor to ACPI. Mine has MPS v1.1 and v1.4 choices, and is set to 1.4. MPS I would guess may only matter in dual CPU setups, or dual-core CPU's, or Hyper-Threaded P4 CPU's which show as dual CPU's in XP. (Mine is the latter). Or it could be that it means nothing and ACPI settings take precedence over it.
More info on "ACPI APIC support" here: http://www.techarp.com/showfreebog.aspx?lang=0&bogno=363 . Interesting what it says there about F5, F6 and F7. I think the F5 or F7 option will allow you to chose a 'dual core-dual CPU-HyperThreaded CPU' type option which may work better if you have one of those type CPU's.
Those of you having this rebooting issue that mentions something about ACPI should look at this for more info that may answer some things: http://www.fceduc.umu.se/~jesruv98/computer_related/apm_acpi_apic/
- My PC is a home built ASUS A7N8X-E with AMD XP 3200+ and I installed WinXP SP2 3 years ago!
I upgraded to SP3 by doing a repair with a WinXP SP3 slipstreamed CD to make sure "old things" get fixed.
Two or three days further, while surfing I got a popup with a serious error (I just don't remember what) and
hurried to post a "verify now" on my partition and the PC shut down and kept rebooting at the same time !
(but I seen later that the verify was posted).
Trying "safe mode" -> kept rebooting
PartitionMagic found my NTFS partition but could not verify it, telling "error 1516 partition incorrectly deleted"
Using my SP3 slipstreamed CD I got to the repair console and issued a CHKDSK /R X: on my NTFS partition
This fixed the problem and at the next reboot, the system verifyied again my partition as it was posted!
Time to do a backup!
Remaining prob: I cannot "Windows Update" nor "Microsoft Update" since installing SP3:
Numéro d'erreur : 0x8007043B
My laptop is a dell latitude d830 with intel core2 duo.
WAY TO GO MICROSOFT! You know, most people in the business world would be FIRED for this kind of lousy programming!!!
I too installed sp3 and at reboot got the blue screen of DEATH! I tried booting in last known good mode, BZZZZZZZZZZ wrong. I tried booting in safe mode, BZZZZZZZZZZ wrong!
I finally had to reinstall and repair to get into windows.
I'm not sure I have enough faith in you people to try reinstalling sp3 again and will NEVER go to your POS vista. Dirty money grubbing Microsoft. Build an OS that works for pete sake!Notice how someone from MS came in once on this thread and asked for more info, received loads of it, then has totally disappeared since then without a single word.
I found the post and that was Shashank, so I'm going to email him.
Re ASUS mb and AMD CPU.
Just checking to see - if intellppm.sys not on there now - will I be OK ?
I have homemade A8n-e w/ AMD3200 / XP SP2 and still running SP2 ( doing homework first - how I found this) and just as FYI, I did a search on my pc for the intelppm.sys file and it's not on my hard drive. I read the 'msinfluentials' info and just to clarify: the 'folks with problems ' - did they have intellppm.sys on there PRIOR to upgrade ? and that's why a problem ? Or did SP3 PUT it on there and tweaked other values so that NOW it's a problem ?
Thanks- I also have an Intel Based system and getting the reboot issue. (Intel Celeron D 346) The computer will not boot, and wont even go into safe mode or anything like that. I have no BSOD, and if I disable "automatically restart on system failure" it doesn't do anything, Just reboots again.
Now I was looking around online and found this:
http://cquirke.mvps.org/sp2intel.htm
I know this relates to SP2 but what if MS accidentally replaced it with an old version? RJ, while I can't answer your question for sure, it appears to have been on SP2 as well. I searched my HD for it (intelppm.sys) and I found it in the SP uninstall folder and it was the same version as most system files on SP2, v2180. On SP3 it's updated to whatever build you have installed, so it would be v5512 for the release SP3. So it may be feasible for those of you using AMD to replace the SP3 version with the SP2 version....(keep in mind I haven't read that webpage yet about this since I'm not using AMD).
And what I'd like to know is if that file has anything to do with this issue for those that are on a P4 system?
- RJ -,
If intelppm.sys is not on your PC, then you will not suffer the particular problem relating to the presence of intelppm.sys. No-one can say you wan't hit some other problem, however!
People who are having intelppm.sys problem are having them because the pre-loaded XP on their PCs included both Intel and AMD processor drivers, something a clean XP installation would never do. With previous versions, this did not cause a problem. With the SP3 versions, intelppm.sys has a violent dislike of finding itself running on an AMD processor, and causes the blue screen error (or a reboot cycle for those who have not disabled automatic reboots).
Since you installed your own XP on a home-made machine, then you would not have had this problem anyway.
This may be of interest to some of you, in the "Comments" area too:
http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/24/484461.aspx (why are the links clickable in my posts but not clickable in anyone elses posts?)
dudeman123 wrote: I also have an Intel Based system and getting the reboot issue. (Intel Celeron D 346) The computer will not boot, and wont even go into safe mode or anything like that. I have no BSOD, and if I disable "automatically restart on system failure" it doesn't do anything, Just reboots again.
Now I was looking around online and found this:
http://cquirke.mvps.org/sp2intel.htm
I know this relates to SP2 but what if MS accidentally replaced it with an old version?It never ceases to amaze me how screwed up Intel's website is. Bad links, incorrect info at the links, etc. The Intel URL on that page http://cquirke.mvps.org/sp2intel.htm is supposed to be for P4 CPU's. I even searched their site for Processor Frequency ID Utility, found this page which is also for Socket 478 P4's, http://www.intel.com/support/processors/pentium4/sb/CS-001479.htm , and the download is for old CPU's that came before the P4!!
Clint D. wrote: dudeman123 wrote: I also have an Intel Based system and getting the reboot issue. (Intel Celeron D 346) The computer will not boot, and wont even go into safe mode or anything like that. I have no BSOD, and if I disable "automatically restart on system failure" it doesn't do anything, Just reboots again.
Now I was looking around online and found this:
http://cquirke.mvps.org/sp2intel.htm
I know this relates to SP2 but what if MS accidentally replaced it with an old version?It never ceases to amaze me how screwed up Intel's website is. Bad links, incorrect info at the links, etc. The Intel URL on that page http://cquirke.mvps.org/sp2intel.htm is supposed to be for P4 CPU's. I even searched their site for Processor Frequency ID Utility, found this page which is also for Socket 478 P4's, http://www.intel.com/support/processors/pentium4/sb/CS-001479.htm , and the download is for old CPU's that came before the P4!!
Yeah but there is a MS fix:
http://www.microsoft.com/downloads/details.aspx?FamilyId=9B99C199-5D75-454F-AE07-B620727BE8D8&displaylang=en&displaylang=enClint D. wrote: dudeman123 wrote: I also have an Intel Based system and getting the reboot issue. (Intel Celeron D 346) The computer will not boot, and wont even go into safe mode or anything like that. I have no BSOD, and if I disable "automatically restart on system failure" it doesn't do anything, Just reboots again.
Now I was looking around online and found this:
http://cquirke.mvps.org/sp2intel.htm
I know this relates to SP2 but what if MS accidentally replaced it with an old version?It never ceases to amaze me how screwed up Intel's website is. Bad links, incorrect info at the links, etc. The Intel URL on that page http://cquirke.mvps.org/sp2intel.htm is supposed to be for P4 CPU's. I even searched their site for Processor Frequency ID Utility, found this page which is also for Socket 478 P4's, http://www.intel.com/support/processors/pentium4/sb/CS-001479.htm , and the download is for old CPU's that came before the P4!!
Yeah but there is a MS fix:
http://www.microsoft.com/downloads/details.aspx?FamilyId=9B99C199-5D75-454F-AE07-B620727BE8D8&displaylang=en&displaylang=endudeman123 wrote: read this!
http://cquirke.mvps.org/sp2intel.htm
I think this may be the problemI don't think that's the problem because that file intelppm.sys is updated in SP3.
Clint D. wrote: dudeman123 wrote: read this!
http://cquirke.mvps.org/sp2intel.htm
I think this may be the problemI don't think that's the problem because that file intelppm.sys is updated in SP3.
I compared the one from that microsoft update to the one currently installed (From SP3) and it IS different. DIfferent MD5 hash and size.Clint D. wrote: dudeman123 wrote: read this!
http://cquirke.mvps.org/sp2intel.htm
I think this may be the problemI don't think that's the problem because that file intelppm.sys is updated in SP3.
wait a minute!!! I'm not talking about intelppm.sys lol... im talking about update.sysThis is incredible. Freakin' morons. I installed that Intel download anyway and as I expected it says it's not supported for my CPU. I clicked the "Web update" button on the interface, and what happens??
Page Not Found
We are sorry, there is no Intel.com page matching your request.
Idiots. [insert the banging your head on the wall emoticon here]
Dudeman that MS download you linked to sounds like that's something that would be fixed with a mobo's BIOS update. The only reason I wanted it is because I might get a Prescott P4 and that page said "If you do have a Prescott or other affected processor, or may upgrade to one later, then it may" (pertain to you). But since my mobo supports Prescotts I don't guess I have that to worry about. ?
- Yeah well I wouldn't have tried to install the Intel update if I were you
Does anyone know why some of my posts have that strange highlight to them like my last one above? I'm not doing anything different when I post!
- I don't know but Microsoft should REALLY fix this REBOOTING ISSUE!!! and like you said.. that one MS guy ran from here!
What they also need to fix are these forums! I'm getting SICK OF having to login every time I come here!
Well this is interesting. I just restarted with an external USB enclosure turned on, and with a HD in it, and guess what? PC booted just fine. I'll have to restart, turn off/on several more times to be sure. So for those of you still having this problem, hook up some kind of an external USB storage device, I guess a HD is all that would do since USB flash drives didn't work for me.
Now this begs the obvious question....WHY does this work?????? Let's try and find out why for those of us for which this has worked:
Is it the external USB HD that's "fixing" the problem, or, will it also work with any type of external USB device that's on with something in it? I have a USB media reader, but nothing in it. So later on I'll try putting a CF card in it and reboot.
What about non-storage USB devices, will they also work? I don't have any other kind of USB devices that can remain on always while booting. So if any of you do that's had this problem and the external USB HD fixed it, try it with these other types of devices. Like scanners, printers, etc., that can remain on with no auto-off during restarting.
Does this have anything to do with USB settings in the mobo's BIOS? Try changing some USB settings, like Legacy support off/on, USB 2.0 off/on, USB 1.1 off/on, etc., etc.
I'll investigate this further tonight.
Grrr... . Clint, I feel your pain. Have you sent an email to the MSFT tech who gave his addy on page 2 (I believe)? He asked me for these files :
a) C:\Windows\svcpack.logb) C:\Windows\setupapi.logFYI - when i tried the USB thumb drive, it did not work. I'm not sure if it was because I use a front USB port or if it was the thumb drive itself. The USB hard drive plugged into a rear port worked for me.Would you like me to experiment on this to determine if it is an thumb drive issue or a port location issue?Both of my PCs are custom built, one had this problem and the other didn't. What ASUS mobo are you running and what chip?thx.Yeah I emailed him, that was Shashank. I just told him the thread was 6 pages (now 7 pages...now make that 8 pages) long and asked if he would get back here. But I didn't remember him asking for those files. I don't even have svcpack.log in the Windows folder. In fact I don't have it anywhere, just the dll version of it and other types, but no .log file of it. But I do have setupapi, and I guess it's a log file, it's a text file (I have 'show extensions' off).
Interesting, my USB flash drive was connected to the rear, didn't work. The USB HD is also connected to a rear port (which did work as a temp fix).
Sure, we're all going to have to experiment with this to nail down why this fix works. I'm about to leave for the day, but I'll be doing some testing tonight on this.
My mobo is the Asus P4C800-E Deluxe, Intel 875P chipset. P4.
Clint, are you sure that your code is 0x0000000A? That's a new one. I don't know why that would be related to the service pack. Usually it indicates a bad driver, but it could also indicate an incompatible driver or faulty hardware. I have also seen it with malware that tried to hook into the system. In that case you could very well expect to see it when you perform a major update as the malware no longer works the way it was designed.
There is some detail on troubleshooting it here: http://support.microsoft.com/kb/314063.
0x804FB806 is the memory address that the process tried to touch. You should not expect to find anything on that. It is only useful if you analyze the crash dump because it will tell you what it was that was being accessed.
Jesper Johansson wrote: Clint, are you sure that your code is 0x0000000A? That's a new one. I don't know why that would be related to the service pack. Usually it indicates a bad driver, but it could also indicate an incompatible driver or faulty hardware. I have also seen it with malware that tried to hook into the system. In that case you could very well expect to see it when you perform a major update as the malware no longer works the way it was designed.
There is some detail on troubleshooting it here: http://support.microsoft.com/kb/314063.
0x804FB806 is the memory address that the process tried to touch. You should not expect to find anything on that. It is only useful if you analyze the crash dump because it will tell you what it was that was being accessed.
Mine are always a "new one". LOL. Yep, it's just like I typed it, that's the first parameter after the STOP: and before the parenthetical parameter inflection. Again, the external USB HD appears to have been a fix for me. And I never got any memory dump, I guess XP didn't load enough to "activate" it.
My mobo is new, memory is new, main HD is new, optical drives new, so I doubt it's HW related, plus the fix for me would indicate it is indeed the same issue that others are having.
I run AdAware, SpyBot, Spyware Blaster, Spyware Terminator, and more, plus KIS7 (Kaspersky Internet Security 7). All clean.
BTW, I saw that MS URL you mentioned earlier when I saw the BSOD, and noticed this:
"Other possible causes of this error are an incompatible device driver, a general hardware problem, and incompatible software*".
*Which could mean OS's as well. All this is something new with regards to SP3, so I wouldn't expect MS to have any info on it yet.
- Maybe that is your problem. Please, everyone, UNINSTALL all such products before attempting a Service Pack.
Clint D. wrote: I run AdAware, SpyBot, Spyware Blaster, Spyware Terminator, and more, plus KIS7 (Kaspersky Internet Security 7). These products are designed to prevent changes to your system. The Service Pack is deisgned to make sweeping changes to your system. These aims and objectives are inherently incompatible. If you try running both, you will just end up with a screwed-up and confused system.
rdhw wrote: Maybe that is your problem. Please, everyone, UNINSTALL all such products before attempting a Service Pack.Clint D. wrote: I run AdAware, SpyBot, Spyware Blaster, Spyware Terminator, and more, plus KIS7 (Kaspersky Internet Security 7). These products are designed to prevent changes to your system. The Service Pack is deisgned to make sweeping changes to your system. These aims and objectives are inherently incompatible. If you try running both, you will just end up with a screwed-up and confused system.
Huh? Now why would I have any of those running while installing SP3? I'm not a newbie at this.
Glad you are up and running Clint!!
The forum does seem to be jacked up today, I have tried posting several times to retract my last post, but no success.
Are there other posters still on this thread who have not be able to get up and running?? (granted, we're all using a temp fix, but at least we're in!)
Clint, I really think your problem is different. Most people had the problem on the first reboot after installing the service pack. You got far beyond that before you had a problem. In fact, if you have all that anti-malware software on there I wouldn't be surprised if one of them isn't conflicting with another and that is what is causing your problem.rdhw wrote: - RJ -,
If intelppm.sys is not on your PC, then you will not suffer the particular problem relating to the presence of intelppm.sys. No-one can say you wan't hit some other problem, however!
People who are having intelppm.sys problem are having them because the pre-loaded XP on their PCs included both Intel and AMD processor drivers, something a clean XP installation would never do. With previous versions, this did not cause a problem. With the SP3 versions, intelppm.sys has a violent dislike of finding itself running on an AMD processor, and causes the blue screen error (or a reboot cycle for those who have not disabled automatic reboots).
Since you installed your own XP on a home-made machine, then you would not have had this problem anyway.
The XP SP2 versions of the intelppm.sys driver also had problems under AMD processor based machines as I've seen here:
http://www.runpcrun.com/0x0000007E
For those XP users who are really using AMD based CPUs, the solutions there on that site have helped in resolving some endless reboot problems in XP SP2 and XP SP3. Not sure for those using recent Intel based CPUs.indycar_89 wrote: Glad you are up and running Clint!!
The forum does seem to be jacked up today, I have tried posting several times to retract my last post, but no success.
Are there other posters still on this thread who have not be able to get up and running?? (granted, we're all using a temp fix, but at least we're in!)
[sign in, sign in, sign in, sign in, sign in....sheeesh]
I've been up and running ok, just haven't been able to start or restart without doing it about 10 times.
Aside from this one issue, I've been able to fix every other SP3 issue I've encountered permanently. In all, SP3 seems great to me, but this one problem is unacceptable--having to have a USB HD on all the time in order for a PC to restart.
Jesper Johansson wrote: Clint, I really think your problem is different. Most people had the problem on the first reboot after installing the service pack. You got far beyond that before you had a problem. In fact, if you have all that anti-malware software on there I wouldn't be surprised if one of them isn't conflicting with another and that is what is causing your problem.
I just restarted and its still working ok.
Naaa. Again, they were not installed until a while had passed, plus I started getting the reboot problem before they were installed. Also, none of them are even running except for KIS. Aside from it, they are all used as scanners, no real-time protection....(except for SpyBot's SDHelper [IE bad download blocker] which I think is a DLL that's "loaded but not running", and its TeaTimer which does usually run, but I haven't been running it because its latest version sucks up 40mb). SpyWare Blaster doesn't run, it uses registry tags and Restricted Sites zone for its protection.
I state again, it cannot be coincidental that turning on a USB HD fixed this issue for me. That's too rare and odd of a thing to work.
Well this is definitely the (temp) fix for me. I've reproduced it several times. If I restart with the USB HD off, no restarting and I get BSOD (as long as it's set to no auto reboot after a stop). With the USB HD on, no problem.
I'm gone for the day, hopefully by tonight I will have received a reply from Shashank. I'll also work on trying to figure out why this works.
- I don't know if my first reply made it, I got an error message that indicated a problem occurred when I tried to send it. Last Tuesday I installed SP3 when it was pushed down to my PC. During the reboot process my PC went into an infinite reboot loop. I tried the selection of booting from the last known good session, but that brings me back to the infinite loop also. I tried to get into Safe mode but can't. I get an error message that \system32\hal.dll is corrupt and should be replaced. I have an HP Pavilion with Windows Media Center 2005 and and AMD Athlon processor. Prior to SP3 I had SP2 and all updates installed. The PC does look nice just sitting there though. I am saving on electricity. Is this a new Green program from Microsoft? Joe
jrednasnh,
What is the error code you are getting? hal.dll being corrupt is bad, but I really want to know what the error code is. If you don't see it, please follow the directions here to halt the reboot process. http://msinfluentials.com/blogs/jesper/archive/2008/05/08/does-your-amd-based-computer-boot-after-installing-xp-sp3.aspx. That will cause the computer to stop on the crash screen and you can then copy down the codes.
I really only need the first code. It will say something like "STOP: 0x12345678 (something, something, something, something) SOME_ERROR_MESSAGE". The parts within parenthesis is not that interesting, but everything else is. 0x12345678 is the error code. That's the most important part.
Clint, are you absolutely sure your error code was 0x0000000A and not 0x000000A5? It definitely sounds like the 0x000000A5 problem if plugging in the USB hard drive helps.
If anyone else has the 0x000000A5 problem and plugging in the USB drive helps, could you please confirm that you must keep it plugged in or the crashing will start back up again? It would be interesting to know one way or the other, but I do not have a computer with that problem handy.
Jesper,
For me plugging in a USB flash drive helped me boot into Windows normally and into safe mode, once I remove the flash and restart my computer I go back to being stuck in a booting loop. Once I reconnect my USB flash drive it's fixed.
Thanks Fragem, that's very helpful.
The next question is for the folks that have to 0x00000024 problem:
Do you have a RAID card in your computer? If so, what kind?
The Problem with the A8N32SLI-Deluxe is the Sil3132 PCIe to 2Port SATA300 Controler.
I have installed SP3 and i got BSOD. I disabled the Controler in my Bios and XP SP3 starts normal.
I have an SATAII Drive on it and now i cant use it
n!vader: that is very very interesting. Is this the 0x24 error you are seeing?
If you disable that controller, what are you booting from? Is there another drive in the computer that is not connected to that controller?
He probably means setting it from AHCI to IDE mode lets his machine boot up.
- Same here.
I have an Asus A8N32-SLI mobo and tried installing SP3 and when I reboot I ended up with the never-ending rebooting situation (0x000000A5). I then freaked out because I had important information on my harddrive so I tried starting up in Safe Mode, no luck. Tried without the automatic reboot on error, no luck. So I reinstalled XP without reformatting, hoping my important documents would still be on the partition somewhere. After the first reboot right after the first blue setup screen when it says its copying files to be installed, I still got the BSOD.
I found this forum and did a little reading and tried booting up with a flash USB drive connected... it worked! Now the question is, how do I ever use my computer normally again without using the flash USB drive because the BSOD even appears when trying to reinstall the OS... maybe it's because I never formatted the HD.
Anyway, thanks for help guys. Jesper - Mine was the 0x000000A5. Will not re-boot unless my USB HD is turned on.
Add me to the list:
Dell Dimension 2300 windows XP professional sp2 1.8Ghz P4 528 MB RAM
Put me into an endless reboot cycle and it won't even boot into safe mood or last known good configuration.
Gave up and restored an Acronis Image and am back to running xp2 until MS fixes this mess.
I pity those who have not made images and then try to install this mess only to see their PCs hosed.
Tahoejoe: what was your error when you ended up in the endless reboot cycle? We just found that some kind of ATI driver also causes a problem with SP3.Can't remember specifically but ended up at the screen where it tells you something changed and would you like to boot into safe, normal, or last known good config. Tried all of them and nothing worked. Always ended up back at that same screen. Far as I know, there is no ATI driver. Graphics capability is buit into the Intel MB.
I to have the ASUS A8N32-SLI Deluxe mobo with AMD 64 FX-60 Dual Core, I got the ACPI error, couldn't get into safe mode at all, I thought all was lost and dug out my restore disc expecting to take my PC back to factory settings losing everything, after pressing F8 during post got the little pop up asking where I would like to boot from, naturally selecting DVD where my restore disc was, this started to do it's thing then took me to the window where it asks if I want to boot in safe mode, safe mode with networking, etc so, I thought one last time tried safe mode, joy of joys it started in safe mode and allowed me to remove sp3 from my machine, all is now back to sp2 and working fine.
Don't know why it booted into safe mode with that disc.
I really thought I was going to loose everything by shoving in the factory restore disc, didn't find this site until after doing this so can't verify if usb pen drive trick works.
I had been offline for a few months due to an illness, today is the first time I booted my XP system since February.
Windows auto update ran and automatically installed XP SP3, as with the above post all my system would do after the SP3 update installed was re-boot.
I was finally able to access Safe Mode, uninstalled the XP SP3 update, and restore the XP SP2 system.
What is the issue with SP3, I have had to disable the auto update feature of windows?
Highwayman, SP3 is not supposed to be deployed via Auto Update yet. Did you have Auto Update set to alert you before download and install? That should be the only way it deploys via AU.Tahoejoe: no, you probably wouldn't have an ATI graphics chip on an Intel motherboard seeing as how ATI is owned by AMD. :-)
Yours sounds odd. Without the error code it is hard to tell what is going on though.
- I am also suffering from the endless reboot issue after installing SP3. I have an Intel Q6600 processor on a Gigabyte GA-P35DS3P version 1 motherboard, 2 Gigabytes of Patriot PC8500 memory, an ATI HD2900 video card, ATI 650 pro PCI Express TV card. I am using the Realtek onboard audio and LAN connections. I am using a Seagate 7200.10 250 GB SATA drive for my system drive with 4 Seagate 7200.10 750 SATA drives for storage, a Samsung SH182-D IDE DVD burner and a Samsung SG203B SATA DVD burner. I have Nero 8, Office 2007 Standard, avast anti-virus, and amazon unbox video installed. I have the latest drivers for all components. I am using a Logitech Cordless Internet Pro keyboard with a Logitech Cordless Trackman trackball. I am unable to boot to safe mode, last known good configuration or anything else. My only choice has been to reinstall Windows XP Pro OEM with SP2 and then download all the updates again. Fortunately I have not run into problems with activation as I have done a "repair" installation. Unfortunately this clears my event logs and there is not a minidump.
Thank you for your quick reply.
I did have auto update enabled and I was prompted to do the update.
When prompted I clicked continue then the Accept License Agreement button.
I have an HP system with an AMD 64 3800+ processor as follows:
OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 2 Build 2600
OS Manufacturer Microsoft Corporation
System Name BERNIE
System Manufacturer HP Pavilion 061
System Model EL466AA-ABA a1330n
System Type X86-based PC
Processor x86 Family 15 Model 47 Stepping 2 AuthenticAMD ~2387 Mhz
BIOS Version/Date Phoenix Technologies, LTD 3.13, 11/15/2005
SMBIOS Version 2.4
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
User Name xxxxxxxxxxxxx
Time Zone Eastern Daylight Time
Total Physical Memory 2,048.00 MB
gswonsn - so are you up and running or no?
05-09-2008,,,, 1013pm e,,, sounds like MS has a problem with admiting they messed up,,,, they should pull the SP3 relaese and fix everyones problems,,,
this is not the first time,,,, that they have messed up,,,,
a note to all users of Windows XP,,,, and they want all to switch to Vista,,
sorry to hear that there are so many problems,,,
thank you for listening,,,,
gswonsn:
Do you happen to have the ATI Catalyst 8.4 drivers installed? It soulds like you might. I'm trying to figure out if that driver kit is incompatible with SP3, so if you can tell me, I'd appreciate it.
- I have Update set to download but not install until I manually do it. I *think* I have SP3 downloaded but I'm not certain. Normally I get a box with the file ID and I can check online before I install it. This time there's no file ID. I get the following message when I check Windows Update from the Start menu:
You need to restart your computer to finish installing a program or updates. You cannot view or get other updates from the site until you restart. Read more about steps you can take to resolve this problem (error number 0x8DDD0007) yourself.
I did have problems installing AVG 8.0 anti-virus today and aborted the install, so it's possible that's the problem, although I have rebooted since aborting that install. I had to go into Safe Mode for the first reboot but did a normal reboot afterwards.
How can I tell if it's SP3 waiting to be installed or if it's the remnants of the AVG aborted install? Given the horror stories I'm reading today, I'm not going to reboot and/or install any updates until I know what's going on. If it is SP3 waiting to be installed, how can I kill it? Clicking on the update tray icon just gives me the options of rebooting now or later, although the box does say "Automatic Updates" - which was what led to me to thinking it was SP3 and not the AVG install.
When I go to Windows Update via IE7, I get the same error message listed above.
If it is the remnants of the aborted AVG install, would it be ok to go back to a restore point prior to the attempted install or would the then necessary reboot install SP3 if that's what's waiting to be installed? I was barely able to get into Safe Mode after the bad AVG install and I'd prefer to stay far away from any trace of it. Highwayman, your system is almost exactly the same as mine. What puzzles me though is that you say you got it from Auto Update. Do you know if your computer uses a Windows Software Update Services (WSUS) server? According to what I have been told, SP3 is not deployed through AU yet.
- I haven't read through all of the messages that were posted overnight yet, I needed to post this first. Now I'm more confused that ever. I cannot reproduce the problem anymore! Now my PC Is booting fine without any USB HD connected!!
Jesper Johansson wrote: Clint, are you absolutely sure your error code was 0x0000000A and not 0x000000A5? It definitely sounds like the 0x000000A5 problem if plugging in the USB hard drive helps.
If anyone else has the 0x000000A5 problem and plugging in the USB drive helps, could you please confirm that you must keep it plugged in or the crashing will start back up again? It would be interesting to know one way or the other, but I do not have a computer with that problem handy.
Yes, 0x0000000A.
n!Vader wrote: The Problem with the A8N32SLI-Deluxe is the Sil3132 PCIe to 2Port SATA300 Controler.
I have installed SP3 and i got BSOD. I disabled the Controler in my Bios and XP SP3 starts normal.
I have an SATAII Drive on it and now i cant use it
FWIW, I haven't seen any 0x00000024 error, and while I don't have a RAID card, I do have the Promise RAID controller enabled, but it's running in IDE mode. That's where my main single SATA HD is hooked, but nothing is hooked up to its IDE controller.
Jesper Johansson wrote: Tahoejoe: what was your error when you ended up in the endless reboot cycle? We just found that some kind of ATI driver also causes a problem with SP3.
Hmmm, I'm using an ATI All-In-Wonder Radeon 9800 Pro, 8x AGP. But.....I had originally installed the ATI drivers, but because ATI are idiots with their software and drivers by consistently ruining them, their latest drivers would not work with the MMC version I wanted to use (MultiMedia Center which is what displays the TV Tuner), so I had to remove the ATI drivers and I went with the latest Omega drivers. http://www.omegadrivers.net/ati.php That was I was able to use MMC v9.08 (which does not have the TV-On-Demand running all the time which screws things up).
I have nothing related to ATI (or Omega) loading with XP, like others do. They are not needed for anything so I always disable them from loading via Msconfig's startup tab. These are usually: "Launch Pad", which is a toolbar with icons for the TV, DVD player, etc. ATIDtc, Ati2mdxx, and atiptaxx. These may be different on other PC's with different driver or MMC versions. But they are usually with the ATI**** prefix. It may be interesting for those of you with ATI cards to disable these from loading via Msconfig's startup tab. Also, there are two Services (also not needed) that are loaded. "ATI HotKey Poller" (Ati2evxx.exe), and "ATI Smart" (ati2sgag.exe), both disabled on mine.
Jesper Johansson wrote: Tahoejoe: no, you probably wouldn't have an ATI graphics chip on an Intel motherboard seeing as how ATI is owned by AMD. :-)
Yours sounds odd. Without the error code it is hard to tell what is going on though.
They're owned by AMD now yes, but they're still ATI branded chips. There are Intel mobo's with integrated ATI video. But I can't say if they are still being made today.
gswonsn wrote: I am also suffering from the endless reboot issue after installing SP3. I have an Intel Q6600 processor on a Gigabyte GA-P35DS3P version 1 motherboard, 2 Gigabytes of Patriot PC8500 memory, an ATI HD2900 video card, ATI 650 pro PCI Express TV card. I am using the Realtek onboard audio and LAN connections. I am using a Seagate 7200.10 250 GB SATA drive for my system drive with 4 Seagate 7200.10 750 SATA drives for storage, a Samsung SH182-D IDE DVD burner and a Samsung SG203B SATA DVD burner. I have Nero 8, Office 2007 Standard, avast anti-virus, and amazon unbox video installed. I have the latest drivers for all components. I am using a Logitech Cordless Internet Pro keyboard with a Logitech Cordless Trackman trackball. Another mention of an ATI product. Is anyone with this problem not using an ATI product?
You also mentioned a Logitech mouse. I'm using a Logitech MX700 cordless optical mouse, and it's USB but I use the adapter so I can hook it up to the PS/2 port. So is everyone here using a USB mouse, or Logitech mouse?
Jesper Johansson wrote: Highwayman, your system is almost exactly the same as mine. What puzzles me though is that you say you got it from Auto Update. Do you know if your computer uses a Windows Software Update Services (WSUS) server? According to what I have been told, SP3 is not deployed through AU yet.
Apparently (from another thread on this forum) although SP3 strictly speaking does not Auto Update, it DOES show up for those of us who use the Auto Update setting to Notify but not download. I got the notification by this method a few days ago.
Jesper Johansson wrote: gswonsn:
Do you happen to have the ATI Catalyst 8.4 drivers installed? It soulds like you might. I'm trying to figure out if that driver kit is incompatible with SP3, so if you can tell me, I'd appreciate it.
BTW, the ATI Omega drivers I use are the latest from Omega, but they are based on Catalyst 7.12. (Could be because that was the latest stable working version of Catalyst).
Hi Jasper,
Cringing Dragon wrote: Jesper Johansson wrote:
Highwayman, your system is almost exactly the same as mine. What puzzles me though is that you say you got it from Auto Update. Do you know if your computer uses a Windows Software Update Services (WSUS) server? According to what I have been told, SP3 is not deployed through AU yet.
Apparently (from another thread on this forum) although SP3 strictly speaking does not Auto Update, it DOES show up for those of us who use the Auto Update setting to Notify but not download. I got the notification by this method a few days ago.
This is exactly what happened on my system yesterday.
I also read in other posts on the thread about a possible ATI video drivers problem that may be causing the SP3 update to fail, my system has an ATI Radeon Xpress 200 Series controller.
(Let's try editing instead of deleting).
AND HERE WE GO AGAIN, the THIRD time trying to post! An entire page of posts was just deleted, plus TWO of mine and I only tried to delete one! I'm going to stop trying to fix posts, if they are duplicated, TUFF.
-----------
I am REALLY getting FED UP with these screwed up forums! Having to log in with every single visit, and:
And, entire posts getting deleted! I just tried to post something and got errors, and the damn post never got posted. Luckily, never trusting the way any forums works, I saved the post! HA! Take that TechNet! So here is the post.....Unknown Error We apologize, but an unknown error has occurred in the forums. This error has been logged.
boxner1 wrote: How can I tell if it's SP3 waiting to be installed or if it's the remnants of the AVG aborted install? Given the horror stories I'm reading today, I'm not going to reboot and/or install any updates until I know what's going on. If it is SP3 waiting to be installed, how can I kill it? Clicking on the update tray icon just gives me the options of rebooting now or later, although the box does say "Automatic Updates" - which was what led to me to thinking it was SP3 and not the AVG install.
If it is the remnants of the aborted AVG install, would it be ok to go back to a restore point prior to the attempted install or would the then necessary reboot install SP3 if that's what's waiting to be installed? I was barely able to get into Safe Mode after the bad AVG install and I'd prefer to stay far away from any trace of it.SP3 INSISTS on setting Auto Updates to automatic. I have had to set mine to disable maybe 5 times. Now make that SEVEN times and still counting.
No one should have Auto Updates set to automatic. We all know, or we all at least should know, that MS cannot be trusted with anything they offer via WU site. Any one single seemingly benign patch can render a PC totally useless. More so with a SP. Every patch, update or SP they release is done so with minimal if any testing, as we are seeing once again. They are more concerned with shoving a patch out the proverbial door to prevent some exploit that may only be experienced by .001% of the people, whereas the patch could screw up 95% of PC's. I have horror stories going back ~10 years regarding their patches. Proof of lack of testing is a patch to fix what another patch messed up that was to fix what another patch messed up that was for what another patch messed up.........etc. It's ridiculous.
This is even worse for newbies or those that know nothing about PC's. Should they install an update or patch that's to prevent what they have a .001% of experiencing, with a patch that could screw up their PC's that they have no idea what caused it nor what do to about it? Or, should they not risk the patch's problems and practice sensible computing with anti-malware programs, AV software, firewalls, and tightened OS and browser security, then investigate on their own if they even need the patch in the first place? The latter seems the more logical choice.
The best thing for anyone to do, and what I do, is subscribe to Secunia alerts. They will send you emails when there is a new MS update or patch out. Then go to the WU site(1), select "Custom", and check out what all is available. Click on the "details" or "more info" links under each available update, go to the MS-**** article or KB article for IT pro's, and read about it. Go to the mitigating factors area on the info pages. I think you have to expand a + sign to get to that area, but it is on the pages. They will list who really needs the patch, and usually even some workarounds to do in lieu of the patch. A big majority of the patches are not even needed if you use a firewall, something that everyone should do. I use a hardware firewall AND a software firewall. Then there's a huge amount of them that are not even needed if you have a certain Service disabled. and still more that are not needed if you don't have the affected software or Windows product installed! That's something else everyone should do; disable all Services that you don't need. http://www.blackviper.com/ is the best site out there for leaning about Services and finding out which you need to have enabled. http://www.blackviper.com/WinXP/servicecfg.htm is the area for SP3, being updated right now. If I find out that I do indeed really need a patch, then and only then do I install it. And I don't install anything else around that time so if my PC does a meltdown I'll know what caused it and I can remove it or do a restore.
MS's constant "handholding" and "hijacking" of PC's is something I will not tolerate. My PC is my PC, I own it, and I will not have someone or something dictate what is best for me when they know absolutely nothing about what they are doing, nor what I have installed or not installed, what I have enabled or disabled, my type of computing--all of which is what really dictates what you need.
Regarding restore, XP's restore is very limited. There's a great free program out there called ERUNT, http://larshederer.homepage.t-online.de/erunt/ , that will automatically make a total and full registry backup including sam, security, software, system, everything, every time you start your PC. I think it's once per day, but you can at any time do a manual backup. I do this before I install anything, you can name the backup anything you want so it won't overwrite the previous one for that day. That way if the install screws up something, you can do this full restore. It can sit in your Start Up folder and that's how it automatically creates a full backup on its own. It does this in a couple of seconds and shuts down. Nothing is running in the background and you don't even know it's happened. It's saved my a$$ numerous times.
Investigate, research, use your heads, and you decide whether or not a patch or update is necessary for you.
(1) I made a vbs and batch file that automatically starts the Auto Updates and BITS Services, and goes to the update site, that is activated when I click the "Windows Update" icon in the Start menu. Then when I leave the update site, it then automatically shuts down the Auto Updates and BITS Services putting them back on Manual. I haven't tried that macro yet with SP3, I'm sure it will work, but there's the problem with SP3 trying to keep putting Auto Updates on automatic. The Services have to be on "manual" for the macro to work. If those Services are on manual on SP3, it will keep setting them to automatic. I'll have to check into this further.
(Always be sure you copy/paste your posts into a Notepad to save when this site screws up and deletes your post! Then you'll be able to try again without having to remember everything you typed! That's something that's screwed up with these forums, the cut/copy & paste! You can't do it via right click like everywhere else, you have to do it from the "Edit" menu in IE's toolbar).- Guys, sorry for the post problems but it's not my fault. I have tried now FIVE TIMES to delete the duplicate post, a post that I was told DID NOT GET POSTED, and THREE posts are deleted when I try and delete it, including your last post Highwayman! Who knows what will happen now with this post.
Another thing that's screwed up is the email notifications. There are no more "Click here to view the post alert details", and even the text in the post is gone from the emails! All I'm seeing in them is the unsubscribe link, and "If this reply answers your question, please visit the link above and........"
- Clint D. and other with the USB HD "fix":
to shed more light on this issue, allow me a question which, as far as I see, has not been asked so far.
Did you have any USB drives (flash or hard disk) attached while installing SP3?
Do you remember?
Different issue: I also had problems with an ATI video card (Sapphire Radeon 7000 PCI, 64MB DDR). Already emailed Shashank about it. I installed SP3 onto an existing XP Pro SP2. Worked fine. Then installed the Radeon card (before that I was using on-board SiS graphics). Because the card is quite old, XP was able to automatically install its own drivers, i.e. one of those whose name ends in ".... (Microsoft Corporation)". After a reboot the PC froze while showing the XP boot logo. No automatic restarts though, most likely because I disabled automatic reboot. But no BSOD either. Just a complete lock-up at every reboot. Safe mode works! And: the Radeon worked fine when I tested it under SP2 a few weeks ago. Hi Jasper,
Cringing Dragon wrote: Jesper Johansson wrote:
Highwayman, your system is almost exactly the same as mine. What puzzles me though is that you say you got it from Auto Update. Do you know if your computer uses a Windows Software Update Services (WSUS) server? According to what I have been told, SP3 is not deployed through AU yet.
Apparently (from another thread on this forum) although SP3 strictly speaking does not Auto Update, it DOES show up for those of us who use the Auto Update setting to Notify but not download. I got the notification by this method a few days ago.
This is exactly what happened on my system yesterday.
I also read in other posts on the thread about a possible ATI video drivers problem that may be causing the SP3 update to fail, my system has an ATI Radeon Xpress 200 Series controller.
Christian Helmrich wrote: Clint D. and other with the USB HD "fix":
to shed more light on this issue, allow me a question which, as far as I see, has not been asked so far.
Did you have any USB drives (flash or hard disk) attached while installing SP3?
Do you remember?
Different issue: I also had problems with an ATI video card (Sapphire Radeon 7000 PCI, 64MB DDR). Already emailed Shashank about it. I installed SP3 onto an existing XP Pro SP2. Worked fine. Then installed the Radeon card (before that I was using on-board SiS graphics). Because the card is quite old, XP was able to automatically install its own drivers, i.e. one of those whose name ends in ".... (Microsoft Corporation)". After a reboot the PC froze while showing the XP boot logo. No automatic restarts though, most likely because I disabled automatic reboot. But no BSOD either. Just a complete lock-up at every reboot. Safe mode works! And: the Radeon worked fine when I tested it under SP2 a few weeks ago.Remember that I said earlier that I can't duplicate or reproduce the problem anymore! My PC is now restarting/rebooting with no external USB HD's connected.
So when I installed SP3.....that's a good question. No I can't really recall if any USB devices were connected, but I do know that none were turned on. I think I may have had my FireWire HD enclosure connected, and I may have had the USB HD connected, but I do know for sure they were not turned on. My combo floppy drive media card reader was connected. It uses the typical floppy ribbon cable, and USB connection for the CF, SD, MMC card slots. But nothing was in it either.
That reminds me of something strange that happened. Before I installed SP3, I hooked up a new HD, formatted and installed my XP Pro SP2 CD. I was getting BSOD's during the install and when the Desktop finally would go to load for the first time after installation. I don't know why, but I unplugged all of my USB and FireWire cables, did it all again, and if I remember correctly all was Ok after that.
I don't know if that means anything or not, but it may be worth noting at least.
- I see there are two more of you that said you're using ATI video. That might call for another "hmmmm". Still waiting to see if anyone here is not using ATI video.
Clint D. wrote: My mobo is also an Asus (P4C800-E Deluxe), but it IS ACPI compliant, it's set that way in the BIOS. Be careful about flashing to new Asus BIOS versions. They suck. They remove features that previous BIOS versions had! In my case, v1015 removed UDMA 6! So I'm using 1014 so my ATA133 and SATA drives will be UDMA 6.You've got to be joking! The Intel ICH5R and all later ICH chips only support up to UDMA-5. Intel refused to jump on the UDMA-6 bandwagon because it was a marketing gimmick with no performance advantage over UDMA-5. The ASUS BIOS was erroneously reporting UDMA-6, which ASUS corrected in BIOS 1014 (not 1015).And you mean to say that you are actually using a deprecated BIOS from 2003 that is a full eight BIOS releases and TWO YEARS behind the latest non-beta BIOS, because you believe that having your system erroneously report UDMA-6 is more important than the numerous bug fixes and improvements that eight newer BIOS releases incorporated over a period of TWO YEARS? Wow.Your motherboard does not become ACPI compliant because its set that way in BIOS. It becomes ACPI compliant when the BIOS is ACPI compliant as a matter of fact. Lots of BIOS versions over the years were (and continue to be) released that were not ACPI compliant due to bugs or flaws in spite of claiming it. That's precisely why we have BIOS updates.As far as your commentary on Intel's website, the webpage from which you attempted to access Intel's website is at least three years old. As you might know, websites are changed every so often, older URLs may become invalid when nobody has verified them for three years. They just started this internet thing about 15 years ago, maybe you haven't got the hang of it, yet?The Intel Processor Frequency ID utility was retired long ago and never supported Prescott-based Pentium 4. Ergo, the webpage linked you to the WRONG utility. It was the wrong utility for Prescott-based Pentium 4 even three years ago when the SP2 v. Prescott issue was reasonably current information. The correct utility for Pentium 4 and later processors is the Intel Processor Identification Utility, not the "Frequency ID" utility which only supports older Intel processors. Intel can't do anything about webpages that link you to the wrong utility.Even so, I was easily able to determine from Intel's website that it was not the correct utility and locate the correct one. OK, maybe that isn't entirely accurate. I experienced the same mix-up you did, only it was about four years ago. So I had prior knowledge about the two different utilities. You got me there.And no, MPS is neither related nor a deprecated precursor to ACPI. MPS is related to APIC (Advanced Programmable Interrupt Controller), not ACPI (Advanced Configuration and Power Interface). MPS is Intel's Multiprocessor Specification, which covers APIC architectures required for multiprocessor (and multicore) systems. ACPI settings do not over-ride or otherwise take precedent over APIC. They are two different things that interact on many levels but neither depends on the other to exist nor can take the other's place.It is interesting that you seem confident in your technical criticisms of Microsoft and yet can't even figure out that your Intel chipset doesn't support UDMA-6, the webpage that linked you to Intel contains out-dated and erroneous information, or running a BIOS that is a full TWO YEARS and eight releases deprecated may not be a technically sound decision or rationale.Have you even updated any of your drivers in the past four or five years?tcsenter wrote: Clint D. wrote: My mobo is also an Asus (P4C800-E Deluxe), but it IS ACPI compliant, it's set that way in the BIOS. Be careful about flashing to new Asus BIOS versions. They suck. They remove features that previous BIOS versions had! In my case, v1015 removed UDMA 6! So I'm using 1014 so my ATA133 and SATA drives will be UDMA 6.You've got to be joking! The Intel ICH5R and all later ICH chips only support up to UDMA-5. Intel refused to jump on the UDMA-6 bandwagon because it was a marketing gimmick with no performance advantage over UDMA-5. The ASUS BIOS was erroneously reporting UDMA-6, which ASUS corrected in BIOS 1014 (not 1015).No they don't. ICH5(R) supports UDMA 6. Intel doesn't have ATA133 support on their IDE controllers, not the ICHxx SATA controllers. The Asus BIOS's starting with I think 1014 removed UDMA6 support and went back to UDMA 5. But, in XP in the Device Manager, even on 1016 it shows UDMA 6 where applicable.BIOS v1014: Revise Ultra DMA Mode max limit (ultra DMA mode 6--->5)And you mean to say that you are actually using a deprecated BIOS from 2003 that is a full eight BIOS releases and TWO YEARS behind the latest non-beta BIOS, because you believe that having your system erroneously report UDMA-6 is more important than the numerous bug fixes and improvements that eight newer BIOS releases incorporated over a period of TWO YEARS? Wow. "Wow" is right. What the hell does that have to do with anything?? What the hell does that have to do with this thread and the SP3 rebooting issue?? NOTHING. Haven't you ever heard of "if it ain't broke don't fix it", which certainly holds true for mobo BIOS's more than anything else! Even the mobo manufacturers tell you to never update your BIOS unless you're having problems!Your motherboard does not become ACPI compliant because its set that way in BIOS. It becomes ACPI compliant when the BIOS is ACPI compliant as a matter of fact. Lots of BIOS versions over the years were (and continue to be) released that were not ACPI compliant due to bugs or flaws in spite of claiming it. That's precisely why we have BIOS updates. All I can say, and what I SAID, is the BIOS has ACPI area in the BIOS with 3 entires and options, [enabled], and, it shows as "ACPI Multiprocessor PC" and "ROOT/ACPI_HAL" in the Device Manager.As far as your commentary on Intel's website, the webpage from which you attempted to access Intel's website is at least three years old. As you might know, websites are changed every so often, older URLs may become invalid when nobody has verified them for three years. They just started this internet thing about 15 years ago, maybe you haven't got the hang of it, yet? Just what the hell is your problem anywhere and where do YOU get off on this kind of chicken $hit attitude and attacks?? Do I know you? Do you know me?? NO. Did I say that websites are NOT CHANGED? NO, I DID NOT. I SAID, THAT EVEN AFTER A SEARCH THE LINKS THAT INTEL PROVIDED WITH THEIR OWN SITE SEARCH WERE WRONG; AND, LINKS ON THEIR OWN PAGES WERE WRONG. How long have you worked for Intel??The Intel Processor Frequency ID utility was retired long ago and never supported Prescott-based Pentium 4. Then Intel SHOULD REMOVE IT, and THEY HAVE NO BUSINESS PUTTING IT FOR DOWNLOAD UNDER THE PENTIUM 4 DOWNLOAD AREA DO THEY!!!Ergo, the webpage linked you to the WRONG utility. AS I STATED, YES! An INTEL WEBSITE WEBPAGE was LINKED TO THE WRONG INFORMATION!!It was the wrong utility for Prescott-based Pentium 4 even three years ago when the SP2 v. Prescott issue was reasonably current information. Again, NOT MY PROBLEM! INTEL's PROBLEM!!The correct utility for Pentium 4 and later processors is the Intel Processor Identification Utility, not the "Frequency ID" utility which only supports older Intel processors. Intel can't do anything about webpages that link you to the wrong utility. And who said they COULD?? NO ONE. READ....I SAID THEY HAVE ERRONEOUS LINKS ON THEIR OWN WEBSITE!! YOU go and tell them, I DID!Even so, I was easily able to determine from Intel's website that it was not the correct utility and locate the correct one. OK, maybe that isn't entirely accurate. I experienced the same mix-up you did, only it was about four years ago. So I had prior knowledge about the two different utilities. You got me there. Which proves you somehow think, for some unfathomable reason, that I am somehow out to "get you", and you are (obviously) out to "get me". Just who in the hell are you??????And no, MPS is neither related nor a deprecated precursor to ACPI. Oh really??http://forums.2cpu.com/archive/index.php/t-5207.html
The ACPI spec includes all of, and replaces, the MPS 1.4 spec, so if you have ACPI enabled you are running MPS 1.4, regardless of what the MPS setting is.http://ols.108.redhat.com/2007/Reprints/brown_1-Reprint.pdf
Many systems today are multi-processor and thus use an IO-APIC to direct multiple interrupt sources to multiple processors. However, they often do not include legacy MPS (Multi-Processor Specification) support. Thus, ACPI is the only way to configure the IO-APIC on these systems, and they’ll run in XT-PIC mode when booted without ACPI. But to look at ACPI-mode vs. legacy (MPS)-mode a bit deeper, it is necessary to look at the specifications that ACPI replaces. The most important one is Advanced PowerManagement [APM], but ACPI also obsoletes the Multi-Processor Specification [MPS] and the PCI IRQ Routing Specification [PIRQ].http://osdir.com/ml/kernel.commits.2-4/2003-08/msg00067.html
- This option enables limited ACPI support -- just enough to
- enumerate processors from the ACPI Multiple APIC Description
- Table (MADT). Note that ACPI supports both logical (e.g. Hyper-
- Threading) and physical processors, where the MultiProcessor
- Specification (MPS) table only supports physical processors.
+ ACPI enumerates both logical (a.k.a. Hyper-Threaded -- HT)
+ and physical processors. It is designed to obsolete several older
+ specifications, including the MultiProcessor Specification (MPS),
+ which supported only physical processors.Enough said on that.It is interesting that you seem confident in your technical criticisms of Microsoft As ALL of the members are here. Am I the ONLY ONE that has criticized MS here? HELL NO!!! AND I WON'T BE THE LAST EITHER, RIGHTFULLY SO!!and yet can't even figure out that your Intel chipset doesn't support UDMA-6, Already covered above.the webpage that linked you to Intel contains out-dated and erroneous information AS DOES the Intel website!!or running a BIOS that is a full TWO YEARS and eight releases deprecated may not be a technically sound decision or rationale. Have you even updated any of your drivers in the past four or five years?Allow me to inform you of what is technically unsound and irrational: F**king around with new BIOS releases and driver updates is a dangerous thing to do if one is not experiencing any issues! If you knew anything about hardware you would know this. Like MS patches, BIOS and driver updates can create more negative issues than one is already experiencing! You don't update a BIOS unless YOU HAVE TO and they will FIX an issue one is having. You don't go out and install the latest drivers for anything UNLESS YOU HAVE TO and they will FIX an issue one is having.Now, get off your irrelevant soapbox, and if you have anymore irrelevant bullsh!t with which to contaminate this thread, and feel compelled to try and start more $hit, how 'bout taking it to a PM or starting your OWN OFF TOPIC thread ELSEWHERE. The forum members thank you.I am NOT using a ATI product. My video is a NVIDIA GeForce 7600gs.
I AM using a USB logitech mouse.
And my system will not boot without the USB HD turned on.
Hello again,
I have made some more tests. I have an Espon Stylus Photo R300, it has a integrated card reader that is seen as "Epson Stylus Storage USB". My PC also boots-up with the printer powered on.
I am very happy that my idea about he USB flash drive was useful for many people.
Someone have any answer from the MS people?
Regards
- Bueno, pues yo tengo el mismo problema. El problema es que no entiendo ingles. Alguien que hable español? Cuando inicio windows mi problema es: 0x000000713(0xF7A85528, 0XC000034, 0X00000000, 0X00000000)
Viendo el tema de arriba, me pregunto... el problema será de las impresoras epson? No creo, pero yo tengo una RX585 con la cual ya he tenido problemas a la hora de drivers.... Please read thread some good news for thoses with the 0xA5 error Stop error:The bios in this system is not fully ACPI Compliant .
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3321532&SiteID=17
n!Vader wrote: The Problem with the A8N32SLI-Deluxe is the Sil3132 PCIe to 2Port SATA300 Controler.
I have installed SP3 and i got BSOD. I disabled the Controler in my Bios and XP SP3 starts normal.
I have an SATAII Drive on it and now i cant use it
What is the error code that you got n!vader?
My SATA2 hard drive is on the Nvidia controller, but I gave this a shot. I tried disabling the Silicon Image controller by going into my BIOS and setting "Silicon Image Mode" to disabled, rebooted without my flash drive installed and it just went back to the booting loop.
So it did not work for me.
Clint D. wrote: I am REALLY getting FED UP with these screwed up forums! I was interested to read of your problems with the forum, as I am not experiencing any such. Are you by any chance running any cookie-blocking software? That might cause such problems.
rdhw wrote: Clint D. wrote: I am REALLY getting FED UP with these screwed up forums! I was interested to read of your problems with the forum, as I am not experiencing any such. Are you by any chance running any cookie-blocking software? That might cause such problems.
No, the MS/Live Cookies are allowed and stored, the malware Webtrends Cookie is blocked. Chris confirmed there are indeed problems