Weird build problem (lock ups, bsod's etc)

Baker · 27 Jan 2007 at 03:39

So i've had a build for about a year now consisting of:

3700+ AMD CPU
X850XT ATI GPU
2x512mb Geil Value RAM
A8N-E ultra ASUS mobo
36gb raptor
some storage drives
etc

And last week i got my first BSOD on it - MACHINE_CHECK_EXCEPTION.

What the hell, i thought. But after a reboot it would work for 5 minutes, then just lock up (saitek lights go off, mouse stops moving, music starts stuttering, everything locks) and i have to reboot a few times then it works no problem.
I saw this as a problem and planned to format friday night. I go to turn my PC on and it doesn't actually boot up at all. After a good 20 tries it gets to XP load screen, then BSOD's. Then doesn't turn on ever (all fans power up etc, just no monitor signal, no keyboard light, no mouse power etc). I googled the BSOD. Took out my CD/DVD drives, storage drives, everything not needed. Wouldn't work.
Reset CMOS - no luck.
Replaced PSU - no luck.
Eventually booted up once, and it gave me a missing/corrupt system32/hal.dll file error (coincidently happened to a mate of mine at almost the same time - we don't even have near identical setups :/).
Can't get it to even get to BIOS anymore, it's really screwed.
I'm guessing it's either CPU, MOBO or HDD. But i can't be sure which.
What option should i take from here?
I can save and get a Core 2 Duo setup (6300 etc), get an AM2 setup a lot cheaper (no saving, straight buy) or try and replace some of my current parts that may be causing the error.

AssaTM · 27 Jan 2007 at 04:17

I'm not expert but the hal.dll is related to the bootfile so when your pc is up and running again you will need to run the Windows XP Repair Utility to fix the bootlog, but as for the specific problem I cant help you there, sorry ;(

Try running the PC without the HDD also, and see if it posts etc, but it does sound like an HDD problem for the bootlog/bootfile to just corrupt like that

hp7909 · 27 Jan 2007 at 05:02

Baker said:
{snip}Replaced PSU - no luck{snip}

What was the reason why you decided to replace the PSU?

Have you run Memtest (here) to rule out the RAM?

Baker · 27 Jan 2007 at 14:28

I replaced the PSU because when turning on the machine, all the insides powered up (fans etc) but no power went to my keyboard, and no signal went to my monitor and so on - thought it may be a power problem.

I'd try and use memtest etc, but it doesn't even get to BIOS. It just powers up the fans and sits there. I will try it without the hard drive/s.

I thought it'd be a hard drive problem, but about an hour into trying to fix the error, a friend rang me up and said his pc is knackered with the exact same error - can't just be coincidence can it?

hp7909 · 27 Jan 2007 at 14:41

Baker said:
I replaced the PSU because when turning on the machine, all the insides powered up (fans etc) but no power went to my keyboard, and no signal went to my monitor and so on - thought it may be a power problem{snip}

If same thing is happening with new PSU, then IMO the problem is the mobo.

If you unplug all essentially even maybe memory, but except GFX & CPU then you should at least get into BIOS or get an error beep/on-screen, not nothing!

Baker · 27 Jan 2007 at 14:52

hp7909 said:
If same thing is happening with new PSU, then IMO the problem is the mobo.

If you unplug all essentially even maybe memory, but except GFX & CPU then you should at least get into BIOS or get an error beep/on-screen, not nothing!

Powered up with just the 24pin mobo psu connector in, the and graphics power lead and nothing. No power to the keyboard (no lights) and no signal on the monitor. No beeps, nothing. Does this mean it's the mobo or the CPU?