BSOD randomly after OCing, error 0x00000124

[Plazzed]

I've finally got around to overclocking my i5 2500k automatically within the BIOS, but ever since, it's been giving me BSODs at random intervals. There is no set trigger for it that I can tell (it's happened during gaming and during random internet browsing). As of right now, I've set everything back to stock levels. I have an ASUS MIVE-Z, and I was using the auto-OC settings within the BIOS (CPU to 4.6GHz, and RAM set on XMP profile where it runs at 2133MHz).

Just to note, I had put my RAM at those levels with NO problems before, so I suspect it has something to do with the CPU. I've also had NO problems with my CPU at it's current level (3.7GHz) EVER, so that just helps solidify that the issue is caused by the bump from 3.7 to 4.6.

I did a little looking around on the web, and I saw a few posts that seem to say it might be a CPU voltage related issue. Also, this isn't the first BSOD I've had, and I compared the output of all the dumps I had via BlueScreenView. All of the related files for each crashdump are identical, so it's definitely the same problem over and over.

This system is about 4-5~ months old, and the OS installation is not even a day old, I had just done a full reloading of the OS last night.

Just a note, the attached tests/reads were with my CPU/RAM at stock/auto levels, NOT the overclocked levels at which my system was BSODing.

ASUS Maximus IV Extreme-Z
i5 2500k
8GB DDR3
GTX 580
Corsair HX1000
Windows 7 Home Premium 64bit

If I left any information out, please tell me. First time posting here.

 

[JMH]

Hello Plazzed,

* Is your "new" computer under Warranty?

* A stop error of 0x124 is a general hardware error.

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress

Some generic advice.

If you are overclocking STOP. return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Plazzed]

Hello Plazzed,

* Is your "new" computer under Warranty?

* A stop error of 0x124 is a general hardware error.

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress

Some generic advice.

If you are overclocking STOP. return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

All of my parts are under warranty (probably not refund, but definitely replace). I have already returned my CPU back to it's stock 3.7GHz (turbo boost was already running fine). I've kept the RAM at XMP profile settings, because I've had it at that before with no errors (and I still haven't had any), so it's almost DEFINITELY related to the CPU overclock.

I was also talking to some people over on Overclockers: The Performance Computing Community for Overclocking Hardware and How to Overclock Information, and they seem to think it's a problem with too little vcore on the CPU when overclocked. That particular thread is here, so you can look over what they said if you're curious. They suggested I turn up the vcore, but knowing not so much about overclocking, I decided against it until I learn more about how to and the drawbacks of manually overclocking.

I'll take a look over that link, too.

 

[JMH]

As a matter of interest only...
What Anti Virus Program have you currently?
Did any come pre installed with your system? If so how was it uninstalled?

 

[Plazzed]

As a matter of interest only...
What Anti Virus Program have you currently?
Did any come pre installed with your system? If so how was it uninstalled?

Microsoft Security Essentials + Malwarebytes Anti-Malware. This wasn't a prebuilt computer, by the way. I ordered the parts from Newegg and constructed them myself.

 

[JMH]

Good choices too.
From a BSOD perspective MSE is the recommended AV.

 

[Plazzed]

Good choices too.
From a BSOD perspective MSE is the recommended AV.

Thanks, I've never heard anything bad about them myself.

As far as the possible factors of the BSOD go, as I said before, people over at Overclockers seem to say it was because I had too little Vcore, which caused instability. Do you agree/disagree with them? Or since 0x124 is a "general hardware error", the provided info from the .dmp file is too vague to pinpoint?

 

[JMH]

* 0x124 is a "general hardware error"

Did you follow ALL of the instructions in my Post 2?

If you are overclocking STOP.
Return to the default settings at least for now.


* Suggest you address your overclocking questions to the link below.

Overclocking and Case Mods - Windows 7 Forums

 

[zigzag3143]

Since we never got any DMP flies from you we are basing our response on the thread title. The only way we can be sure is to look through them ourselves.

Generally speaking, one of the first things you do when trying to diagnose a 124 is to not overclock anything, then see if it crashes

 

[Plazzed]

* 0x124 is a "general hardware error"
Did you follow ALL of the instructions in my Post 2?
If you are overclocking STOP. return to the default settings at least for now.


* Suggest you address your overclocking questions to the link below.

Overclocking and Case Mods - Windows 7 Forums

I have already reset the OC on my CPU back to what it was before. My RAM is still at XMP profile, and I personally don't see a reason to lower it, because I know for a fact that it's not part of the problem, as I've had it set to this before with no issues. I'll check over that link, too.

Since we never got any DMP flies from you we are basing our response on the thread title. The only way we can be sure is to look through them ourselves.

Generally speaking, one of the first things you do when trying to diagnose a 124 is to not overclock anything, then see if it crashes

Oh, I'm sorry. I thought I put .dmp files in my original .zip file in the first post. Forgive me for that blunder.

 

[NotYourHero]

From personal experience, your ram/cpu is not stable. If you OC'd via FSB, you will probably need to increase ram voltage and loosen timings. I don't overclock my cpu anymore as its a pain in the ass, but from personal experience, when I got this bsod, that was the issue.