BSOD 0x00000124 (happening at random times)

[stavee]

Hay guys,

My computer recently has been getting the BSOD and not too sure as too why this is occurring, as i have built a pretty good system and only up until late last year its started happening but more often now

i receive the STOP 0x00000124 message randomly whilst using my computer or i've also noticed when i wake it up from 'sleep'

i understand this is error is hardware? so i updated most drivers and performed some stress tests (which passed) and still get it

any clue guys i need my comp for heavy work load

the latest dump file is uploaded here Zippyshare.com - 041011-82337-01.dmp
could you please have a look at it and analyse it for me so we can work out what the problem is!
Im computer literate so i should be able to understand most things you say!

Thanks heaps guys

 

[yowanvista]

Are you overclocking any hardware? Updating your BIOS might help

 

[stavee]

no overclocking and yes the latest bios F11 is what i have

thanks for the quick reply, amazing!

 

[DeanP]

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[stavee]

have read that post numerous times

is there any chance of analyzing the dump file to pin point or at least get close to finding the problem?

 

[DeanP]

Bugcheck 0x124 = Hardware WHEA = Hardware Failure
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html
http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

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


Loading Dump File [C:\Users\Dean\Downloads\041011-82337-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: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`0329ee50
Debug session time: Mon Apr 11 11:02:30.469 2011 (UTC + 12:00)
System Uptime: 0 days 0:00:30.484
Loading Kernel Symbols
...............................................................
.....................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007dbb028, f2000000, 20008f}

Probably caused by : hardware

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

7: 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: fffffa8007dbb028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000020008f, 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:  
fffff880`03172b58 fffff800`0302a903 : 00000000`00000124 00000000`00000000 fffffa80`07dbb028 00000000`f2000000 : nt!KeBugCheckEx
fffff880`03172b60 fffff800`031e75a3 : 00000000`00000001 fffffa80`0705e630 00000000`00000000 fffffa80`0705e680 : hal!HalBugCheckSystem+0x1e3
fffff880`03172ba0 fffff800`0302a5c8 : 00000000`00000728 fffffa80`0705e630 fffff880`03172f30 fffff880`03172f00 : nt!WheaReportHwError+0x263
fffff880`03172c00 fffff800`03029f1a : fffffa80`0705e630 fffff880`03172f30 fffffa80`0705e630 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03172d50 fffff800`03029dd5 : 00000000`00000008 00000000`00000001 fffff880`03172fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03172d90 fffff800`0301de88 : fffff880`0316a180 fffff880`0316a180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`03172dc0 fffff800`030cffec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`03172df0 fffff800`030cfe53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03172f30 fffff800`03035652 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`03192c98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalProcessorIdle+0x2


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN

BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN

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

7: kd> lmtsmn
start             end                 module name
fffff880`00f5e000 fffff880`00fb5000   ACPI     ACPI.sys     Tue Jul 14 11:19:34 2009 (4A5BC106)
fffff880`03d51000 fffff880`03ddb000   afd      afd.sys      Tue Jul 14 11:21:40 2009 (4A5BC184)
fffff880`00c0b000 fffff880`00c16000   amdxata  amdxata.sys  Wed May 20 05:56:59 2009 (4A12F2EB)
fffff880`00dc6000 fffff880`00dcf000   atapi    atapi.sys    Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`00dcf000 fffff880`00df9000   ataport  ataport.SYS  Tue Jul 14 11:19:52 2009 (4A5BC118)
fffff880`02df6000 fffff880`02dfd000   Beep     Beep.SYS     Tue Jul 14 12:00:13 2009 (4A5BCA8D)
fffff880`01800000 fffff880`0182a000   cdrom    cdrom.sys    Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`00ce2000 fffff880`00da2000   CI       CI.dll       Tue Jul 14 13:32:13 2009 (4A5BE01D)
fffff880`01990000 fffff880`019c0000   CLASSPNP CLASSPNP.SYS Tue Jul 14 11:19:58 2009 (4A5BC11E)
fffff880`00c84000 fffff880`00ce2000   CLFS     CLFS.SYS     Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`010da000 fffff880`0114d000   cng      cng.sys      Tue Jul 14 11:49:40 2009 (4A5BC814)
fffff880`019c0000 fffff880`019ce000   crashdmp crashdmp.sys Tue Jul 14 12:01:01 2009 (4A5BCABD)
fffff880`0197a000 fffff880`01990000   disk     disk.sys     Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`019ce000 fffff880`019da000   dump_dumpata dump_dumpata.sys Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`019e5000 fffff880`019f8000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 11:21:51 2009 (4A5BC18F)
fffff880`019da000 fffff880`019e5000   dump_msahci dump_msahci.sys Tue Jul 14 12:01:01 2009 (4A5BCABD)
fffff880`03f18000 fffff880`03f8e000   eeCtrl64 eeCtrl64.sys Sat May 22 09:44:45 2010 (4BF6FECD)
fffff880`02dcd000 fffff880`02ded000   ENG64    ENG64.SYS    Sat Mar 05 11:02:16 2011 (4D716168)
fffff880`02c0a000 fffff880`02dcd000   EX64     EX64.SYS     Sat Mar 05 11:10:51 2011 (4D71636B)
fffff880`01068000 fffff880`0107c000   fileinfo fileinfo.sys Tue Jul 14 11:34:25 2009 (4A5BC481)
fffff880`0101c000 fffff880`01068000   fltmgr   fltmgr.sys   Tue Jul 14 11:19:59 2009 (4A5BC11F)
fffff880`013ed000 fffff880`013f7000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 11:19:45 2009 (4A5BC111)
fffff880`01940000 fffff880`0197a000   fvevol   fvevol.sys   Sat Sep 26 14:34:26 2009 (4ABD7DB2)
fffff880`0148b000 fffff880`014d5000   fwpkclnt fwpkclnt.sys Tue Jul 14 11:21:08 2009 (4A5BC164)
fffff800`03018000 fffff800`03061000   hal      hal.dll      Tue Jul 14 13:27:36 2009 (4A5BDF08)
fffff880`01937000 fffff880`01940000   hwpolicy hwpolicy.sys Tue Jul 14 11:19:22 2009 (4A5BC0FA)
fffff800`00bcb000 fffff800`00bd5000   kdcom    kdcom.dll    Tue Jul 14 13:31:07 2009 (4A5BDFDB)
fffff880`013c2000 fffff880`013dc000   ksecdd   ksecdd.sys   Tue Jul 14 11:20:54 2009 (4A5BC156)
fffff880`01460000 fffff880`0148b000   ksecpkg  ksecpkg.sys  Fri Dec 11 19:03:32 2009 (4B21E0B4)
fffff880`00c2c000 fffff880`00c70000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Tue Jul 14 13:29:10 2009 (4A5BDF66)
fffff880`018e1000 fffff880`01937000   MDFSYSNT MDFSYSNT.sys Fri Oct 08 09:39:16 2010 (4CAE2FF4)
fffff880`01200000 fffff880`0120d000   MDPMGRNT MDPMGRNT.SYS Fri Oct 22 09:59:58 2010 (4CC0A9CE)
fffff880`00dac000 fffff880`00dc6000   mountmgr mountmgr.sys Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`00c00000 fffff880`00c0b000   msahci   msahci.sys   Tue Jul 14 12:01:01 2009 (4A5BCABD)
fffff880`03cf8000 fffff880`03d03000   Msfs     Msfs.SYS     Tue Jul 14 11:19:47 2009 (4A5BC113)
fffff880`00fbe000 fffff880`00fc8000   msisadrv msisadrv.sys Tue Jul 14 11:19:26 2009 (4A5BC0FE)
fffff880`0107c000 fffff880`010da000   msrpc    msrpc.sys    Tue Jul 14 11:21:32 2009 (4A5BC17C)
fffff880`03f0d000 fffff880`03f18000   mssmbios mssmbios.sys Tue Jul 14 11:31:10 2009 (4A5BC3BE)
fffff880`015e4000 fffff880`015f6000   mup      mup.sys      Tue Jul 14 11:23:45 2009 (4A5BC201)
fffff880`00da2000 fffff880`00dac000   mv91cons mv91cons.sys Wed Sep 23 09:36:37 2009 (4AB94365)
fffff880`014da000 fffff880`015cc000   ndis     ndis.sys     Tue Jul 14 11:21:40 2009 (4A5BC184)
fffff880`03c74000 fffff880`03c83000   netbios  netbios.sys  Tue Jul 14 12:09:26 2009 (4A5BCCB6)
fffff880`03c00000 fffff880`03c45000   netbt    netbt.sys    Tue Jul 14 11:21:28 2009 (4A5BC178)
fffff880`01400000 fffff880`01460000   NETIO    NETIO.SYS    Tue Jul 14 11:21:46 2009 (4A5BC18A)
fffff880`03d03000 fffff880`03d14000   Npfs     Npfs.SYS     Tue Jul 14 11:19:48 2009 (4A5BC114)
fffff880`03f01000 fffff880`03f0d000   nsiproxy nsiproxy.sys Tue Jul 14 11:21:02 2009 (4A5BC15E)
fffff800`03061000 fffff800`0363e000   nt       ntkrnlmp.exe Wed Oct 27 15:43:09 2010 (4CC791BD)
fffff880`0121f000 fffff880`013c2000   Ntfs     Ntfs.sys     Tue Jul 14 11:20:47 2009 (4A5BC14F)
fffff880`02ded000 fffff880`02df6000   Null     Null.SYS     Tue Jul 14 11:19:37 2009 (4A5BC109)
fffff880`03c4e000 fffff880`03c74000   pacer    pacer.sys    Tue Jul 14 12:09:41 2009 (4A5BCCC5)
fffff880`00e0d000 fffff880`00e22000   partmgr  partmgr.sys  Tue Jul 14 11:19:58 2009 (4A5BC11E)
fffff880`00fc8000 fffff880`00ffb000   pci      pci.sys      Tue Jul 14 11:19:51 2009 (4A5BC117)
fffff880`00e93000 fffff880`00e9a000   pciide   pciide.sys   Tue Jul 14 11:19:49 2009 (4A5BC115)
fffff880`00e9a000 fffff880`00eaa000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 11:19:48 2009 (4A5BC114)
fffff880`013dc000 fffff880`013ed000   pcw      pcw.sys      Tue Jul 14 11:19:27 2009 (4A5BC0FF)
fffff880`00c70000 fffff880`00c84000   PSHED    PSHED.dll    Tue Jul 14 13:32:23 2009 (4A5BE027)
fffff880`03eb0000 fffff880`03f01000   rdbss    rdbss.sys    Tue Jul 14 11:24:09 2009 (4A5BC219)
fffff880`03cdd000 fffff880`03ce6000   RDPCDD   RDPCDD.sys   Tue Jul 14 12:16:34 2009 (4A5BCE62)
fffff880`03ce6000 fffff880`03cef000   rdpencdd rdpencdd.sys Tue Jul 14 12:16:34 2009 (4A5BCE62)
fffff880`03cef000 fffff880`03cf8000   rdprefmp rdprefmp.sys Tue Jul 14 12:16:35 2009 (4A5BCE63)
fffff880`01199000 fffff880`011d3000   rdyboost rdyboost.sys Tue Jul 14 11:34:34 2009 (4A5BC48A)
fffff880`01000000 fffff880`0101a000   SCDEmu   SCDEmu.SYS   Mon Nov 09 16:27:29 2009 (4AF78C21)
fffff880`03c83000 fffff880`03ca0000   serial   serial.sys   Tue Jul 14 12:00:40 2009 (4A5BCAA8)
fffff880`015dc000 fffff880`015e4000   spldr    spldr.sys    Tue May 12 04:56:27 2009 (4A0858BB)
fffff880`0182a000 fffff880`0189d000   SRTSP64  SRTSP64.SYS  Thu Jan 29 15:55:07 2009 (49811A8B)
fffff880`011d3000 fffff880`011e7000   SRTSPX64 SRTSPX64.SYS Thu Jan 29 15:57:42 2009 (49811B26)
fffff880`0189d000 fffff880`018d3000   SYMEVENT64x86 SYMEVENT64x86.SYS Thu May 29 12:35:19 2008 (483DFA47)
fffff880`01601000 fffff880`017fe000   tcpip    tcpip.sys    Mon Jun 14 15:39:04 2010 (4C15A458)
fffff880`03d32000 fffff880`03d3f000   TDI      TDI.SYS      Tue Jul 14 11:21:18 2009 (4A5BC16E)
fffff880`03d14000 fffff880`03d32000   tdx      tdx.sys      Tue Jul 14 11:21:15 2009 (4A5BC16B)
fffff880`011e7000 fffff880`011fb000   termdd   termdd.sys   Tue Jul 14 12:16:36 2009 (4A5BCE64)
fffff880`00e00000 fffff880`00e0d000   vdrvroot vdrvroot.sys Tue Jul 14 12:01:31 2009 (4A5BCADB)
fffff880`018d3000 fffff880`018e1000   vga      vga.sys      Tue Jul 14 11:38:47 2009 (4A5BC587)
fffff880`03ca8000 fffff880`03ccd000   VIDEOPRT VIDEOPRT.SYS Tue Jul 14 11:38:51 2009 (4A5BC58B)
fffff880`015cc000 fffff880`015dc000   vmstorfl vmstorfl.sys Tue Jul 14 11:42:54 2009 (4A5BC67E)
fffff880`00e22000 fffff880`00e37000   volmgr   volmgr.sys   Tue Jul 14 11:19:57 2009 (4A5BC11D)
fffff880`00e37000 fffff880`00e93000   volmgrx  volmgrx.sys  Tue Jul 14 11:20:33 2009 (4A5BC141)
fffff880`0114d000 fffff880`01199000   volsnap  volsnap.sys  Tue Jul 14 11:20:08 2009 (4A5BC128)
fffff880`03ddb000 fffff880`03df6000   wanarp   wanarp.sys   Tue Jul 14 12:10:21 2009 (4A5BCCED)
fffff880`03ccd000 fffff880`03cdd000   watchdog watchdog.sys Tue Jul 14 11:37:35 2009 (4A5BC53F)
fffff880`00eab000 fffff880`00f4f000   Wdf01000 Wdf01000.sys Tue Jul 14 11:22:07 2009 (4A5BC19F)
fffff880`00f4f000 fffff880`00f5e000   WDFLDR   WDFLDR.SYS   Tue Jul 14 11:19:54 2009 (4A5BC11A)
fffff880`03c45000 fffff880`03c4e000   wfplwf   wfplwf.sys   Tue Jul 14 12:09:26 2009 (4A5BCCB6)
fffff880`00fb5000 fffff880`00fbe000   WMILIB   WMILIB.SYS   Tue Jul 14 11:19:51 2009 (4A5BC117)
fffff880`03d3f000 fffff880`03d51000   wpsdrvnt wpsdrvnt.sys Thu Apr 23 10:07:15 2009 (49EF9513)

 

[stavee]

running test now thanks

ps, quick question
how does it become a hardware problem when everything was working fine before it started happening?

 

[stavee]

CPU TEST

approx 6 hours

0 errors 0 warnings

 

[fimble]

running test now thanks

ps, quick question
how does it become a hardware problem when everything was working fine before it started happening?

Ask yourself, Why did my car start OK yesterday, but not today?

 

[stavee]

Good point!!

Running memtest now/overnight and see how that goes


For the gpu test how hot can my graphics get cause i tried it briefly and it went high so I stopped so I could ask question before I leave it on

 

[DeanP]

If it goes above 90C, then it's likely your GPU is overheating.

 

[stavee]

RAM TEST

7hours 40mins

no errors

and for the GPU TEST
i got to 95 and i stopped it
so should i take my graphics card out and give it a clean?

 

[stavee]

cleaned gpu test has been on for 20mins at 87degrees now
way better than before

how long do i leave it on for?

 

[stavee]

30 mins stayed the same so i stopped it there

all components passed tests

so hopefully bsod is solved? ill report back if it happens again

 

[fimble]

Yeah, you are (were!!) looking for it to "peak" then stabilise, obviously at a not too hot temp. 87 sounds fine for a maxxed out graphics card. Hope all goes well.

 

[stavee]

cheers mate!

and yeah i hope it works im sick of this bsod randomly occurring especially with pretty decent specs

 

[DeanP]

Go ahead and run the Memtest.

 

[stavee]

i ran it already my results passed!

crash again

please analyse the new dump to see if anything else shows
Zippyshare.com - 041111-84583-01.dmp

 

[stavee]

bump

 

[DeanP]

Please do not bump - if your thread has been missed, VM or PM me.

Dump still points to Hardware (STOP 0x124)
Bugcheck 0x124 = Hardware WHEA = Hardware Failure

Since you already run hardware tests, I suggest that you go to BIOS, take photos of the settings and upload it on your next post (I'm thinking of incorrect settings in your BIOS). If you are overclocking anything (CPU, GPU, RAM) - stop and return to default values.

Regards. . .

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


Loading Dump File [C:\Users\Dean\Downloads\041111-84583-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: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03018000 PsLoadedModuleList = 0xfffff800`03255e50
Debug session time: Mon Apr 11 18:45:52.604 2011 (UTC + 12:00)
System Uptime: 0 days 7:18:40.524
Loading Kernel Symbols
.................................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000

Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007dbe028, f2000000, 20008f}

Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
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: fffffa8007dbe028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000020008f, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER                ***
***                                                                   ***
*************************************************************************

BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`00ba8fd8 fffff880`04213c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort
fffff800`00b9cc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`04213c61


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN

BUCKET_ID:  X64_0x124_GenuineIntel__UNKNOWN

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

0: kd> lmtsmn
start             end                 module name
fffff880`00e0f000 fffff880`00e66000   ACPI     ACPI.sys     unavailable (00000000)
fffff880`00de7000 fffff880`00df2000   amdxata  amdxata.sys  unavailable (00000000)
fffff880`00c86000 fffff880`00c8f000   atapi    atapi.sys    unavailable (00000000)
fffff880`00db2000 fffff880`00ddc000   ataport  ataport.SYS  unavailable (00000000)
fffff880`00e9a000 fffff880`00f5a000   CI       CI.dll       unavailable (00000000)
fffff880`018c0000 fffff880`018f0000   CLASSPNP CLASSPNP.SYS unavailable (00000000)
fffff880`00cf7000 fffff880`00d55000   CLFS     CLFS.SYS     unavailable (00000000)
fffff880`0112b000 fffff880`0119e000   cng      cng.sys      unavailable (00000000)
fffff880`018aa000 fffff880`018c0000   disk     disk.sys     unavailable (00000000)
fffff880`010b9000 fffff880`010cd000   fileinfo fileinfo.sys unavailable (00000000)
fffff880`0106d000 fffff880`010b9000   fltmgr   fltmgr.sys   unavailable (00000000)
fffff880`0122b000 fffff880`01235000   Fs_Rec   Fs_Rec.sys   unavailable (00000000)
fffff880`01870000 fffff880`018aa000   fvevol   fvevol.sys   unavailable (00000000)
fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys unavailable (00000000)
fffff800`035f5000 fffff800`0363e000   hal      hal.dll      Tue Jul 14 13:27:36 2009 (4A5BDF08)
fffff880`01867000 fffff880`01870000   hwpolicy hwpolicy.sys unavailable (00000000)
fffff800`00bad000 fffff800`00bb7000   kdcom    kdcom.dll    Tue Jul 14 13:31:07 2009 (4A5BDFDB)
fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   unavailable (00000000)
fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  unavailable (00000000)
fffff880`00c9f000 fffff880`00ce3000   mcupdate mcupdate.dll unavailable (00000000)
fffff880`01811000 fffff880`01867000   MDFSYSNT MDFSYSNT.sys unavailable (00000000)
fffff880`015f3000 fffff880`01600000   MDPMGRNT MDPMGRNT.SYS unavailable (00000000)
fffff880`00c6c000 fffff880`00c86000   mountmgr mountmgr.sys unavailable (00000000)
fffff880`00ddc000 fffff880`00de7000   msahci   msahci.sys   unavailable (00000000)
fffff880`00e6f000 fffff880`00e79000   msisadrv msisadrv.sys unavailable (00000000)
fffff880`010cd000 fffff880`0112b000   msrpc    msrpc.sys    unavailable (00000000)
fffff880`015e1000 fffff880`015f3000   mup      mup.sys      unavailable (00000000)
fffff880`00e8d000 fffff880`00e97000   mv91cons mv91cons.sys unavailable (00000000)
fffff880`0148f000 fffff880`01581000   ndis     ndis.sys     unavailable (00000000)
fffff880`01581000 fffff880`015e1000   NETIO    NETIO.SYS    unavailable (00000000)
fffff800`03018000 fffff800`035f5000   nt       ntkrnlmp.exe Wed Oct 27 15:43:09 2010 (4CC791BD)
fffff880`0125c000 fffff880`013ff000   Ntfs     Ntfs.sys     unavailable (00000000)
fffff880`00d88000 fffff880`00d9d000   partmgr  partmgr.sys  unavailable (00000000)
fffff880`00d55000 fffff880`00d88000   pci      pci.sys      unavailable (00000000)
fffff880`00e86000 fffff880`00e8d000   pciide   pciide.sys   unavailable (00000000)
fffff880`00c5c000 fffff880`00c6c000   PCIIDEX  PCIIDEX.SYS  unavailable (00000000)
fffff880`0121a000 fffff880`0122b000   pcw      pcw.sys      unavailable (00000000)
fffff880`00ce3000 fffff880`00cf7000   PSHED    PSHED.dll    unavailable (00000000)
fffff880`01000000 fffff880`0103a000   rdyboost rdyboost.sys unavailable (00000000)
fffff880`01485000 fffff880`0148d000   spldr    spldr.sys    unavailable (00000000)
fffff880`01603000 fffff880`01800000   tcpip    tcpip.sys    unavailable (00000000)
fffff880`00e79000 fffff880`00e86000   vdrvroot vdrvroot.sys unavailable (00000000)
fffff880`01475000 fffff880`01485000   vmstorfl vmstorfl.sys unavailable (00000000)
fffff880`00d9d000 fffff880`00db2000   volmgr   volmgr.sys   unavailable (00000000)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  unavailable (00000000)
fffff880`0119e000 fffff880`011ea000   volsnap  volsnap.sys  unavailable (00000000)
fffff880`00f5a000 fffff880`00ffe000   Wdf01000 Wdf01000.sys unavailable (00000000)
fffff880`00e00000 fffff880`00e0f000   WDFLDR   WDFLDR.SYS   unavailable (00000000)
fffff880`00e66000 fffff880`00e6f000   WMILIB   WMILIB.SYS   unavailable (00000000)