PC Restarts on Boot

[AdamPC]

My PC is always kept in sleep mode. Whenever I leave it for more than a couple of hours, when I come back and wake the PC up, it logins to windows and then the blue screen comes up showing a percentage of windows gathering information. I'm then prompted to restart and I restart (my computer then works).

 

This issue occurs more than 2 times each day and it is very inconvenient. I have looked at what drivers I have and they are all up to date and not corrupted. I have done other things like cleaning the disk and managing the OS.

 

I have also used WhoCrashed to see if there is obvious issue and I have not found it.

 

Please, does anyone know what I should do? I have gotten so desperate that I've ordered a m.2 SSD to install a fresh copy of windows.

 

My specs are: Ryzen 5, gtx 1050ti, 8 gb ram, b350 motherboard.

 

 

WHO CRASHED - shown below

 

On Mon 2019-01-28 8:14:08 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012819-36687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1AA0A0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8018ADBBD67, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 

[Bazrat]

After some googling it says that the ntoskrnl.exe BSOD " is usually related to memory, possibly caused by a faulty driver". Try using Memtest/Windows Memory Diagnostic tool and see if that finds any issues. You could try re-seating your RAM and see if that fixes anything, if you know how to do that.

[AdamPC]

2 minutes ago, Bazrat said:

After some googling it says that the ntoskrnl.exe BSOD " is usually related to memory, possibly caused by a faulty driver". Try using Memtest/Windows Memory Diagnostic tool and see if that finds any issues. You could try re-seating your RAM and see if that fixes anything, if you know how to do that.

2

I have already done the windows memory diagnostic tool procedure and no problems were detected. And as for re-seating my memory, it's single channel, so I doubt that anything would change with a re-seating.

[Bazrat]

Maybe try moving your RAM stick into another slot? Or updating the motherboard BIOS?

[Bitter]

Run Memtest86+ for 24hrs and if that passes then run something that heavily stresses the system memory like Prime95 on blend for 24hrs. This will help to rule out an issue with RAM. Is it suspending to RAM or suspending to disk? Is the system overclocked in any way?