I'm finding it hard to keep my cool... Please help me? Dr. Debug errors, failed posts, etc...

[Akagi]

Hey guys, really am coming to the end of my tether with this ****** computer now...

During the process of sorting out my BSOD problem (see my previous thread if you wish) I took out my watercooling setup and cleaned it all out, which dropped temperatures by a whopping 20°C, but still didnt stop the BSOD's.

So I went into my BIOS and put the OC down to 4.6GHz from 4.7GHz, it seemed to have fixed the problem, prime95 was stable after a reasonable amount of time etc etc.

Then I went to turn on my PC again, it powers on and starts to rapidly flick through the Dr.Debug thingamajigs as normal in its usual check procedure until it reaches 60 (DXE Core is started), pauses for a moment and 'resets' (the fan speed dips slightly for a moment and then goes back to normal again) it runs through the same checks, and then hangs on a 70 error (Southbridge DXE initialisation is started) and I have to hard reset. It then hangs on a 70 error every time I try to power it on until I reset the CMOS.

I went into the BIOS and checked everything, and it all appeared fine, applied changes, and it repeated the above.

I then changed the BIOS settings to the saved set which was 100% working before I cleaned my radiator out, and the same problem occurred.

I persisted, and eventually it did boot into windows, however it would pause for a moment on the 60 error, do the brief 'reboot' cycle, pass the 70 test and then boot. However most times it just hangs.

When I shut off the system an 05 error flicks onto the Dr.Debug display just for a brief moment before the system turns off. 05 is OEM initialisation before microcode loading.

What the hell is going on? All I did was unplug and remove the WC kit, clean it out, and put it back in again... All the plugs are in the same places, even the fans are configured the same. I worked in a safe environment with an antistatic band as always, and the system powered on fine and worked fine the first two times after I did the work on it.

Before now (talking before any of this even started) the system would *occasionally* pause on an F2 error (recovery process started), restart fully (system would fully turn off and on again) and then hang on a 70 error. Then after a hard reset from there it would load up fine.

And my damn internet is being crap... And one of my case fans has suddenly developed a really annoying buzzing sound... Urgh...

 

[JonJ678]

Does the system behave itself at stock speeds? I blame your RAM, on the basis that memory is infuriatingly unreliable. Plus I think the memory in my computer has gone bad, since it's running perfectly with one stick but crashes frequently with all six. So I have crappy ram on my mind.

 

[Akagi]

Does the system behave itself at stock speeds? I blame your RAM, on the basis that memory is infuriatingly unreliable. Plus I think the memory in my computer has gone bad, since it's running perfectly with one stick but crashes frequently with all six. So I have crappy ram on my mind.

It has never been run at stock speeds, so I wouldn't know. I will put it on stock speeds in a bit though because of the above issue.

Do you have any base for your theory that it is the RAM other than that RAM is indeed quite prone to failiure when compared with other parts, and your own personal PC issue relating to RAM?

 

[JonJ678]

Probabilities I'm afraid. Failing SSD could do this too. For that matter, all the hardware could be fine but windows has decided to fall over. And indeed a faulty motherboard or CPU could cause your symptoms. (the struggling-to-boot bit isn't window's fault, clearly - but the rest still could be).

On the balance of probabilities, it's time to knock the speeds back to stock and start pulling out sticks of ram. I hope you'll find more motivation for that than I have. Dull troubleshooting

 

[Akagi]

Probabilities I'm afraid. Failing SSD could do this too. For that matter, all the hardware could be fine but windows has decided to fall over. And indeed a faulty motherboard or CPU could cause your symptoms. (the struggling-to-boot bit isn't window's fault, clearly - but the rest still could be).

On the balance of probabilities, it's time to knock the speeds back to stock and start pulling out sticks of ram. I hope you'll find more motivation for that than I have. Dull troubleshooting

Well I just tried with different memory, nothing changed.

 

[JonJ678]

I'm sorry to hear that. Do you have much else in the spare parts box? PSU is relatively easy to swap out, trying to pin down whether the motherboard is playing up is harder.

 

[bignev72]

First things first. Remove the overclock and get everything running at stock.

If that works then slowly build from there, changing one thing at a time.

If running at stock you still have problems then cut down to basics - MLB, CPU, one stick of RAM, one HDD and then see if that works. If that fails try a different stick of RAM. If that works then build from there.

If you are still having problems then it's time to ask a friend to swap some bits out from their machine until you find the problem component.

 

[Akagi]

First things first. Remove the overclock and get everything running at stock.

If that works then slowly build from there, changing one thing at a time.

If running at stock you still have problems then cut down to basics - MLB, CPU, one stick of RAM, one HDD and then see if that works. If that fails try a different stick of RAM. If that works then build from there.

If you are still having problems then it's time to ask a friend to swap some bits out from their machine until you find the problem component.

Take a look at my newest thread and let me know what you think. My suspicions and lots of symptoms etc are summarised in there.

 

[Akagi]

I'm sorry to hear that. Do you have much else in the spare parts box? PSU is relatively easy to swap out, trying to pin down whether the motherboard is playing up is harder.

Take a look at my latest thread