Windows Xp Service Pack 3 Build 5512 Final Download For Mac

May 24, 2014. I did find what I think was the final version of SP3 for XP. 'Windows XP Service Pack 3 Build 5512 FINAL'. I grabbed one of my old machines with an Intel D865Perl board and a new SATA drive and did a fresh install of XP.

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 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.

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. 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... 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!). 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. 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.

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]. 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. 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. '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]. 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. 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. 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.

'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. System configuration 2. Does safe mode boot succeed? 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. System event viewer logs (from safe mode) and/or contents of%windir% minidump.

Please share any/all of this information at shashankbansalmicrosoftcom 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? 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.

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.

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. 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. 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 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. My system configuration is: Asus A8N32 SLI Deluxe -skt939 Athlon 64 3700 @ 2.72 GHz.

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.' 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. ***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.

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.' 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. That's what bothers me. There is a solution to the GDI32 problem posted here: Here is what you do: 1. boot from a Windows CD and go for the repair option. 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. 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? 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/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. 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? Here are my pc's components: Asus A8N32 SLI Deluxe -skt939 Athlon 64 3700 @ 2.72 GHz.

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+. 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.

Can you please clarify that? The way you wrote 'USB FLASH DRIVE, nor an external HD' means neither of them worked, and the 'or a new internal HD connected to the SATA or PATA controllers' I'm not sure about at all. 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: Here is what you do: 1. boot from a Windows CD and go for the repair option. 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.'

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.

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. 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: (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:. 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. 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!

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? 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. 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: 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 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,, and the download is for old CPU's that came before the P4!!

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: 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 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,, and the download is for old CPU's that came before the P4!! Yeah but there is a MS fix. 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: 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 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,, and the download is for old CPU's that came before the P4!! Yeah but there is a MS fix.

This 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. [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.? 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. 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. 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:. 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:.

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'. 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). Wrote: I run AdAware, SpyBot, Spyware Blaster, Spyware Terminator, and more, plus KIS7 (Kaspersky Internet Security 7). Maybe that is your problem. Please, everyone, UNINSTALL all such products before attempting a Service Pack. 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. Wrote: I run AdAware, SpyBot, Spyware Blaster, Spyware Terminator, and more, plus KIS7 (Kaspersky Internet Security 7). Maybe that is your problem. Please, everyone, UNINSTALL all such products before attempting a Service Pack. 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. Now why would I have any of those running while installing SP3? I'm not a newbie at this.

Furthermore, they were not even installed on the HD when SP3 was installed. I reformatted [edited to add: hooked up new HD and formatted], installed XP Pro + SP2, then installed SP3, THEN installed drivers, then installed software. Rdhw wrote: - RJ -, If intelppm. Fps Creator X9 Model Pack 53 Download Youtube. 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: 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. Yes, it's good to at least have a temp. 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. 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. 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? 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..

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. 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. 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.

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 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.

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.

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!! I thought at first that maybe I just needed to do it once and maybe some kind of driver was permanently placed in a Windows folder somewhere that fixed it. But then I remembered that yesterday I was able to reproduce the error several times when I turned off the USB HD. Nothing was installed or changed since then.

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. 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). Hp Quicklook 3 Software Download. 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.

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. 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. 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: Unknown Error We apologize, but an unknown error has occurred in the forums.

This error has been logged. 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! Take that TechNet!

So here is the post. 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. Is the best site out there for leaning about Services and finding out which you need to have enabled. 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,, 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.' 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. 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. 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.

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.

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, 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 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. 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]. 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. 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. 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. 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 here. ' IE not remembering logon on the TechNet forum is not specific to OS or IE. It's an unrelated issue that forum folks are investigating.' Rgg071178 wrote: 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? Interesting, thanks for that input. Yesterday I posted that the issue with me went away and I could no longer reproduce it. Today when I started my PC, it was back!

If I can reproduce it again and make it disappear again with the USB HD, then I'm going to try my USB card reader with something in it and see if that works. No, I emailed Shashank again and still no reply. I would guess they have absolutely no idea what's going on nor any way of fixing it, so they're going to ignore it. I find it very hard to believe that in 'all of their testing' they never came across this problem. Is anyone with this problem NOT using an Asus mobo? Well I see Indycar is not using an ATI card, so much for that speculation that it has something to do with ATI. But I see you too are using a USB mouse, and, it's a Logitech.

