BSOD while playing Torchlight 2, Win32k.sys related. Help appreciated!

[eagle132]

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:

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
---------

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.

Thanks again!
eagle132

 

[koolkat77]

avgidsdrivera.sys           Fri Mar 29 07:40:56 2013 (5154F128)
avgidsha.sys                Fri Feb  8 09:14:48 2013 (51146DA8)
avgldx64.sys                Fri Feb  8 09:14:24 2013 (51146D90)
avgloga.sys                 Fri Feb  8 09:14:29 2013 (51146D95)
avgmfx64.sys                Fri Feb  8 09:14:48 2013 (51146DA8)

AVG is contributing to your BSOD's. Replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials - Microsoft Windows

Malwarebytes Free​

• :info: Do not start the trial version of MalwareBytes
  
  

You may also take a look at:

Good & Free System Security Combination​

Uninstall all VMware software with Revo Uninstaller for the time being.
And, RivaTuner/EVGA Precision/MSI Afterburner (known BSOD issues w/Win7)

   Note

Download and install Revo Uninstaller free from here:

Download Revo Uninstaller Freeware​

Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall Daemon Tools.

dtsoftbus01.sys             Fri Jan 13 19:45:46 2012 (4F10358A)

DuplexSecure - FAQ​

Reduce items at start up:

Performing a Clean Startup in Windows 7

Add, or Remove Startup Programs in Windows 7
​

Your Antivirus software is basically whats just needed there.

Use the System File Checker tool and Run Disk Check:

Repair Windows 7 System Files with System File Checker

Run Disk Check in Windows 7 for Bad Sectors & Errors​

Make scans with -

TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US

Online Virus Scanner Eset​

Test and Diagnose RAM Issues with Memtest86+:

RAM - Test with Memtest86+​

:info: Pay close attention to part 3 of the tutorial "If you have errors"

   Tip

• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

BSOD SUMMARY:

[FONT="Lucida Console"]Debug session time: Wed Jul 24 10:51:55.399 2013 (UTC + 6:00)
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 0:55:36.211
Probably caused by : win32k.sys ( win32k!PopThreadGuardedObject+16 )
BugCheck 50, {ffffffffffffffff, 1, fffff96000266b8e, 0}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000050]PAGE_FAULT_IN_NONPAGED_AREA (50)[/url]
Bugcheck code 00000050
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)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  HWMonitor.exe
FAILURE_BUCKET_ID:  X64_0x50_win32k!PopThreadGuardedObject+16
MaxSpeed:     3400
CurrentSpeed: 3400
BiosVersion = P2.60
BiosReleaseDate = 01/16/2013
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[eagle132]

Thanks so much for the reply! I'll go about some of the steps you listed.

So, for this particular crash, is there no visible specific issue that caused it? I noticed the other issues that you pointed out, though those are mostly from earlier in the year.

I can't help feeling like there's something in particular wrong since this has only happened while playing Torchlight 2. I am hoping that it wasn't a hardware issue. I saw you mentioned running Memtest... could this issue be anything besides memory if it is a hardware issue? I am not experienced enough at reading minidumps to determine this.

Thanks again!

 

[koolkat77]

You can test ram at a later time.