Windows 10: BSOD Ntoskrnl.exe windows 10

thank you all SO much!!

 

You are most welcome! *Smile

 

so after a week, I got another one with a different message about attempting to write to read only memory so I am uplading my info again and asking for help *SadAttachment 118267

 

Your latest error is usually associated with a faulty driver but unfortunately the driver does not show up in the analysis.

In this case it would be worth running Driver Verifier to see if Windows can find any misbehaving drivers. Please note the warnings and make sure you have backups and restore points set.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please read and run driver verifier.

If you suspect a driver is causing a problem but do not have a clear idea which one it is then 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 until you have a bluescreen, whichever 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 driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your 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'm not sure i'm comfortable doing that level of testing. Would a windows reinstall fix the stupid ntoskrnl.exe +155829?

 

Not necessarily since there is nothing actually wrong with ntoskrnl.exe; that just happens to be the process that is running when the BSOD occurs. The trigger is nearly always a bad driver.

 

So the only way to fix it is the driver verifier?

 

Well it is just a suggestion to try and flush out any faulty driver. Otherwise you just have to wait for more BSOD events and post up new files for us to look at. How frequently do you think they are happening now?

 

here is the newest error list

 

I could not find any new BSOD files in this latest log.

Looking at the eventlog all I could see was a startup repair failed back on 29th Jan.

Code: Event[17215]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2017-01-29T11:22:22.406 Event ID: 1121 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-MGLGIS0 Description: The following file necessary for Windows startup was corrupt: c:\windows\system32\drivers\ntfs.sys[/quote] Please open a command prompt and run sfc /scannow to see if any of your system files can be repaired.

 

didn't find any integrity issues. though when it ran the first time, it did BSOD. with a system thread exception not handled in the windows file manager.