Windows 10: Keep getting BSOD after long periods of Shutdown

I bought a new Asus Tuf 15 gaming laptop FX517ZR-F15.173070 then upgraded the RAM and both SDD. Now I get BSODs at least once a day. They occur after the laptop has been completely powered-off for a while. It gets to the ASUS logo then BSOD's or will BSOD as soon as soon as the windows login screen loads. Its even happened ocassionally while using the laptop, but not consistentl. The most frequent error is get is "Memory_Management" but there are others. I've done clean windows installs, run driver updaters, run the sys file checker, and done memory diagnostics but none of these solve the pr

:)

 

Get kernel_security_check_failure BSOD randomly at shutdown

Sometimes, when I shutdown the system, I get the BSOD screen with error 139, it then shuts down and reboots. There doesn't seem to be any pattern to it, and it doesn't always do it, nor does there seem to be any bad aftereffects. Any suggestions/ideas? I'm a techie, so don't be afraid to use jargon *Wink Last HD/RAM checks were clear of errors. Everything's on the latest rollups. Win 10 works fine from startup and sitting/using. It's only the random BSOD at shutdown, and I do not get any disorderly shutdown BSOD.

 

Help needed for periodic BSODs on MSI laptop

I believe I ran this hard drive scan yesterday and nothing out of the ordinary showed up in the benchmark, no bad sectors.. I will test it again and post the results. I will also post the results of memtest, I left it while I went to work so hopefully it has not booted to Windows while I was out

- - - Updated - - -

I have completed the tests

First pass of memtest86






Second pass








And the results from HDTune which for some reason does not show the health of the OS drive

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.