Blue Screen of Death while playing Battlefield 3

#1
Hello everybody,

I'm expiriencing BSOD while playing Battlefield 3 for the past couple of weeks. Every other game runs normally except BF. I overlocked my CPU a few months ago and everything was fine. Even then I was playing BF3 without any crashes. Now its impossible to play without having crashes every 30 min. I tried higher voltages and reinstalling graphics drivers but that didn't help. Usually I keep all my drivers up to date.

Heres my system:


OS: Windows 7 64 bit
Version 6.1.7601 Service Pack 1 Build 7601
Chassis: Asus Vento A8 (with two 80mm fans)
Motherboard: Asus P5E
[FONT=inherit !important][FONT=inherit !important]Graphics
[FONT=inherit !important]Card[/FONT][/FONT]: XFX 6870 (8.92-111109a-129966C-ATI)
Processor: Core 2 Quad Q6600 2.4GHz (Overclocked to 3.0 GHz, I tried 1.23750 and atm its 1.25000 V)
Aftermarket Cooler: AC Freezer 13 (Arctic Silver 5)
Memory: 6 GB (667 MHz)
PSU: Asus model A-55GA (550W)
Back-UPS CS 500 (APC)



Heres the crash log :


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1050

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF8000316C575
BCP3: FFFFF8800A51B0E0
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\122511-18798-01.dmp
C:\Users\Nino\AppData\Local\Temp\WER-50076-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?li [...] cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


If anybody has any suggestions what might be the problem and how to solve it I would be grateful!



[/FONT]
 


Trouble

Noob Whisperer
#2
Hello and welcome to the forums.
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Confirm that your computer is configured properly for collecting dump files:
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Good luck
Randy
 


#3
Thank you for your reply. I think I gathered all the info you need. Hope we can fix this :)

EDIT: One question, do I have to leave my windows permamently configured as you told me for collecting dump files or should I eventually restore the default settings?
 


Attachments

Last edited:

Trouble

Noob Whisperer
#4
Update the following drivers
yk62x64.sys 9/28/2009 from here Marvell - Support - Driver Downloads get the 11.45.1.3 9/8/11 for your Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller.
ASACPI.sys 3/27/2005 from here ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE expand utilities and it's about the 12th one down (ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit)
GEARAspiWDM.sys 5/18/2009 from here Driver updates - GEAR Software
If Blue Screens persist, remove
hamachi.sys 2/19/2009 Uninstall or rename
and
Avast Uninstall
Temporarily for testing, you can put them back later if they prove not to be at issue. Suggest replacing Avast with MSE for the time being. Reasonably sure that it hasn't been associated with any BSODs to date.
Regards
Randy
 


#5
I did everything you told me and it worked! I played BF3 for almost 2 hours and I havent expirienced a single crash.
Thank you very much for your time and help :)
 


Trouble

Noob Whisperer
#6
Well that's good news and thanks for posting back and updating your thread with that information.
May be a little premature but I'll certainly keep my fingers crossed that your issue is resolved.
If Blue Screens reoccur just return to this thread and attach your latest dump files.
Regards
Randy
 


#7
You are right, it might be premature but I hope its not. Usually I would get BSOD after playing BF3 for about 30 min. Today I played around 2 hours without any problems. Only thing I havent changed is hamachi and the rest I did as you told me. If I get any BSOD again I will report back.
Thank you one more time for helping me out.
 


#8
Unfortunately I expirienced BSOD again while playing BF3. The only difference this time is that it happened after playing for a few hours instead of 30 minutes. I collected the data again so maybe there is something more I can do about this.
 


Attachments

Trouble

