Multiple BSOD playing Battlefield 3

Page 2 of 4 FirstFirst 1234 LastLast

  1. Posts : 17
    Windows 7 Proffesional 64bit
    Thread Starter
       #11

    I borrowed my friends RAM and tried it in my motherboard but it made no difference to the BSOD/Crashes while playing BF3.

    His RAM is:
    2 x Elixir 4GB DDR3 PC3-10600 1333Mhz 240-PIN MEMORY

    If you need more information on it I could try get a hold of it again.
      My Computer


  2. Posts : 17
    Windows 7 Proffesional 64bit
    Thread Starter
       #12

    Mistake
    Last edited by ShaunMac; 06 Mar 2012 at 15:26. Reason: Multi post
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #13

    There have been a lot of BF3 related crashes of late. Check their forums for issues as well. I am more concerned about the problems you have had running Memtest86+ and outside of gaming because that points to a hardware issue.

    For hardware concerns:
    Last edited by writhziden; 06 Mar 2012 at 15:36. Reason: Clear your CMOS
      My Computer


  4. Posts : 17
    Windows 7 Proffesional 64bit
    Thread Starter
       #14

    I ran all the test but was only at the computer for the 2 video test as its the only free time I had to watch it.
    I have attached screens of results I could get, I know the stress test only shows 1 pass, but Im only using that screen to show the code for 'Not Supported'

    Test Results:

    Video:

    FurMark - Run for 15-20min with temperature not exceeding 75*C and no problems showing.
    Memory Stress Test - Run for 7 Passes with no errors, only thing to show up was it saying 'Not Supported'.

    Hardware:

    Prime95 Test 1 - Computer crashed while test was running and I wasn't at the keyboard.
    Prime95 Test 2 - Hardware Failure Detected, 50 Tests in 3h 22min, 1 Error.
    Prime95 Test 3 - Computer crashed while test was running and I wasn't at the keyboard.
    Last edited by ShaunMac; 09 Mar 2012 at 12:36. Reason: Attaching File
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #15

    What CPU temperatures are you getting during Prime95 tests?
      My Computer


  6. Posts : 17
    Windows 7 Proffesional 64bit
    Thread Starter
       #16

    I wasn't actualy at the computer for the test but I will run 1 just now and monitor the temperature of the CPU, which test would be the best to run?
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #17

    In-place large FFTs will maximize the temperature.
      My Computer


  8. Posts : 17
    Windows 7 Proffesional 64bit
    Thread Starter
       #18

    The test found errors twice in the first couple of minutes with a temperature of 46*C, then on a third attempt of testing it ran for 40min before it found an error and blue screened on me mentioning win32k.sys. The teperature was at 49*C.

    I have attached a load of new dumps, the BSOD and crashing seems to be getting worse, they have started happening outside of BF3, and most of the time when the computer tries to restart it wont start. I need to completely power it down before I can get it to load up.
    Last edited by ShaunMac; 09 Mar 2012 at 14:08. Reason: Attaching Files
      My Computer


  9. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #19

    Code:
    Loading Dump File [D:\Kingston\BSODDmpFiles\ShaunMac\Lots More Dumps\Windows_NT6_BSOD_jcgriff2\030812-19593-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 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03090670
    Debug session time: Wed Mar  7 18:15:52.497 2012 (UTC - 7:00)
    System Uptime: 0 days 0:36:26.699
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 24, {1904fb, fffff88002ecb348, fffff88002ecaba0, fffff880012d3f7f}
    
    Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquireAllFiles+7f )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    NTFS_FILE_SYSTEM (24)
        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: fffff88002ecb348
    Arg3: fffff88002ecaba0
    Arg4: fffff880012d3f7f
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_RECORD:  fffff88002ecb348 -- (.exr 0xfffff88002ecb348)
    ExceptionAddress: fffff880012d3f7f (Ntfs!NtfsAcquireAllFiles+0x000000000000007f)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    CONTEXT:  fffff88002ecaba0 -- (.cxr 0xfffff88002ecaba0)
    rax=fffffa8006d839e0 rbx=dffff8a0093da010 rcx=fffffa80079ff370
    rdx=fffffa80079ff370 rsi=fffff8a00009e5c0 rdi=fffffa80079ff180
    rip=fffff880012d3f7f rsp=fffff88002ecb580 rbp=fffff88002ecb960
     r8=fffff8a00944a5c0  r9=fffff8a00944a5e0 r10=fffff88002ecb5d8
    r11=000000000000001a r12=fffffa80072c6900 r13=fffffa8008317500
    r14=0000000000000000 r15=0000000000000001
    iopl=0         nv up ei ng nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
    Ntfs!NtfsAcquireAllFiles+0x7f:
    fffff880`012d3f7f 0fba630408      bt      dword ptr [rbx+4],8 ds:002b:dffff8a0`093da014=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.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:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fa100
     ffffffffffffffff 
    
    FOLLOWUP_IP: 
    Ntfs!NtfsAcquireAllFiles+7f
    fffff880`012d3f7f 0fba630408      bt      dword ptr [rbx+4],8
    
    FAULTING_IP: 
    Ntfs!NtfsAcquireAllFiles+7f
    fffff880`012d3f7f 0fba630408      bt      dword ptr [rbx+4],8
    
    BUGCHECK_STR:  0x24
    
    LAST_CONTROL_TRANSFER:  from fffff880013434fb to fffff880012d3f7f
    
    STACK_TEXT:  
    fffff880`02ecb580 fffff880`013434fb : fffffa80`083175a0 fffff8a0`0944a5c0 00000000`00000001 fffff880`02ecb960 : Ntfs!NtfsAcquireAllFiles+0x7f
    fffff880`02ecb5d0 fffff880`013445be : fffffa80`072c6900 fffffa80`07ab9c10 fffffa80`083175a0 fffffa80`07188150 : Ntfs!NtfsDefragFileInternal+0xaa8
    fffff880`02ecb7a0 fffff880`01304cf2 : fffff880`00000000 fffffa80`06e82370 fffffa80`079ff180 fffffa80`083175a0 : Ntfs!NtfsDefragFile+0x43e
    fffff880`02ecb840 fffff880`012bd53d : fffffa80`072c6900 00000000`00000000 fffff880`02ecb960 00000000`00000000 : Ntfs! ?? ::NNGAKEGL::`string'+0x1d079
    fffff880`02ecb880 fffff880`0105fbcf : fffff880`02ecb9d0 fffffa80`07ab9c10 fffff880`02ecb901 fffffa80`072c6900 : Ntfs!NtfsFsdFileSystemControl+0x13d
    fffff880`02ecb920 fffff880`0107f95e : fffffa80`07963860 fffffa80`06c1ed10 fffffa80`07963800 fffffa80`07ab9c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
    fffff880`02ecb9b0 fffff800`031e2a97 : fffffa80`06c1ed10 fffff880`02ecbca0 fffffa80`07ab9ff8 fffffa80`07ab9c10 : fltmgr!FltpFsControl+0xee
    fffff880`02ecba10 fffff800`031a2342 : fffff680`003b9f00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
    fffff880`02ecbb40 fffff800`02ec6ed3 : 00000000`00000000 0000007f`ffffffff fffff880`02ecbca0 00000980`00000000 : nt!NtFsControlFile+0x56
    fffff880`02ecbbb0 00000000`773816aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00f9eaf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773816aa
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  Ntfs!NtfsAcquireAllFiles+7f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Ntfs
    
    IMAGE_NAME:  Ntfs.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d79997b
    
    STACK_COMMAND:  .cxr 0xfffff88002ecaba0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireAllFiles+7f
    
    BUCKET_ID:  X64_0x24_Ntfs!NtfsAcquireAllFiles+7f
    
    Followup: MachineOwner
    ---------
    Your latest .dmp files are pointing to hard disk corruption.


    Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log


    Run the long and short hard disk tests with SeaTools
      My Computer


  10. Posts : 17
    Windows 7 Proffesional 64bit
    Thread Starter
       #20

    This is my Disk Check log, I will start my scans with SeaTools and get them posted tomorrow.

    I have ran the Short scan with SeaTools in the last couple of weeks and it passed but i will try it again.
      My Computer


 
Page 2 of 4 FirstFirst 1234 LastLast

  Related Discussions
Our Sites
Site Links
About 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 17:36.
Find Us