Do you have any old HDDs lying around that you could install Windows on so that we can rule out motherboard, PSU, etc...?
Bugchecks on the last 3 dumps -
`
Rich (BB code):
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\072519-9562-01.dmp]
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Debug session time: Thu Jul 25 15:44:36.983 2019 (UTC - 4:00)
System Uptime: 0 days 0:08:02.673
Probably caused by : ntkrnlmp.exe ( nt!ExpGetProcessInformation+f08 )
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: firefox.exe
FAILURE_BUCKET_ID: AV_INVALID_nt!ExpGetProcessInformation
Bugcheck code 00000050
Arguments ffffd48b`bc517550 00000000`00000002 fffff805`47c24b48 00000000`00000002
BiosVersion = 3406
BiosReleaseDate = 07/10/2017
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed: 4000
CurrentSpeed: 4008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\072519-10265-01.dmp]
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Debug session time: Thu Jul 25 15:31:48.118 2019 (UTC - 4:00)
System Uptime: 0 days 0:26:40.819
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption ( nt!MiDeletePteRun+15e2d8 )
BUGCHECK_STR: 0x1a_41790
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0x1a_41790_nt!MiDeletePteRun
Bugcheck code 0000001A
Arguments 00000000`00041790 ffffa400`064d5c20 00000000`00000027 00000000`00000028
BiosVersion = 3406
BiosReleaseDate = 07/10/2017
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed: 4000
CurrentSpeed: 4008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\072519-10078-01.dmp]
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Debug session time: Thu Jul 25 15:01:02.529 2019 (UTC - 4:00)
System Uptime: 0 days 0:06:33.219
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+2ae )
BUGCHECK_STR: 0x7f_8
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: 0x7f_8_STACKPTR_ERROR_nt!KiDoubleFaultAbort
Bugcheck code 0000007F
Arguments 00000000`00000008 ffffdd00`c2fb9050 00000000`56e75300 fffff805`8169f283
BiosVersion = 3406
BiosReleaseDate = 07/10/2017
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed: 4000
CurrentSpeed: 4008
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Bugchecks
0x50 - invalid memory referenced
0x1a - severe memory management error
0x7f (0x8,,,) - double fault -- an error occurred while the error handler was processing another error (an "error within an error"; hence a "double fault"
2 dumps named NT (Windows kernel) as the probable cause; the
0x1a BSOD named "memory corruption"; it also warned that symbols could not be found for the Win32 subsystem driver,
win32k.sys, the likely victim of the memory corruption. It is a Microsoft Windows driver, so it cannot be the cause.
If you're satisfied with the RAM tests, then SSD would be the next logical place to go.
But as I mentioned earlier, it would be a good idea to stick a SATA HDD into your system (ONLY THAT DRIVE - none others) and install Windows onto it and see if the system regains stability.
If it does not, or if you're unable to install Windows on to it, you can then assume that the failing hardware may be the mobo, PSU or other unknown part.
There is absolutely no way that these BSODs are software (driver) related, Stephen. The sheer number of different bugchecks tells us that.
Regards. . .
John