You wouldn't get much from the debugger for this error. But, FYI, here's a post that I wrote about how to use it: Diagnosing Bsod's (originally posted 02Oct08) - Vox

The STOP 0x124 error is a hardware error that was generated by something other than Windows (most likely your CPU) using the Windows Hardware Error Architecture (WHEA) reporting methods. The error is (IMO and IME) nearly indecipherable for most people (me included).

But, there are several different things that can cause this:
- most people will agree that malfunctioning hardware can cause this.
- a lot of those people will agree that incompatible hardware can cause this
- and less will agree that bad drivers can cause this (I'm one of these).

So first, please give us a brief history of your system and this problem. It's unusual if it happened on a system that you've been using for a while - and more likely if you've just been messing around inside of the case. Is this a Desktop or a laptop?

Once that's done, we may be able to deduce the area that this comes from. Also, you can zip up the minidump file(s) located in the C:\Windows\Minidump folder and upload them with your next post (if it doesn't work, try copying them to your desktop).

While an analysis of the dump file likely won't tell us much, we can see what drivers may need to be updated.

Ahhh - an overclocker!

Troubleshooting overclocked systems is not very easy. That's because the system is being stressed beyond it's normal use - and we can't rely on things being stable. Additionally, over time overclocking may degrade components - causing failures.

So, I always recommend resetting the system to default before starting the troubleshooting (learned this when I was overclocking - back in the day

Then, if the problem goes away - it was caused by the overclock. If it doesn't, then it'll be more amenable to traditional troubleshooting steps (while it's not overclocked).