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

Arc said:

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 said:

xCloudy said:

Arc said:

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: Stop 0x124 - what it means and what to try

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.