Noob Whisperer
#9
Told you it might be a bit premature.
Unfortunately I'm not seeing anything frightening with you latest dump. Looks like the only old driver still hanging around out there is hamachi and of course you already know that.
This one:
Code:
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[U][B]BugCheck 24, {1904fb, fffff8800713e3e8, fffff8800713dc40, fffff880010b2290}[/B][/U]
[U][B]Probably caused by : Ntfs.sys[/B][/U] ( Ntfs!NtfsExtendedCompleteRequestInternal+114 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[U][B]NTFS_FILE_SYSTEM (24)[/B][/U]
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800713e3e8
Arg3: fffff8800713dc40
Arg4: fffff880010b2290
Debugging Details:
------------------
EXCEPTION_RECORD:  fffff8800713e3e8 -- (.exr 0xfffff8800713e3e8)
ExceptionAddress: fffff880010b2290 (fltmgr!FltpPurgeVolumeNameCache+0x0000000000000050)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: ffffffffffffffff
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT:  fffff8800713dc40 -- (.cxr 0xfffff8800713dc40)
rax=83485708245c8948 rbx=fffff88004bd2160 rcx=fffffa80062e0518
rdx=fffff88004bd2101 rsi=0000000000000000 rdi=fffffa80062e0010
rip=fffff880010b2290 rsp=fffff8800713e620 rbp=83485708245c8918
 r8=ffffffffffffffff  r9=ffffffffffffffff r10=fffff80002e59000
r11=fffff8a003b6d208 r12=fffffa80062e0580 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010283
fltmgr!FltpPurgeVolumeNameCache+0x50:
fffff880`010b2290 f083454401      lock add dword ptr [rbp+44h],1 ss:0018:83485708`245c895c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
PROCESS_NAME:  chrome.exe
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  ffffffffffffffff
EXCEPTION_PARAMETER2:  0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003108100
 0000000000000000 
FOLLOWUP_IP: 
Ntfs!NtfsExtendedCompleteRequestInternal+114
fffff880`01255e84 488b5c2450      mov     rbx,qword ptr [rsp+50h]
FAULTING_IP: 
fltmgr!FltpPurgeVolumeNameCache+50
fffff880`010b2290 f083454401      lock add dword ptr [rbp+44h],1
BUGCHECK_STR:  0x24
LAST_CONTROL_TRANSFER:  from fffff880010a9a10 to fffff880010b2290
STACK_TEXT:  
fffff880`0713e620 fffff880`010a9a10 : fffffa80`05a10740 fffffa80`062e0010 00000000`00000000 fffffa80`078b86c0 : fltmgr!FltpPurgeVolumeNameCache+0x50
fffff880`0713e660 fffff880`010a4b9b : fffffa80`062e0010 00000000`00000000 fffffa80`078b86c0 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1a04
fffff880`0713e6a0 fffff880`01084eca : fffffa80`07951010 fffffa80`061259e0 00000000`00000000 0070006d`0075004a : fltmgr!FltpReinstateNameCachingAllFrames+0x4b
fffff880`0713e6d0 fffff800`02ed9021 : 00000000`00000000 fffff800`031d1c81 00000000`00000000 fffff880`01084132 : fltmgr!FltpPassThroughCompletion+0x8a
fffff880`0713e710 fffff880`01255e84 : fffffa80`08376560 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`0713e800 fffff880`012e220c : fffff8a0`10d2d140 fffffa80`0628a180 00000000`00000000 00000000`00000701 : Ntfs!NtfsExtendedCompleteRequestInternal+0x114
fffff880`0713e840 fffff880`01253574 : fffffa80`08376560 fffffa80`081dd010 fffff880`0713e901 fffff880`0713e900 : Ntfs!NtfsCommonSetInformation+0xef3
fffff880`0713e920 fffff880`01081bcf : fffffa80`081dd3b0 fffffa80`081dd010 fffffa80`08376560 fffff880`0713e948 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`0713e9a0 fffff880`010806df : fffffa80`061259e0 fffffa80`081dd010 fffffa80`06125900 fffffa80`081dd010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0713ea30 fffff800`031b5063 : 00000000`000000b4 fffff880`0713eca0 00000000`00000000 fffffa80`0801d230 : fltmgr!FltpDispatch+0xcf
fffff880`0713ea90 fffff800`02ed4ed3 : 00000000`00000c38 fffffa80`0573b900 00000000`0334e5f8 fffff800`000000b4 : nt!NtSetInformationFile+0x91f
fffff880`0713ebb0 00000000`776f158a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0334e5d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776f158a
SYMBOL_STACK_INDEX:  5
SYMBOL_NAME:  Ntfs!NtfsExtendedCompleteRequestInternal+114
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME:  Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b
STACK_COMMAND:  .cxr 0xfffff8800713dc40 ; kb
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114
BUCKET_ID:  X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114
Followup: MachineOwner
Looks more like an issue with your hard disk;
Likely causes: Disk corruption, insufficient physical memory, device driver, disk or drive controller failing or failure.
So we should probably chase down any potential disk issues.
Open an elevated command prompt and type
chkdsk C: /R
hit enter
answer yes "Y" to the prompt
and reboot
Let it finish all five stages and see what that produces in the way of worth while information if any. If you miss the report at the end you can examine the log file in Event Viewer->Windows Logs->Application
Let us know what that produces.
And probably next up you'll likely want to
Download Memtest86+ from this location here. Burn the ISO to a CD and boot the computer from the CD.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Test RAM sticks individually. When you find a good one then test it in all slots. Post back with the results.
See this Guide to using Memtest 86+
Additionally since that particular game seems to really stess the CPU you may want to look into increasing the associated voltage to help support the added burden (vcore or VccIO) you may need to check your motherboard documentation regarding that particular task or perhaps see if there might be a specific support forum for your individual board or board manufacturer where you might get some information regarding the process and its' associated Pro's and Con's. Typically a bump in Vcore will likely result in a slight increase in temps which should be monitored to guard against overheating and possible damage.
 


#10
I have also tried ur steps, going to start game now.. I wil post my feedback soon.

Thanks

Update the following drivers
yk62x64.sys 9/28/2009 from here Marvell - Support - Driver Downloads get the 11.45.1.3 9/8/11 for your Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller.
ASACPI.sys 3/27/2005 from here ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE expand utilities and it's about the 12th one down (ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit)
GEARAspiWDM.sys 5/18/2009 from here Driver updates - GEAR Software
If Blue Screens persist, remove
hamachi.sys 2/19/2009 Uninstall or rename
and
Avast Uninstall
Temporarily for testing, you can put them back later if they prove not to be at issue. Suggest replacing Avast with MSE for the time being. Reasonably sure that it hasn't been associated with any BSODs to date.
Regards
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top