Windows 10: BSOD from a Bugcheck - Forced Reboot Solved

  1.    13 Jan 2017 #1

    BSOD from a Bugcheck - Forced Reboot


    Hello:

    Earlier today I had a forced reboot. Checked Reliability History to discover the following:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffc08c1453a1d8, 0x00000000f2000040, 0x0000000000000800). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b10d934f-a9bf-4192-a3e0-75c025c26b9d.

    I'm attaching a zip file of the Windows Dump and would appreciate any advice on this shocking event.

    JOHN-PC-13_01_2017_185218_91.zip
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 4,723
    Windows 10 Pro X64 14393.969
       13 Jan 2017 #2

    The zip file you uploaded is empty. Please try dm_log_collector again.

    Also, if C:\WINDOWS\MEMORY.DMP is there, zip it up then upload to a file sharing site like OneDrive and post a link to it here.
      My ComputersSystem Spec

  3.    13 Jan 2017 #3

    Thanks for your reply. I have tried again as you asked, and attach zip file here. I have never used a file sharing service, and would need to learn how.

    When I tried to attach the TFdebug files to this reply, I was unable to find it on the list of desktop items despite that I can see it there.

    JOHN-PC-13_01_2017_223243_79.zip

    Hope this zip is not empty.
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 4,723
    Windows 10 Pro X64 14393.969
       14 Jan 2017 #4

    Windows 10 comes with OneDrive. Use it to upload the zipped file. See if this explains it better: How to Share Files and Folders from OneDrive in Windows 10

    The dump shows a hardware machine check:
    Code:
    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: ffffc08c1453a1d8, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000f2000040, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000800, Low order 32-bits of the MCi_STATUS value.
    Code:
    1: kd> !errrec ffffc08c1453a1d8
    ===============================================================================
    Common Platform Error Record @ ffffc08c1453a1d8
    -------------------------------------------------------------------------------
    Record Id     : 01d26db6155d456e
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/13/2017 21:46:37 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc08c1453a258
    Section       @ ffffc08c1453a330
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : BUS error
    Operation     : Generic
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x000000000001067a
    Processor ID  : 0x0000000000000001
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc08c1453a2a0
    Section       @ ffffc08c1453a3f0
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000001
    CPU Id        : 7a 06 01 00 00 08 02 01 - fd e3 08 0c ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ ffffc08c1453a3f0
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc08c1453a2e8
    Section       @ ffffc08c1453a470
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 1 Bank 0)
      Status      : 0xf200004000000800
    That error (BUSL0_SRC_ERR_M_NOTIMEOUT_ERR) means the processor sent out a read request to L0 cache, and there was a delay in return (either a cache miss, or invalid data in cache). - cluberti.

    Several possible causes for this.

    1. CPU is defective or overheating
    2. Power supply low or fluctuating

    Check that the vents on the laptop are not blocked. Blow out with a can of compressed air.

    Run a program like Speedfan or CPUZ to monitor temperatures and voltages, see what that shows.

    This is a 5-6 year old laptop with a BIOS from 2011 and no drivers later than Windows 7 available from the manufacturer.

    Noticed you have a lot of old drivers:
    Code:
    2008/03/18 08:12:13 PM  C:\WINDOWS\system32\drivers\qcfilterhp.sys
    2008/09/24 02:28:20 PM  C:\WINDOWS\system32\drivers\SiSRaid2.sys
    2008/10/01 05:56:04 PM  C:\WINDOWS\system32\drivers\sisraid4.sys
    2008/11/10 10:01:35 AM  C:\WINDOWS\system32\DRIVERS\agrsm64.sys
    2009/01/09 12:51:28 PM  C:\WINDOWS\system32\DRIVERS\qcusbserhp.sys
    2009/01/09 12:53:45 PM  C:\WINDOWS\system32\drivers\qcusbnethp.sys
    2009/04/29 09:48:30 AM  C:\WINDOWS\system32\drivers\HpqKbFiltr.sys
    2009/05/18 01:31:55 PM  C:\WINDOWS\system32\drivers\ADIHdAud.sys
    2009/06/23 03:50:00 PM  C:\WINDOWS\system32\drivers\HECIx64.sys
    2009/06/25 04:04:18 AM  C:\WINDOWS\system32\drivers\rimmpx64.sys
    2009/07/20 05:30:52 AM  C:\WINDOWS\system32\DRIVERS\rismcx64.sys
    2010/01/13 11:37:13 AM  C:\WINDOWS\system32\DRIVERS\NETw5s64.sys
    2010/02/23 03:44:48 PM  C:\WINDOWS\system32\DRIVERS\cpqbttn.sys
    2010/04/07 06:58:49 PM  C:\WINDOWS\system32\DRIVERS\e1y62x64.sys
    2010/05/19 11:31:31 PM  C:\WINDOWS\system32\Drivers\ATSwpWDF.sys
    2010/06/03 09:27:13 PM  C:\WINDOWS\system32\DRIVERS\SynTP.sys
    2011/04/11 02:48:16 PM  C:\WINDOWS\system32\drivers\iaStorV.sys
    2011/05/13 02:47:02 PM  C:\WINDOWS\system32\DRIVERS\Accelerometer.sys
    2011/05/13 02:47:02 PM  C:\WINDOWS\system32\DRIVERS\hpdskflt.sys
    2012/01/23 05:44:07 PM  C:\WINDOWS\system32\drivers\NETwNs64.sys
    2012/11/26 07:02:51 PM  C:\WINDOWS\system32\drivers\stexstor.sys
    2012/12/11 04:21:44 PM  C:\WINDOWS\system32\drivers\amdsbs.sys
    2013/01/21 02:00:28 PM  C:\WINDOWS\system32\drivers\vstxraid.sys
    2013/03/15 07:39:38 PM  C:\WINDOWS\system32\drivers\lsi_sss.sys
    2013/03/26 05:36:54 PM  C:\WINDOWS\system32\drivers\HpSAMD.sys
    2013/06/03 06:02:39 PM  C:\WINDOWS\system32\drivers\megasr.sys
    Might be a good idea to try doing a clean install. Backup your data first.
    Follow this tutorial: Windows 10 - Clean Install

    Since this is an older laptop, I would not be surprised if the problem is over heating though.
      My ComputersSystem Spec

  5.    14 Jan 2017 #5

    Thank you so much for the information. Yes it is a refurbished HP Elitebook with Windows 7, upgraded to Windows 10. I'll review the file sharing info that you sent.

    On the matter of drivers, is there a software that will update drivers, and is it recommended to do so?
      My ComputerSystem Spec

  6. Ztruker's Avatar
    Posts : 4,723
    Windows 10 Pro X64 14393.969
       16 Jan 2017 #6

    Stay away from automated driver update software. You never know what you 're getting and it's often not good. I'm sure some are better than others but I much prefer locating updated drivers manually.
      My ComputersSystem Spec

  7.    16 Jan 2017 #7

    Thank you for your help and advice. Happy New Year. Be well...
      My ComputerSystem Spec

  8. Ztruker's Avatar
    Posts : 4,723
    Windows 10 Pro X64 14393.969
       17 Jan 2017 #8

    Same to you. If you have any questions, please ask but over in the General Support | Windows 10 Forums, not here in the BSOD forum.
      My ComputersSystem Spec


 

Related Threads
Solved BSOD from a Bugcheck - Forced Reboot in BSOD Crashes and Debugging
My computer suddenly encountered a BSOD and then forced a reboot. I got the following error message: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000fc (0xfffff8003f291fe8, 0x80000002203e8121, 0xffffd000258dd050,...
Hi Guys, I recently purchased a MSI laptop (GT72VR 6RE), and upgraded Win 10 version from Home to Pro. Performed the upgrade as soon as I fired up the laptop for the first time. Last couple of weeks, while working on Google Drive (via Chrome)...
So I've been having these random Thread Stuck In Driver errors in my poor laptop for a good while now. This time around I had Skype Preview open, Chrome, and League. It happened when I wasn't even in a game on League--- I was responding to a friend...
Possible BSOD from bugcheck. in BSOD Crashes and Debugging
Hello, in my last three months with my new computer, with Windows 10, I've come across a large amount of issues. Most I have found fixes for, some I have not been able to. One of the many I haven't successfully found a fix for, is an error that...
My machine reboot last night, likely due to an update that got pushed out, and now I can no longer click on the start menu. Windows key does not pull it up either. Also, the volume button in the bottom right of the screen, I cannot click on that...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 03:02.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums