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: Stop 0x124 with dump data


01 Apr 2011   #1

Windows 7 x64
 
 
Stop 0x124 with dump data

Hey, I have been getting frequent 0x124 stop errors when I play Battlefield: Bad Company 2 Multiplayer and Assassins Creed: Brotherhood Multiplayer. I have no idea what to do. I am using Windows 7 Ultimate x64

I have also read the information page regarding stop 0x124 and nothing has helped.

Here is the dump data related to the Battlefield stop error:fasdf
Opened log file 'c:debuglog.txt'

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\031811-40809-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: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03259000 PsLoadedModuleList = 0xfffff800`03496e50
Debug session time: Fri Mar 18 12:19:00.161 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:08.597
Loading Kernel Symbols
......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8002cb36f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* 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: fffffa8002cb36f8, 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_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02fc06b0 fffff800`03513a99 : fffffa80`02cb36d0 fffffa80`018d1b60 fffff8a0`0000000e 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc0bd0 fffff800`033f5677 : fffffa80`02cb36d0 fffff800`0346e5f8 fffffa80`018d1b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc0c00 fffff800`0335dc45 : fffff800`034d0360 fffffa80`02cff9e8 fffffa80`02cff9e0 fffffa80`018d1b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc0c40 fffff800`032d6961 : fffff880`00c30e00 fffff800`0335dc20 fffffa80`018d1b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc0c70 fffff800`0356c7c6 : 840974cd`3b48004c fffffa80`018d1b60 00000000`00000080 fffffa80`018bcae0 : nt!ExpWorkerThread+0x111
fffff880`02fc0d00 fffff800`032a7c26 : fffff880`009e9180 fffffa80`018d1b60 fffff880`009f3f40 ff58244c`8b480019 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc0d40 00000000`00000000 : fffff880`02fc1000 fffff880`02fbb000 fffff880`02fc0320 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

rax=fffffa8002d94000 rbx=fffffa8002cb36f8 rcx=fffff88002fc06f0
rdx=fffff88002f00000 rsi=0000000000000000 rdi=fffffa8002d94000
rip=fffff800036ff1cc rsp=fffff88002fc06b0 rbp=0000000000000001
r8=000000000000f1e0 r9=000000000000060c r10=00000000000007ff
r11=000000000000060c r12=fffff800034d03c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`036ff1cc 48897c2438 mov qword ptr [rsp+38h],rdi ss:0018:fffff880`02fc06e8=fffffa8000000950
Child-SP RetAddr : Args to Child : Call Site
fffff880`02fc06b0 fffff800`03513a99 : fffffa80`02cb36d0 fffffa80`018d1b60 fffff8a0`0000000e 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fc0bd0 fffff800`033f5677 : fffffa80`02cb36d0 fffff800`0346e5f8 fffffa80`018d1b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fc0c00 fffff800`0335dc45 : fffff800`034d0360 fffffa80`02cff9e8 fffffa80`02cff9e0 fffffa80`018d1b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fc0c40 fffff800`032d6961 : fffff880`00c30e00 fffff800`0335dc20 fffffa80`018d1b60 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fc0c70 fffff800`0356c7c6 : 840974cd`3b48004c fffffa80`018d1b60 00000000`00000080 fffffa80`018bcae0 : nt!ExpWorkerThread+0x111
fffff880`02fc0d00 fffff800`032a7c26 : fffff880`009e9180 fffffa80`018d1b60 fffff880`009f3f40 ff58244c`8b480019 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc0d40 00000000`00000000 : fffff880`02fc1000 fffff880`02fbb000 fffff880`02fc0320 00000000`00000000 : nt!KxStartSystemThread+0x16
start end module name
fffff800`00bca000 fffff800`00bd4000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff800`03210000 fffff800`03259000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff800`03259000 fffff800`03836000 nt ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff880`00c00000 fffff880`00c4c000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`00c50000 fffff880`00c94000 mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00c94000 fffff880`00ca8000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00ca8000 fffff880`00d06000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00d06000 fffff880`00dc6000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00dc6000 fffff880`00df0000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00e00000 fffff880`00e15000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`00e15000 fffff880`00e2a000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00e2a000 fffff880`00e86000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`00e86000 fffff880`00e96000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`00e96000 fffff880`00eb6000 jraid jraid.sys Mon May 31 01:44:28 2010 (4C034CBC)
fffff880`00eb6000 fffff880`00ed0000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00ed0000 fffff880`00ed9000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00ed9000 fffff880`00ee4000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00ee4000 fffff880`00ef8000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00eff000 fffff880`00fa3000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00fa3000 fffff880`00fb2000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00fb2000 fffff880`00fbf000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00fbf000 fffff880`00ff2000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00ff2000 fffff880`00ffe040 PxHlpa64 PxHlpa64.sys Tue Oct 20 14:08:42 2009 (4ADDFCAA)
fffff880`01000000 fffff880`0102f000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`0102f000 fffff880`01086000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`01086000 fffff880`01090000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01090000 fffff880`01097000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`01097000 fffff880`011f4000 sptd sptd.sys Tue Aug 24 02:13:12 2010 (4C7362F8)
fffff880`011f4000 fffff880`011fd000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`01200000 fffff880`013a3000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`013a3000 fffff880`013d3000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`013d3000 fffff880`013e1000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`013e1000 fffff880`013ea000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`013ea000 fffff880`013fd000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`01400000 fffff880`0144c000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`0144c000 fffff880`01486000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`01486000 fffff880`014c0000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`014c4000 fffff880`01522000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`01522000 fffff880`0153c000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`0153c000 fffff880`015af000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`015af000 fffff880`015c0000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`015c0000 fffff880`015ca000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`015ca000 fffff880`015e0000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`015e0000 fffff880`015ea000 avgrkx64 avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21)
fffff880`015ea000 fffff880`015f4000 AVGIDSEH AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE)
fffff880`015f4000 fffff880`01600000 dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01600000 fffff880`0162b000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0162b000 fffff880`01675000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`01675000 fffff880`01685000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`01685000 fffff880`0168d000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0168d000 fffff880`01696000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`01698000 fffff880`0178a000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`0178a000 fffff880`017ea000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`017ea000 fffff880`017fc000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01800000 fffff880`019fd000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458)
Mini Kernel Dump does not contain unloaded driver list
Closing open log file c:debuglog.txt


