BSOD dxgkrnl.sys

TheRong · 27 Nov 2010

Hello

My computer gets a BSOD randomly when I'm playing Starcraft II, don't seem to be an issue with other games. I checked one of the dumps and it seems to be a dxgkrnl.sys error, but I can't seem to fix it

- Windows 7 64bit
- No original OS installed
- Full retail version
- Hardware is around 1 year old
- Around 3 month since last re-install

CarlTR6 · 27 Nov 2010

Hi and welcome to the forum. Sorry you are having a problem. Oops, you uploaded the JCGriff tool rather than the files it generates. Run the tool and try again.

TheRong · 27 Nov 2010

oh.. my bad, it should be there now

CarlTR6 · 27 Nov 2010

Yep, you got it this time. Thanks. I looked at your three most recent dumps.

Error code 50 (2X), PAGE_FAULT_IN_NONPAGED_AREA. Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Error code A, IRQL_NOT_LESS_OR_EQUAL. Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility.

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Mon Nov 22 19:09:05.337 2010 (GMT-5)
System Uptime: 0 days 7:12:18.690
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a043779590, 1, fffff8800fc01983, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmDestroyAllocation+43 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a043779590, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800fc01983, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb60e0
 fffff8a043779590 

FAULTING_IP: 
dxgmms1!VidMmDestroyAllocation+43
fffff880`0fc01983 4c8908          mov     qword ptr [rax],r9

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  hon.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008eb4830 -- (.trap 0xfffff88008eb4830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a043779590 rbx=0000000000000000 rcx=fffffa8007c49000
rdx=fffff8a008faff00 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800fc01983 rsp=fffff88008eb49c0 rbp=fffffa8007c49000
 r8=fffff8a00b8ce730  r9=fffff8a003779590 r10=0000000000000000
r11=fffff88003ee3120 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
dxgmms1!VidMmDestroyAllocation+0x43:
fffff880`0fc01983 4c8908          mov     qword ptr [rax],r9 ds:fffff8a0`43779590=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002afd8c1 to fffff80002a7e740

STACK_TEXT:  
fffff880`08eb46c8 fffff800`02afd8c1 : 00000000`00000050 fffff8a0`43779590 00000000`00000001 fffff880`08eb4830 : nt!KeBugCheckEx
fffff880`08eb46d0 fffff800`02a7c82e : 00000000`00000001 fffff8a0`03779590 fffffa80`079ff000 fffffa80`0793f010 : nt! ?? ::FNODOBFM::`string'+0x40e8b
fffff880`08eb4830 fffff880`0fc01983 : fffffa80`07914680 fffff880`08eb4a10 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`08eb49c0 fffff880`10926fb3 : 00000000`00000000 00000000`00000000 fffff8a0`09d24000 00000000`00000174 : dxgmms1!VidMmDestroyAllocation+0x43
fffff880`08eb49f0 fffff880`1093967c : fffff8a0`09d29130 00000000`00000000 00000000`00000000 fffff8a0`09d24068 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb
fffff880`08eb4ae0 fffff880`1091e815 : 00000000`fffffeda fffff8a0`084b60b0 fffff880`08eb4ca0 fffffa80`07c21000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`08eb4b50 fffff880`1093a7ea : fffffa80`08376060 fffffa80`08376060 00000000`fffdb000 fffff8a0`09d24000 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`08eb4b80 fffff960`0024b8b2 : 00000000`00000020 fffff880`08eb4c00 00000000`000007da 00000000`74ba5fe4 : dxgkrnl!DxgkDestroyDevice+0x1f6
fffff880`08eb4bf0 fffff800`02a7d993 : fffffa80`08376060 fffff880`08eb4ca0 00000000`fffdb000 fffffa80`0685c7f0 : win32k!NtGdiDdDDIDestroyDevice+0x12
fffff880`08eb4c20 00000000`74bc123a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74bc123a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidMmDestroyAllocation+43
fffff880`0fc01983 4c8908          mov     qword ptr [rax],r9

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidMmDestroyAllocation+43

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidMmDestroyAllocation+43

BUCKET_ID:  X64_0x50_dxgmms1!VidMmDestroyAllocation+43

Followup: MachineOwner
---------

Debug session time: Sat Nov 27 10:43:32.892 2010 (GMT-5)
System Uptime: 0 days 3:22:22.985
Loading Kernel Symbols
...............................................................
................................................................
..........
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa80457ee173, 2, 0, fffff80002a931fc}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+555 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa80457ee173, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a931fc, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb20e0
 fffffa80457ee173 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiInsertPageInFreeOrZeroedList+3cc
fffff800`02a931fc 0fb6472b        movzx   eax,byte ptr [rdi+2Bh]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  SC2.exe

