New
#1
BSOD while playing Torchlight 2, Win32k.sys related. Help appreciated!
Hello and thanks in advance for any help!
I have a great custom computer that I've been gaming on for over a year now. I had 2 blue screens today while playing Torchlight 2 (I had been playing Max Payne 3 earlier with no issues and many other games on a daily basis).
I am attaching the zipped dump file to this thread in hopes someone can help me figure out what the problem is. I have WinDbg myself but I always seem to have problems reading the minidump files.
Here is what my WinDbg outputs, though it might be best to view the file yourself:
You will notice that I was running HWMonitor during this crash and it mentions it. I was running it to make sure my SLI'd EVGA 670 FTW's weren't overheating, which they were not. During the first crash HWMonitor was not running, but the crash did not produce a dump file.Code:Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\072413-15038-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\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.18113.amd64fre.win7sp1_gdr.130318-1533 Machine Name: Kernel base = 0xfffff800`0301d000 PsLoadedModuleList = 0xfffff800`03260670 Debug session time: Wed Jul 24 00:51:55.399 2013 (UTC - 4:00) System Uptime: 0 days 0:55:36.211 Loading Kernel Symbols ............................................................... ................................................................ ............................................................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {ffffffffffffffff, 1, fffff96000266b8e, 0} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!PopThreadGuardedObject+16 ) 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: ffffffffffffffff, memory referenced. Arg2: 0000000000000001, value 0 = read operation, 1 = write operation. Arg3: fffff96000266b8e, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032ca100 GetUlongFromAddress: unable to read from fffff800032ca1c0 ffffffffffffffff FAULTING_IP: win32k!PopThreadGuardedObject+16 fffff960`00266b8e 4c8918 mov qword ptr [rax],r11 MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: HWMonitor.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff880095a8090 -- (.trap 0xfffff880095a8090) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffffffffffffff rbx=0000000000000000 rcx=fffff900c4efea90 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff96000266b8e rsp=fffff880095a8220 rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000 r10=00ffffff00ffffff r11=fffff900c4d37c70 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc win32k!PopThreadGuardedObject+0x16: fffff960`00266b8e 4c8918 mov qword ptr [rax],r11 ds:ffffffff`ffffffff=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80003110be0 to fffff80003092c00 STACK_TEXT: fffff880`095a7f28 fffff800`03110be0 : 00000000`00000050 ffffffff`ffffffff 00000000`00000001 fffff880`095a8090 : nt!KeBugCheckEx fffff880`095a7f30 fffff800`03090d2e : 00000000`00000001 ffffffff`ffffffff 00000003`00000000 fffff900`c4efea90 : nt! ?? ::FNODOBFM::`string'+0x4518f fffff880`095a8090 fffff960`00266b8e : fffff900`c0000de0 fffff900`c0000de0 00000000`00000000 00000000`00ffffff : nt!KiPageFault+0x16e fffff880`095a8220 fffff960`000c7e77 : fffff900`c328e000 fffff900`c4f24630 fffff900`c0133010 00000000`00000000 : win32k!PopThreadGuardedObject+0x16 fffff880`095a8250 fffff960`00239eee : fffff900`c328e018 fffff900`c427f018 00000000`00000000 fffff900`c4efeab0 : win32k!FreeThreadBufferWithTag+0x17 fffff880`095a8280 fffff960`000cb49b : ffffffff`c7011d3a fffffa80`107c6b50 fffff880`095a85c0 00000000`0012eef8 : win32k!NtGdiBitBltInternal+0xd76 fffff880`095a8460 fffff800`03091e93 : fffffa80`0fb58580 00000000`00000000 00000000`00000001 00000000`00000000 : win32k!NtGdiBitBlt+0x5b fffff880`095a84d0 000007fe`fe6e25ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0012eed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe6e25ba STACK_COMMAND: kb FOLLOWUP_IP: win32k!PopThreadGuardedObject+16 fffff960`00266b8e 4c8918 mov qword ptr [rax],r11 SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: win32k!PopThreadGuardedObject+16 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 51aeb1a7 FAILURE_BUCKET_ID: X64_0x50_win32k!PopThreadGuardedObject+16 BUCKET_ID: X64_0x50_win32k!PopThreadGuardedObject+16 Followup: MachineOwner ---------
Thanks again!
eagle132