Hi

Run it with both then if it finds a problem you could then do it one at a time .

Good Luck

 frangione,

Let me ask you something. Have you tried to install anything recently aside from the SP3 attempt? If so, did you have problems with whatever it was? When SP1 and SP2 were released there were dozens of software-based problems & incompatibilities with various system configurations that caused the installation of those service packs to fail or severely corrupt Windows XP. With SP2 in particular i can recall the presence of any spyware creating situations where computers would no longer boot into Windows at all. SP3 isn't without its share of the same, in fact Microsoft provides free setup and compatibility support for customers who install Windows XP SP3. The poin is it's likely there isn't anything wrong with your 8400's hardware. I'd suggest reviewing the Microsoft article before, which includes a link to their free support resources for SP3.

I've read everything Microsoft has to offer about SP3. I had no problems with the SP2 install. I have not had any other install issues.

Since the BSOD led me to a microsoft webpage suggesting a driver error, too, I ran the driver verifier. Looks like the problem could be Norton, as I got a BSOD listing GoBack2k.sys. So, this will be the next thing I look into.

No, of course not EVERYTHING. But, I have been online for 2 days reading as much as I can. Usually the SP3 access denied problem is pretty much always solved by resetting permissions, which I couldn't do as subinacl.exe caused the BSOD. And the underlying problem has nothing to do specifically with SP3. The install process just is revealing that I have another problem to deal with.

Anyway, I am going to assume that you know a lot more about computers than I do. Would you happen to know of the easiest way to rid myself of this driver problem? Obviously I could uninstall System Works, but I was wondering if there was a simple solution, even if temporary, to see if this is really the cause of my grief. I do not use GOBack and it has been disabled on my system for a while.

I don't think it can be installed separately. It is part of System Works and it isn't listed separately in the Add/Remove programs. But, I don't really use anything in System Works that matters that much to me and my subscription is up in 5 months, so it won't be a big loss. I will remove it and see what happens.

If the BSOD has consistently referenced GoBack2k.sys then uninstalling all of System Works is probably unnecessary. Go Back is just one program that's part of the suite so the simplest possible solution would be to uninstall it, especially since you don't even use it. The SP3 installation may complete after that. There's really only one way to find out for sure though.