TRAP_FRAME:  fffff88009794020 -- (.trap 0xfffff88009794020)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=00000000057ee003
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a931fc rsp=fffff880097941b0 rbp=fffff88009794200
 r8=fffff80002c48720  r9=fffff88009794258 r10=fffff80002cb4840
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiInsertPageInFreeOrZeroedList+0x3cc:
fffff800`02a931fc 0fb6472b        movzx   eax,byte ptr [rdi+2Bh] ds:00000000`0000002b=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a79ca9 to fffff80002a7a740

STACK_TEXT:  
fffff880`09793ed8 fffff800`02a79ca9 : 00000000`0000000a fffffa80`457ee173 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09793ee0 fffff800`02a78920 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09794020 fffff800`02a931fc : fffff800`02c48728 fffff880`09794200 00000000`00000002 00000000`00000001 : nt!KiPageFault+0x260
fffff880`097941b0 fffff800`02aac0bf : 00000000`00000000 fffff680`002aed80 00000000`00000000 fffffa80`0809c3a0 : nt!MiInsertPageInFreeOrZeroedList+0x3cc
fffff880`097942b0 fffff800`02aab381 : 00000000`00000200 fffff680`002aed80 fffffa80`0691ca60 fffffa80`0691ca60 : nt!MiDeletePteRun+0x49f
fffff880`09794460 fffff800`02abc0da : 00000000`00000000 00000000`55db1fff fffffa80`00000000 fffffa80`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`09794620 fffff800`02a79993 : ffffffff`ffffffff fffff8a0`02b429d0 fffff8a0`02b429c8 fffff8a0`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`09794710 fffff800`02a75f30 : fffff880`04864a0d fffff880`09794ca0 00000000`00000003 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`097948a8 fffff880`04864a0d : fffff880`09794ca0 00000000`00000003 00000000`00000000 00000000`00000600 : nt!KiServiceLinkage
fffff880`097948b0 fffff880`0488a64a : fffff8a0`02b42990 fffffa80`06b16570 00000000`00003000 00000000`00000400 : dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+0x555
fffff880`09794980 fffff960`0021bb16 : 00000000`0aeae6b0 fffff880`09794ca0 00000000`08823800 fffff800`00003000 : dxgkrnl!DxgkRender+0x502
fffff880`09794bf0 fffff800`02a79993 : fffffa80`05993780 00000000`00000300 00000000`00000000 fffffa80`058f4b00 : win32k!NtGdiDdDDIRender+0x12
fffff880`09794c20 00000000`7593143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0aeae688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7593143a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+555
fffff880`04864a0d 4c8b5c2448      mov     r11,qword ptr [rsp+48h]

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+555

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac5509e

FAILURE_BUCKET_ID:  X64_0xA_dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+555

BUCKET_ID:  X64_0xA_dxgkrnl!DXGCONTEXT::ResizeUserModeBuffers+555

Followup: MachineOwner
---------

You have one out of date driver loading on your system. Update this driver.

Rt64win7.sys - Latest PCIe GBE (GigaBit Ethernet) drivers here: Realtek

Enable Driver Verifier following the instructions in this tutorial: Driver Verifier - Enable and Disable. Use your computer normally while Driver Verifier is running. If Driver Verifier enables a faulty driver, it will trigger a BSOD. Upload and and all Driver Verifier enabled dumps. Run it for about 36 hours.

TheRong · 27 Nov 2010

Okay thanks, ill try that and reply back

CarlTR6 · 27 Nov 2010

You are welcome.

TheRong · 27 Nov 2010

Hello again

Not sure if it is the same BSOD but this just happend when i tried to alt tab from full screen. But this isn't the first time.
(I have already installed the missing driver)