SYSTEM_SERVICE_EXCEPTION (3b) needs more information

OSR_Community_User · April 8, 2015, 8:19pm

Can someone shed more light into whats the cause of the below exception.
It seems the screen is not refreshed and system enters TDR and the gfx is not reset within the required time frame. Beyond that I am curious to know what caused the screen to freeze.

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8001d64f765, Address of the instruction which caused the bugcheck
Arg3: ffffd000215f5d10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8001d64f765

BUGCHECK_P3: ffffd000215f5d10

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
dxgkrnl!TdrIsEnabled+8865
fffff800`1d64f765 488b8884000000 mov rcx,qword ptr [rax+84h]

CONTEXT: ffffd000215f5d10 – (.cxr 0xffffd000215f5d10)
rax=0000000000000000 rbx=fffff901400da310 rcx=ffffd000215f6990
rdx=000000000000ffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8001d64f765 rsp=ffffd000215f6730 rbp=ffffd000215f6830
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8001d581103 r12=0000000000000000 r13=fffff961dfe6c690
r14=ffffd000215f6990 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgkrnl!TdrIsEnabled+0x8865:
fffff8001d64f765 488b8884000000 mov rcx,qword ptr [rax+84h] ds:002b:0000000000000084=???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8001d5cf204 to fffff8001d64f765

STACK_TEXT:
ffffd000215f6730 fffff8001d5cf204 : ffffd000215f6990 ffffd000215f6990 0000000000000000 0000000000000000 : dxgkrnl!TdrIsEnabled+0x8865
ffffd000215f68b0 fffff8001d6170fd : 0000000000000001 0000000000008000 ffffd000215f69f0 0000000000000000 : dxgkrnl!g_TdrForceTimeout+0x1a484
ffffd000215f6970 fffff961dfdc13e5 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : dxgkrnl!TdrHistoryInit+0x481d
ffffd000215f6a00 fffff961dfddde3b : 0000000000000001 fffff90141736cc0 0000000000000000 0000000000000000 : win32kbase+0x313e5
ffffd000215f6b40 fffff961dfe0f527 : 00000000c000000d 0000000000000048 0000000080070605 0000000000000001 : win32kbase+0x4de3b
ffffd000215f6ca0 fffff803861e5863 : ffffe00000000001 ffffd000215f6ec0 0000000000000002 0000000005456f60 : win32kbase+0x7f527
ffffd000215f6dd0 00007ff875bd39aa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
000000000745e8b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`75bd39aa

OSR_Community_User · April 8, 2015, 10:19pm

Your symbol is not accurate. The faulting IP is too far from TdrIsEnabled. So it’s most probably no relation with TDR at all.
dxgkrnl!TdrIsEnabled+8865

I guess you didn’t set symbol path right. Try:

.symfix c:\symbols
.reload
// Analyze again.
!analyze -v

BRs, Raymond

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@intel.com
Sent: Thursday, April 09, 2015 8:19 AM
To: Kernel Debugging Interest List
Subject: [windbg] SYSTEM_SERVICE_EXCEPTION (3b) needs more information

Can someone shed more light into whats the cause of the below exception.
It seems the screen is not refreshed and system enters TDR and the gfx is not reset within the required time frame. Beyond that I am curious to know what caused the screen to freeze.

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8001d64f765, Address of the instruction which caused the bugcheck
Arg3: ffffd000215f5d10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8001d64f765

BUGCHECK_P3: ffffd000215f5d10

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
dxgkrnl!TdrIsEnabled+8865
fffff800`1d64f765 488b8884000000 mov rcx,qword ptr [rax+84h]

CONTEXT: ffffd000215f5d10 – (.cxr 0xffffd000215f5d10)
rax=0000000000000000 rbx=fffff901400da310 rcx=ffffd000215f6990 rdx=000000000000ffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8001d64f765 rsp=ffffd000215f6730 rbp=ffffd000215f6830
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8001d581103 r12=0000000000000000 r13=fffff961dfe6c690
r14=ffffd000215f6990 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgkrnl!TdrIsEnabled+0x8865:
fffff8001d64f765 488b8884000000 mov rcx,qword ptr [rax+84h] ds:002b:0000000000000084=???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8001d5cf204 to fffff8001d64f765

STACK_TEXT:
ffffd000215f6730 fffff8001d5cf204 : ffffd000215f6990 ffffd000215f6990 0000000000000000 0000000000000000 : dxgkrnl!TdrIsEnabled+0x8865
ffffd000215f68b0 fffff8001d6170fd : 0000000000000001 0000000000008000 ffffd000215f69f0 0000000000000000 : dxgkrnl!g_TdrForceTimeout+0x1a484
ffffd000215f6970 fffff961dfdc13e5 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : dxgkrnl!TdrHistoryInit+0x481d
ffffd000215f6a00 fffff961dfddde3b : 0000000000000001 fffff90141736cc0 0000000000000000 0000000000000000 : win32kbase+0x313e5
ffffd000215f6b40 fffff961dfe0f527 : 00000000c000000d 0000000000000048 0000000080070605 0000000000000001 : win32kbase+0x4de3b
ffffd000215f6ca0 fffff803861e5863 : ffffe00000000001 ffffd000215f6ec0 0000000000000002 0000000005456f60 : win32kbase+0x7f527
ffffd000215f6dd0 00007ff875bd39aa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
000000000745e8b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`75bd39aa

