Unknown Crashes

Page 1 of 2 12 LastLast

  1. Posts : 14
    Windows 7 Ultimate x64
       #1

    Unknown Crashes


    Windows 7 is x64 bit.
    Windows 7 is the original OS on the system.
    Windows 7 is an OEM version.

    The system is about 8 months old.
    The OS is about 8 months old.


    When my computer is attempting to install or uninstall a large amount of things or download for a long period of time the system will crash in a strange way. Usually my mouse will work fine but nothing on screen will respond (Like everything is in a No Response state) so I end up having to force a shutdown. Any help would be appreciated.
      My Computer


  2. Posts : 670
    Windows 7 x64
       #2

    WHEA_UNCORRECTABLE_ERROR (124)
    X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV


    Stop 0x124 - what it means and what to try

    https://www.sevenforums.com/tutorials...t-prime95.html

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [G:\101910-22932-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e5d000 PsLoadedModuleList = 0xfffff800`0309ae50
    Debug session time: Tue Oct 19 19:41:09.510 2010 (UTC - 5:00)
    System Uptime: 0 days 0:00:14.679
    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, fffffa8006800038, 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: fffffa8006800038, 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
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031b66f0 fffff800`03117a89 : fffffa80`06800010 fffffa80`04f1b040 00000000`00000008 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`031b6c10 fffff800`02ff9547 : fffffa80`06800010 fffff800`030725f8 fffffa80`04f1b040 00000000`00000202 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`031b6c40 fffff800`02f61b95 : fffff800`030d4360 fffffa80`069df1d8 fffffa80`069df1d0 fffffa80`04f1b040 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`031b6c80 fffff800`02edc161 : fffff880`00d8ee00 fffff800`02f61b70 fffffa80`04f1b040 bb000000`98880fc0 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`031b6cb0 fffff800`03172166 : fffffcfc`e8c48b4d fffffa80`04f1b040 00000000`00000080 fffffa80`04f06040 : nt!ExpWorkerThread+0x111
    fffff880`031b6d40 fffff800`02ead486 : fffff880`02f63180 fffffa80`04f1b040 fffff880`02f6dfc0 41564155`41544157 : nt!PspSystemThreadStartup+0x5a
    fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`037ef540 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_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [G:\101910-24538-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`03099e50
    Debug session time: Tue Oct 19 23:45:10.462 2010 (UTC - 5:00)
    System Uptime: 0 days 0:00:15.631
    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, fffffa8006b03038, 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: fffffa8006b03038, 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
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`031bd6f0 fffff800`03116a89 : fffffa80`06b03010 fffffa80`04f1bb60 00000000`00000007 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
    fffff880`031bdc10 fffff800`02ff8547 : fffffa80`06b03010 fffff800`030715f8 fffffa80`04f1bb60 00000003`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
    fffff880`031bdc40 fffff800`02f60b95 : fffff800`030d3360 fffffa80`069ddbe8 fffffa80`069ddbe0 fffffa80`04f1bb60 : nt!WheapProcessWorkQueueItem+0x57
    fffff880`031bdc80 fffff800`02edb161 : fffff880`0115fe00 fffff800`02f60b70 fffffa80`04f1bb60 00000554`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
    fffff880`031bdcb0 fffff800`03171166 : 00000554`00000000 fffffa80`04f1bb60 00000000`00000080 fffffa80`04f06040 : nt!ExpWorkerThread+0x111
    fffff880`031bdd40 fffff800`02eac486 : fffff880`02f63180 fffffa80`04f1bb60 fffff880`02f6dfc0 00000554`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`03d0d540 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_AuthenticAMD_PROCESSOR_BUS_PRV
    
    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmtn
    start             end                 module name
    fffff800`00bba000 fffff800`00bc4000   kdcom    kdcom.dll    Tue Jul 14 04:31:07 2009 (4A5BDFDB)
    fffff800`02e13000 fffff800`02e5c000   hal      hal.dll      Tue Jul 14 04:27:36 2009 (4A5BDF08)
    fffff800`02e5c000 fffff800`03439000   nt       ntkrnlmp.exe Tue Jul 14 02:40:48 2009 (4A5BC600)
    fffff880`00c00000 fffff880`00c0f000   WDFLDR   WDFLDR.SYS   Tue Jul 14 02:19:54 2009 (4A5BC11A)
    fffff880`00c13000 fffff880`00c20000   mcupdate mcupdate.dll Tue Jul 14 04:29:09 2009 (4A5BDF65)
    fffff880`00c20000 fffff880`00c34000   PSHED    PSHED.dll    Tue Jul 14 04:32:23 2009 (4A5BE027)
    fffff880`00c34000 fffff880`00c92000   CLFS     CLFS.SYS     Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`00c92000 fffff880`00d52000   CI       CI.dll       Tue Jul 14 04:32:13 2009 (4A5BE01D)
    fffff880`00d52000 fffff880`00df6000   Wdf01000 Wdf01000.sys Tue Jul 14 02:22:07 2009 (4A5BC19F)
    fffff880`00e26000 fffff880`00f4c000   spfp     spfp.sys     Sun Oct 11 23:55:14 2009 (4AD24632)
    fffff880`00f4c000 fffff880`00f55000   WMILIB   WMILIB.SYS   Tue Jul 14 02:19:51 2009 (4A5BC117)
    fffff880`00f55000 fffff880`00f84000   SCSIPORT SCSIPORT.SYS Tue Jul 14 03:01:04 2009 (4A5BCAC0)
    fffff880`00f84000 fffff880`00fdb000   ACPI     ACPI.sys     Tue Jul 14 02:19:34 2009 (4A5BC106)
    fffff880`00fdb000 fffff880`00fe5000   msisadrv msisadrv.sys Tue Jul 14 02:19:26 2009 (4A5BC0FE)
    fffff880`00fe5000 fffff880`00ff2000   vdrvroot vdrvroot.sys Tue Jul 14 03:01:31 2009 (4A5BCADB)
    fffff880`01007000 fffff880`0103a000   pci      pci.sys      Tue Jul 14 02:19:51 2009 (4A5BC117)
    fffff880`0103a000 fffff880`0104f000   partmgr  partmgr.sys  Tue Jul 14 02:19:58 2009 (4A5BC11E)
    fffff880`0104f000 fffff880`01064000   volmgr   volmgr.sys   Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`01064000 fffff880`010c0000   volmgrx  volmgrx.sys  Tue Jul 14 02:20:33 2009 (4A5BC141)
    fffff880`010c0000 fffff880`010c7000   pciide   pciide.sys   Tue Jul 14 02:19:49 2009 (4A5BC115)
    fffff880`010c7000 fffff880`010d7000   PCIIDEX  PCIIDEX.SYS  Tue Jul 14 02:19:48 2009 (4A5BC114)
    fffff880`010d7000 fffff880`010f1000   mountmgr mountmgr.sys Tue Jul 14 02:19:54 2009 (4A5BC11A)
    fffff880`010f1000 fffff880`010fa000   atapi    atapi.sys    Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`010fa000 fffff880`01124000   ataport  ataport.SYS  Tue Jul 14 02:19:52 2009 (4A5BC118)
    fffff880`01124000 fffff880`0112f000   amdxata  amdxata.sys  Tue May 19 20:56:59 2009 (4A12F2EB)
    fffff880`0112f000 fffff880`0117b000   fltmgr   fltmgr.sys   Tue Jul 14 02:19:59 2009 (4A5BC11F)
    fffff880`0117b000 fffff880`0118f000   fileinfo fileinfo.sys Tue Jul 14 02:34:25 2009 (4A5BC481)
    fffff880`0118f000 fffff880`011ed000   msrpc    msrpc.sys    Tue Jul 14 02:21:32 2009 (4A5BC17C)
    fffff880`01200000 fffff880`0121a000   ksecdd   ksecdd.sys   Tue Jul 14 02:20:54 2009 (4A5BC156)
    fffff880`01246000 fffff880`013e9000   Ntfs     Ntfs.sys     Tue Jul 14 02:20:47 2009 (4A5BC14F)
    fffff880`01400000 fffff880`01430000   CLASSPNP CLASSPNP.SYS Tue Jul 14 02:19:58 2009 (4A5BC11E)
    fffff880`01430000 fffff880`0143c000   dump_ataport dump_ataport.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`0143c000 fffff880`0144f000   dump_dumpfve dump_dumpfve.sys Tue Jul 14 02:21:51 2009 (4A5BC18F)
    fffff880`01457000 fffff880`014ca000   cng      cng.sys      Tue Jul 14 02:49:40 2009 (4A5BC814)
    fffff880`014ca000 fffff880`014db000   pcw      pcw.sys      Tue Jul 14 02:19:27 2009 (4A5BC0FF)
    fffff880`014db000 fffff880`014e5000   Fs_Rec   Fs_Rec.sys   Tue Jul 14 02:19:45 2009 (4A5BC111)
    fffff880`014e5000 fffff880`015d7000   ndis     ndis.sys     Tue Jul 14 02:21:40 2009 (4A5BC184)
    fffff880`01600000 fffff880`01612000   mup      mup.sys      Tue Jul 14 02:23:45 2009 (4A5BC201)
    fffff880`01612000 fffff880`0161b000   hwpolicy hwpolicy.sys Tue Jul 14 02:19:22 2009 (4A5BC0FA)
    fffff880`0161b000 fffff880`01655000   fvevol   fvevol.sys   Tue Jul 14 02:22:15 2009 (4A5BC1A7)
    fffff880`01655000 fffff880`0166b000   disk     disk.sys     Tue Jul 14 02:19:57 2009 (4A5BC11D)
    fffff880`0166b000 fffff880`01673000   AtiPcie  AtiPcie.sys  Tue May 05 18:00:22 2009 (4A005486)
    fffff880`01673000 fffff880`01681000   crashdmp crashdmp.sys Tue Jul 14 03:01:01 2009 (4A5BCABD)
    fffff880`01681000 fffff880`0168a000   dump_atapi dump_atapi.sys Tue Jul 14 02:19:47 2009 (4A5BC113)
    fffff880`0168a000 fffff880`016ea000   NETIO    NETIO.SYS    Tue Jul 14 02:21:46 2009 (4A5BC18A)
    fffff880`016ea000 fffff880`01715000   ksecpkg  ksecpkg.sys  Tue Jul 14 02:50:34 2009 (4A5BC84A)
    fffff880`01715000 fffff880`0175f000   fwpkclnt fwpkclnt.sys Tue Jul 14 02:21:08 2009 (4A5BC164)
    fffff880`0175f000 fffff880`0176f000   vmstorfl vmstorfl.sys Tue Jul 14 02:42:54 2009 (4A5BC67E)
    fffff880`0176f000 fffff880`017bb000   volsnap  volsnap.sys  Tue Jul 14 02:20:08 2009 (4A5BC128)
    fffff880`017bb000 fffff880`017c3000   spldr    spldr.sys    Mon May 11 19:56:27 2009 (4A0858BB)
    fffff880`017c3000 fffff880`017fd000   rdyboost rdyboost.sys Tue Jul 14 02:34:34 2009 (4A5BC48A)
    fffff880`01802000 fffff880`019ff000   tcpip    tcpip.sys    Tue Jul 14 02:25:34 2009 (4A5BC26E)
    Mini Kernel Dump does not contain unloaded driver list
      My Computer


  3. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #3

    cybercore is spot on. Error code 124 is a hardware issue. I will add that I have found an almost guaranteed BSOD maker on your system, Daemon tools:
    Please uninstall any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dump, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads. Select delete; do not select reinstall.

    Here is an alternative virtualization program that does not user the sptd.sys driver:
    Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview
    Also update this driver:
    AtiPcie.sys Tue May 05 11:00:22 2009 - ATI PCIE Driver for ATI PCIE chipsetGlobal Provider of Innovative Graphics, Processors and Media Solutions | AMD
    Try this and see if it helps your problem.
      My Computer


  4. Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       #4

    Thank you very much for the replies, sorry I haven't responded since yesterday but I was all day doing stress tests on my comp which took longer than I expected.

    I also found that my ATI was severely out of date (thank you for pointing that out) and went ahead and updated it. Since then I've had no crashes so far I will check up on the sptd.sys just to be sure I'll get back again once I've checked up on everything again thank you.
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #5

    You are welcome. Good job on updating ATI. Driver conflicts can cause the 124 error code; but usually it is a deeper problem than device drivers. However, you have to troubleshoot a 124 and that means eliminating every potential BSOD cause. I urge you to go ahead and uninstall Daemon tools and sptd.sys since sptd.sys is a well know BSOD maker.
      My Computer


  6. Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       #6

    Thanks for the tips on Daemon, after uninstalling the sptd.sys my computer even rebooted 5 seconds quicker. I went ahead and started using Magic ISO as well so thank you for that advice and heads up. I think I should be fine on the crashes now since I haven't had any since updating ATI even (so far.) Hopefully this continues if not I know where to go! Thanks a lot I appreciate it.
      My Computer


  7. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #7

    You are welcome, Cecil. Glad you can see an improvement in your system. Post back in two or three days and let us know how your system is running and if all is well, we can ask the moderators to mark this thread as solved.
      My Computer


  8. Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       #8

    Will do, but in case i forget to come back mark it as solved anyway! :)

    Thanks again!
      My Computer


  9. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #9

    We can do that. Don't be a stranger to the forum. :)
      My Computer


  10. Posts : 14
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Just following up (it's been a few more than 3 days but :P) So far there are no crashes since so thanks for the quick responses and fixes. I'll try to come around but in the meantime thanks so much for the help!
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
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 13:55.
Find Us