New PC randomly blue screening, usually when idle

Bleeping Computer - https://www.bleepingcomputer.com/forums/t/708364/new-pc-randomly-blue-screening-usually-when-idle/

I processed the 5 kernel memory dumps in your Sysnative zip file and believe the BSODs to be caused by unknown hardware failure.

The bugchecks -

BugCheck 1E, {ffffffffc0000005, fffff805537c4795, 0, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt!KiIsrLinkage+2f4 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {41792, ffffa98000042ec0, 200000000000, 0}
Probably caused by : memory_corruption ( ONE_BIT )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 3B, {c0000005, ffffcbd5be074e4c, ffff918441813fe0, 0}
Probably caused by : win32kfull.sys ( win32kfull!NtUserBuildHwndList+58c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {61941, 296936564b0, d, ffffca8940d40b00}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1A, {61941, 6753cadc, d, fffffe0f444d8b00}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

0x1a = severe memory management error
0x1e (0xc0000005,,,) = kernel threw an exception; the excp = 0xc5 = memory access violation
0x3b (0xc0000005,,,) = system service threw an exception; excp = 0xc5 = memory access violation

You can see in the above code boxes the various "Probably caused by" notations -
- ntkrnlmp.exe = the Windows kernel & Executive -- it cannot be a cause. It is likely listed as a default because the real cause could not be determined
- memory_corruption - self explanatory
- Unknown_Image - this should be a driver name. Seeing Unknown Image tells me that memory corruption occurred

Test RAM one stick at a time and alternate the slots - https://www.sysnative.com/forums/threads/test-ram-with-passmark-memtest86.24300/

I see that you have 3 internal hard drives. Test each with SeaTools for DOS, LONG test - https://www.sysnative.com/forums/threads/hard-drive-hdd-diagnostics-sea-tools-for-dos-ssd-test.4072/

If any of the drives are SSDs, go to the drive manufacturer's support site and check for a firmware upgrade. *** VERY IMPORTANT ***

Also, please follow the suggestions of others that have posted in this thread.

hamluis for example is an absolute master of Windows Internals and knows a great deal more about the inner workings of Windows than I do. So, please follow his and the other's instructions. THANK YOU.

Are these the very first BSODs that you have encountered on this new 2 month old new system?

Do you recall installing any new apps/programs prior to the start of the BSODs?

Any hardware changes since building and finishing the system two months ago?

These types of BSODs are tough to solve because they are more than likely [unknown] hardware related. Unfortunately, dump files and Windbg (the kernel debugger) were invented to assist app and driver developers (software developers) debug their source code; not to aid in troubleshooting hardware failure. The dumps are incapable of telling us the exact piece of hardware that has failed. The closest it will bring us is what it has reported to us here - e.g., the "memory  management" error; the clue that Unknown Modules are caused by memory corruption (that just comes with my 12+ years of experience processing over 1 million BSOD dumps since 2007); and other things that I have picked up over the last 12+ years.

So, sorry that I could not be more helpful to you here.

Perhaps more dumps will yield clues.

Before the RAM and SeaTools diagnostic tests, run Driver Verifier - https://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/

It must run for at least 24 ours in the background. You can continue to use your system, but may notice some system slowness as D/V is very resource intensive.

If a BSOD does occur, go to \windows\minidumps and copy out the latest dump (the filenames contain the date) to Documents or Desktop; then zip the dump file and attach it to your next post. Windows will not allow you to zip up the dump file in place (\windows\minidumps) due to permission settings.

That should be enough to get you started/.

Good luck to you.

Regards. . .

jcgriff2

On a side note which really  has nothing to do with your BSOD epidemic, I noticed in Speccy that you have your screen saver disabled -

Screen saver:  Disabled

I have mine turned on as I usually fall asleep at night with a video playing.