New
#31
I had edited the picture as you were posting, so here it is again.
Attachment 37720
I had edited the picture as you were posting, so here it is again.
Attachment 37720
*sigh* Another crash, kernel_error strikes back.
Attachment 37779
Last edited by derek704; 15 Sep 2015 at 23:45.
Most of the dumps are blaming the Nvidia drivers, most likely the other too.
Please try uninstalling the drivers via Display Driver Uninstaller and install the drivers fresh.
Memory_management crash
Attachment 38505
Please try the following again:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
Good,
Unfortunately, the dump didn't reveal much.
Usually with a 0x1a you need to do a memory test or driver verifier if the memory fine.
You already did both, but there could be changes in the time you did the tests and now.
Thus, I post again the instructions.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
Note
MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
WarningPlease make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
NoteYour system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
I ran Memtest for 37 hours, ram checker for 8 hours, and driver verifier for 48 hours without any errors.
Attachment 39281Attachment 39282