BSOD help....yes that old chesnut

david_129

david_129

david_129

Associate
Joined
17 Jan 2009
Posts
113
Hi Guys, wondering if anyone is any good at analysing these things,

I have turned off my overclock, wasn't doing anything but downloading at the time. System was built around 1 month ago.

This is happening intermittently (last crash 6 days ago)

BSOD.jpg


REALLY appreciate any help on this
 
I would reset the CMOS and then set memory up manually in the BIOS (save and exit) and then run memtest overnight to try and rule in/out the memory as the problem.

EDIT: Make sure you d/l the latest version (it's SB compatible)
 
Last edited:
I had the same problem on my system (pre build from OCUK). I called their helpline and was advised to increase the CPU voltage. I would get BSODs regularly with code 124, 95% of the time when the system was idle or doing minor things such as downloading or watching videos on youtube. Very rarely would it crash under load.

I have the i5-2500k processor, now running stable at 4.5ghz with 1.355v. The default OCUK setting of 1.34v gave me several BSODs a day, 1.350 would BSOD a couple of times a week. Now rock solid at 1.355v.

Before contacting OCUK I tried resetting the BIOS and ran at stock with default voltage - still got BSODs with code 124.
 
david_129 said:
the memory is all defaulted. Shall i try memtest anyway like this?
Click to expand...

If you were still getting the BSOD with the CPU at stock - i would, personally, reset the CMOS, and then set the memory up manually at its recommended spec and then run the latest memtest overnight.
 
david_129 said:
Ok plec, i just didn't want to lose the OC from OCUK which is in the profile of the bios thats all..
Click to expand...

You should have a profile saved in the BIOS called 'OcUK' or similar - double check (a CMOS reset wont lose the profile - it can be loaded up at a later date.)

Could you also clarify that you were getting the BSOD at stock?
 
david_129 said:
Well the BSOD happened when the processor wasn't doing anything so was automatically downlocked to 1.6ghz
Click to expand...

Sorry, I still need to establish if the BIOS was clocked, regardless of whether the computer was idle.

If the chip was clocked (even if it was idle/speedstep at the time) the BSOD could still be as a result of an unstable clock. Neary all of my stability issues, when setting up a clock, have showed themselves when idle or browsing etc...

Unfortunately, if it was clocked when it last BSOD then you can't rule out the clock as the problem.

If it was clocked set the sytem to stock and use and abuse for a few days and see if it replicates the problem - if it wasn't do the above suggestion in post #2.

You could still run memtest as it's always good to rule out.
 
Last edited:
Thank you for your help.

Well then yes at the time it was running OCUK profile.

I will turn this off then and try it for a few days, i can run memtest86 tonight and report back in the morning.

Really appreciate the help
 
No problem - an intermittent unstable clock can be hard to identify. The only sure way to rule it out is to take it out of the equation altogether.

If it does transpire that the clock has become unstable after all your testing try a post in the ‘Bundles and Systems Support Forum’ – link.

Outline the basics of your problem and direct them to this thread. They’re usually very quick to respond and will be better equipped to advise you on your next step – plus you have your warranty to think about so any settings tweaks above their pre-set instructions will need to be verified by thmeselves first.

Best of luck – post back when you have some news.
 
Really helpful thank you.

I'll try it for a week or so then no OC then speak to systems as i would imagine i'd have to get it RMA'd or something if i can't run the clock i purchased.
 
david_129 said:
OCUK just told me to increase to 1.375 cpu pll 1.86 and dram to 1.58....
Click to expand...

If the problem is an unstable clock -and there's every possibilty that it is - the settings OcUK have given should hopeully stop the BSODs.

However, if they don't i would contact them again - and in the interim i would follow my advice in post # 2 and rule out the memory as a possible cause (as it's always good to rule out the memory with random BSODs)..

Hopefully, the new settings will resolve your issues and you can ignore memory diagnostics - good luck.
 
You must log in or register to reply here.
Back
Top Bottom