WINDBG is sponsored by OSR

OSR is hiring!! Info at http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

OSR_Community_User · April 9, 2015, 4:21pm

True. The symbols where not loaded correctly. Now the issue is fixed.

Thanks,

Prasad

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Zhang, Raymond
Sent: Wednesday, April 08, 2015 7:19 PM
To: Kernel Debugging Interest List
Subject: RE: [windbg] SYSTEM_SERVICE_EXCEPTION (3b) needs more information

Your symbol is not accurate. The faulting IP is too far from TdrIsEnabled. So it’s most probably no relation with TDR at all.
dxgkrnl!TdrIsEnabled+8865

I guess you didn’t set symbol path right. Try:

.symfix c:\symbols
.reload
// Analyze again.
!analyze -v

BRs, Raymond

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@intel.com
Sent: Thursday, April 09, 2015 8:19 AM
To: Kernel Debugging Interest List
Subject: [windbg] SYSTEM_SERVICE_EXCEPTION (3b) needs more information

Can someone shed more light into whats the cause of the below exception.
It seems the screen is not refreshed and system enters TDR and the gfx is not reset within the required time frame. Beyond that I am curious to know what caused the screen to freeze.

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8001d64f765, Address of the instruction which caused the bugcheck
Arg3: ffffd000215f5d10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8001d64f765

BUGCHECK_P3: ffffd000215f5d10

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP:
dxgkrnl!TdrIsEnabled+8865
fffff800`1d64f765 488b8884000000 mov rcx,qword ptr [rax+84h]

CONTEXT: ffffd000215f5d10 – (.cxr 0xffffd000215f5d10)
rax=0000000000000000 rbx=fffff901400da310 rcx=ffffd000215f6990 rdx=000000000000ffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8001d64f765 rsp=ffffd000215f6730 rbp=ffffd000215f6830
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8001d581103 r12=0000000000000000 r13=fffff961dfe6c690
r14=ffffd000215f6990 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgkrnl!TdrIsEnabled+0x8865:
fffff8001d64f765 488b8884000000 mov rcx,qword ptr [rax+84h] ds:002b:0000000000000084=???
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8001d5cf204 to fffff8001d64f765

STACK_TEXT:
ffffd000215f6730 fffff8001d5cf204 : ffffd000215f6990 ffffd000215f6990 0000000000000000 0000000000000000 : dxgkrnl!TdrIsEnabled+0x8865
ffffd000215f68b0 fffff8001d6170fd : 0000000000000001 0000000000008000 ffffd000215f69f0 0000000000000000 : dxgkrnl!g_TdrForceTimeout+0x1a484
ffffd000215f6970 fffff961dfdc13e5 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : dxgkrnl!TdrHistoryInit+0x481d
ffffd000215f6a00 fffff961dfddde3b : 0000000000000001 fffff90141736cc0 0000000000000000 0000000000000000 : win32kbase+0x313e5
ffffd000215f6b40 fffff961dfe0f527 : 00000000c000000d 0000000000000048 0000000080070605 0000000000000001 : win32kbase+0x4de3b
ffffd000215f6ca0 fffff803861e5863 : ffffe00000000001 ffffd000215f6ec0 0000000000000002 0000000005456f60 : win32kbase+0x7f527
ffffd000215f6dd0 00007ff875bd39aa : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
000000000745e8b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`75bd39aa

WINDBG is sponsored by OSR

OSR is hiring!! Info at http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

WINDBG is sponsored by OSR

OSR is hiring!! Info at http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer