BSOD Overclocking Problem?

Radwimp

Distinguished
Nov 22, 2010
9
0
18,520
I'm not quite sure if it's the overclocking that's the problem. I'm using the built in overclocker that came with my motherboard. I remember I thought it was an overclocking problem before and I turned it off for a while. I believe I got less BSOD's, but I think it still happened once in a while.I turned it back on, it's back, and I'm not sure what it is anymore.

Motherboard: MSI Z87-G45 Gaming LGA 1150
CPU: Intel Core i5-4670K Haswell Quad-Core 3.4GHz LGA 1150
RAM: G.SKILL Sniper Low Voltage Series 8GB (2 x 4GB)
PSU: SeaSonic M12II 750

Any other info you guys need, let me know.
 
Solution



Lol, no I meant turning off the overclock. I turned it off a couple months ago, but I do think that I still got BSOD although much less frequent. I'll turn it off again guys, and check back soon.
Yep, what PopaTim says, start by disabling the OC Genie function, you can set your ram with XMP if you'd like at this point but you'll want to ensure everything is stable before overclocking. We can get you through manual settings* for overclocks later (once you're sure your system is stable to begin with)

*manual setting are usually quite a bit better for the system than generic "this should work" settings
 
You mean when the computer is off the problem goes away? Lol

Never trust auto over clocking tools,even ones built into the bios. Take the time to learn your CPU and motherboard for a truly stable overclock and you're gaurenteed to learn a bit in the process.
 

Radwimp

Distinguished
Nov 22, 2010
9
0
18,520



Lol, no I meant turning off the overclock. I turned it off a couple months ago, but I do think that I still got BSOD although much less frequent. I'll turn it off again guys, and check back soon.
 
Solution


did you try memtest? do you know the stop code of the BSOD?
 

Radwimp

Distinguished
Nov 22, 2010
9
0
18,520
So after a month of testing without the OC, I think it's crashed about three to four times. The error was 0x00000124. I believe there were other 0x numbers after, but this was the first one. I'll try to take a picture next time.
 


yeah unfortunately that's a pretty broad stop code to get (00000124). I would start with downloading SlimDrivers and getting the drivers up to date (windows update is not enough alone, though that should be up to date too).

Check for corrupt files and viruses with Spybot Search and Destroy/Malwarebytes (both great programs I use side by side).

Also from an elevated command prompt (cmd) (right click 'cmd' and run as administrator) then type in "sfc /scannow" without the quotes.

Download HardDisk Sentinel or CrystalDiskInfo to check the status of the hard drive.

Lastly I would get a CD or USB and load it with Memtest86 to test the RAM.

IF you do all that and still have problems I suspect a hardware issue somewhere..
 


yeah that's true, Slimdrivers is the best 3rd party software thought for finding drivers, ive only had one buddy who got a BSOD after using SlimDrivers and it turned out his ram stick was bad (his laptop worked after we took out one of the RAM sticks). Ive had nothing but good experiences on all 3 of my PC's (including my own laptop). Finding the drivers on your own can be a pain lol
 

Radwimp

Distinguished
Nov 22, 2010
9
0
18,520
Alright, so I did a scan with SlimDrivers and since you guys said it could make it worse, I wanted to check here first before updating anything. http://i.imgur.com/leuaXSR.png These are the drivers available for me to update. Could you guys take a look and see if I should update everything or leave some things out?

I've ran Malwarebytes and Spybot, and cleaned stuff up.

I did sfc /scannow , but when I click on the CBS file it says "Access Denied." However, it says "Windows Resource Protection found corrupt files but was unable to fix some of them" in the cmd window.

I downloaded HardDisk Sentinel and the performance is 100%, but the health is 95% on my SSD.

Memtest came up with no errors.
 
Wow the fact that slim drivers found so many updates is a worrying sign. It makes sense considering the stop code is pretty broad. Personally I think that's definitely the cause of the bsods.

The concern is updating that all at once, with so much updates for each component it's a lot likelier to cause some problems when dealing with so many sensitive files at once (because of various dependencies etc).

I would approach that carefully and update maybe some at a time and allow the system to restart in between every so many updates. You could also just manually find the drivers for each component if it makes you feel safer .. Good luck. Let me know how it turns out.