unexpected shutdown

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by rien, Feb 7, 2011.

  1. rien

    rien Well-Known Member

    Joined:
    Aug 9, 2010
    Messages:
    39
    Likes Received:
    0
  2. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Hello and welcome to the forums.

    Unfortunately this is stop 0x124 caused by hardware. Even uninstalling Symantec and updating Intel Matrix Storage Manager won't help.

    http://windows7forums.com/blue-screen-death-bsod/54459-important-every-thread-starter-please-see.html.

    Stop 0x124 - what it means and what to try - Windows 7 Forums

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred
    Probably caused by : hardware
    0x124_GenuineIntel_PROCESSOR_BUS_PRV






    Crash Dumps:

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\092110-24102-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 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`02c11000 PsLoadedModuleList = 0xfffff800`02e4ee50
    Debug session time: Tue Sep 21 14:01:54.900 2010 (UTC - 5:00)
    System Uptime: 0 days 0:00:05.555
    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, fffffa8004219038, 0, 0}
    
    Probably caused by : hardware
    
    Followup: MachineOwner
    ---------
    
    1: 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: fffffa8004219038, 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`02db26b0 fffff800`02ecba89 : fffffa80`04219010 fffffa80`0246f040 00000000`00000008 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`02db2bd0 fffff800`02dad667 : fffffa80`04219010 fffff800`02e265f8 fffffa80`0246f040 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`02db2c00 fffff800`02d15c45 : fffff800`02e88360 fffffa80`04192bc8 fffffa80`04192bc0 fffffa80`0246f040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`02db2c40 fffff800`02c8e961 : fffff880`01030e00 fffff800`02d15c20 fffffa80`0246f040 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`02db2c70 fffff800`02f25c06 : 00000000`00000000 fffffa80`0246f040 00000000`00000080 fffffa80`023e7410 : nt!ExpWorkerThread+0x111
    fffff880`02db2d00 fffff800`02c5fc26 : fffff880`009e7180 fffffa80`0246f040 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02db2d40 00000000`00000000 : fffff880`02db3000 fffff880`02dad000 fffff880`035aa500 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
    ---------
    
    
    
    



    Drivers:

    Code:
    start             end                 module name
    fffff880`00f55000 fffff880`00fac000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
    fffff880`011e5000 fffff880`011f0000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
    fffff880`011b2000 fffff880`011bb000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`011bb000 fffff880`011e5000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
    fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
    fffff880`00da3000 fffff880`00dd3000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00d45000 fffff880`00da3000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`01200000 fffff880`01273000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
    fffff880`017ec000 fffff880`017fa000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`013d2000 fffff880`013e8000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`02b2d000 fffff880`02b40000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`02a11000 fffff880`02b2d000   dump_iaStor dump_iaStor.sys Thu Jun 04 21:53:40 2009 (4A287AA4)
    fffff880`01325000 fffff880`01339000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`01000000 fffff880`0104c000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
    fffff880`0142b000 fffff880`01435000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
    fffff880`0104c000 fffff880`01086000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
    fffff800`031ed000 fffff800`03236000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
    fffff880`017e3000 fffff880`017ec000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
    fffff880`01096000 fffff880`011b2000   iaStor   iaStor.sys   Thu Jun 04 21:53:40 2009 (4A287AA4)
    fffff800`00ba3000 fffff800`00bad000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
    fffff880`01400000 fffff880`0141a000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
    fffff880`01660000 fffff880`0168b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
    fffff880`00ced000 fffff880`00d31000   mcupdate mcupdate.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
    fffff880`00e86000 fffff880`00ea0000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00fb5000 fffff880`00fbf000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`01374000 fffff880`013d2000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
    fffff880`017d1000 fffff880`017e3000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`016df000 fffff880`017d1000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`01600000 fffff880`01660000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
    fffff800`02c11000 fffff800`031ed000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
    fffff880`0144a000 fffff880`015ed000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
    fffff880`00e00000 fffff880`00e15000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00fbf000 fffff880`00ff2000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`0141a000 fffff880`0142b000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`00d31000 fffff880`00d45000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`01273000 fffff880`012ad000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
    fffff880`016d7000 fffff880`016df000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`012b7000 fffff880`01325000   SYMDS64  SYMDS64.SYS  Mon Aug 17 19:35:30 2009 (4A89E942)
    fffff880`01339000 fffff880`01374000   SYMEFA64 SYMEFA64.SYS Wed Apr 21 17:47:39 2010 (4BCF727B)
    fffff880`00ff2000 fffff880`00fff000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`00e15000 fffff880`00e2a000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00e2a000 fffff880`00e86000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
    fffff880`0168b000 fffff880`016d7000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
    fffff880`00ea2000 fffff880`00f46000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
    fffff880`00f46000 fffff880`00f55000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00fac000 fffff880`00fb5000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
    Mini Kernel Dump does not contain unloaded driver list
    
    
     
  3. davehc

    davehc Microsoft MVP
    Premium Supporter Microsoft MVP

    Joined:
    May 1, 2008
    Messages:
    5,116
    Likes Received:
    301
    Could be a CPU overheating problem. How long after a new start does it take before shutdown? If immediately, then I doubt overheating. Do you have a monitor installed, from which you can see the temperatures?

    What happens if you run in safe mode?
     
    1 person likes this.
  4. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Also, stop 0x124 is often caused by overclocking.
     

Share This Page

Loading...