1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Stop 0x124 with DUMP DATA

Discussion in 'Windows 7' started by Cadx, 2011/04/01.

  1. 2011/04/01
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    Hey, I have been experiencing frequent 0x124 stop errors. I have no idea what to do with this. The stops only happen when I play Battlefield: Bad Company 2 multiplayer and Assassin's Creed: Brotherhood multiplayer. The following information pertains to the dump:

    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
     
    Cadx,
    #1
  2. 2011/04/03
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    You are having hardware problems. It may very well be your CPU.

    First I would check your temperatures, running a stress test.

    Next test your memory.

    See what you find.
     
    Arie,
    #2

  3. to hide this advert.

  4. 2011/04/12
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    Hey Arie, thanks for your reply. I have been thinking that it may be my CPU as well. All my temps are reasonable, I suppose, and I have already ran stress tests and memory tests with no problems. I have a spare e8400 processor I can try switching but not able to do so at the moment with one of my arms being in a sling from shoulder surgery. I can try running tests again.
     
    Cadx,
    #3
  5. 2011/04/13
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    OK, keep us updated.
     
    Arie,
    #4
  6. 2011/05/03
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    Hey Arie, I just got the okay from my doctor to remove the sling. I will replace my CPU at my earliest convenience and post back.
     
    Cadx,
    #5
  7. 2011/05/10
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    I replaced my CPU and RAM also and haven't encountered any errors so far. I will post back with any updates.
     
    Cadx,
    #6
  8. 2011/05/10
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    I guess I spoke too soon. Even though I replaced my CPU and RAM I still encountered the 0x124 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\051011-26301-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`03217000 PsLoadedModuleList = 0xfffff800`03454e50
    Debug session time: Tue May 10 14:37:20.785 2011 (UTC - 4:00)
    System Uptime: 0 days 0:00:08.424
    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, fffffa8002a60748, 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: fffffa8002a60748, 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`02fce6f0 fffff800`034d1a99 : fffffa80`02a60720 fffffa80`018da680 fffff8a0`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`02fcec10 fffff800`033b3677 : fffffa80`02a60720 fffff800`0342c5f8 fffffa80`018da680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`02fcec40 fffff800`0331bc45 : fffff800`0348e360 fffffa80`02a1dae8 fffffa80`02a1dae0 fffffa80`018da680 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02fcec80 fffff800`03294961 : fffff880`010a6e00 fffff800`0331bc20 fffffa80`018da680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02fcecb0 fffff800`0352a7c6 : 00000000`00000000 fffffa80`018da680 00000000`00000080 fffffa80`018c7040 : nt!ExpWorkerThread+0x111
    fffff880`02fced40 fffff800`03265c26 : fffff880`009e9180 fffffa80`018da680 fffff880`009f3f40 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
    fffff880`02fced80 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`03748750 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=fffffa8002af9000 rbx=fffffa8002a60748 rcx=fffff88002fce730
    rdx=fffffa800180e000 rsi=0000000000000000 rdi=fffffa8002af9000
    rip=fffff800036bd1cc rsp=fffff88002fce6f0 rbp=0000000000000001
    r8=000000000000f1e0 r9=000000000000060c r10=00000000000007ff
    r11=000000000000060c r12=fffff8000348e3c0 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`036bd1cc 48897c2438 mov qword ptr [rsp+38h],rdi ss:0018:fffff880`02fce728=fffffa8000000910
    Child-SP RetAddr : Args to Child : Call Site
    fffff880`02fce6f0 fffff800`034d1a99 : fffffa80`02a60720 fffffa80`018da680 fffff8a0`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`02fcec10 fffff800`033b3677 : fffffa80`02a60720 fffff800`0342c5f8 fffffa80`018da680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`02fcec40 fffff800`0331bc45 : fffff800`0348e360 fffffa80`02a1dae8 fffffa80`02a1dae0 fffffa80`018da680 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02fcec80 fffff800`03294961 : fffff880`010a6e00 fffff800`0331bc20 fffffa80`018da680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02fcecb0 fffff800`0352a7c6 : 00000000`00000000 fffffa80`018da680 00000000`00000080 fffffa80`018c7040 : nt!ExpWorkerThread+0x111
    fffff880`02fced40 fffff800`03265c26 : fffff880`009e9180 fffffa80`018da680 fffff880`009f3f40 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x5a
    fffff880`02fced80 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`03748750 00000000`00000000 : nt!KxStartSystemThread+0x16
    start end module name
    fffff800`00bb9000 fffff800`00bc3000 kdcom kdcom.dll Sat Feb 05 07:21:45 2011 (4D4D40D9)
    fffff800`03217000 fffff800`037f4000 nt ntkrnlmp.exe Tue Oct 26 22:43:09 2010 (4CC791BD)
    fffff800`037f4000 fffff800`0383d000 hal hal.dll Mon Jul 13 21:27:36 2009 (4A5BDF08)
    fffff880`00c00000 fffff880`00cc0000 CI CI.dll Mon Jul 13 21:32:13 2009 (4A5BE01D)
    fffff880`00ccc000 fffff880`00d10000 mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
    fffff880`00d10000 fffff880`00d24000 PSHED PSHED.dll Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`00d24000 fffff880`00d82000 CLFS CLFS.SYS Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00d82000 fffff880`00da2000 jraid jraid.sys Mon May 31 01:44:28 2010 (4C034CBC)
    fffff880`00da2000 fffff880`00dd1000 SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
    fffff880`00dd1000 fffff880`00deb000 mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00deb000 fffff880`00df4000 atapi atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00e00000 fffff880`00e10000 PCIIDEX PCIIDEX.SYS Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`00e13000 fffff880`00eb7000 Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
    fffff880`00eb7000 fffff880`00ec6000 WDFLDR WDFLDR.SYS Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00ec6000 fffff880`00f1d000 ACPI ACPI.sys Mon Jul 13 19:19:34 2009 (4A5BC106)
    fffff880`00f1d000 fffff880`00f26000 WMILIB WMILIB.SYS Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00f26000 fffff880`00f30000 msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`00f30000 fffff880`00f3d000 vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`00f3d000 fffff880`00f70000 pci pci.sys Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00f70000 fffff880`00f85000 partmgr partmgr.sys Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00f85000 fffff880`00f9a000 volmgr volmgr.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00f9a000 fffff880`00ff6000 volmgrx volmgrx.sys Mon Jul 13 19:20:33 2009 (4A5BC141)
    fffff880`00ff6000 fffff880`00ffd000 pciide pciide.sys Mon Jul 13 19:19:49 2009 (4A5BC115)
    fffff880`01000000 fffff880`0103a000 rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
    fffff880`01041000 fffff880`0106b000 ataport ataport.SYS Mon Jul 13 19:19:52 2009 (4A5BC118)
    fffff880`0106b000 fffff880`01076000 amdxata amdxata.sys Tue May 19 13:56:59 2009 (4A12F2EB)
    fffff880`01076000 fffff880`010c2000 fltmgr fltmgr.sys Mon Jul 13 19:19:59 2009 (4A5BC11F)
    fffff880`010c2000 fffff880`010d6000 fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`010d6000 fffff880`010e2040 PxHlpa64 PxHlpa64.sys Tue Oct 20 14:08:42 2009 (4ADDFCAA)
    fffff880`010e3000 fffff880`01141000 msrpc msrpc.sys Mon Jul 13 19:21:32 2009 (4A5BC17C)
    fffff880`01141000 fffff880`011b4000 cng cng.sys Mon Jul 13 19:49:40 2009 (4A5BC814)
    fffff880`011b4000 fffff880`01200000 volsnap volsnap.sys Mon Jul 13 19:20:08 2009 (4A5BC128)
    fffff880`01200000 fffff880`01211000 pcw pcw.sys Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`01211000 fffff880`0121b000 Fs_Rec Fs_Rec.sys Mon Jul 13 19:19:45 2009 (4A5BC111)
    fffff880`0123a000 fffff880`013dd000 Ntfs Ntfs.sys Mon Jul 13 19:20:47 2009 (4A5BC14F)
    fffff880`013dd000 fffff880`013f7000 ksecdd ksecdd.sys Mon Jul 13 19:20:54 2009 (4A5BC156)
    fffff880`01400000 fffff880`0144a000 fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
    fffff880`0144a000 fffff880`0145a000 vmstorfl vmstorfl.sys Mon Jul 13 19:42:54 2009 (4A5BC67E)
    fffff880`0145f000 fffff880`01551000 ndis ndis.sys Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`01551000 fffff880`015b1000 NETIO NETIO.SYS Mon Jul 13 19:21:46 2009 (4A5BC18A)
    fffff880`015b1000 fffff880`015dc000 ksecpkg ksecpkg.sys Fri Dec 11 01:03:32 2009 (4B21E0B4)
    fffff880`015dc000 fffff880`015e4000 spldr spldr.sys Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`015e4000 fffff880`015f6000 mup mup.sys Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`015f6000 fffff880`015ff000 hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
    fffff880`01603000 fffff880`01800000 tcpip tcpip.sys Sun Jun 13 23:39:04 2010 (4C15A458)
    fffff880`01806000 fffff880`01840000 fvevol fvevol.sys Fri Sep 25 22:34:26 2009 (4ABD7DB2)
    fffff880`01840000 fffff880`01856000 disk disk.sys Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`01856000 fffff880`01886000 CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`01886000 fffff880`01890000 avgrkx64 avgrkx64.sys Mon Sep 06 20:49:37 2010 (4C858C21)
    fffff880`01890000 fffff880`0189a000 AVGIDSEH AVGIDSEH.Sys Mon Sep 13 18:46:38 2010 (4C8EA9CE)
    fffff880`0189a000 fffff880`018a8000 crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`018a8000 fffff880`018b4000 dump_ataport dump_ataport.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`018b4000 fffff880`018bd000 dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`018bd000 fffff880`018d0000 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
     
    Cadx,
    #7
  9. 2011/05/10
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    Please enter your System Details. It helps us in answering your questions!
     
  10. 2011/05/10
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    PC Make & Model - Self assembled/home built
    Motherboard - Asus P5K-E Wifi AP
    Processor - Intel Core 2 Duo e8400 @3.0GHz
    Memory - OCZ 4GB (2 x 2GB) PC 6400
    Video Card - EVGA NVIDIA GeForce GTX 470 1280MB GDDR5 PCI-E 2.0
    Hard Drives - Western Digital SATA 300GB , Seagate SATA 500GB & 1TB
    Optical Drive - Lite-on DVD-RW LH-20A1S ATA Device
    Power Supply - [Could not locate manufacture name on power supply] 560W
    Sound Card - Soundmax integrated audio (onboard audio)
    Floppy Drive - No
    Internet Connectivity - Bell DSL
    Connection to Internet through - DSL modem
    Monitor - 23" Samsung Syncmaster 2343, native resolution at 2048x1152 60Hz
    Operating System - Windows 7 64 bit
     
    Cadx,
    #9
  11. 2011/05/11
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Well, a Stop 0x124 error is an indication of a hardware error.

    So you'll have to start testing your hardware. You should work through these steps:

    1. Make sure you are not overclocking your hardware
    2. Update all your drivers. Motherboard, Chipset, Video, Sound, RAID, Network
    3. Make sure you have the latest BIOS version
    4. Make sure your computer is adequately cooled
    5. Make sure your Power Supply is adequate
    6. Start stress testing. For memory, run MDSCHED, for your hard drive run chkdsk /r from a command prompt
     
  12. 2011/05/11
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Your memory is not on the Qualified Vendors List for your motherboard.

    OCZ's Memory Configurator isn't working either, so I'd first try to get some decent memory that's on your motherboards QVL list
     
  13. 2011/05/11
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    I did overclock at one point but now my CPU has been set to defaults. I have updated all my drivers and my BIOS, my tower has 5 fans two of which are 200mm with an aftermarket CPU heat sink and I think my 560 watt power supply should be enough. I ran MDSCHED and chkdsk /r with no errors. I have my cousin's old ASUS P5QL PRO motherboard that I could try using in which OCZ is on the QVL but I think I may need to format if I switch my motherboard unless it is unnecessary.
     
  14. 2011/05/11
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    I also have crash files where I used a program called Windows_NT6_BSOD_v3.03_jcgriff2.exe and a saved system health report using perfmon /report if that helps. Just not too sure how to attach the files because I don't see an attachment tool.
     
  15. 2011/05/12
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    There is of course a chance you damaged your hardware.

    Last resort would be to format your system, re-install Windows & see if it'll work that way. To be honest I doubt it.
     
  16. 2011/05/12
    Cadx

    Cadx Inactive Thread Starter

    Joined:
    2011/04/01
    Messages:
    9
    Likes Received:
    0
    This problem occurred even before I overclocked my CPU.
     
  17. 2011/05/12
    Admin.

    Admin. Administrator Administrator Staff

    Joined:
    2001/12/30
    Messages:
    6,687
    Likes Received:
    107
    Return your hardware... it is damaged. Can't make it more clear.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.