Random frequent BSOD 0x124 / 0x00000124 ntoskrnl.exe?

Hello sevenforums.
My PC has always given me trouble in the past by randomly restarting and getting BSODed. I used to "live with it" but over last 2-3 months it has gotten out of hand. My PC restarts at least 2-3 times per day. I always get 0x124 bug check code and so tested the processor with prime95 (for 2-3 hours) and ram with memtest86+(3 passes) but got clean results. I've attached the latest 10 minidumps. I'm at my wits end and REALLY dont want to reinstall windows! :O
Thanks in advance.
Edit: It does not even show a bsod but directly reboots.

Minidumps attached

Someone..? Anyone..?

Code:

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 86ca6a0c
Section       @ 86ca6b94
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_SRC_ERR_*_NOTIMEOUT_ERR (Proc 1 Bank 0)
  Status      : 0xb20000001040080f

There's seems to be an error with either your processor bus, or the processor itself, as a result it is best to stress test the CPU for confirmation:

• Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

x BlueRobot said:

Code:

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ 86ca6a0c
Section       @ 86ca6b94
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_SRC_ERR_*_NOTIMEOUT_ERR (Proc 1 Bank 0)
  Status      : 0xb20000001040080f

There's seems to be an error with either your processor bus, or the processor itself, as a result it is best to stress test the CPU for confirmation:

• Hardware - Stress Test With Prime95

Enable "Round off checking" before the test (see first post below tutorial).

I had tested it earlier for 3 hours and i tested it again now for 4 hours. Both times there were 0 warnings and 0 errors. Can my problem be due to some driver? I have updated them all last week still I feel some driver might be causing it.

Here is a list of the most common cause of the 0x124 bugcheck:

Code:

Usual causes:  Hardware, Incompatibility, May be driver corruption

In rare cases, it can be due to driver corruption, I would update all your drivers and then see if the system crashes with th same bugcheck or even a bugcheck.

Checked my drivers. They were already up to date. So basically there's no choice but to buy a new processor right?

jingad said:

I had tested it earlier for 3 hours and i tested it again now for 4 hours. Both times there were 0 warnings and 0 errors. Can my problem be due to some driver? I have updated them all last week still I feel some driver might be causing it.

Trust me, you can run Prime 95 for 8-12hrs and not be stable. Also, when you ran it, did you go to the edit menu and check on the: SUM(INPUTS) error checking, and Round Off Checking options?

Also make sure you run the BLEND test. Maybe even try running a custom test set at:
MaxFFT size to: 1792
Memory to use (in MB): Half of your total ram or greater. If you have 4096MB, set it at least to 2048MB
Time to run each FFT Size to: 5 minutes

Code:

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 86ca68fc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

The first parameter or argument has the value of 0x0, which is a Machine Check Exception, which means the CPU has detected a hardware problem and the address points to a processor error because the CPU has found one, so it could be a different form of hardware which is causing the issue. Thanks to Archie for pointing this out to me.

• Stop 0x124 - what it means and what to try

If all the hardware checks and swaps seem to be fine, then it could be due to a bad motherboard.