New
#11
As it shows a memory corruption (it may be caused something other than the RAM too), let us start with the RAM tests.
Test your RAM modules for possible errors.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa824b00d6b8, 0, fffff80002aaf7ca, 5} Could not read faulting driver name Probably caused by : memory_corruption ( nt!MiRemoveWorkingSetPages+3b2 ) Followup: MachineOwner ---------
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
Let us know the results.