Windows 10: Almost Daily ntoskrnl.exe BSOD, Desperately Need Help...

Title says it all. I'm not completely clueless when it comes to computer stuffs. My laptop is Asus A456UR with i56200U CPU and nVidia 930MX GPU. I have 8GB DDR4 RAM installed (4 onboard, 4 from Corsair stick). More info is in the zipped file. Almost every BSOD is caused by ntoskrnl, which is difficult for me to point out exactly what causes the persisten problem.

TLDR; Help me identify the true culprit behind ntoskrnl BSOD, thanks...

EDIT : Logfiles finally changed to the newer ones, my bad...

:)

 

[BSOD] SYSTEM_SERVICE_EXCEPTION 00000000`c0000096 ntoskrnl.exe

Hi, I get random BSOD usually saying SYSTEM_SERVICE_EXCEPTION and in bluescreenviewer it says that ntoskrnl.exe is the problem. I get this BSOD almost everyday. Can anyone help me I can attach the dump file if possible.

Dropbox - ntoskrnl.exeSYSTEM_SERVICE_EXCEPTION dump.txt

 

daily BSOD (ntoskrnl.exe)

I have yet to run 8 or more loops of memtest since it takes quite a while and I'm working a lot on my PC atm.. I should be able to do it in the next 48 hours though.

Today's bluescreen (after 13hours) had something to do with my USB Audio Interface.. Never had that one before but agian showing the "USBXHCI.SYS". Here is the minidump file : 010818-7015-01.dmp

and here my System Information File : SystemInfo.nfo

 

The Forum rules prevent me helping you while you have software running for piracy.

 

May you elaborate which software you were talking about? Tor Browser? Bittorent?

 

I assumed you would know - https://www.microsoft.com/en-us/wdsi...:Win32/AutoKMS

 

That's too bad. Is there no way to go around it? Though I won't mind getting rid of KMS if that would make my slate clean.

Time to pay for Office license then. My Win 10 is of course genuine.

 

Once everything is legal you will be able to get help. A new set of log files will need to be submitted too.

 

I've removed every trace of KMSAuto including the automated tasks... If there's still something off, please let me know.

Thanks for your time up until this point, Phil *Smile

EDIT : Forgot to mention I've reuploaded the newer system log after removing KMS

 

The logfiles are no different - are you sure the new ones got uploaded?

 

My bad... Although I'm careful enough to choose the newer file as attachment, I'm not familiar enough with how file submission works yet. This time I made sure to attach the correct file.

 

Did you restart your PC after removing the software? I'm still seeing the last but one entry in the log is the loading of windivert. Sorry, but such software can have harmful effects.

 

I've restarted my PC, then make a new log.

Rules and regulations make everything more complicated huh...

If you still find slightest trace of violations etc, better give up on this, I'll mark this as solved.

 

Many thanks, it looks like everything is now sorted.

I can see that you have been getting a lot of windows update failures. Please run the troubleshooter for windows update to see if it will fix this problem.





The bluescreen crash dump file does not reveal which driver is causing the problem - therefore you will need to run a program to try and force the drivers to crash until you find the one that is the problem. The details to do this are in the tutorial listed below. Please follow all the instructions carefully and make a system backup and system recovery disk before you do so because there is a risk you will not be able to get back to a working system.





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.

 

Many thanks, Phil... I've ran Windows Update troubleshooting and it said some errors were fixed. Will try verifier very soon...

Thanks for the help so far, will report back in.