New
#11
It's too bad it did not generate a new .dmp file. It may indicate something else causing the problem.
It's too bad it did not generate a new .dmp file. It may indicate something else causing the problem.
Like what
Hard to say without the .dmp file. I was saying the .dmp file may indicate a different cause or better clues. Since the .dmp file is not being generated, that may indicate corruption on the system. Check for data/Windows corruption.
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
For any drives that do not give the message:
Windows has checked the file system and found no problems
run disk check again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.
- Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
Well i have ran the chkdsk and it hasn't shown any errors will give a try on sfc though.
Can you post the logs for the disk check?
Also, let us know how SFC /SCANNOW goes. You can upload the sfcdetails.txt file if you continue to get errors. The instructions for generating the sfcdetails.txt file from the CBS.log file are within OPTION THREE of SFC /SCANNOW Command - System File Checker