Re: windows hardware error message



Hi --

I hate to say it, but it sounds to me like you've tried everything under the sun *except* what I'd guess it probably is -- Namely, that the power supply is dying and needs to be replaced. These random errors, coupled with the spontaneous shut-downs "to prevent damage to the computer" (probably meaning to prevent your CPU and Mobo from frying) seem to point in that direction.

Of course, if a faulty power supply *has* led to other components overheating, it may not be *just* the PSU *anymore*... I'd say try replacing the power supply. If problems persist (and especially if you smell something burning), try to replace the mobo and other components.

But be sure you have a fresh new PSU first. I know whereof I speak: I'm a PC tech, and I think I've replaced more power supplies in my clients' systems that any other component. I can also offer the following sad story from my youth as a cautionary tale: In my early PC days, when the idea of opening one up, let alone building one was alien to me, I had a Compaq Presario Windows 95 system that developed a problem whereby the PSU fan kept stalling. I was in the middle of a semester at college at the time, and felt I could not afford taking it in to repairs and be without a PC. So I ignored the problem, and would just give the PSU a slap, which would start the fan up again, albeit for a short time, and whirring unnaturally loudly.

Finally, the semester ended and I took the system in to replace the PSU, and for good measure, I had them install a new HDD and more RAM too. When I got the system back, within a few minutes, the system locked up.
Repeated reboots led to the same result, full system lockup within minutes, and the nasty smell of burnt rubber emanating from the PC.

I returned it to the shop and was informed that the mobo and CPU (as well as the brand new RAM I had installed) were toast, and I basically had to have most of the system replaced at no small expense. The mobo et al. had apparently been deteriorating all the time I was using it with the failing PSU, and the system finally snuffed it on return from the first trip to repairs. (I guess it wanted to come home to die.)

Moral: When the computer starts "behaving badly", and the symptoms are too random to readily pinpoint, suspect the power supply first, before any potential problem with it leads to the premature death of any other components.

Hope this helps... Please keep us posted on your progress...

--
Dave


Maxis wrote:
Hello, my computer started behaving badly, documents seemed to be corrupted,
I'd have to restart, then I started getting BSODs; but with different
error messsages, sometime it claimed it was corrupt drivers, other
times Boot Sector problems. Then nothing, not even beeps.
Things I've tried: new hard drive, reinstall of windows xp, install of
windows 2k, new graphics cards, single graphics card, turning off
shadowing in bios, turning on and off ECC in bios, updating bios,
swearing and hitting with hammer, taking out all cards except 1 very
basic graphics card, changing the battery. And always the same result, I can usually install windows, but either
after the first re-boot or during the installation windows says it is
shutting down to prevent damage to the computer, and I get a bsod,
with, usually, a master boot record error.

the mobo is a tyan tiger mpx, the processors are amd athlon mp's, and
there are 3, 1 gig modules in the memory bank's. It's worked ok (well
as well as any windows box works) for about 2 years)

Any ideas anyone? and thanks very much for even getting this far...

.



Relevant Pages

  • Re: Starting Windows 2000 hangs on new install.
    ... but at the moment I've got all the fancy bits on the mobo turned off ... the Windows 2000 install CD when the Duron 650 is in instead of the XP2400. ...
    (microsoft.public.win2000.setup)
  • Re: Motherboard died - can I transfer my OEM MCE license?
    ... The hashes for activation are done on client (i.e the machine that windows is installed on), not by something on the server. ... Your MAC addresses won't be exactly the same between two computers, your Hard drive serial numbers won't be the same, other identifiers won't be exactly the same. ... Then install both PCs with the same OS and key and activated the OS. ... So if your MOBO failed then the Product Key you have can not be used again unless it is used for a MOBO replacement with the same make/model MOBO. ...
    (microsoft.public.windows.mediacenter)
  • Re: Inaccessible_boot_device with new mobo - no IDE driver?
    ... Replace the Motherboard on a Computer That Is Running Windows ... > Win2k CD and then install the nforce2 drivers. ... > load Win2k, but then gives BSOD with INACCESSIBLE_BOOT_DEVICE error. ... > mobo, restore the old mobo, boot Win2k, try to install the nforce2 IDE ...
    (microsoft.public.win2000.setup)
  • Problems Remain After Reinstall
    ... old PSU and found that it would hang at the Winodws XP screen with the ... (not in Windows). ... so that I could get online and install XP Service Pack 2 so that I ... the blue bar scrolling across and I had to restart with the last good ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Problems Remain After Reinstall
    ... old PSU and found that it would hang at the Winodws XP screen with the ... got an EBAB0003 error so I formatted the C drive, installed Windows ... so that I could get online and install XP Service Pack 2 so that I ... the blue bar scrolling across and I had to restart with the last good ...
    (microsoft.public.windowsxp.help_and_support)