Debugging Stop 0x3D - INTERRUPT_EXCEPTION_NOT_HANDLED

x BlueRobot · Mar 20, 2022

Rich (BB code):

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)
Arguments:
Arg1: fffff8066247e7c8 << EXCEPTION_RECORD
Arg2: fffff8066247e000 << CONTEXT_RECORD
Arg3: 0000000000000000
Arg4: 0000000000000000

There isn't any bugcheck description provided by Microsoft for this exception in dump file, although, it is documented on MSDN. Quite simply, an unhandled exception has occurred during the handling of an interrupt. The call stack indicates the type of exception which has happened and in this case, we can clearly see that it was a general protection fault.

Rich (BB code):

0: kd> knL
 # Child-SP          RetAddr               Call Site
00 fffff806`6247d838 fffff806`5f313bd5     nt!KeBugCheckEx
01 fffff806`6247d840 fffff806`5f2004df     nt!KiInterruptHandler+0x21
02 fffff806`6247d880 fffff806`5f0e6f97     nt!RtlpExecuteHandlerForException+0xf
03 fffff806`6247d8b0 fffff806`5f0e5b96     nt!RtlDispatchException+0x297
04 fffff806`6247dfd0 fffff806`5f2096ac     nt!KiDispatchException+0x186
05 fffff806`6247e690 fffff806`5f2053e0     nt!KiExceptionDispatch+0x12c
06 fffff806`6247e870 fffff806`5f014cd3     nt!KiGeneralProtectionFault+0x320
07 fffff806`6247ea00 fffff806`5f014c11     nt!KiInsertQueueDpc+0xb3
08 fffff806`6247eab0 fffff806`79b7f4bd     nt!KeInsertQueueDpc+0x11
09 fffff806`6247eaf0 fffff806`6247ec00     nvlddmkm+0x8f4bd
0a fffff806`6247eaf8 fffff806`6247ebf0     0xfffff806`6247ec00
0b fffff806`6247eb00 00000000`00000000     0xfffff806`6247ebf0

The parameters of the bugcheck refer to the address of the exception record and the context record respectively.

Rich (BB code):

0: kd> .exr 0xfffff8066247e7c8
ExceptionAddress: fffff8065f014cd3 (nt!KiInsertQueueDpc+0x00000000000000b3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

It would seem that the nt!KiInsertQueueDpc function is reading from an invalid memory address. If we examine the context record for the crash, we'll be able to see what was happening:

Rich (BB code):

0: kd> .cxr 0xfffff8066247e000
rax=10518948c3c0950f rbx=61622d6f77742d63 rcx=000000000000c7c3
rdx=0000000000000000 rsi=0000000000000000 rdi=fffff80679af6a84
rip=fffff8065f014cd3 rsp=fffff8066247ea00 rbp=fffff80659cfd180
 r8=0000000000000000  r9=0000000000000000 r10=000000000000ccc3
r11=fffff8065ee00000 r12=0000000000000000 r13=0000000000000009
r14=ffffdf033c287000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!KiInsertQueueDpc+0xb3:
fffff806`5f014cd3 488583c8000000  test    qword ptr [rbx+0C8h],rax ds:002b:61622d6f`77742e2b=????????????????

The pointer is complete junk and of course cause a general protection fault which is unable to be resolved. The issue appears to have been caused by the graphics card driver and therefore it is recommended that the user either update it or roll back to an older version.

Rich (BB code):

0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff806`79af0000 fffff806`7c189000   nvlddmkm T (no symbols)          
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b7184c0e1c94c102\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Nov  9 16:35:03 2021 (618AA337)
    CheckSum:         025D417D
    ImageSize:        02699000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

References:

Bug Check 0x3D INTERRUPT_EXCEPTION_NOT_HANDLED - Windows drivers

Search

Search

Debugging Stop 0x3D - INTERRUPT_EXCEPTION_NOT_HANDLED

x BlueRobot

Administrator