BSOD while playing GTAV SYSTEM_SERVICE_EXCEPTION

Ragnakak · Apr 19, 2015

I've been receiving the SYSTEM_SERVICE_EXCEPTION BSOD while playing GTAV. I suspected that the new beta catalyst drivers (15.4) from AMD were the cause of the issue, so I uninstalled the drivers using the Display Driver Uninstaller program in Safe Mode and reinstalled the 14.12 catalyst drivers. I am still receiving the BSOD after going back to the stable drivers.

I also had a Canon CanoScan LiDE 70 scanner that technically isn't supported by Windows 8.1, but I had drivers/software working through Windows 7 compatibility mode. I uninstalled the drivers and software, then unplugged the hardware, to see if that was causing the issue, but still have the same problem.

I used BlueScreenView to determine the crash is caused by driver ntoskrnl.exe 0x0000003b.

Attached is my .zip created from the DM Log Collector Tool. Any help is appreciated.

blueelvis · Apr 23, 2015

Hi Ragnakak & welcome to the forums ^_^,

I have analysed your dump files and below has been provided an analysis of the same for informative purposes -

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.

Code:

4: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffd000`25b0f3e8 fffff801`21f5e7e9 nt!KeBugCheckEx
01 ffffd000`25b0f3f0 fffff801`21f5e0fc nt!KiBugCheckDispatch+0x69
02 ffffd000`25b0f530 fffff801`21f5a1ed nt!KiSystemServiceHandler+0x7c
03 ffffd000`25b0f570 fffff801`21ecb0a5 nt!RtlpExecuteHandlerForException+0xd
04 ffffd000`25b0f5a0 fffff801`21ecf45e nt!RtlDispatchException+0x1a5
05 ffffd000`25b0fc70 fffff801`21f5e8c2 nt!KiDispatchException+0x646
06 ffffd000`25b10360 fffff801`21f5cdfe nt!KiExceptionDispatch+0xc2
07 ffffd000`25b10540 fffff801`21eec7a0 nt!KiGeneralProtectionFault+0xfe
08 ffffd000`25b106d0 fffff801`21ec47e8 nt!KxWaitForLockOwnerShipWithIrql+0x14
09 ffffd000`25b10700 fffff801`60d5a379 nt!ExAcquireResourceExclusiveLite+0x218
0a ffffd000`25b10770 fffff801`60d5a0a3 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x69
0b ffffd000`25b107e0 fffff801`61098796 dxgmms1!VidSchSubmitCommand+0x333
0c ffffd000`25b10900 fffff801`6108d8ca dxgkrnl!DXGCONTEXT::SubmitPresent+0x4a6
0d ffffd000`25b10ec0 fffff801`6108ef70 dxgkrnl!DXGCONTEXT::Present+0xa6a
0e ffffd000`25b118b0 fffff801`21f5e4b3 dxgkrnl!DxgkPresent+0x3e0
0f ffffd000`25b11a80 00007ffa`d546173a nt!KiSystemServiceCopyEnd+0x13
10 00000051`feefe898 00000000`00000000 0x00007ffa`d546173a

We see that we enter the kernel mode with the second last instruction. Then the DirectX performs some operations which causes the Windows Kernel to acquire an exclusive lock on a resource but since the resource is not available for *exclusive* access, it needs to wait which in turn causes an exception which ultimately leads to the system crash

Below is a list of 3rd party drivers present on your system -

Code:

**************************Sun Apr 19 22:53:10.330 2015 (UTC + 5:30)**************************
[COLOR=#FF0000][U][B]AsUpIO.sys                  Tue Aug  3 08:17:59 2010 (4C57835F)
[/B][/U][/COLOR]Rt630x64.sys                Mon Jul 30 21:33:12 2012 (5016B040)
[COLOR=#FF0000][U][B]AsIO.sys                    Wed Aug 22 15:24:47 2012 (5034AC67)
[/B][/U][/COLOR]npf.sys                     Fri Mar  1 07:01:24 2013 (513004EC)
cmudaxp.sys                 Mon Jul 22 06:54:04 2013 (51EC89B4)
AODDriver2.sys              Tue Feb 11 16:36:52 2014 (52FA044C)
usbfilter.sys               Mon Feb 17 11:53:43 2014 (5301AAEF)
[COLOR=#0000FF][U][B]rzpmgrk.sys                 Fri Apr 18 01:06:12 2014 (53502D2C)
[/B][/U][/COLOR]mwac.sys                    Wed Jun 18 07:37:00 2014 (53A0F444)
mbam.sys                    Wed Sep  3 23:20:25 2014 (540754E1)
amd_sata.sys                Tue Sep 23 12:36:57 2014 (54211C11)
amd_xata.sys                Tue Sep 23 12:36:59 2014 (54211C13)
[COLOR=#0000FF][U][B]rzpnk.sys                   Sat Oct 18 01:08:10 2014 (54417022)
[/B][/U][/COLOR]amdkmpfd.sys                Tue Oct 28 04:56:38 2014 (544ED4AE)
AMDACPKSL.SYS               Sun Dec 21 09:08:02 2014 (5496409A)
AtihdWB6.sys                Sun Dec 21 09:08:19 2014 (549640AB)
[COLOR=#0000FF][U][B]rzendpt.sys                 Tue Dec 30 15:02:47 2014 (54A2713F)
rzudd.sys                   Tue Dec 30 15:02:50 2014 (54A27142)
[/B][/U][/COLOR]MBAMSwissArmy.sys           Fri Jan  9 08:15:43 2015 (54AF40D7)
atikmpag.sys                Wed Apr  1 01:39:30 2015 (551AFEFA)
atikmdag.sys                Wed Apr  1 02:01:21 2015 (551B0419)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Apr 19 03:09:36.136 2015 (UTC + 5:30)**************************
AMDACPKSL.SYS               Sun Jun 22 08:01:43 2014 (53A6400F)
AtihdWB6.sys                Sun Jun 22 08:02:00 2014 (53A64020)
atikmpag.sys                Fri Nov 21 07:38:54 2014 (546E9EB6)
atikmdag.sys                Fri Nov 21 08:00:27 2014 (546EA3C3)

Ragnakak · Apr 23, 2015

I had to remove the two ASUS drivers manually, which I was able to do without any problems. I uninstalled the razer software and swapped out the keyboard and mouse with an older microsoft mouse and keyboard.

I played GTA for about two hours when the game froze, went to an all red screen with no text and then the system restarted.

Core Temp was reporting a temperature of 62c, which seems abnormally high.

I checked BlueScreenView and it reported atikmdag.sys+56e07 as cause of the crash.

I'm assuming this is now an overheating issue. I'll check inside my case and components for any blockages.

edit: I checked inside my case and there are no blockages in any of the case, cpu or gpu fans.

Mysers Briggs · Apr 24, 2015

Code:

4: kd> .trap ffffd000`25b10540
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd00025b10720
rdx=0200000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80121eec7a0 rsp=ffffd00025b106d0 rbp=0000000000000001
 r8=ffffd00025b10770  r9=0000000000000000 r10=0000000000000002
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff801`21eec7a0 48890a          mov     qword ptr [rdx],rcx ds:02000000`00000000=????????????????