Here is the dump data related to the Assassins Creed stop error:

Opened log file 'c:debuglog.txt'

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040111-26847-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: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`0321f000 PsLoadedModuleList = 0xfffff800`0345ce50
Debug session time: Fri Apr 1 17:08:59.100 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:06.661
Loading Kernel Symbols
......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8002ccb038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
*******************************************************************************
* *
* 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: fffffa8002ccb038, 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_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02fce6b0 fffff800`034d9a99 : fffffa80`02ccb010 fffffa80`018d9040 00000000`00000002 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fcebd0 fffff800`033bb677 : fffffa80`02ccb010 fffff800`034345f8 fffffa80`018d9040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fcec00 fffff800`03323c45 : fffff800`03496360 fffffa80`02b7aa18 fffffa80`02b7aa10 fffffa80`018d9040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fcec40 fffff800`0329c961 : fffff880`00dd6e00 fffff800`03323c20 fffffa80`018d9040 fffff8a0`00205270 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fcec70 fffff800`035327c6 : fffffdff`bfdf77ff fffffa80`018d9040 00000000`00000080 fffffa80`018c6ae0 : nt!ExpWorkerThread+0x111
fffff880`02fced00 fffff800`0326dc26 : fffff880`009e9180 fffffa80`018d9040 fffff880`009f3f40 feffefff`ffffff77 : nt!PspSystemThreadStartup+0x5a
fffff880`02fced40 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`02fce0d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

rax=fffffa8002d5e000 rbx=fffffa8002ccb038 rcx=fffff88002fce6f0
rdx=fffff88002f00000 rsi=0000000000000000 rdi=fffffa8002d5e000
rip=fffff800036c51cc rsp=fffff88002fce6b0 rbp=0000000000000001
r8=000000000000f1e0 r9=000000000000060c r10=00000000000007ff
r11=000000000000060c r12=fffff800034963c0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000286
nt!WheapCreateLiveTriageDump+0x6c:
fffff800`036c51cc 48897c2438 mov qword ptr [rsp+38h],rdi ss:0018:fffff880`02fce6e8=fffffa8000000950
Child-SP RetAddr : Args to Child : Call Site
fffff880`02fce6b0 fffff800`034d9a99 : fffffa80`02ccb010 fffffa80`018d9040 00000000`00000002 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fcebd0 fffff800`033bb677 : fffffa80`02ccb010 fffff800`034345f8 fffffa80`018d9040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fcec00 fffff800`03323c45 : fffff800`03496360 fffffa80`02b7aa18 fffffa80`02b7aa10 fffffa80`018d9040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fcec40 fffff800`0329c961 : fffff880`00dd6e00 fffff800`03323c20 fffffa80`018d9040 fffff8a0`00205270 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fcec70 fffff800`035327c6 : fffffdff`bfdf77ff fffffa80`018d9040 00000000`00000080 fffffa80`018c6ae0 : nt!ExpWorkerThread+0x111
fffff880`02fced00 fffff800`0326dc26 : fffff880`009e9180 fffffa80`018d9040 fffff880`009f3f40 feffefff`ffffff77 : nt!PspSystemThreadStartup+0x5a
fffff880`02fced40 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`02fce0d0 00000000`00000000 : nt!KxStartSystemThread+0x16
start end module name
fffff800`00bc0000 fffff800`00bca000 kdcom kdcom.dll Mon Jul 13 21:31:07 2009 (4A5BDFDB)
fffff800`0321f000 fffff800`037fc000 nt ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
fffff800`037fc000 fffff800`03845000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08)
fffff880`00c00000 fffff880`00c14000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`00c14000 fffff880`00c20040 PxHlpa64 PxHlpa64.sys Tue Oct 20 14:08:42 2009 (4ADDFCAA)
fffff880`00c25000 fffff880`00c69000 mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
fffff880`00c69000 fffff880`00c7d000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`00c7d000 fffff880`00cdb000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`00cdb000 fffff880`00d9b000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D)
fffff880`00d9b000 fffff880`00da6000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
fffff880`00da6000 fffff880`00df2000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F)
fffff880`00e00000 fffff880`00e20000 jraid jraid.sys Mon May 31 01:44:28 2010 (4C034CBC)
fffff880`00e20000 fffff880`00e3a000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00e3a000 fffff880`00e64000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118)
fffff880`00e67000 fffff880`00f0b000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f0b000 fffff880`00f1a000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f1a000 fffff880`00f71000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106)
fffff880`00f71000 fffff880`00fa4000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`00fa4000 fffff880`01000000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141)
fffff880`01000000 fffff880`01015000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01015000 fffff880`0101c000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`0101c000 fffff880`0102c000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`01032000 fffff880`0118f000 sptd sptd.sys Tue Aug 24 02:13:12 2010 (4C7362F8)
fffff880`0118f000 fffff880`01198000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`01198000 fffff880`011c7000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
fffff880`011c7000 fffff880`011d1000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`011d1000 fffff880`011de000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`011de000 fffff880`011f3000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`011f3000 fffff880`011fc000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01200000 fffff880`01230000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
fffff880`01230000 fffff880`0123e000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`0123e000 fffff880`0124a000 dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`0124c000 fffff880`013ef000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F)
fffff880`01400000 fffff880`0143a000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
fffff880`0143a000 fffff880`01474000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2)
fffff880`01474000 fffff880`0147e000 AVGIDSEH AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE)
fffff880`01485000 fffff880`014e3000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C)
fffff880`014e3000 fffff880`014fd000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156)
fffff880`014fd000 fffff880`01570000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814)
fffff880`01570000 fffff880`01581000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`01581000 fffff880`0158b000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0158b000 fffff880`015d7000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128)
fffff880`015d7000 fffff880`015ed000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`015ed000 fffff880`015f7000 avgrkx64 avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21)
fffff880`015f7000 fffff880`01600000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`01600000 fffff880`0162b000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4)
fffff880`0162b000 fffff880`01675000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
fffff880`01675000 fffff880`01685000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
fffff880`01685000 fffff880`0168d000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0168d000 fffff880`0169f000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`016a1000 fffff880`01793000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
fffff880`01793000 fffff880`017f3000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A)
fffff880`017f3000 fffff880`017fc000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
fffff880`01800000 fffff880`019fd000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458)
fffff880`03ae2000 fffff880`03af5000 dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
Mini Kernel Dump does not contain unloaded driver list
Closing open log file c:debuglog.txt

Any help would be appreciated.

My System SpecsSystem Spec
.

01 Apr 2011   #2

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

http://www.sevenforums.com/crashes-d...tructions.html
Stop 0x124 - what it means and what to try

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative: Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
My System SpecsSystem Spec
02 Apr 2011   #3

Windows 7 x64
 
 

Thanks for the reply DeanP. I checked to see if CD virtualization programs had been installed before removing them and then I removed the sptd.sys as per your instructions. However, I still ran into a stop 0x124. Attached to this is a rar folder that contains the minidump file, system health report, Windows_NT6_BSOD_jcgriff2 folder and the dump data debuglog file. Hope this is more than enough information. The information was created April 2, 2011.

Attachment 147041
My System SpecsSystem Spec
.


02 Apr 2011   #4

Windows Server 2008 R2
 
 

Code:
// CPU Information (sysinfo doesn't work - dump doesn't contain the smbios info, so I have to use the raw data):
1: kd> !cpuinfo
CP  F/M/S Manufacturer  MHz PRCB Signature    MSR 8B Signature Features
 1  6,23,10 GenuineIntel 3603 00000a0700000000                   215b3ffe
 
// The WHEA error record (relevant) information:
1: kd> !errrec fffffa8002c80378
...
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8002c80488
Section       @ fffffa8002c80610
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800
I'm looking at the CPU (Family 6, Model 23, Stepping 10), and it appears this is either an Intel Q8300 - Q9550 (2.5 - 2.66GHz) or a Xeon X3xxx (up to 2.83GHz)? Given Intel's re-use of model and stepping, I could be wrong (I can't see the metadata via smbios, as previously mentioned, and you didn't fill out your system specs, so I'm using Intel's documentation as a guide instead). However, if this CPU falls anywhere in those ranges, it is way overclocked, and that could be the root of all evil here.
My System SpecsSystem Spec
02 Apr 2011   #5

Windows 7 x64
 
 

Hey cluberti,

I apologize for that. I just updated my system specs. I'm using an E8400 and overlocked it to 3.6Ghz. The problems occurred even before the overclocking of my processor, well, at least it did for Bad Company 2.
My System SpecsSystem Spec
02 Apr 2011   #6

Windows Server 2008 R2
 
 

It would be beneficial to set it back, make sure your drivers are all updated, and then post any new dump data after those two are taken care of. Overclocking is the #1 culprit for a CPU-related stop 0x124 - bad CPUs (overclocked or not) will cause it. The second most likely cause is bad RAM, the third a bad video card, in that order, although the fact you're (very) overclocked would indicate that's the best place to start troubleshooting, and move on from there.
My System SpecsSystem Spec
21 Apr 2011   #7

Windows 7 x64
 
 

Hey cluberti, sorry for the late reply. I underwent shoulder surgery recently and one of my arms is in a sling so I was unable to do any testing (gameing to see if I continued to experience stop 0x124) I set back my CPU to original settings and I made sure all my drivers are updated. I also removed the sptd.sys as per your instructions. I recently crashed again and I'm starting to think that I have a bad CPU. Attached is the new info relating to the recent crash.

Attachment 150435
My System SpecsSystem Spec
21 Apr 2011   #8

Windows 7 Ultimate 32 bit
 
 

Hi, Cadex. Cluberti is not online right now. Your latest dump is another bugcheck 124. Following up on his analysis, I suggest that you stress test your CPU and your RAM using Prime95. Follow the instructions in this tutorial: http://www.sevenforums.com/tutorials...t-prime95.html. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results.

Outdated drivers can cause stop error 124 and I found two out dated drivers loading on your system.

Update your Razer Mouse driver to a driver dated July 13, 2009 or later. If there is no update, upgrade your mouse to one certified compatible with Win 7. Use the link below. This driver is quite obsolete.
Quote:
Lachesis.sys 8/17/2007 - Razer Lachesis Mouse driver. Razer Support
Your sound card driver is a little out of date. Try to update it through your motherboard manufacturer's website. You might consider upgrading your sound card.
Quote:
ADIHdAud.sys 5/21/2009 - SoundMAX Digital HD Audio Driver. OEM - none at Analog Devices | Semiconductors and Signal Processing ICs
Once you get your system stable, I recommend updating your OS by installing Service Pack 1.

Code:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03263000 PsLoadedModuleList = 0xfffff800`034a0e50
Debug session time: Thu Apr 21 16:48:24.317 2011 (GMT-4)
System Uptime: 0 days 0:00:07.956
Loading Kernel Symbols
.....................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8002a6e038, 0, 0}

