this is a core windows service detecting that data that it has stored in memory has been corrupted.
It can be caused by outdated BIOS, bad RAM BIOS settings, bad RAM, or another kernel driver that modifies memory data that it does not own.
Normally, you would, update the BIOS, (or reset it to defaults), run memtest86 and confirm your memory subsystem is ok, then boot windows
run cmd.exe as an admin then run
sfc.exe /scannow
(to confirm your core windows files are not corrupted)
if corrupted, the system file checker will attempt repair from the hidden backup copy if both copies are bad it will fail and you will have to do a repair with the windows DVD. (windows 8.x added a new command to make the repair)
then you need to find out what made the change, generally a hacking program or malware/virus, Run malwarebytes and virus scan, reboot and run
sfc.exe /scannow command again (malware often undoes the fixes right after you make a repair)
if you don't find a problem from the above, then you need to assume that a device driver is the cause,
Best to update your motherboard device drivers from the machine vendors website and retest for failure, if it still fails, then
run cmd.exe as an admin
run
verifier.exe /standard /all
reboot
this will force a bugcheck if window detects any driver that is overwriting memory it does not own.
you can then use bluescreenviewer or whocrashed.exe and see the driver name or
put the memory dump on a server and post a link so it can be looked at.
For some problems (plug and play or USB related you have to change the memory dump type to kernel in order to keep the debug info in the memory dump)
Note: use
verifier.exe /reset
to turn off verifier functions after you are done testing.
- you can also put your current memory dumps on a server and post a link
mini dumps are at c:\windows\minidump directory by default (various files named after the date and .dmp file extension)
kernel dumps are at c:\windows\memory.dmp FILE by default
Facebook
Twitter
Instagram