Windows 7: Win7 BSOD while playing

Jonathan_King · 08 May 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 · 08 May 2010

Okay now i had driver verifier on and bsod again :P

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

zigzag3143 · 08 May 2010

Quote: Originally Posted by Ville

Okay now i had driver verifier on and bsod again :P

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 · 08 May 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 · 09 May 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 · 09 May 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 · 09 May 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 · 09 May 2010

Quote: Originally Posted by Ville

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

Quote: Originally Posted by Ville

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?

Windows 7: Win7 BSOD while playing

Win7 BSOD while playing problems?