BSOD BugCheck 124 - Help please

Page 1 of 2 12 LastLast

  1. Glandoux
    Posts : 8
    Window 7 7600.16385
       New #1

    BSOD Win 7 BugCheck 124 - Help please


    I'm getting this BSOD at least once every day.
    I'm not sure if it could be a hardware problem, or a driver problem?
    The dump analysis is not really clear, unless it's me having a problem understanding it.

    So here's my dump file

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

    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    Symbol search path is: SRV*d:\websymbols*http://msdl.microsoft.com/download/s...ols;D:\Symbols
    Executable search path is:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
    Debug session time: Wed Oct 28 06:05:59.553 2009 (GMT-4)
    System Uptime: 0 days 10:02:18.443
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 124, {0, fffffa8004a07028, b2000000, 10005}
    Probably caused by : hardware
    Followup: MachineOwner
    ---------
    0: 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: fffffa8004a07028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000010005, Low order 32-bits of the MCi_STATUS value.
    Debugging Details:
    ------------------

    BUGCHECK_STR: 0x124_GenuineIntel
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    PROCESS_NAME: System
    CURRENT_IRQL: f
    STACK_TEXT:
    fffff800`03fe7a98 fffff800`02c24903 : 00000000`00000124 00000000`00000000 fffffa80`04a07028 00000000`b2000000 : nt!KeBugCheckEx
    fffff800`03fe7aa0 fffff800`02de1513 : 00000000`00000001 fffffa80`04a0aa60 00000000`00000000 fffffa80`04a0aab0 : hal!HalBugCheckSystem+0x1e3
    fffff800`03fe7ae0 fffff800`02c245c8 : 00000000`00000728 fffffa80`04a0aa60 fffff800`03fe7e70 fffff800`03fe7e00 : nt!WheaReportHwError+0x263
    fffff800`03fe7b40 fffff800`02c23f1a : fffffa80`04a0aa60 fffff800`03fe7e70 fffffa80`04a0aa60 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`03fe7c90 fffff800`02c23dd5 : 00000000`00000008 00000000`00000001 fffff800`03fe7ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`03fe7cd0 fffff800`02c17e88 : fffffa80`064fe938 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`03fe7d00 fffff800`02ccb7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`03fe7d30 fffff800`02ccb613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`03fe7e70 fffff800`02cd89ee : 00000000`00000002 00000000`00000000 fffff800`03fdb608 00000000`00000002 : nt!KiMcheckAbort+0x153
    fffff800`03fdb5b0 fffff800`02cd83b7 : fffffa80`064fe8f0 00000000`00235907 00000000`00000000 00000000`00000102 : nt!KiReadyThread+0xe
    fffff800`03fdb5e0 fffff800`02cd8e7e : 00000054`2430edc3 fffff800`03fdbc58 00000000`00235908 fffff800`02e48388 : nt!KiProcessExpiredTimerList+0x157
    fffff800`03fdbc30 fffff800`02cd8697 : 0000001f`39797bc1 0000001f`00235908 0000001f`39797b3f 00000000`00000008 : nt!KiTimerExpiration+0x1be
    fffff800`03fdbcd0 fffff800`02cd56fa : fffff800`02e45e80 fffff800`02e53c40 00000000`00000000 fffff880`03e79db0 : nt!KiRetireDpcList+0x277
    fffff800`03fdbd80 00000000`00000000 : fffff800`03fdc000 fffff800`03fd6000 fffff800`03fdbd40 00000000`00000000 : nt!KiIdleLoop+0x5a

    STACK_COMMAND: kb
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: hardware
    IMAGE_NAME: hardware
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
    BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
    Followup: MachineOwner
    ---------
    0: kd> lmvm hardware
    start end module name
    0: kd> lmvm hardware
    start end module name



    At first, my PC was often crashing when i was encoding movies to mp4, so i thought it was a problem.

    But last night, i started the encoding a a file to see if it would crash. The encoding finished at 3am, but the computer crashed around 6am. So the PC was completely idle when it crashed..

    Can somebody help me?
    Many thanks,
    Last edited by Glandoux; 28 Oct 2009 at 10:43.
      My Computer
    Quote Quote

  3. Glandoux
    Posts : 8
    Window 7 7600.16385
    Thread Starter
       New #2

    I guess this thread should go under : Crashes and Debugging.

    Sorry about that.
    Can somebody move it there?

    thanks,
      My Computer
    Quote Quote

  4. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #3

    Glandoux said:
    I guess this thread should go under : Crashes and Debugging.

    Sorry about that.
    Can somebody move it there?

    thanks,
    G

    are you overclocking?

    Can you do us a favor and upload the actual dump file zipped. we can examine it in more details than the text you provided

    ken
      My Computer
    Quote Quote

  6. Glandoux
    Posts : 8
    Window 7 7600.16385
    Thread Starter
       New #4

    Here's the dump file.

    Also, yes i am overclocking, but my system passed every stress test.
    Memtest for 12+ hours
    OCCT 3.1 for 6+ hours.

    And i didn't have any problems, but sometimes, for some reason, the PC just crash.

    thanks,
      My Computer
    Quote Quote

  7. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #5

    Glandoux said:
    Here's the dump file.

    Also, yes i am overclocking, but my system passed every stress test.
    Memtest for 12+ hours
    OCCT 3.1 for 6+ hours.

    And i didn't have any problems, but sometimes, for some reason, the PC just crash.

    thanks,
    G

    Ok so its definately hardware. Overclocking, Bios, heat,etc

    HAL (hardware abstraction layer) probably caused it.

    Since all the files involved are system files you should do a system file check
    in search>cmd>right click run as admin> sfc /scannow

    When done Im going to post the entire dump for you to look at.

    Ken
      My Computer
    Quote Quote

  8. chev65
    Posts : 8,870
    Windows 7 Ult, Windows 8.1 Pro,
       New #6

    This is a typical overclocking crash which is to be expected when trying to dial in an overclock.

    When overclocking the i7, the Prime error 124 relates to low CPU VTT or CPU Vcore voltage for the overclock being attempted. It's typical to get error 124 when the CPU VTT is too low. Raising the CPU VTT voltage should help get you more stable.
    Last edited by chev65; 28 Oct 2009 at 14:24.
      My Computer
    Quote Quote

  10. Glandoux
    Posts : 8
    Window 7 7600.16385
    Thread Starter
       New #7

    I'm running the sfc /scannow right now.

    My QPI/VTT is already @ 1.4v right now.

    thanks,
      My Computer
    Quote Quote

  11. zigzag3143
    Posts : 28,845
    Win 8 Release candidate 8400
       New #8

    G
    The dump was long so I zipped the total dump these are excerpts. This was caused by a hardware problem involving HAL, and atikmdag.sys (your video driver)
    I know you have run memtest, and other tests.
    things that can cause these kinds of hware problems
    cpu, gpu, psu, memory, optical drives, mobo,
    you should update the BIOS, video driver since both were implicated.
    You should stop overclocking (if just to prove it is/isnt the cause)
    You can re-run the memtest overnight intense mode.
    the system file check should be run to eliminate system files as the cause

    If you BSOD upload them.

    Hope this helps

    Ken
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\102809-29437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
Debug session time: Wed Oct 28 06:05:59.553 2009 (GMT-4)
System Uptime: 0 days 10:02:18.443
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004a07028, b2000000, 10005}

Probably caused by : hardware

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

0: kd> !thread;!analyze -v;r;kv;lmtn;lmtsmn
GetPointerFromAddress: unable to read from fffff80002f03000
THREAD fffff80002e53c40  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80002e41b74
Owning Process            fffff80002e54140       Image:         <Unknown>
Attached Process          fffffa800366d9e0       Image:         System
fffff78000000000: Unable to get shared data
Wait Start TickCount      2316551      
Context Switch Count      7029972             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!KiIdleLoop (0xfffff80002cd56a0)
Stack Init fffff80003fdbdb0 Current fffff80003fdbd40
Base fffff80003fdc000 Limit fffff80003fd6000 Call 0
Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff800`03fe7a98 fffff800`02c24903 : 00000000`00000124 00000000`00000000 fffffa80`04a07028 00000000`b2000000 : nt!KeBugCheckEx
fffff800`03fe7aa0 fffff800`02de1513 : 00000000`00000001 fffffa80`04a0aa60 00000000`00000000 fffffa80`04a0aab0 : hal!HalBugCheckSystem+0x1e3
fffff800`03fe7ae0 fffff800`02c245c8 : 00000000`00000728 fffffa80`04a0aa60 fffff800`03fe7e70 fffff800`03fe7e00 : nt!WheaReportHwError+0x263
fffff800`03fe7b40 fffff800`02c23f1a : fffffa80`04a0aa60 fffff800`03fe7e70 fffffa80`04a0aa60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`03fe7c90 fffff800`02c23dd5 : 00000000`00000008 00000000`00000001 fffff800`03fe7ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`03fe7cd0 fffff800`02c17e88 : fffffa80`064fe938 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`03fe7d00 fffff800`02ccb7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`03fe7d30 fffff800`02ccb613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`03fe7e70 fffff800`02cd89ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 (TrapFrame @ fffff800`03fe7e70)
fffff800`03fdb5b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiReadyThread+0xe

*******************************************************************************
*                                                                             *
*                        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: fffffa8004a07028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010005, 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:  f

STACK_TEXT:  
fffff800`03fe7a98 fffff800`02c24903 : 00000000`00000124 00000000`00000000 fffffa80`04a07028 00000000`b2000000 : nt!KeBugCheckEx
fffff800`03fe7aa0 fffff800`02de1513 : 00000000`00000001 fffffa80`04a0aa60 00000000`00000000 fffffa80`04a0aab0 : hal!HalBugCheckSystem+0x1e3
fffff800`03fe7ae0 fffff800`02c245c8 : 00000000`00000728 fffffa80`04a0aa60 fffff800`03fe7e70 fffff800`03fe7e00 : nt!WheaReportHwError+0x263
fffff800`03fe7b40 fffff800`02c23f1a : fffffa80`04a0aa60 fffff800`03fe7e70 fffffa80`04a0aa60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`03fe7c90 fffff800`02c23dd5 : 00000000`00000008 00000000`00000001 fffff800`03fe7ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`03fe7cd0 fffff800`02c17e88 : fffffa80`064fe938 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`03fe7d00 fffff800`02ccb7ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`03fe7d30 fffff800`02ccb613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`03fe7e70 fffff800`02cd89ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`03fdb5b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiReadyThread+0xe


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------
    Last edited by zigzag3143; 16 Mar 2011 at 19:35.
      My Computer
    Quote Quote

  12. Glandoux
    Posts : 8
    Window 7 7600.16385
    Thread Starter
       New #9

    Thanks for the info, it's really appreciated!

    Results of the scan:
    Beginning system scan. This process will take some time.
    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection did not find any integrity violations.

    So this is ok for this.

    I was somewhat suspecting the my video card could be the problem..
    This is a new build (except for my video card, an old ati HD3850).
    I already have the latest bios/driver for everything.

    I guess i could run everything @ stock speed and see if the error occurs.
      My Computer
    Quote Quote

  13. Glandoux
    Posts : 8
    Window 7 7600.16385
    Thread Starter
       New #10

    The only thing weird is that my system crashed when it was totally idled, doing nothing...
      My Computer
    Quote Quote

 
Page 1 of 2 12 LastLast

  Related Discussions
I have been having multiple BSOD's for the last 4-5 months. Sometimes I don't even get a blue screen, it just goes black. I ran the attached file while in safe mode with networking. I have no idea how to check display drivers. (I've read on other posts that these seem to be the problem) This...
We've been getting a BSOD on one of our computers on startup recently. The exact message the BSOD gives varies but often mentions atapi.sys. Having done extensive research we've come to the conclusion that it could be a rootkit or it could be the fact that we have Daemon Tools installed on the...
I'm new to this forum and in fact new to forums generally. I just tend to struggle on and spend a lot of time reading other peoples solutions. I hope you can help me with my periodically BSOD and I tend to go back to a good known recovery point. But recently these BSOD have been happening more...
T61 4GB Kingston T61 specific Ram 2.5GHz 6459CTO T9300 (965 Chipset) Fresh, Full licensed copy of Win 7 Ultimate loaded onto system, without issues. All device drivers from the Lenovo site have been loaded successfully without incident. Device Manager showing Zero issues.
Help me!... I dont know why this started to happen but happens somewhere between twice and three times per day. I attached my Memory.DMP file which is where it said the error was logged. To be specific this was my error. The computer has rebooted from a bugcheck. The bugcheck was:...
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 21:27.
Find Us