Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


crucial m4 ssd 0x00000124 windows 7 installation crash/hang

  • Please log in to reply
No replies to this topic

#1 sumaznstyle


  • Members
  • 1 posts
  • Local time:10:47 PM

Posted 09 February 2012 - 07:06 AM

crucial m4 ssd 0x00000124 windows 7 installation crashes/hang after the registry register during windows installation and gives me a BSOD... BIOS and SSD FW has all been updated... Here is the report if someone can help me out...

CPU: AMD FX 8120

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\AZn-VI\Desktop\DUMP3006.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:
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`0260d000 PsLoadedModuleList = 0xfffff800`0284ae50
Debug session time: Tue Jan 1 03:36:56.871 2008 (UTC - 6:00)
System Uptime: 0 days 0:00:04.432
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, fffffa800d9e78f8, 0, 0}

Probably caused by : hardware

Followup: MachineOwner

6: 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: 0000000000000000, Machine Check Exception
Arg2: fffffa800d9e78f8, 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_AuthenticAMD




fffff880`03b7e6f0 fffff800`028c7a89 : fffffa80`0d9e78d0 fffffa80`0cd88b60 fffffa80`00000004 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03b7ec10 fffff800`027a9547 : fffffa80`0d9e78d0 fffff800`028225f8 fffffa80`0cd88b60 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03b7ec40 fffff800`02711b95 : fffff800`02884360 fffffa80`0dacdea8 fffffa80`0dacdea0 fffffa80`0cd88b60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03b7ec80 fffff800`0268c161 : fffff880`017bae00 fffff800`02711b70 fffffa80`0cd88b60 fffffa80`0cd88b60 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03b7ecb0 fffff800`02922166 : 24848b48`432cb70f fffffa80`0cd88b60 00000000`00000080 fffffa80`0ccec9e0 : nt!ExpWorkerThread+0x111
fffff880`03b7ed40 fffff800`0265d486 : fffff880`0396a180 fffffa80`0cd88b60 fffff880`039750c0 78244489`44000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b7ed80 00000000`00000000 : fffff880`03b7f000 fffff880`03b79000 fffff880`043ba590 00000000`00000000 : nt!KxStartSystemThread+0x16



MODULE_NAME: hardware

IMAGE_NAME: hardware




Followup: MachineOwner

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users