1. Computer problem? Tech Support Guy is completely free -- paid for by advertisers and donations. Click here to join today! If you're new to Tech Support Guy, we highly recommend that you visit our Guide for New Members.

Vista BSOD - STOP 0x00000124

Discussion in 'Windows Vista' started by VistaBSOD, Jul 17, 2007.

Thread Status:
Not open for further replies.
  1. VistaBSOD

    VistaBSOD Thread Starter

    Jul 17, 2007
    I have some regular BSOD crashes in Vista x86 (once a day)
    They are not heat related. Temperatures of the CPU and GPU are fine.
    I also used memtest, prime95 torture test and 3dmark 2005, but get no errors. I also can play 3D games for hours without problems.
    The crashes usually occur when doing something quite simple, like opening a new window.

    When I get a crash I often see that the harddisk led keeps burning and Vista is unable to write the dump file (no warning, but nothing happens).
    The BSOD alyways contains this error:

    STOP: 0x00000124 (0x00000000, 0x866C6440, B2000000, 0X00070F0F)

    When the BSOD did manage to make a dump I used the Windows Debugger to get the following information.
    Any suggestions are welcome.

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

    Loading Dump File [C:\Windows\Minidump\Mini071707-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6000.16386.x86fre.vista_rtm.061101-2205
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111db0
    Debug session time: Tue Jul 17 20:37:02.965 2007 (GMT+2)
    System Uptime: 0 days 2:36:02.554
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * *
    * Bugcheck Analysis *
    * *

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, 866c6440, b2000000, 70f0f}

    Probably caused by : hardware

    Followup: MachineOwner

    0: kd> !analyze -v
    * *
    * Bugcheck Analysis *
    * *

    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.
    Arg1: 00000000, MCA_ASSERT
    Arg2: 866c6440, Address of WHEA_ERROR_RECORD structure
    Arg3: b2000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
    the error
    Arg4: 00070f0f, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
    the error

    Debugging Details:

    WHEA_ERROR_RECORD: !errrec ffffffff866c6440

    BUGCHECK_STR: 0x124_AuthenticAMD





    820eef84 823a6e93 00000124 00000000 866c6440 nt!KeBugCheckEx+0x1e
    820eefa0 820cecb6 866c6440 866c7ad8 00000001 hal!HalBugCheckSystem+0x37
    820eefc0 823a6e52 866c7ad8 866c7bf0 820eeff4 nt!WheaReportHwError+0x10c
    820eefd0 823a6f73 00000003 866c7ad8 00000000 hal!HalpReportMachineCheck+0x28
    820eeff4 823a389f 80156000 00000000 00000000 hal!HalpMcaExceptionHandler+0xc3
    820eeff4 00000000 80156000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x77


    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware


    FAILURE_BUCKET_ID: 0x124_AuthenticAMD

    BUCKET_ID: 0x124_AuthenticAMD

    Followup: MachineOwner
  2. ~Candy~

    ~Candy~ Retired Administrator

    Jan 27, 2001
    Were you able to find a solution to this?
  3. Stomper88


    Jul 12, 2008
    After a couple of weeks of trying out every idea that I could come up with, the solution to my 0x00000124 error was quite shocking.

    When I first setup my PC, I set my drive to SATAII mode by removing the jumper on the back. If the jumper is in, it is SATAI (1.5gbps) mode, if the jumper is out, it is SATAII (3.0gpbs) mode. If you dont do anything to the drive, it is in SATAI mode (jumper in). So I thought, "I want the best performance, pull that stinkin jumper out!"

    I was getting BSOD 0x00000124 crashes randomly and they never created a dump file. The key was that no dump file was being created. I tried everything you could think of, and as a last resort, I popped the drive back to SATAI mode.... and the BSODs are gone!

    My motherboard is the Gigabyte EX38-DS4.
  4. ~Candy~

    ~Candy~ Retired Administrator

    Jan 27, 2001
    Hi and welcome.

As Seen On
As Seen On...

Welcome to Tech Support Guy!

Are you looking for the solution to your computer problem? Join our site today to ask your question. This site is completely free -- paid for by advertisers and donations.

If you're not already familiar with forums, watch our Welcome Guide to get started.

Join over 733,556 other people just like you!

Thread Status:
Not open for further replies.

Short URL to this thread: https://techguy.org/596989

  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.
    Dismiss Notice