Windows 10: BSOD System_Service_Exception when playing Games

Alright, Ill switch to Chrome and see if I get an error. I've also been planning to upgrade my motherboard. Do you think the problem will carry over?

 

It's hard to say, I'm not getting anything concrete at the moment from the latest dumps, I need to read up some more on LUA Virtualisation to see if it really can be the cause. I presume if you install a new motherboard you'll be clean reinstalling the OS?

 

Yeah, I'm gonna do a clean Windows install.

 

There every chance it may well help, but I don't want to commit by saying it definitely will.

 

hmm some more dump files to post. Both came while playing Far Cry 4. One with the Xbox App open and another with youtube open. Actually, there might be 3 new ones. I can't remember.

Attachment 31151

 

Another 0x3B and a 0x1E, both could be down to drivers but none are showing in the dumps. Let's enable Driver Verifier and see if that shows us any offending drivers, read the following tutorial carefully before proceeding.






Diagnostic Test

DRIVER VERIFIER
Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums



Warning Make a System Restore point before enabling Driver Verifier.


Note Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Post any resulting dump files.

 

I did get an BSOD mentioning nvlddmkm which I'm pretty sure is an NVIDIA driver. I just checked and NVIDIA released a new Windows 10 driver yesterday. I'm going to update and then run the Driver Verifier.

Attachment 31266

 

Just a quick update, Driver Verifier continues to run since yesterday at around 10am, with no errors so far. My pc was turned off during the night from about 10pm to 8am. After the last crash I did run a chkdsk /f at startup but I don't know if anything actually happened as it just told me "completed" and I have no idea where to view the results. Anyways, the next time I'll post will be tomorrow if Driver Verifier finds no errors (I dont want to leave it on so long) or If it does find an error. Whichever happens first.

 

OK keep us posted. DV probably would have found something by now I'd have thought but let it run the 48 hours just to be sure.

 

Alright, I'll admit that i probably shouldn't be playing games with Driver Verifier going. I did get a KMODE exception BSOD while playing Heroes of the Storm and I had the XBOX APP open (connected to a party with friends on the XBOXONE). I'm not sure if this has anything to do with Driver Verifier but I'm posting the log. I'm also going to disable Driver Verifier and reenable it to make sure the settings are all correct.

Attachment 31651

 

Nothing particular showing in that dump. When you enable DV next don't check Force Pending I/O Requests.

 

Attachment 32607

Not much to say about this one because it happened while I wasnt around. I can say that Driver Verifier was disabled.

 

Another BSOD semmingly pointing to RAM, but we know that's good. Scroll down the code to see that the dump is suggesting that DV is still enabled.
Code: EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. FAULTING_IP: nt!KxWaitForLockOwnerShipWithIrql+12 fffff802`356de762 48890a mov qword ptr [rdx],rcx CONTEXT: ffffd00029dbe200 -- (.cxr 0xffffd00029dbe200;r) rax=0000000000000000 rbx=ffffe00199955110 rcx=ffffd00029dbec70 rdx=0020000000000000 rsi=ffffe001a6c45800 rdi=ffffd00029dbec70 rip=fffff802356de762 rsp=ffffd00029dbec20 rbp=ffffd00029dbecb0 r8=ffffd00029dbece0 r9=ffffe00199955110 r10=7ffff901402146b8 r11=7ffffffffffffffc r12=0000000000000002 r13=000000000129fda0 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up di ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210086 nt!KxWaitForLockOwnerShipWithIrql+0x12: fffff802`356de762 48890a mov qword ptr [rdx],rcx ds:002b:00200000`00000000=???????????????? Last set context: rax=0000000000000000 rbx=ffffe00199955110 rcx=ffffd00029dbec70 rdx=0020000000000000 rsi=ffffe001a6c45800 rdi=ffffd00029dbec70 rip=fffff802356de762 rsp=ffffd00029dbec20 rbp=ffffd00029dbecb0 r8=ffffd00029dbece0 r9=ffffe00199955110 r10=7ffff901402146b8 r11=7ffffffffffffffc r12=0000000000000002 r13=000000000129fda0 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up di ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210086 nt!KxWaitForLockOwnerShipWithIrql+0x12: fffff802`356de762 48890a mov qword ptr [rdx],rcx ds:002b:00200000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0x3B PROCESS_NAME: Steam.exe CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff8023565ca5f to fffff802356de762[/quote]
I'm almost certain this is down to a driver but it's just not showing. Did you try Verifier without Force pending I/O requests checked?