Ntoskrnl.exe (nt +0x4ADB3C) WINDOWS CRASH/RESTART

[xCloudy]

Basically I am not getting a bluescreen, instead it goes black and then restarts.
This has been happening the past week and I even tried restoring my computer to factory settings and today, have gotten it 3-4 times.

The exact error I'm getting:

crash dump file: C:\Windows\Minidump\110913-31871-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x4ADB3C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8006129038, 0x0, 0x0)
Error: [FONT=Segoe UI, Arial]WHEA_UNCORRECTABLE_ERROR[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe

 

[xCloudy]

Still need help with this issue. :x

 

[Arc]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also fill up your system specs.
See your system specs and fill it up here.

 

[xCloudy]

Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also fill up your system specs.
See your system specs and fill it up here.

I have now done both.

 

[Arc]

Use the "GRAB ALL" button of the SF Diag tool?

 

[xCloudy]

Use the "GRAB ALL" button of the SF Diag tool?

I have attached it.

 

[xCloudy]

Any help is appreciated.

 

[Arc]

Follow it: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

 

[xCloudy]

Follow it: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

Have you checked the zip file as what the issue might be?

 

[Arc]

The issue is stop 0x124 with 0 as first argument (=machine check exception). That means, it is hardware failure reported by the CPU (not necessarily a CPU error). In that situation, there is no way to pin-point to the exact issue.

Sorry to say, but you have to work more to resolve it, only if you are not extremely lucky.

 

[xCloudy]

The issue is stop 0x124 with 0 as first argument (=machine check exception). That means, it is hardware failure reported by the CPU (not necessarily a CPU error). In that situation, there is no way to pin-point to the exact issue.

Sorry to say, but you have to work more to resolve it, only if you are not extremely lucky.

Hardware failure. What exactly? Like the gpu? ram? etc? Specifics

 

[Arc]

The issue is stop 0x124 with 0 as first argument (=machine check exception). That means, it is hardware failure reported by the CPU (not necessarily a CPU error). In that situation, there is no way to pin-point to the exact issue.

Sorry to say, but you have to work more to resolve it, only if you are not extremely lucky.

Hardware failure. What exactly? Like the gpu? ram? etc? Specifics

No specification is possible for a Machine check exception.

A Machine Check Exception (MCE) is a type of computer hardware error that occurs when a computer's [central processing unit detects a hardware problem.

Normal causes for MCE errors include overheating and/or incorrect hardware installation. Specific manually-induced causes include:

overclocking (which normally increases heat-output)
poorly-fitted heatsink/computer fans (the same problem can happen with excessive dust in the CPU fan)
an overloaded internal or external power-supply (fixable by upgrading)

Computer software can also cause MCE errors (normally by corrupting data which programs read or write). For example, software performing read or write operations from or to non-existent memory regions can lead to confusion for the processor and/or the system bus.[citation needed] Accessing memory marked off-limits by UEFI may cause MCE errors.

Source: Machine-check exception - Wikipedia, the free encyclopedia

In our article, we have an elaborated list of possible causes and tests. Look at this part ...

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.

Source: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

If there is a way to a specific suggestion, it would have been there.

 

[xCloudy]

The issue is stop 0x124 with 0 as first argument (=machine check exception). That means, it is hardware failure reported by the CPU (not necessarily a CPU error). In that situation, there is no way to pin-point to the exact issue.

Sorry to say, but you have to work more to resolve it, only if you are not extremely lucky.

Hardware failure. What exactly? Like the gpu? ram? etc? Specifics

No specification is possible for a Machine check exception.

Normal causes for MCE errors include overheating and/or incorrect hardware installation. Specific manually-induced causes include:

overclocking (which normally increases heat-output)
poorly-fitted heatsink/computer fans (the same problem can happen with excessive dust in the CPU fan)
an overloaded internal or external power-supply (fixable by upgrading)

Computer software can also cause MCE errors (normally by corrupting data which programs read or write). For example, software performing read or write operations from or to non-existent memory regions can lead to confusion for the processor and/or the system bus.[citation needed] Accessing memory marked off-limits by UEFI may cause MCE errors.

Source: Machine-check exception - Wikipedia, the free encyclopedia

In our article, we have an elaborated list of possible causes and tests. Look at this part ...

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.

Source: http://www.sevenforums.com/crash-lo...top-0x124-what-means-what-try.html#post354696

If there is a way to a specific suggestion, it would have been there.

Do you think restoring my computer back to factory settings had something to do with it? Been happening ever since but surprisingly has not happened to me for the past 10 hours.