Yesterday I mentioned something about those of you using USB mice. On another SP3 boot issue thread (which I am trying to consolidate into one thread), an MS employee, Emily, is having the problems with her laptop and her and MS TS seemed to pin it down to a (I assume USB) mouse!

Emily, hopefully you're looking at this thread now, please let us know what software you 'cleaned up' that seemed to help at first. Is your mouse USB? Sorry if I missed this, but are all of us using Asus mobo's and Logitech mice, or USB mice? I guess we can rule out ATI, but if the Asus mobo or Logitech/USB mice correlation holds up, then that may narrow down the cause. Most mice are USB these days, but not all of them. Also please state if you're using a PS/2 adapter on a USB mouse, I am. Eric777 wrote: Please read thread some good news for thoses with the 0xA5 error Stop error:The bios in this system is not fully ACPI Compliant.

Jesper I think it was maybe you that asked a couple of times about my 0x0A error and if I was sure about it. My post above from about 2.5 hours ago I mentioned the problem is back for me. I checked again then and it indeed was the 0x0A stop code. I just had to go to the store and I shut off my PC.

When I got back and started it, I got the boot problem once again, and it was still 0x0A. Looks like it may happen to me more so turning on the PC after it's been OFF, more than just a restart. I'll check into this further, and when I can successfully duplicate it again I'm going to test some other USB and FireWire devices. Eric777 wrote: Please read thread some good news for thoses with the 0xA5 error Stop error:The bios in this system is not fully ACPI Compliant. [Edited.Eric I didn't notice that was your posts! So it's edited now to reflect that] And look at that last post on that thread, once again a USB mouse issue, this time an MS mouse. And, it's not a Logitech issue since his worked, Eric I assume your Logitech was PS/2?

So I guess that just leaves Asus mobo's remaining as a commonality, and a USB mouse. Is anyone having this problem using a mobo OTHER THAN Asus, and or using a true PS/2 mouse? You say to use at least a 2gb flash drive, mine was 2gb and that method did not work for me, so unfortunately that's a not a fix for all (I guess it's just for the ACPI BSOD error type like you said). It could depend on whether or not the flash drive supports boot-from. Some USB drives do, some don't.

Eric do you know if your 2gb and 128mb flash drives support being a bootable device? What brand are they? Eric this is worth putting on this thread: Ok I found the error for the ACPI Compliant BSOD stop error code: 0x000000A5 and AMD Athlon™ 64 FX-60 Dual Core and ASUS A8N32-SLI Deluxe PCI-Express Mainboard. In my case it was the onboard network controllers Marvell Yokon and Nvidia nforce network adapters.

I have two because I was using a wireless network adapter.I disabled both in the bios.If I left one enabled I never got the BSOD. If you disable both in windows in Device Manager no errors. So are you saying that in your case it didn't have anything to after all with the USB mouse? If so, that's not good news because we're back to square one since not everyone is going to have both of those controllers. I only have one LAN/Ethernet and it's the Intel PRO/1000 Gigabit. No commonality there, at least not as far as brand or dual LAN's go. Rdhw wrote: Is the common factor behind the problems on this thread that you all have nForce chipsets on your motherboard?

No, I mentioned a couple of posts back I don't have those LAN controllers on my mobo, (I have one Intel PRO/1000 Gigabit), and the main chipset is the Intel 875P chipset. Also with the ICH5(R) controllers (not running RAID), and Promise 378 SATA & IDE controller. Getting confusing. So far, someone please correct me if I'm wrong, looks like the only common factor is a USB mouse, and/or maybe an Asus mobo. Still awaiting input on that regarding the mobo's. I don't have any true PS/2 mice I can easily get to, (and if I changed I'd had to uninstall all the Logitech software).

If anyone has a true PS/2 mouse handy that's having this problem, please try it and see if the boot problem goes away. Not a USB with a PS/2 adapter, but a real PS/2 mouse.

Windows XP SP3 (Service Pack 3) code bits are now been uploaded to Windows Update server, ahead of its public availability on April 29, 2008 for through Windows Update. Users who wary of downloading and applying the can now used the direct download links to download Windows XP SP3 setup installer from Microsoft WU servers.