Windows 7 Troubleshooting 0x124 BSOD After 40 Minutes of Battlefield 3 Gameplay

Feariss

Senior Member
Joined
Nov 29, 2011
Messages
2
Hi, after I play Battlefield3 for 40/50 minutes i get a 0x124 BSOD. I searched a lot through the internet but none of the solutions I found worked for me, so I hope you can help me.
I read the guide on how to post a help thread and I hope that in the attachment you'll find everything you need (SF Diagnostic files, CPUz screens, rammon report).

Thanks in advance.
 

Attachments

Solution
Hi Feariss and Welcome to The Forum.
Apologies for the delay in a response, you seem to have slipped through the safety net (what safety net?? ).

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes:
Hardware, Incompatibility, May be driver corruption.

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.


As a Priority:

The dtsoftbus driver has been known to cause problems on some Windows 7 systems. This belongs to Daemon Tools Light. I suggest uninstalling until your blue screens are resolved.

You're getting a...
Hi Feariss and Welcome to The Forum.
Apologies for the delay in a response, you seem to have slipped through the safety net (what safety net?? ).

STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes:
Hardware, Incompatibility, May be driver corruption.

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.


As a Priority:

The dtsoftbus driver has been known to cause problems on some Windows 7 systems. This belongs to Daemon Tools Light. I suggest uninstalling until your blue screens are resolved.

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.

