Windows 10: Windows 10 suddenly reboot event viewer : bugcheck event 1001

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 14/2/2020 3:54:07 PM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-2KU1BMF
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 0xffffce8fcc3e2460, 0xfffff80141def814, 0xffffffffc0000001, 0x0000000000000003. A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a13ba184-41d2-493a-977f-f613acb9bc61.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-02-14T07:54:07.901291800Z" />
<EventRecordID>17223</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DESKTOP-2KU1BMF</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000116 0xffffce8fcc3e2460, 0xfffff80141def814, 0xffffffffc0000001, 0x0000000000000003</Data>
<Data Name="param2">C:\WINDOWS\MEMORY.DMP</Data>
<Data Name="param3">a13ba184-41d2-493a-977f-f613acb9bc61</Data>
</EventData>

</Event>

:)

 

EVENT 1001 BugCheck and Critical EVENT 41 Kernel-Power

I've had my PC since January (completely new + running Windows 10) but ever since February it has been restarting without any warning for seemingly no reason. It's happened around 10 times since and seems to be on some kind of count down, restarting after
a certain amount of hours use. Just yesterday it rebooted 10 minutes after I had started the PC up, and half an hour from me writing this it rebooted again. I finally dived into the Event Viewer and found that there has been a consistent chain of Critical
errors, namely Event 41 Kernel Power, with Event 1001 BugCheck sitting right underneath it every time. I've been scouring the net to try and figure out how to fix the issue, but I'm not really sure what's going on and I am fairly new to all the deep-seated
technological terms. Any help would be greatly appreciated (and relayed in simple terms) because I'm honestly clueless.

EVENT 1001 BugCheck:

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffe4853ab1f8f8, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\032618-26531-01.dmp. Report Id: 5f9ad654-be7a-4f6e-82bb-5d947f7e661c.

 

EVENT 1001 - BugCheck - The computer has rebooted from a bugcheck.

Lately my computer has been restarting out of nowhere at random times, doesn't show a BSOD it just black screens and restarts.

This is the error that shows on eventviewer:

Event 1001, BugCheck

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffab0182114038, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\010618-40156-01.dmp. Report Id: 3e609480-61a7-4589-a40c-3f315d745e16.

and the critical error is:

Event 41, Kernel-Power

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

The two instances I remember it crashing was when playing a game and when downloading a file.

Haven't made any changes into hardware/software lately.

Shared items 1-6-2018

 

Windows 10 bugcheck every few hours with event id 1001

Unfortunately, I have now had a further two bugcheck reboots with event id 1001.

The event text is:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009c (0x0000000000000000, 0xffffd0006a879760, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 092615-4281-01.

I have saved the MEMORY.DMP file on onedrive here: http://1drv.ms/1KBbXmO

On both occasions I was running VMWare Workstation 12.

Please can someone with the necessary tools inspect the MEMORY.DMP to find out what is going on?

Thanks,

Paul