Win7 BSOD while playing

Ville · May 5, 2010

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

View attachment 71178

Jonathan_King · May 5, 2010

Welcome to SF!

We need your dmp files. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-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.

Ville · May 5, 2010

Ty.

I added the Dmp file.

Jonathan_King · May 5, 2010

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: http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

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

Ville · May 7, 2010

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 · May 7, 2010

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

Capt.Jack Sparrow · May 7, 2010

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:

[B][COLOR=red]DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)[/COLOR][/B]
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:  [B][COLOR=red]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR][/B]
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:  [B][COLOR=red]LGBusEnum.sys[/COLOR][/B]
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

Ville · May 8, 2010

Ok, I'm trying that. Do i need have Driver verifier still on?

jcgriff2 · May 8, 2010

Yes. . . After you update the driver flagged, run the Driver Verifier again as it may pick up another rogue driver.

Regards. . .

jcgriff2

.

Ville · May 8, 2010

I was hoping that would fix the BSOD once for all but it didnt. :/ At least got only one, usually i get two or three.

Didn't have Driver verifier on but perhaps this help little.

Jonathan_King · May 8, 2010

Try updating your video card drivers.

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\050910-29109-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`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Sat May  8 17:21:08.645 2010 (GMT-4)
System Uptime: 0 days 11:05:07.941
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88004023ca8, fffff88006d00fc0, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::IsAllocationInUse+20 )

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

Ville · May 8, 2010

Okay now i had driver verifier on and bsod again

Edit1: I have latest Ati and Bios drivers, :/

zigzag3143 · May 8, 2010

Ville said:
Okay now i had driver verifier on and bsod again

Edit1: I have latest Ati and Bios drivers, :/

This one was probably caused by BFBC2(b).exe. Several possible reasons. If it is a beta thats one, memory is another.

I would re-install the newest version of the game.

Ken

Code:

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


Loading Dump File [C:\Users\K\Desktop\050910-30778-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;srv*e:\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`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Sat May  8 20:56:05.684 2010 (GMT-4)
System Uptime: 0 days 3:25:41.578
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, 2, 1, fffff80002a974b2}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+f2 )

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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002a974b2, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc30e0
 0000000000000008 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+f2
fffff800`02a974b2 48894808        mov     qword ptr [rax+8],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:   BFBC2Game.exe

TRAP_FRAME:  fffff80000ba2cd0 -- (.trap 0xfffff80000ba2cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80002c08ca8
rdx=0000000000000051 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a974b2 rsp=fffff80000ba2e60 rbp=00000000000c1251
 r8=fffff80002c2f290  r9=00000000000000c1 r10=0000000000000051
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac po cy
nt!KiTimerExpiration+0xf2:
fffff800`02a974b2 48894808        mov     qword ptr [rax+8],rcx ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a8ab69 to fffff80002a8b600

STACK_TEXT:  
fffff800`00ba2b88 fffff800`02a8ab69 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`00ba2b90 fffff800`02a897e0 : 00000000`00000282 0000001c`bc2761f7 00000000`74012450 00000000`74012450 : nt!KiBugCheckDispatch+0x69
fffff800`00ba2cd0 fffff800`02a974b2 : 0000001c`bc2713d6 fffff800`00ba2e88 00000000`000c1251 fffff800`02c08ca8 : nt!KiPageFault+0x260
fffff800`00ba2e60 fffff800`02a96d97 : fffff800`02c05ec1 fffffa80`000c1251 00000000`00000000 00000000`00000051 : nt!KiTimerExpiration+0xf2
fffff800`00ba2f00 fffff800`02a91765 : 00000000`00000000 fffffa80`05878b60 00000000`00000000 fffff880`040c6588 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`02a9157c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`027d39e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+f2
fffff800`02a974b2 48894808        mov     qword ptr [rax+8],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+f2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiTimerExpiration+f2

BUCKET_ID:  X64_0xA_VRF_nt!KiTimerExpiration+f2

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

Ville · May 8, 2010

Had another bsod after last one with different message
Its not beta, and i have the latest version of the game. :/
I'm trying to get memtest86 working.

Ville · May 9, 2010

Another BSOD :/ this time it was : 0x0000003b
I dont know how to boot memtest86. :/ I'm going to Re-install Bfbc2.

Sry for double post.

Jonathan_King · May 9, 2010

Looks like bad RAM. 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.

To boot from the CD after you burn it, set the CD drive to be the first in the priority list for boot devices in your BIOS. You can also manually boot from the drive by using the popup boot menu (F11 or F12 during BIOS POST).

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\Temp6_Minidump.zip\Minidump\050910-20389-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`02a10000 PsLoadedModuleList = 0xfffff800`02c4de50
Debug session time: Sun May  9 06:41:09.717 2010 (GMT-4)
System Uptime: 0 days 0:18:04.395
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff80002d2ab32, fffff88007426a30, 0}

Probably caused by : hardware ( nt!SepAdtAuditPrivilegeUseWithContext+2 )

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

Ville · May 9, 2010

After hundreds tries I couldn't get the memtest86 working. :/ So I used windows memory diagnostic and I setted it to pass 6 time and it came clean, no errors on memory :/
Perhaps I dont have enough memory and thats why its crashing ? Only got 2GB.

zigzag3143 · May 9, 2010

Ville said:
After hundreds tries I couldn't get the memtest86 working. :/ So I used windows memory diagnostic and I setted it to pass 6 time and it came clean, no errors on memory :/
Perhaps I dont have enough memory and thats why its crashing ? Only got 2GB.

1- 64 bit or 32?

2-Memtestx86 needs to be burned to a cd.

3- windows memory diag does not stress the memory enough. If you cant get memtest to run use prime95 instead, but it really does look like ram.

4- when running any ram test you need to run it for several passes in a row to stress it
\

Ken

Ville · May 9, 2010

I have 64. I burned it to a CD but when i boot from it, its just blank 10 sec and boots normally. And it passed six time in row.

zigzag3143 · May 9, 2010

Ville said:
I have 64. I burned it to a CD but when i boot from it, its just blank 10 sec and boots normally. And it passed six time in row.

DO you have boot from cd enabled in BIOS?

Win7 BSOD while playing

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Crash Dump Analyst

My Computer

New member

My Computer

Account closed

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer