Ever since XP SP3 came out, my system has been hosed. First, it was
dead, 6 saying it couldn't find some file in the system directory.
After fighting with it all night, I reinstalled Windows. Once
everything was back up, and I reapplied SP3, things started going to
crap again. This time, the messages suggested I had a hard drive
issue. Considering I had just rebuilt this system last December and
replaced everything BUT the system drive, that was a possibility. So,
I went and bought a brand new Maxtor 300GB IDE drive. Reinstalled
Windows. Let that burn in for a day, and everything seemed OK, so I
started reinstalling my apps. Shortly thereafter, the system started
going haywire again. Locking up with no entry in the system or
application event log. I had 4 GB of memory in it, so I took out one
stick, and ran WinDiag on it for something like 26 hous with no errors
found, then I ran MEMTEST86 on it for 49 hours with no errors found.
Confident the problem wasn't memory, I started over again. Formatted
the drive, reinstalled Windows, and let that burn in for 2 days.
Everything was hunky-dory. Once again, reinstalled the rest of my
apps, and let Microsoft Update bring everything back up to date.
Everything was cool for about 3 days, then the system started going
nuts on me again. Locking up, and giving me BSODs. The last one I
captured had stop error
0x0000007F(0x00000000,0x00000000,0x00000000,0x0000 0000). Trying to
boot using safe mode, I kept seeing the system would reboot right
after mup.sys loaded. Researching this pointed to power supply as a
potential problem. I have a Power & Cooling 750W PSU that is less than
6 months old, but I went ahead and bought a brand new Rosewill 750W
PSU that came highly recommended on NewEgg. Tonight, I swapped the
PSUs out, and I still can't get Windows to boot. I ran the repair
console, ran CHKDSK /R. It took forever, said that it found some
errors and fixed them. When I attempted to reboot the system, it went
to a BSOD, which flashed by so quickly I couldn't read it. Then it
went into a reboot loop that I could only stop by powering down. What
do I do now?
My system (all new within the last 6 months):
AMD Athlon 64 X2 Dual 6000+
3 GB RAM, DDR2, Single Channel
Gigabyte GA-MA69GM-S2H MoBo
System drive: Maxtor 300 GB IDE (100GB boot partition, 200GB other
drive)
Second drive: Seagate Barracuda 500 GB SATA drive
eVGA GeForce 8500GT PCIExpress video card, 512 MB RAM
NetGear G311 Gigabit Ethernet card
On Wed, 28 May 2008 21:56:31 -0700 (PDT), Pat
<pat_whitted@hotmail.com> wrote:
>Ever since XP SP3 came out, my system has been hosed.
<snip>
>AMD Athlon 64 X2 Dual 6000+
There are known problems with SP3 and AMD processors.
There are known problems with SP3 and Norton Antivirus.
I don't have either of these, so I wasn't really paying attention, but
you can check at WindowsSecrets.com. Look for the free edition with
date 5/29/08.
"The problems with XP SP3 include AMD-based Hewlett-Packard desktop
computers constantly rebooting and Symantec antivirus products
developing strange behaviors."
There may be other problems as well, but I think this has you covered.
"Pat" <pat_whitted@hotmail.com> wrote in message
news:624c72c4-c25d-4e27-8273-79579dcf221c@b9g2000prh.googlegroups.com...
> Ever since XP SP3 came out, my system has been hosed. First, it was
> dead, 6 saying it couldn't find some file in the system directory.
> After fighting with it all night, I reinstalled Windows. Once
> everything was back up, and I reapplied SP3, things started going to
> crap again. This time, the messages suggested I had a hard drive
> issue. Considering I had just rebuilt this system last December and
> replaced everything BUT the system drive, that was a possibility. So,
> I went and bought a brand new Maxtor 300GB IDE drive. Reinstalled
> Windows. Let that burn in for a day, and everything seemed OK, so I
> started reinstalling my apps. Shortly thereafter, the system started
> going haywire again. Locking up with no entry in the system or
> application event log. I had 4 GB of memory in it, so I took out one
> stick, and ran WinDiag on it for something like 26 hous with no errors
> found, then I ran MEMTEST86 on it for 49 hours with no errors found.
> Confident the problem wasn't memory, I started over again. Formatted
> the drive, reinstalled Windows, and let that burn in for 2 days.
> Everything was hunky-dory. Once again, reinstalled the rest of my
> apps, and let Microsoft Update bring everything back up to date.
> Everything was cool for about 3 days, then the system started going
> nuts on me again. Locking up, and giving me BSODs. The last one I
> captured had stop error
> 0x0000007F(0x00000000,0x00000000,0x00000000,0x0000 0000). Trying to
> boot using safe mode, I kept seeing the system would reboot right
> after mup.sys loaded. Researching this pointed to power supply as a
> potential problem. I have a Power & Cooling 750W PSU that is less than
> 6 months old, but I went ahead and bought a brand new Rosewill 750W
> PSU that came highly recommended on NewEgg. Tonight, I swapped the
> PSUs out, and I still can't get Windows to boot. I ran the repair
> console, ran CHKDSK /R. It took forever, said that it found some
> errors and fixed them. When I attempted to reboot the system, it went
> to a BSOD, which flashed by so quickly I couldn't read it. Then it
> went into a reboot loop that I could only stop by powering down. What
> do I do now?
>
> My system (all new within the last 6 months):
> AMD Athlon 64 X2 Dual 6000+
> 3 GB RAM, DDR2, Single Channel
> Gigabyte GA-MA69GM-S2H MoBo
> System drive: Maxtor 300 GB IDE (100GB boot partition, 200GB other
> drive)
> Second drive: Seagate Barracuda 500 GB SATA drive
> eVGA GeForce 8500GT PCIExpress video card, 512 MB RAM
> NetGear G311 Gigabit Ethernet card
Reinstall XP up to SP2 and turn off automatic updates. Do not install SP3
until the issue is known, acknowledged, and corrected by MS. Complain
loudly. They are hard of hearing.
On May 29, 1:42*am, overl...@spam.ftc.gov wrote:
> On Wed, 28 May 2008 21:56:31 -0700 (PDT), Pat
>
> <pat_whit...@hotmail.com> wrote:
> >Ever since XP SP3 came out, my system has been hosed.
>
> <snip>
>
> >AMD Athlon 64 X2 Dual 6000+
>
> There are known problems with SP3 and AMD processors.
> There are known problems with SP3 and Norton Antivirus.
>
> I don't have either of these, so I wasn't really paying attention, but
> you can check at *WindowsSecrets.com. Look for the free edition with
> date 5/29/08.
>
> "The problems with XP SP3 include AMD-based Hewlett-Packard desktop
> computers constantly rebooting and Symantec antivirus products
> developing strange behaviors."
>
> There may be other problems as well, but I think this has you covered.
>
> Jim
Thanks for the info Jim, but I'm neither running an HP nor NAV. My
system is a beige box, with Windows installed from the original
Windoze CD instead of a manufacturer image.
On Wed, 28 May 2008 21:56:31 -0700 (PDT), Pat <pat_whitted@hotmail.com> wrote:
| Ever since XP SP3 came out, my system has been hosed. First, it was
| dead, 6 saying it couldn't find some file in the system directory.
| After fighting with it all night, I reinstalled Windows. Once
| everything was back up, and I reapplied SP3, things started going to
| crap again. This time, the messages suggested I had a hard drive
| issue. Considering I had just rebuilt this system last December and
| replaced everything BUT the system drive, that was a possibility. So,
| I went and bought a brand new Maxtor 300GB IDE drive. Reinstalled
| Windows. Let that burn in for a day, and everything seemed OK, so I
| started reinstalling my apps. Shortly thereafter, the system started
| going haywire again. Locking up with no entry in the system or
| application event log. I had 4 GB of memory in it, so I took out one
| stick, and ran WinDiag on it for something like 26 hous with no errors
| found, then I ran MEMTEST86 on it for 49 hours with no errors found.
| Confident the problem wasn't memory, I started over again. Formatted
| the drive, reinstalled Windows, and let that burn in for 2 days.
| Everything was hunky-dory. Once again, reinstalled the rest of my
| apps, and let Microsoft Update bring everything back up to date.
| Everything was cool for about 3 days, then the system started going
| nuts on me again. Locking up, and giving me BSODs. The last one I
| captured had stop error
| 0x0000007F(0x00000000,0x00000000,0x00000000,0x0000 0000). Trying to
| boot using safe mode, I kept seeing the system would reboot right
| after mup.sys loaded. Researching this pointed to power supply as a
| potential problem. I have a Power & Cooling 750W PSU that is less than
| 6 months old, but I went ahead and bought a brand new Rosewill 750W
| PSU that came highly recommended on NewEgg. Tonight, I swapped the
| PSUs out, and I still can't get Windows to boot. I ran the repair
| console, ran CHKDSK /R. It took forever, said that it found some
| errors and fixed them. When I attempted to reboot the system, it went
| to a BSOD, which flashed by so quickly I couldn't read it. Then it
| went into a reboot loop that I could only stop by powering down. What
| do I do now?
|
| My system (all new within the last 6 months):
| AMD Athlon 64 X2 Dual 6000+
| 3 GB RAM, DDR2, Single Channel
| Gigabyte GA-MA69GM-S2H MoBo
| System drive: Maxtor 300 GB IDE (100GB boot partition, 200GB other
| drive)
| Second drive: Seagate Barracuda 500 GB SATA drive
| eVGA GeForce 8500GT PCIExpress video card, 512 MB RAM
| NetGear G311 Gigabit Ethernet card
Are you sure you got the latest official SP3 rather than an earlier beta
version? There were definitely problems such as you're having in earlier betas.
Your SP3 file should be 316MB in size. If it's any other size (especially
315MB), it's the wrong SP3 file.
Assuming SP3 is installed...
Make sure Windows isn't rebooting on errors. When a file name that can't be
found comes up, write it down. Then restart Windows with the XP installation
disc and go to Repair Console. Copy the missing file from
WINDOWS\ServicePackFiles\i386\ to WINDOWS\system32\. Overwrite a file by the
same name if one happens to be in system32 (it probably will be). EXIT from
Repair Console and allow Windows to boot normally.
If you don't have the correct SP3 installed, delete it in Add or Remove Programs
and fall back to SP2 once you've got into Windows as result of copying the
missing file into system32.
If you're still having problems, it's probably for some reason other than SP3.
On Thu, 29 May 2008 05:55:32 -0700 (PDT), Pat
<pat_whitted@hotmail.com> wrote:
>On May 29, 1:42*am, overl...@spam.ftc.gov wrote:
>> On Wed, 28 May 2008 21:56:31 -0700 (PDT), Pat
>>
>> <pat_whit...@hotmail.com> wrote:
>> >Ever since XP SP3 came out, my system has been hosed.
>>
>> <snip>
>>
>> >AMD Athlon 64 X2 Dual 6000+
>>
>> There are known problems with SP3 and AMD processors.
>> There are known problems with SP3 and Norton Antivirus.
>>
>> I don't have either of these, so I wasn't really paying attention, but
>> you can check at *WindowsSecrets.com. Look for the free edition with
>> date 5/29/08.
>>
>> "The problems with XP SP3 include AMD-based Hewlett-Packard desktop
>> computers constantly rebooting and Symantec antivirus products
>> developing strange behaviors."
>>
>> There may be other problems as well, but I think this has you covered.
>>
>> Jim
>
>Thanks for the info Jim, but I'm neither running an HP nor NAV. My
>system is a beige box, with Windows installed from the original
>Windoze CD instead of a manufacturer image.
The problem applies to all AMD machines, not just HP. There's some
file that's used only for intel machines that gets loaded by mistake.
The details are in the article.
SP3 is still considered a beta version; it hasn't been offically released.
Why did you reapply it after the first snafu?
--
--DaveW
"Pat" <pat_whitted@hotmail.com> wrote in message
news:624c72c4-c25d-4e27-8273-79579dcf221c@b9g2000prh.googlegroups.com...
> Ever since XP SP3 came out, my system has been hosed. First, it was
> dead, 6 saying it couldn't find some file in the system directory.
> After fighting with it all night, I reinstalled Windows. Once
> everything was back up, and I reapplied SP3, things started going to
> crap again. This time, the messages suggested I had a hard drive
> issue. Considering I had just rebuilt this system last December and
> replaced everything BUT the system drive, that was a possibility. So,
> I went and bought a brand new Maxtor 300GB IDE drive. Reinstalled
> Windows. Let that burn in for a day, and everything seemed OK, so I
> started reinstalling my apps. Shortly thereafter, the system started
> going haywire again. Locking up with no entry in the system or
> application event log. I had 4 GB of memory in it, so I took out one
> stick, and ran WinDiag on it for something like 26 hous with no errors
> found, then I ran MEMTEST86 on it for 49 hours with no errors found.
> Confident the problem wasn't memory, I started over again. Formatted
> the drive, reinstalled Windows, and let that burn in for 2 days.
> Everything was hunky-dory. Once again, reinstalled the rest of my
> apps, and let Microsoft Update bring everything back up to date.
> Everything was cool for about 3 days, then the system started going
> nuts on me again. Locking up, and giving me BSODs. The last one I
> captured had stop error
> 0x0000007F(0x00000000,0x00000000,0x00000000,0x0000 0000). Trying to
> boot using safe mode, I kept seeing the system would reboot right
> after mup.sys loaded. Researching this pointed to power supply as a
> potential problem. I have a Power & Cooling 750W PSU that is less than
> 6 months old, but I went ahead and bought a brand new Rosewill 750W
> PSU that came highly recommended on NewEgg. Tonight, I swapped the
> PSUs out, and I still can't get Windows to boot. I ran the repair
> console, ran CHKDSK /R. It took forever, said that it found some
> errors and fixed them. When I attempted to reboot the system, it went
> to a BSOD, which flashed by so quickly I couldn't read it. Then it
> went into a reboot loop that I could only stop by powering down. What
> do I do now?
>
> My system (all new within the last 6 months):
> AMD Athlon 64 X2 Dual 6000+
> 3 GB RAM, DDR2, Single Channel
> Gigabyte GA-MA69GM-S2H MoBo
> System drive: Maxtor 300 GB IDE (100GB boot partition, 200GB other
> drive)
> Second drive: Seagate Barracuda 500 GB SATA drive
> eVGA GeForce 8500GT PCIExpress video card, 512 MB RAM
> NetGear G311 Gigabit Ethernet card
Pat wrote:
> Ever since XP SP3 came out, my system has been hosed. First, it was
> dead, 6 saying it couldn't find some file in the system directory.
> After fighting with it all night, I reinstalled Windows. Once
> everything was back up, and I reapplied SP3, things started going to
> crap again. This time, the messages suggested I had a hard drive
> issue. Considering I had just rebuilt this system last December and
> replaced everything BUT the system drive, that was a possibility. So,
> I went and bought a brand new Maxtor 300GB IDE drive. Reinstalled
> Windows. Let that burn in for a day, and everything seemed OK, so I
> started reinstalling my apps. Shortly thereafter, the system started
> going haywire again. Locking up with no entry in the system or
> application event log. I had 4 GB of memory in it, so I took out one
> stick, and ran WinDiag on it for something like 26 hous with no errors
> found, then I ran MEMTEST86 on it for 49 hours with no errors found.
> Confident the problem wasn't memory, I started over again. Formatted
> the drive, reinstalled Windows, and let that burn in for 2 days.
> Everything was hunky-dory. Once again, reinstalled the rest of my
> apps, and let Microsoft Update bring everything back up to date.
> Everything was cool for about 3 days, then the system started going
> nuts on me again. Locking up, and giving me BSODs. The last one I
> captured had stop error
> 0x0000007F(0x00000000,0x00000000,0x00000000,0x0000 0000). Trying to
> boot using safe mode, I kept seeing the system would reboot right
> after mup.sys loaded. Researching this pointed to power supply as a
> potential problem. I have a Power & Cooling 750W PSU that is less than
> 6 months old, but I went ahead and bought a brand new Rosewill 750W
> PSU that came highly recommended on NewEgg. Tonight, I swapped the
> PSUs out, and I still can't get Windows to boot. I ran the repair
> console, ran CHKDSK /R. It took forever, said that it found some
> errors and fixed them. When I attempted to reboot the system, it went
> to a BSOD, which flashed by so quickly I couldn't read it. Then it
> went into a reboot loop that I could only stop by powering down. What
> do I do now?
>
> My system (all new within the last 6 months):
> AMD Athlon 64 X2 Dual 6000+
> 3 GB RAM, DDR2, Single Channel
> Gigabyte GA-MA69GM-S2H MoBo
> System drive: Maxtor 300 GB IDE (100GB boot partition, 200GB other
> drive)
> Second drive: Seagate Barracuda 500 GB SATA drive
> eVGA GeForce 8500GT PCIExpress video card, 512 MB RAM
> NetGear G311 Gigabit Ethernet card
I have an AMD Turion 64 X2 in an Acer and no problems. Did you let SP3
finish? It was a slow upgrade.
So, I've rebuilt the system - AGAIN, and per TVeblen's recommendation,
I've not installed SP3. It's better than 24 hours since I finished the
rebuild, and the system has been stable with no errors logged in
either the System or Applications event log. To answer some of the
questions that have been posted here:
1. Jim - WRT to the AMD vs. HP problem: I've read multiple articles on
this topic, and it seems to be tied to systems that have been built
with a sysprep-type of image, that contains drivers for multiple
devices and CPUs. Those systems seem to have the problem with the
Intel power management feature getting turned on. Since my AMD system
isn't built that way, I don't see how that applies to my situation.
2. Larc - You asked if I had the correct SP3 installed. I was actually
originally running a pre-release version of SP3, which my system ran
just fine on for about 4 weeks. Right up until the day the official
release came out, and auto-updated my system and I came home and found
it hosed. The first time I rebuilt it, I had downloaded the full SP3
ISO image and burned it on to CD, and installed it that way when I
rebult my system. I went straight from the base install that include
SP1a to SP3. That died shortly therafter, so the next time I rebuilt
it, I applied SP2, then SP3 from my disk. THAT died shortly
thereafter, so I installed SP2, then let Microsoft Update apply SP3.
THAT died too! So - I've had just about every flavor of SP3 you can
get...
3. Dave W - I think your information is dated. The RTM version of SP3
was officially released on April 21st, and then released via Windows
Update on May 6th - the day my system got hosed the first time. Why
did I reinstall it? I must be a glutton for punishment! :-) Actually,
the first time my system was hosed, happened to be the day that
Comcast was working on the lines in my neighborhood, and I was
optimistic that it was just a case of the update being interrupted. I
have no excuse for the subsequent times. I guess I'm just an optimist.
Or crazy!
4. Claude Hopper - See response #2.
Thanks everyone for weighing in. I'll report back on how this goes,
and if I happen to learn anything about SP3, I'll be sure to share it
back. Cheers! - Pat
XP Pro System is hosed 
Linear Mode
