Win7 BSOD while playing

I keep getting Bluescreen of death when playing BFBC2, L4d2 and MW2. It usually comes after playing 5min-1h.

0x0000003b (0x00000000c0000005, 0xfffff960001c6269, 0xfffff8800605d9b0, 0x0000000000000000

Win32k.sys

Windows 7 64
AMD Phenom II 965 3.4ghz
2048MB memory
HIS Radeon 5770
M4a785TD-V EVO

Attachment 71178

Welcome to SF!

We need your dmp files. https://www.sevenforums.com/crash-loc...d-problem.html

All I can tell in the mean time is your bugcheck 3B:

Usual causes: System service, Device driver, graphics driver, ?memory

BSOD Index

As you can see, that's a start, but not very helpful.

I suggest a memory test. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

If it comes out clean, follow these instructions for enabling Driver Verifier: Using Driver Verifier to identify issues with Drivers

Please upload the new dmps that result. I suggest deleting the dmps in the minidump folder now, to avoid confusion with the new dmps.

Code:

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


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp5_Minidump.zip\Minidump\050510-35240-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a14000 PsLoadedModuleList = 0xfffff800`02c51e50
Debug session time: Wed May  5 10:35:53.430 2010 (GMT-4)
System Uptime: 0 days 2:25:26.100
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001c6269, fffff8800605d9b0, 0}

Probably caused by : win32k.sys ( win32k!SetOrClrWF+69 )

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

0: 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: fffff960001c6269, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800605d9b0, 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!SetOrClrWF+69
fffff960`001c6269 488b4808        mov     rcx,qword ptr [rax+8]

CONTEXT:  fffff8800605d9b0 -- (.cxr 0xfffff8800605d9b0)
rax=000000cc4b91650f rbx=fffffa8005b724f0 rcx=0000000000000004
rdx=0000000003218e30 rsi=000000000008ca80 rdi=fffffa8005b724f0
rip=fffff960001c6269 rsp=fffff8800605e380 rbp=fffff8800605e520
 r8=00000000000004fb  r9=0000000000000001 r10=00000000fffff880
r11=0000000006055000 r12=00000000734db1cc r13=000000000008fd20
r14=000000000008d420 r15=0000000073442450
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
win32k!SetOrClrWF+0x69:
fffff960`001c6269 488b4808        mov     rcx,qword ptr [rax+8] ds:002b:000000cc`4b916517=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  steam.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001c6269

STACK_TEXT:  
fffff880`0605e380 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SetOrClrWF+0x69


FOLLOWUP_IP: 
win32k!SetOrClrWF+69
fffff960`001c6269 488b4808        mov     rcx,qword ptr [rax+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!SetOrClrWF+69

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

STACK_COMMAND:  .cxr 0xfffff8800605d9b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!SetOrClrWF+69

BUCKET_ID:  X64_0x3B_win32k!SetOrClrWF+69

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

Had different bluescreen today : 0x000000fc (0xfffff88002f93818, 0x800000002c852963, 0xfffff88002f93510, 0x0000000000000000

I had Driver verifier on, Couldn't get memtest86 working, I tried to burn but instant finish
When i go to CD it say its empty.

Ville said:

Third Bluescreen today 0x0000001e (0xffffffffc000001d, 0xfffff80002af35b1, 0x0000000000000000, 0x8be000005e763800)

Hello !!

I guess the issue is with your Logitech GamePanel Virtual Bus Enumerator (LGBusEnum.sys) try to remove the Drviers completely and

Goto C:\Windows\System32\Drivers and rename LGBusEnum.sys to LGBusEnum.old

Then lets it run without the Drivers and see if crashes again if not then we know its the problem so we can either try with a update driver if that fails then it know be the device itself that is damaged.

Code:

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000024c, A driver has returned STATUS_PENDING but did not mark the IRP pending via a
 call to IoMarkIrpPending.
Arg2: fffff880044a79c4, The address in the driver's code where the error was detected.
Arg3: fffff9803ccbadc0, IRP address.
Arg4: 0000000000000103, Status code.
Debugging Details:
------------------
 
BUGCHECK_STR:  0xc9_24c
DRIVER_VERIFIER_IO_VIOLATION_TYPE:  24c
FAULTING_IP: 
LGBusEnum+29c4
fffff880`044a79c4 4883ec28        sub     rsp,28h
FOLLOWUP_IP: 
LGBusEnum+29c4
fffff880`044a79c4 4883ec28        sub     rsp,28h
IRP_ADDRESS:  fffff9803ccbadc0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002f053dc to fffff80002a7b600
STACK_TEXT:  
fffff880`009e89e8 fffff800`02f053dc : 00000000`000000c9 00000000`0000024c fffff880`044a79c4 fffff980`3ccbadc0 : nt!KeBugCheckEx
fffff880`009e89f0 fffff800`02f0f47a : fffff800`02f039f0 fffff880`044a79c4 fffff980`3ccbadc0 00000000`00000103 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`009e8a30 fffff800`02f1034e : 00000000`0000024c 00000000`00000103 fffff980`3ccbadc0 00000000`fffffffd : nt!ViErrorFinishReport+0xda
fffff880`009e8a80 fffff800`02f1b71f : fffff980`3ccbadc0 fffffa80`05ce3d40 fffffa80`05ce3df8 fffff800`02b96a00 : nt!VfErrorReport6+0x6e
fffff880`009e8b50 fffff800`02f1bb63 : fffffa80`05ce3d40 00000000`00000002 fffffa80`050e0d50 fffff800`02b7e4b2 : nt!IovpCallDriver2+0x13f
fffff880`009e8bb0 fffff800`02f21c2e : fffff980`3ccbadc0 fffff980`3ccbadc0 00000000`00000002 fffffa80`050e0d50 : nt!VfAfterCallDriver+0x353
fffff880`009e8c00 fffff800`02f20c42 : fffff980`3ccbaf20 00000000`00000000 fffffa80`050e0c50 fffffa80`05ce3d40 : nt!IovCallDriver+0x57e
fffff880`009e8c60 fffff800`02b96e15 : 00000000`00000001 00000000`00000000 fffffa80`050e0b00 fffff980`3ccbae68 : nt!ViFilterDispatchPower+0x62
fffff880`009e8c90 fffff800`02d20a86 : 00000000`00000000 fffffa80`018d9b60 00000000`00000080 00000000`00000000 : nt!PopIrpWorker+0x3c5
fffff880`009e8d40 fffff800`02a59b06 : fffff880`02fd5180 fffffa80`018d9b60 fffff880`02fdffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009e8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
SYMBOL_NAME:  LGBusEnum+29c4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: LGBusEnum
IMAGE_NAME:  LGBusEnum.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5d0805
FAILURE_BUCKET_ID:  X64_0xc9_24c_VRF_LGBusEnum+29c4
BUCKET_ID:  X64_0xc9_24c_VRF_LGBusEnum+29c4
Followup: MachineOwner
---------

Hope this helps,
Captain