Re: XP Pro System is hosed
- From: Larc <larc@xxxxxxxxxxxxxxxx>
- Date: Thu, 29 May 2008 12:10:36 -0400
On Wed, 28 May 2008 21:56:31 -0700 (PDT), Pat <pat_whitted@xxxxxxxxxxx> 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,0x00000000). 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.
Good luck!
Larc
.
- References:
- XP Pro System is hosed
- From: Pat
- XP Pro System is hosed
- Prev by Date: Re: adding USB connectors
- Next by Date: Re: OT besides all the spam, Google Groups is screwing up the USENET archive
- Previous by thread: Re: XP Pro System is hosed
- Next by thread: Re: XP Pro System is hosed
- Index(es):
Relevant Pages
|
