Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Bad Company 2 BSOD!!!

31 Mar 2010   #1
chainw0

window 7 professional
 
 
Bad Company 2 BSOD!!!

I recently just buy this game , I am able to ran the game. Play it for 10-15 min.. then it crash into blue screen!!!! 30 min is the max!

[12:08:42 AM] chainw0: Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: 857F7510
BCP2: 91925A50
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


I am attaching the last 3 minidump along with this post... please help T.T



My System SpecsSystem Spec
.
31 Mar 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by chainw0 View Post
I recently just buy this game , I am able to ran the game. Play it for 10-15 min.. then it crash into blue screen!!!! 30 min is the max!

[12:08:42 AM] chainw0: Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: 857F7510
BCP2: 91925A50
BCP3: 00000000
BCP4: 00000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


I am attaching the last 3 minidump along with this post... please help T.T

These were all caused by your video driver. I would get the uninstall tool remove the current driver and re-install a fresh copy


Let us know the results and if you need help

Ken

Code:
032910-27128-01.dmp    3/29/2010 9:31:40 PM        0x00000116    0x87fbb008    0x926f2a30    0x00000000    0x00000002    nvlddmkm.sys    nvlddmkm.sys+e2a30                    32-bit        C:\Users\K\Desktop\minidump\032910-27128-01.dmp    8    15    7600    
033110-22292-01.dmp    3/31/2010 12:06:55 AM        0x00000116    0x857f7510    0x91925a50    0x00000000    0x00000002    nvlddmkm.sys    nvlddmkm.sys+eaa50                    32-bit        C:\Users\K\Desktop\minidump\033110-22292-01.dmp    8    15    7600    
033110-30435-01.dmp    3/31/2010 12:41:40 AM        0x00000116    0x880da0a8    0x91911a50    0x00000000    0x00000002    nvlddmkm.sys    nvlddmkm.sys+eaa50                    32-bit        C:\Users\K\Desktop\minidump\033110-30435-01.dmp    8    15    7600
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\minidump\033110-22292-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82c0a000 PsLoadedModuleList = 0x82d52810
Debug session time: Wed Mar 31 03:05:32.262 2010 (GMT-4)
System Uptime: 0 days 1:00:25.261
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 857f7510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 91925a50, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 82c0a000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b9f3e13

FAULTING_IP: 
nvlddmkm+eaa50
91925a50 55              push    ebp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

CURRENT_IRQL:  0

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8d458b74 923d1adb 00000116 857f7510 91925a50 nt+0xdce10
8d458b98 923d28fa 91925a50 00000000 00000002 dxgkrnl+0x8cadb
8d458bbc 9180692c 00000000 00000102 88136008 dxgkrnl+0x8d8fa
8d458c34 91830a32 fffffcfb 00038ae8 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8d458c5c 91831153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8d458c98 9180d8f0 8d458c90 891e19c8 89078600 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8d458d28 918324b7 88136008 82c463e1 88136008 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8d458d3c 91832573 88136008 00000000 88150948 dxgmms1!VidSchiRun_PriorityTable+0xf
8d458d50 82e1866d 88136008 a9f3aa1b 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8d458d90 82cca1d9 918324f4 88136008 00000000 nt+0x20e66d
00000000 00000000 00000000 00000000 00000000 nt+0xc01d9


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+eaa50
91925a50 55              push    ebp

SYMBOL_NAME:  nvlddmkm+eaa50

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------
My System SpecsSystem Spec
31 Mar 2010   #3
chainw0

window 7 professional
 
 

do u know any recommend uninstall tool???? I am a noob in all of this stuff..
My System SpecsSystem Spec
.

31 Mar 2010   #4
smarteyeball

 
 

Uninstall through Control Panel\Programs\Programs and Features > Uninstall a program and then remove the nvidia component

Alternatively you can uninstall the driver itself through Device Manger > right click on Display Adapters > and select Uninstall from the context menu


To wipe the driver, you can re-boot into safe mode, use Driver Sweeper to analyze / clean the nvidia drivers, rebooting normally and install the latest driver for your card. (install Driver sweeper before booting into safe mode)