Update your bios to the latest available. You'll have to use the Vista x64 OS as an option as Windows 7 isn't listed. ASUSTeK (double check I've the right Mobo!!).

You have two different sets of RAM installed, it may be worth running with only 2gb installed just to check stability. I'd go with the Kingston RAM first, making sure they are installed in the recommended slots for your Mobo. (Note this is only to see if your machine becomes more stable, not to check if you have faulty ram).

Some hardware tests you should be prepared to run:
Run Link Removed
Run the correct Link Removed for your HDD.
Memtest86+ iso download.
Guide to using Memtest86+
Link Removed Run the "Blend" and "Small FFTs" tests (but see below link).
Link Removed


As you are having problems when gaming I would reset the graphics drivers.

  • Download and install Driver Sweeper.
  • Uninstall your current Graphics setup through Programs and Features
  • Boot to (preferably) Safe Mode and run Driver Sweeper to clean up the remnants of your current Graphics set up.
  • Reboot to Normal Mode.
  • Install your new Graphics set up.
  • Link Removed

Then I would stress test the Graphics Card as listed above under Hardware tests.


Bugcheck Analysis:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800444b6d8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner

Your drivers list is very limited, usually happens when the bsod's are saying it's a hardware related fault.
Drivers:
Code:
fffff880`00f8e000 fffff880`00fe5000   ACPI     ACPI.sys     Sat Nov 20 09:19:16 2010 (4CE79294)
fffff880`00ded000 fffff880`00df8000   amdxata  amdxata.sys  Fri Mar 19 16:18:18 2010 (4BA3A3CA)
fffff880`00c86000 fffff880`00c8f000   atapi    atapi.sys    Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`00dc3000 fffff880`00ded000   ataport  ataport.SYS  Sat Nov 20 09:19:15 2010 (4CE79293)
fffff880`00e1b000 fffff880`00edb000   CI       CI.dll       Sat Nov 20 13:12:36 2010 (4CE7C944)
fffff880`01988000 fffff880`019b8000   CLASSPNP CLASSPNP.SYS Sat Nov 20 09:19:23 2010 (4CE7929B)
fffff880`00d08000 fffff880`00d66000   CLFS     CLFS.SYS     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`01000000 fffff880`01072000   cng      cng.sys      Sat Nov 20 10:08:45 2010 (4CE79E2D)
fffff880`019b8000 fffff880`019c6000   crashdmp crashdmp.sys Tue Jul 14 01:01:01 2009 (4A5BCABD)
fffff880`01972000 fffff880`01988000   disk     disk.sys     Tue Jul 14 00:19:57 2009 (4A5BC11D)
fffff880`019d2000 fffff880`019db000   dump_atapi dump_atapi.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`019c6000 fffff880`019d2000   dump_ataport dump_ataport.sys Tue Jul 14 00:19:47 2009 (4A5BC113)
fffff880`019db000 fffff880`019ee000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 00:21:51 2009 (4A5BC18F)
fffff880`01140000 fffff880`01154000   fileinfo fileinfo.sys Tue Jul 14 00:34:25 2009 (4A5BC481)
fffff880`010f4000 fffff880`01140000   fltmgr   fltmgr.sys   Sat Nov 20 09:19:24 2010 (4CE7929C)
fffff880`0122c000 fffff880`01236000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 00:19:45 2009 (4A5BC111)
fffff880`01938000 fffff880`01972000   fvevol   fvevol.sys   Sat Nov 20 09:24:06 2010 (4CE793B6)
fffff880`0182b000 fffff880`01875000   fwpkclnt fwpkclnt.sys Sat Nov 20 09:21:37 2010 (4CE79321)
fffff800`02e13000 fffff800`02e5c000   hal      hal.dll      Sat Nov 20 13:00:25 2010 (4CE7C669)
fffff880`0192f000 fffff880`01938000   hwpolicy hwpolicy.sys Sat Nov 20 09:18:54 2010 (4CE7927E)
fffff880`00e0d000 fffff880`00e15000   intelide intelide.sys Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff800`00bb7000 fffff800`00bc1000   kdcom    kdcom.dll    Sat Feb 05 16:52:49 2011 (4D4D8061)
fffff880`01200000 fffff880`0121b000   ksecdd   ksecdd.sys   Sat Nov 20 09:21:15 2010 (4CE7930B)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Sat Nov 20 10:10:34 2010 (4CE79E9A)
fffff880`00ca5000 fffff880`00cf4000   mcupdate mcupdate.dll Sat Nov 20 13:03:51 2010 (4CE7C737)
fffff880`00c6c000 fffff880`00c86000   mountmgr mountmgr.sys Sat Nov 20 09:19:21 2010 (4CE79299)
fffff880`00fee000 fffff880`00ff8000   msisadrv msisadrv.sys Tue Jul 14 00:19:26 2009 (4A5BC0FE)
fffff880`01154000 fffff880`011b2000   msrpc    msrpc.sys    Sat Nov 20 09:21:56 2010 (4CE79334)
fffff880`0191d000 fffff880`0192f000   mup      mup.sys      Tue Jul 14 00:23:45 2009 (4A5BC201)
fffff880`014a5000 fffff880`01598000   ndis     ndis.sys     Sat Nov 20 09:23:30 2010 (4CE79392)
fffff880`01598000 fffff880`015f8000   NETIO    NETIO.SYS    Sat Nov 20 09:23:13 2010 (4CE79381)
fffff800`02e5c000 fffff800`03445000   nt       ntkrnlmp.exe Thu Jun 23 03:53:23 2011 (4E02AAA3)
fffff880`01246000 fffff880`013e9000   Ntfs     Ntfs.sys     Fri Mar 11 03:39:39 2011 (4D79997B)
fffff880`00d99000 fffff880`00dae000   partmgr  partmgr.sys  Sat Nov 20 09:20:00 2010 (4CE792C0)
fffff880`00d66000 fffff880`00d99000   pci      pci.sys      Sat Nov 20 09:19:11 2010 (4CE7928F)
fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 00:19:48 2009 (4A5BC114)
fffff880`0121b000 fffff880`0122c000   pcw      pcw.sys      Tue Jul 14 00:19:27 2009 (4A5BC0FF)
fffff880`00cf4000 fffff880`00d08000   PSHED    PSHED.dll    Tue Jul 14 02:32:23 2009 (4A5BE027)
fffff880`018e3000 fffff880`0191d000   rdyboost rdyboost.sys Sat Nov 20 09:43:10 2010 (4CE7982E)
fffff880`018d9000 fffff880`018e3000   speedfan speedfan.sys Fri Mar 18 16:08:46 2011 (4D83838E)
fffff880`018d1000 fffff880`018d9000   spldr    spldr.sys    Mon May 11 17:56:27 2009 (4A0858BB)
fffff880`01627000 fffff880`0182b000   tcpip    tcpip.sys    Thu Sep 29 04:43:04 2011 (4E83E948)
fffff880`00e00000 fffff880`00e0d000   vdrvroot vdrvroot.sys Tue Jul 14 01:01:31 2009 (4A5BCADB)
fffff880`01875000 fffff880`01885000   vmstorfl vmstorfl.sys Sat Nov 20 09:57:30 2010 (4CE79B8A)
fffff880`00dae000 fffff880`00dc3000   volmgr   volmgr.sys   Sat Nov 20 09:19:28 2010 (4CE792A0)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Sat Nov 20 09:20:43 2010 (4CE792EB)
fffff880`01885000 fffff880`018d1000   volsnap  volsnap.sys  Sat Nov 20 09:20:08 2010 (4CE792C8)
fffff880`00edb000 fffff880`00f7f000   Wdf01000 Wdf01000.sys Tue Jul 14 00:22:07 2009 (4A5BC19F)
fffff880`00f7f000 fffff880`00f8e000   WDFLDR   WDFLDR.SYS   Tue Jul 14 00:19:54 2009 (4A5BC11A)
fffff880`00fe5000 fffff880`00fee000   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.
 
Last edited:
Solution