4: kd> !pte 0200000000000000
                                           VA 0200000000000000
PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00000    PDE at FFFFF6FB40000000    PTE at FFFFF68000000000
contains 04300000305D0867  contains 197000003B0A2867  contains 0000000000000000
GetUlongFromAddress: unable to read from fffff8012216510c
pfn 305d0     ---DA--UWEV  pfn 3b0a2     ---DA--UWEV  not valid

The actual ERESOURCE routine tried to acquire the lock with exclusive access, but was passed a bad pointer, thus the exception.

blueelvis said:
We see that we enter the kernel mode with the second last instruction. Then the DirectX performs some operations which causes the Windows Kernel to acquire an exclusive lock on a resource but since the resource is not available for *exclusive* access, it needs to wait which in turn causes an exception which ultimately leads to the system crash

The second function that is displayed in the stack nt!KiSystemServiceCopyEnd indicates the transition to Kernel mode, if that's what you mean.
It's not that the resource isn't available, it's that it simply hasn't been pointed to in the correct way, by passing a bad pointer, it accessed the wrong memory.
Given that this is a minidump, we don't know what the actual shared resource is.

Code:

4: kd> lmvm atikmdag
start             end                 module name
fffff801`618df000 fffff801`62bbe000   atikmdag   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Tue Mar 31 21:31:21 2015 (551B0419)
    CheckSum:         01277AAA
    ImageSize:        012DF000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I don't know if you've tried a display driver update, but I highly recommend it if you haven't, it's most likely a driver error.
Given that the error is consistent with trying to acquire a lock, it's almost indefinately bad programming code passing bad pointers.
As for the red screen, I'm not sure, it could be a bad card, but I've seen display drivers cause all kinds of strange errors.

Ragnakak · Apr 24, 2015

Mysers Briggs said:
I don't know if you've tried a display driver update, but I highly recommend it if you haven't, it's most likely a driver error.
Given that the error is consistent with trying to acquire a lock, it's almost indefinately bad programming code passing bad pointers.
As for the red screen, I'm not sure, it could be a bad card, but I've seen display drivers cause all kinds of strange errors.

Right now, I am using the latest beta drivers from AMD (Catalyst 15.4.) The beta drivers came out with performance improvements for GTAV. The latest stable release is 14.12. Should I try to downgrade to the stable driver and see if that helps? Could the temperatures I reported be causing the video card driver crash?

Mysers Briggs · Apr 24, 2015

Ragnakak said:
Mysers Briggs said:

I don't know if you've tried a display driver update, but I highly recommend it if you haven't, it's most likely a driver error.
Given that the error is consistent with trying to acquire a lock, it's almost indefinately bad programming code passing bad pointers.
As for the red screen, I'm not sure, it could be a bad card, but I've seen display drivers cause all kinds of strange errors.

Click to expand...

Right now, I am using the latest beta drivers from AMD (Catalyst 15.4.) The beta drivers came out with performance improvements for GTAV. The latest stable release is 14.12. Should I try to downgrade to the stable driver and see if that helps? Could the temperatures I reported be causing the video card driver crash?

That would be your best bet, yes.
No, it's unlikely, 62C while it is above some people's comfortable level, it is still cool enough for it to function properly with little risk of damage. Some GPUs can be stable up to 100C.

Ragnakak · Apr 24, 2015

I went back to the 14.12 Catalyst drivers, started up gtav again and crashed again after about an hour of play. BlueScreenViewer is showing the crash was caused this time by dxgmms1.sys (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED).

BSOD while playing GTAV SYSTEM_SERVICE_EXCEPTION

Ragnakak

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Ragnakak

New Member

My Computer

System One

Mysers Briggs

Member

My Computer

System One

Ragnakak

New Member

My Computer

System One

Mysers Briggs

Member

My Computer

System One

Ragnakak

New Member

My Computer

System One