BSOD win32k.sys

white0devil · 20 Jan 2012

Had this crash some 10 minutes ago which was tightly followed by another crash minutes later.

Computer specs:
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506) Full Retail
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: EP43-DS3L
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM)2 Quad CPU Q9650 @ 3.00GHz (4 CPUs), ~3.0GHz
Memory: 4096MB RAM
Card name: NVIDIA GeForce GTX 560 Ti
Driver Version: 8.17.12.8562

None of my components are overclocked in any way.

First crash is 22370-01. Just before the crash I was watching a movie on my main screen and was opening a new tab in firefox. A while earlier my graphic drivers had crashed and reset. I was running BOINC manager which tends to take up a lot of CPU although I've capped it at 50% and a couple of hours earlier I had updated Itunes which wanted to restart to afterwards.

Second crash, 21028-01 was maybe three to five minutes after I had rebooted from the first crash. I was watching another a different movie whilst browsing the web for information on my BSOD.

I'm using Windows Media Player Classic for my movies with the CCCP codec pack although it would be weird if that started to cause problems now since I've used it for a really long time without any problems.

I might also mention that I've had my graphic drivers crash and reset previously but never before a BSOD.

If there's any other information that is needed please say so and I'll get it up.

//White-Devil

writhziden · 20 Jan 2012

We would prefer that you follow the https://www.sevenforums.com/crashes-d...tructions.html so we can have as much information as possible about your system and possible causes of the crashes. I will analyze your .dmp files now, but please try to follow those instructions when you respond.

Code:



Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\white0devil\012012-22370-01\012012-22370-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03265000 PsLoadedModuleList = 0xfffff800`034aa670
Debug session time: Fri Jan 20 06:26:35.266 2012 (UTC - 7:00)
System Uptime: 0 days 6:00:16.640
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000d7d2e, fffff88009108880, 0}

Probably caused by : win32k.sys ( win32k!XCLIPOBJ::vSetup+4e )

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

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

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

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


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

FAULTING_IP: 
win32k!XCLIPOBJ::vSetup+4e
fffff960`000d7d2e 8b421c          mov     eax,dword ptr [rdx+1Ch]

CONTEXT:  fffff88009108880 -- (.cxr 0xfffff88009108880)
rax=0000000086868685 rbx=fffff88009109300 rcx=0000000085858584
rdx=8585858585858585 rsi=fffff900c00bf070 rdi=00000000000000a0
rip=fffff960000d7d2e rsp=fffff88009109260 rbp=0000000000000001
 r8=0000000086868685  r9=0000000084838383 r10=fffff880091093e0
r11=0000000085848484 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=fffff900c1d599f0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210246
win32k!XCLIPOBJ::vSetup+0x4e:
fffff960`000d7d2e 8b421c          mov     eax,dword ptr [rdx+1Ch] ds:002b:85858585`858585a1=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff960000eca46 to fffff960000d7d2e

STACK_TEXT:  
fffff880`09109260 fffff960`000eca46 : fffff900`c206da70 fffff900`c00bf070 fffff900`c206da70 00000000`00000000 : win32k!XCLIPOBJ::vSetup+0x4e
fffff880`091092c0 fffff960`000e5a38 : fffff900`c00bf010 fffffa80`05cfb030 00000000`00000000 fffff900`c00bf010 : win32k!vSpUpdateSpriteVisRgn+0x1a2
fffff880`09109820 fffff960`000e6f1e : fffff900`c0180010 00000000`00000002 fffff900`c0180070 00000000`ffffffff : win32k!GreUpdateSpriteVisRgn+0x210
fffff880`09109890 fffff960`000eaef1 : fffff900`c391f0c8 00000000`ffffffff 00000000`00000000 fffffa80`00000000 : win32k!zzzLockDisplayAreaAndInvalidateDCCache+0x1be
fffff880`091098e0 fffff960`000ea37e : fffff960`00335340 00000000`00000000 fffff960`00000000 fffff960`00000001 : win32k!zzzBltValidBits+0x365
fffff880`091099e0 fffff960`000ea14a : fffff900`00000001 fffff900`c062a7a0 00000000`00000002 00000000`00000000 : win32k!xxxEndDeferWindowPosEx+0x1f2
fffff880`09109aa0 fffff960`000def89 : fffff900`c062a7a0 fffff900`c062a7a0 00000000`00000000 00000000`00000000 : win32k!xxxSetWindowPos+0x156
fffff880`09109b20 fffff960`000ed70b : 00000000`00000000 00000000`00000000 fffff880`09109c60 00000000`00000000 : win32k!xxxShowWindow+0x37d
fffff880`09109b90 fffff800`032e0ed3 : fffffa80`05afeb60 00000000`14cdef20 00000000`00000020 00000000`7481e6b8 : win32k!NtUserShowWindow+0xe3
fffff880`09109be0 00000000`747f2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e8d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x747f2e09


FOLLOWUP_IP: 
win32k!XCLIPOBJ::vSetup+4e
fffff960`000d7d2e 8b421c          mov     eax,dword ptr [rdx+1Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!XCLIPOBJ::vSetup+4e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5a

STACK_COMMAND:  .cxr 0xfffff88009108880 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!XCLIPOBJ::vSetup+4e

BUCKET_ID:  X64_0x3B_win32k!XCLIPOBJ::vSetup+4e

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

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\white0devil\012012-22370-01\012012-21028-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0324b000 PsLoadedModuleList = 0xfffff800`03490670
Debug session time: Fri Jan 20 06:52:07.253 2012 (UTC - 7:00)
System Uptime: 0 days 0:23:51.001
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004722410, fffff8800fe9aae4, ffffffffc000009a, 4}

Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+c3bae4 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8004722410, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fe9aae4, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

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


FAULTING_IP: 
nvlddmkm+c3bae4
fffff880`0fe9aae4 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06099b48 fffff880`0ff38000 : 00000000`00000116 fffffa80`04722410 fffff880`0fe9aae4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`06099b50 fffff880`0ff0b867 : fffff880`0fe9aae4 fffffa80`058e1000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06099b90 fffff880`0ff37e0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`04722410 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`06099c40 fffff880`0f237ec1 : fffffa80`05584d50 00000000`00000080 00000000`00000000 fffffa80`0586e410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`06099cc0 fffff800`03562fee : 00000000`02ca6fe9 fffffa80`0553da10 fffffa80`036e4b30 fffffa80`0553da10 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`06099d00 fffff800`032b95e6 : fffff800`0343de80 fffffa80`0553da10 fffff800`0344bcc0 fffff880`01251384 : nt!PspSystemThreadStartup+0x5a
fffff880`06099d40 00000000`00000000 : fffff880`0609a000 fffff880`06094000 fffff880`06099830 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+c3bae4
fffff880`0fe9aae4 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+c3bae4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e99233b

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

If you are overclocking anything, please stop.

Your first crash was somewhat inconclusive. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...
Your second crash was caused by your graphics card driver in a way. It did not respond to the system in a timely manner.

Both crashes could be due to the graphics card driver, so we will start with the second cause. The second crash requires STOP 0x116: VIDEO_TDR_ERROR troubleshooting. Follow the first three posts closely in that thread by usasma.

Thanks to Dave76 for help understanding possible causes.