Guru3D - Driver Sweeper

it is best to use the driver from nvidias site instead of using Windows Update.
My System SpecsSystem Spec
31 Mar 2010   #5
chainw0

window 7 professional
 
 
still doens't work

Lol
it still crash after I do a clean up on nvidia driver.....I dont really know what is going on anymore.... It's only this game that it happen.

my graphic card is Nvidia GeForce gts 250 1gb any way....
My System SpecsSystem Spec
31 Mar 2010   #6
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by chainw0 View Post
do u know any recommend uninstall tool???? I am a noob in all of this stuff..
Try here. nVidia driver removal tool - NVIDIA Forums

let us know if you need help

Ken
My System SpecsSystem Spec
31 Mar 2010   #7
chainw0

window 7 professional
 
 
It still not working

I still can't get it fix... here is the latest minidump....I am really confuse why doesn't it work... So please help T.T Is it possible that my graphic card is broken? but i have no problem with other game' It's only this Bad company2 that screw my computer over?
My System SpecsSystem Spec
31 Mar 2010   #8
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by chainw0 View Post
I still can't get it fix... here is the latest minidump....I am really confuse why doesn't it work... So please help T.T Is it possible that my graphic card is broken? but i have no problem with other game' It's only this Bad company2 that screw my computer over?
The Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following:
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds



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\033110-30435-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82c56000 PsLoadedModuleList = 0x82d9e810
Debug session time: Wed Mar 31 03:39:34.522 2010 (GMT-4)
System Uptime: 0 days 0:11:48.521
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
......
My System SpecsSystem Spec
31 Mar 2010   #9
chainw0

window 7 professional
 
 
oh yea

i forget to mention this but re install windows before twice and I still have window.old folders...should I delete that? will that help?
My System SpecsSystem Spec
31 Mar 2010   #10
chainw0

window 7 professional
 
 
an dif i need to wipe my os

How do I wipe my hard drive clean??? Do I just install another window over it????
My System SpecsSystem Spec
Reply

 Bad Company 2 BSOD!!!




Thread Tools




Similar help and support threads
Thread Forum
BSOD playing Bad Company 2
Hi, My system is about 2 years old and I've never had any issues with it until last month when my HDD died. I replaced it temporarily with a laptop hdd and I started getting a 0x0..124 error after about 15-20minutes of play. A few days ago my replacement HDD arrived and I seem to get the...
BSOD Help and Support
BSOD while playing Bad Company 2, HELP ME PLEASE !!!
I dont know where to start. Okay, I bought the game on october but couldnt play it properly because of my on board graphics. I bought Sapphire Radeon HD 6670 1gb DDR3 version a few weeks later and lo ! I could the play the game maxed out ! I played online for over a month until about 3 weeks ago, I...
BSOD Help and Support
BSOD during Bad Company 2, unknown error, jcgriff2 BSOD files attached
I recently built a new system. When playing Bad Company 2 I have gotten a consistent BSOD about 1/2 hour into playing. I am not really familiar with BSOD codes and my computer restarted so quickly I was unable to get the exact code. When I play again I will try to get the code and add it to the...
BSOD Help and Support
BSOD playing Bad Company 2
Phenom II X4 955 MSI 890fx XFX 6870 4gb Wintec AMPX DDR3 Samsung F3 500gb Ultra X4 750w PSU Aftermarket VGA cooler Aftermarket CPU cooler WIndows 7 Home 64bit
BSOD Help and Support
BSOD while playing BF bad company 2
I have received 3 BSOD tongiht while trying to play the multiplayer of Bad company 2. It only happens when I play this game and only when I play online. The Stop code I get is 0x00000124 I am running Windows 7 x64 Ultimate. After I restart windows i get an error message saying directx 9 could...
BSOD Help and Support
BSOD when playing Bad Company 2.
Hi, I've started getting BSODs during Bad Company 2 only, here's a report from Bluescreenview: ================================================== Dump File : 031210-20888-01.dmp Crash Time : 12/03/2010 01:39:20 Bug Check String : Bug Check Code : 0x00000124 Parameter...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:50.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App