BSOD during Battlefield 3 Multiplayer and after

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Flower, Jan 3, 2012.

  1. Flower

    Flower New Member

    Joined:
    Jan 3, 2012
    Messages:
    6
    Likes Received:
    1
    Hello,
    First time asking for help on these forums so tell me if I missed something. I have attached all the info according to the sticky, however there were 4 total BSODs during the past 2 days but only infodumps were recorded, not sure why. I have owned BF3 for a while and the first time this issue happened yesterday, I thought that it must be some random error but then it happened again 20 minutes later. I looked up the issue online and assumed that it must be Punkbuster interfering with RealTek audiodrivers (other people are having that issue) so I tried reinstalling Punkbuster but that did not fix it and shortly after quitting the game the PC crashed. Today I did not even play the dam game but the computer crashed shortly after i QUIT playing a different game (Dawn of War 2 : Retribution) so now i am concerned whether BSOD is contained to just BF 3.

    I have attached the folder but if you need additional info please do no hesitate to ask.
     

    Attached Files:

  2. Flower

    Flower New Member

    Joined:
    Jan 3, 2012
    Messages:
    6
    Likes Received:
    1
    Here is what I have done since the last post:
    memtest 86+ (time only for 2 passes but no errors)
    Increased vcore to 1.4 (max 1.5)
    CPU stress test, RAM stress test, GPU stress tests (no bsod during or after)


    However, with a minute or two AFTER playing a graphically intensive game I got a BSOD, while browsing the web. The codes was 124 and I have attached the minidump file. When I was booting up the bios message read: Hyper transport sync flood error has occurred during the last boot attempt>.
     

    Attached Files:

  3. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    Hi flower and Welcome to The Forum.

    Your latest dump file lists hardware as the probable cause.
    Old and incompatible drivers can and do cause issues with Windows 7, often giving false error codes. Random stop codes can often indicate hardware issues.

    You're getting a stop0x124, which means blame the hardware.

    Stop 0x124 Checks
    • Ensure that none of the hardware is being over-clocked.
    • Ensure that the machine is adequately cooled. Chase out those dust bunnies!
    • Make sure all hardware related drivers are up to date.
    • Possibly update the motherboard BIOS according to the manufacturer's instructions.
    • Always keep The Windows system itself up to date.
    See this thread for additional pointers: Stop 0x124 - what to try.

    As a Priority:

    sptd.sys Sun Feb 27 19:29:52 2011 The sptd.sys driver is notorious for causing BSOD's with Windows 7. It's a driver used and installed along with Daemon Tools and Alcohol 120 which you'll also have to uninstall.
    Then use the correct (32bit or 64bit) download from Duplex Secure - Downloads to uninstall the SPTD.SYS driver.
    Make sure to select the uninstall button! DO NOT SELECT INSTALL!!

    Drivers that pre-date Windows 7. Update:

    speedfan.sys Sun Sep 24 14:26:48 2006 Speedfan.

    Bugcheck Analysis:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa80069518f8, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa80069518f8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031bd6f0 fffff800`03115979 : fffffa80`069518d0 fffffa80`0521a680 fffffa80`051da660 fffff880`00fc9efe : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`031bdc10 fffff800`02ff75c7 : fffffa80`069518d0 fffff800`030705f8 fffffa80`0521a680 fffffa80`06117860 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`031bdc40 fffff800`02f5fb55 : fffff800`030d2360 fffffa80`06117860 fffffa80`06117860 fffffa80`0521a680 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`031bdc80 fffff800`02ed8961 : fffff800`03070500 fffff800`02f5fb30 fffffa80`0521a680 00000554`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`031bdcb0 fffff800`0316ebc6 : 00000554`00000000 fffffa80`0521a680 00000000`00000080 fffffa80`05209040 : nt!ExpWorkerThread+0x111
    fffff880`031bdd40 fffff800`02ea9bc6 : fffff880`02f64180 fffffa80`0521a680 fffff880`02f6efc0 00000554`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd2c0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: hardware
    
    IMAGE_NAME:  hardware
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    Drivers:
    Code:
    fffff880`02cb5000 fffff880`02d01000   a5zon6sp a5zon6sp.SYS Sat Jan 08 21:47:20 2011 (4D28DB68)
    fffff880`01186000 fffff880`011dd000   ACPI     ACPI.sys     Tue Jul 14 00:19:34 2009 (4A5BC106)
    fffff880`00fd5000 fffff880`00fe0000   amdxata  amdxata.sys  Tue May 19 18:56:59 2009 (4A12F2EB)
    fffff880`00fa2000 fffff880`00fab000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`00fab000 fffff880`00fd5000   ataport  ataport.SYS  Tue Jul 14 00:19:52 2009 (4A5BC118)
    fffff880`0143a000 fffff880`01442000   AtiPcie  AtiPcie.sys  Tue May 05 16:00:22 2009 (4A005486)
    fffff880`00cc0000 fffff880`00d80000   CI       CI.dll       Tue Jul 14 02:32:13 2009 (4A5BE01D)
    fffff880`01200000 fffff880`01230000   CLASSPNP CLASSPNP.SYS Tue Jul 14 00:19:58 2009 (4A5BC11E)
    fffff880`00c62000 fffff880`00cc0000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`014c7000 fffff880`0153a000   cng      cng.sys      Tue Jul 14 00:49:40 2009 (4A5BC814)
    fffff880`01230000 fffff880`0123e000   crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
    fffff880`015e4000 fffff880`015fa000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`013e7000 fffff880`013f0000   dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`01442000 fffff880`0144e000   dump_ataport dump_ataport.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
    fffff880`00e00000 fffff880`00e13000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
    fffff880`00fe0000 fffff880`00ff4000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
    fffff880`00d80000 fffff880`00dcc000   fltmgr   fltmgr.sys   Tue Jul 14 00:19:59 2009 (4A5BC11F)
    fffff880`0154b000 fffff880`01555000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
    fffff880`01400000 fffff880`0143a000   fvevol   fvevol.sys   Sat Sep 26 03:34:26 2009 (4ABD7DB2)
    fffff880`0162b000 fffff880`01675000   fwpkclnt fwpkclnt.sys Tue Jul 14 00:21:08 2009 (4A5BC164)
    fffff800`02e12000 fffff800`02e5b000   hal      hal.dll      Tue Jul 14 02:27:36 2009 (4A5BDF08)
    fffff880`015db000 fffff880`015e4000   hwpolicy hwpolicy.sys Tue Jul 14 00:19:22 2009 (4A5BC0FA)
    fffff800`00bac000 fffff800`00bb6000   kdcom    kdcom.dll    Sat Feb 05 12:21:45 2011 (4D4D40D9)
    fffff880`014ad000 fffff880`014c7000   ksecdd   ksecdd.sys   Tue Jul 14 00:20:54 2009 (4A5BC156)
    fffff880`01600000 fffff880`0162b000   ksecpkg  ksecpkg.sys  Fri Dec 11 06:03:32 2009 (4B21E0B4)
    fffff880`00c41000 fffff880`00c4e000   mcupdate mcupdate.dll Tue Jul 14 02:29:09 2009 (4A5BDF65)
    fffff880`00f88000 fffff880`00fa2000   mountmgr mountmgr.sys Tue Jul 14 00:19:54 2009 (4A5BC11A)
    fffff880`011e6000 fffff880`011f0000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
    fffff880`0144f000 fffff880`014ad000   msrpc    msrpc.sys    Tue Jul 14 00:21:32 2009 (4A5BC17C)
    fffff880`017ea000 fffff880`017fc000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
    fffff880`01698000 fffff880`0178a000   ndis     ndis.sys     Tue Jul 14 00:21:40 2009 (4A5BC184)
    fffff880`0178a000 fffff880`017ea000   NETIO    NETIO.SYS    Tue Jul 14 00:21:46 2009 (4A5BC18A)
    fffff800`02e5b000 fffff800`03437000   nt       ntkrnlmp.exe Sat Apr 09 05:14:44 2011 (4D9FDD34)
    fffff880`01244000 fffff880`013e7000   Ntfs     Ntfs.sys     Tue Jul 14 00:20:47 2009 (4A5BC14F)
    fffff880`01000000 fffff880`01015000   partmgr  partmgr.sys  Tue Jul 14 00:19:58 2009 (4A5BC11E)
    fffff880`00ed4000 fffff880`00f07000   pci      pci.sys      Tue Jul 14 00:19:51 2009 (4A5BC117)
    fffff880`01015000 fffff880`0101c000   pciide   pciide.sys   Tue Jul 14 00:19:49 2009 (4A5BC115)
    fffff880`00f78000 fffff880`00f88000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
    fffff880`0153a000 fffff880`0154b000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
    fffff880`00c4e000 fffff880`00c62000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
    fffff880`015a1000 fffff880`015db000   rdyboost rdyboost.sys Tue Jul 14 00:34:34 2009 (4A5BC48A)
    fffff880`02d01000 fffff880`02d30000   SCSIPORT SCSIPORT.SYS Tue Jul 14 01:01:04 2009 (4A5BCAC0)
    fffff880`0168d000 fffff880`01694000   speedfan speedfan.sys Sun Sep 24 14:26:48 2006 (45168798)
    fffff880`01685000 fffff880`0168d000   spldr    spldr.sys    Mon May 11 17:56:27 2009 (4A0858BB)
    fffff880`01020000 fffff880`01186000   sptd     sptd.sys     Sun Feb 27 19:29:52 2011 (4D6AA630)
    fffff880`01800000 fffff880`019fd000   tcpip    tcpip.sys    Mon Apr 25 03:47:33 2011 (4DB4E0C5)
    fffff880`011f0000 fffff880`011fd000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
    fffff880`01675000 fffff880`01685000   vmstorfl vmstorfl.sys Tue Jul 14 00:42:54 2009 (4A5BC67E)
    fffff880`00f07000 fffff880`00f1c000   volmgr   volmgr.sys   Tue Jul 14 00:19:57 2009 (4A5BC11D)
    fffff880`00f1c000 fffff880`00f78000   volmgrx  volmgrx.sys  Tue Jul 14 00:20:33 2009 (4A5BC141)
    fffff880`01555000 fffff880`015a1000   volsnap  volsnap.sys  Tue Jul 14 00:20:08 2009 (4A5BC128)
    fffff880`00e21000 fffff880`00ec5000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
    fffff880`00ec5000 fffff880`00ed4000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
    fffff880`011dd000 fffff880`011e6000   WMILIB   WMILIB.SYS   Tue Jul 14 00:19:51 2009 (4A5BC117)
    Mini Kernel Dump does not contain unloaded driver list
    Let us know how it goes. If you get further problems with blue screens, attach your new dump files and details and we'll move on from there.


    HTH.
     
  4. Flower

    Flower New Member

    Joined:
    Jan 3, 2012
    Messages:
    6
    Likes Received:
    1
    Hello,
    I have followed your advice about checking hardware:turned up fans, opened the tower, made sure everything is properly connected, and cleaned everything out.I found the main cause of the problem: huge amount of dust in the heatsink for the CPU water cooling system. My CPU and core temperatures have fallen by about 10-20 C during idle times and barely increase during load times. No BSODs so far so thank you for your help, I will reply after a few days if it holds. In the meantime, I will perform the reccommended software changes.

    Once again thank you for your help and time, greatly appreciated.
     
    1 person likes this.
  5. Elmer

    Elmer Extraordinary Member

    Joined:
    Mar 5, 2010
    Messages:
    3,873
    Likes Received:
    284
    Fingers crossed for you :up:
     

Share This Page

Loading...