Blue screen on boot. Im assuming memory, but need opinions

Solution
error code 0x5003 indicates that the working set list is corrupted.

this means the list that windows uses to keep track of paging between the pagefile.sys (virutal memory ) and what is in RAM has been corrupted.

it can be caused by bad RAM settings, drivers corrupting windows kernel memory, bugs any where in the storage system (sata drivers, errors from the drives, firmware of SSD) Malware attacking the storage system.

not a fun problem to figure out. Mostly I have people:
check your windows files for corruption:
ie run cmd.exe as an admin, then run
sfc.exe /scannow
if you have windows 8.x and above, run
dism.exe /online /cleanup-image /restorehealth

if you find problems, reboot and run the sfc.exe /scannow command again...
error code 0x5003 indicates that the working set list is corrupted.

this means the list that windows uses to keep track of paging between the pagefile.sys (virutal memory ) and what is in RAM has been corrupted.

it can be caused by bad RAM settings, drivers corrupting windows kernel memory, bugs any where in the storage system (sata drivers, errors from the drives, firmware of SSD) Malware attacking the storage system.

not a fun problem to figure out. Mostly I have people:
check your windows files for corruption:
ie run cmd.exe as an admin, then run
sfc.exe /scannow
if you have windows 8.x and above, run
dism.exe /online /cleanup-image /restorehealth

if you find problems, reboot and run the sfc.exe /scannow command again. Some malware will reinfect right after you fix the files.
then run malwarebytes scan.

if still having problems, turn off virtual memory (pagefiles) reboot, and delete the hidden pagefiles, reboot again, turn the virutal memory back on. This assumes you were getting errors from the particular spot on the drive.

you would then run crystaldiskinfo.exe and have it read the smart data from the drive and get an idea of how healthy the drive is.
if you have a SSD you can also get the firmware version from the SSD and look up if there is a required firmware update you should install. SSD drives have various issues that can cause this error. IE if they get full the drive may not be able to move bad blocks around, or it it is too busy, it might not get time to run its cleanup routines. (boot in to BIOS and leave the drive powered and not in use for a few hours to let it do its cleanup routines to fix this case)




 
Solution