Question Daily BSOD shortly after inactivity. What is my issue, hardware or software?

Silentfox18

Distinguished
Jul 20, 2015
8
0
18,510
I have tried new windows install, is it my ram? I've done memtest before and didn't find any faults..

Here are the BSOD I experience
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY ntoskrnl.exe (nt+0x3F71D0)

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY ntkrnlmp.exe (nt!memset+0x79BB2)

KERNEL_SECURITY_CHECK_FAILURE ntoskrnl.exe (nt+0x3F71D0)

DRIVER_IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe (nt+0x3F6F20)

IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe (nt+0x3F6F20)
Sys info https://drive.google.com/file/d/19fbfYAq8_Fbsnn65fQJPSnb4S7OfXbeX/view?usp=sharing

Here is SysNative collection if this will help

https://drive.google.com/file/d/1hfpieVbgLrFvMVk6zhJUOSY2--yew-b6/view?usp=sharing
 
I have tried new windows install, is it my ram? I've done memtest before and didn't find any faults..

Here are the BSOD I experience
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY ntoskrnl.exe (nt+0x3F71D0)

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY ntkrnlmp.exe (nt!memset+0x79BB2)

KERNEL_SECURITY_CHECK_FAILURE ntoskrnl.exe (nt+0x3F71D0)

DRIVER_IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe (nt+0x3F6F20)

IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe (nt+0x3F6F20)
Sys info https://drive.google.com/file/d/19fbfYAq8_Fbsnn65fQJPSnb4S7OfXbeX/view?usp=sharing

Here is SysNative collection if this will help

https://drive.google.com/file/d/1hfpieVbgLrFvMVk6zhJUOSY2--yew-b6/view?usp=sharing
I was also having that problem, blue screens related to ntoskrnl.exe file (and also the ram memories did not show errors in the memtest) and it seems to be something of windows 10 itself, so far it has been solved by disabling windows10 fast startup.
https://help.uaudio.com/hc/en-us/articles/213195423-How-To-Disable-Fast-Startup-in-Windows-10
 
If turning off fast startup fixes it, it just means the problem is really old drivers that don't like win 10 power modes.

I will ask a friend to convert dump files.
I was actually experiencing this problem even with updated drivers and latest bios, and with the latest windows update, it was a headache and in the end it was the only thing I needed to try, luckily it has worked so far.