Probably caused by : hardware

Followup: MachineOwner
---------
My System SpecsSystem Spec
22 Apr 2011   #9

Windows 7 x64
 
 

Thanks for the reply CarlTR6. I have updated the Razer Lachesis driver through your link and the Soundmax drivers through the Asus website. I have stress tested my CPU and RAM with Prime95 before for 2 hours with no errors but I will test again with your suggested settings and I will post the results.

I also have a spare CPU (Intel e8400) that I could swap out but currently unable to do so at the moment because of recent shoulder surgery and the corresponding arm being in a sling. I will swap out CPU when I am able to do so. I will keep you and others updated throughout the process of this issue.
My System SpecsSystem Spec
22 Apr 2011   #10

Win 7 Pro x64 SP1 OS X Snow Leopard 10.6.7
 
 

Keep us posted and sorry to hear about your recent shoulder surgery - Get well soon...!

Dean
My System SpecsSystem Spec
Reply

 Stop 0x124 with dump data




Thread Tools



Similar help and support threads for2: Stop 0x124 with dump data
Thread Forum
Stop 0x124 - what it means and what to try Crash and lockup debug 'How To'
Stop 0x124 Troubleshooting - 'New Method' Crash and lockup debug 'How To'
Random BSODs, STOP 0x124 BSOD Help and Support
BSOD stop 0x124 BSOD Help and Support
Win 7 BSOD stop 0x124 BSOD Help and Support
0x124 STOP Error - Possible nVidia? 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 10:34 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33