Page 1 of 2 12 LastLast
  1.    15 Mar 2017 #1
    Join Date : Mar 2017
    Posts : 7
    Windows 10 Pro N 64-bit

    BSOD seemingly caused by hardware fault


    Hi Guys,

    Been battling with a BSOD for a while that according to blue screen viewer is being caused by hal.dll. Traced this to mean some sort of hardware error so have tried cleaning out PC to eliminate and heat issues and run memory tests a couple of times which have always come back fine.

    It doesnt seem to be caused by me doing anything in particular and seems to happen fairly randomly, often a few times in an hour and then run fine for a while.

    My next plan was to do a BIOS update but figured I should check in and see if I was missing anything obvious before hand (plus to make sure I was applying the right update!) Could potentially do with some driver updates if that might be the cause?

    The dump files should be attached.

    Any help would be great, thanks!
      My ComputerSystem Spec
  2.    16 Mar 2017 #2
    Join Date : Jun 2015
    Posts : 12,882
    Windows 10 Pro

    All dumps are similar, a read error with core 3.
    Have BSOD occured from the beginning?
    Code:
    ===============================================================================
    Common Platform Error Record @ ffffc00bb5fe2028
    -------------------------------------------------------------------------------
    Record Id     : 01d29b6c0319a61f
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 3/13/2017 19:23:17 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc00bb5fe20a8
    Section       @ ffffc00bb5fe2180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Data Read
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100f43
    Processor ID  : 0x0000000000000003
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc00bb5fe20f0
    Section       @ ffffc00bb5fe2240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000003
    CPU Id        : 43 0f 10 00 00 08 04 03 - 09 20 80 00 ff fb 8b 17
                    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  @ ffffc00bb5fe2240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc00bb5fe2138
    Section       @ ffffc00bb5fe22c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL1_DRD_ERR (Proc 3 Bank 0)
      Status      : 0xb633200062000135
      Address     : 0x00000001f4185a00
      Misc.       : 0x0000000000000000
      My ComputersSystem Spec
  3.    16 Mar 2017 #3
    Join Date : Mar 2017
    Posts : 7
    Windows 10 Pro N 64-bit
    Thread Starter

    Quote Originally Posted by axe0 View Post
    All dumps are similar, a read error with core 3.
    Have BSOD occured from the beginning?
    Code:
    ===============================================================================
    Common Platform Error Record @ ffffc00bb5fe2028
    -------------------------------------------------------------------------------
    Record Id     : 01d29b6c0319a61f
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 3/13/2017 19:23:17 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc00bb5fe20a8
    Section       @ ffffc00bb5fe2180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Data Read
    Flags         : 0x00
    Level         : 1
    CPU Version   : 0x0000000000100f43
    Processor ID  : 0x0000000000000003
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc00bb5fe20f0
    Section       @ ffffc00bb5fe2240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000003
    CPU Id        : 43 0f 10 00 00 08 04 03 - 09 20 80 00 ff fb 8b 17
                    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  @ ffffc00bb5fe2240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc00bb5fe2138
    Section       @ ffffc00bb5fe22c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL1_DRD_ERR (Proc 3 Bank 0)
      Status      : 0xb633200062000135
      Address     : 0x00000001f4185a00
      Misc.       : 0x0000000000000000
    I want to say no, but its a 6 year old build(with a few changes but same cpu) so difficult to remember.

    Definitely had a bsod problem for a long while, with varying severity. Usually, when it got bad I could clean out my pc and it would fix it so I have always just attributed it to heat.
      My ComputerSystem Spec
  4.    17 Mar 2017 #4
    Join Date : Jan 2017
    Karlsruhe
    Posts : 733
    Windows 10 Pro

    Could be overheating:




    BSOD seemingly caused by hardware fault Diagnostic Test BSOD seemingly caused by hardware fault
     CPU TEST

    Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums



    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
      My ComputerSystem Spec
  5.    17 Mar 2017 #5
    Join Date : Jun 2015
    Posts : 12,882
    Windows 10 Pro

    A couple of questions:
    What is your case, PSU and cooler?
    When was the last time that you replaced the thermal paste?
    Have you in those years kept an eye on the temps of the CPU?
    What changes have you made?
      My ComputersSystem Spec
  6.    17 Mar 2017 #6
    Join Date : Mar 2016
    Posts : 42
    Windows 10

    Hi Shuff,

    As BSODHunter stated this could be an overheating issue so I recommend running prime95 and reporting your temps.

    I would also recommend resetting your Cmos and updating your BIOS.
      My ComputerSystem Spec
  7.    17 Mar 2017 #7
    Join Date : Mar 2017
    Posts : 7
    Windows 10 Pro N 64-bit
    Thread Starter

    Quote Originally Posted by BSODHunter View Post
    Could be overheating:




    BSOD seemingly caused by hardware fault Diagnostic Test BSOD seemingly caused by hardware fault
     CPU TEST

    Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums



    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
    Crashed after about 30 secs, HWMonitor said it was at 67oC. Have seen it at 71 when streaming video and playing games.
      My ComputerSystem Spec
  8.    17 Mar 2017 #8
    Join Date : Mar 2017
    Posts : 7
    Windows 10 Pro N 64-bit
    Thread Starter

    Quote Originally Posted by axe0 View Post
    A couple of questions:
    What is your case, PSU and cooler?
    When was the last time that you replaced the thermal paste?
    Have you in those years kept an eye on the temps of the CPU?
    What changes have you made?
    Case - Cooler Master: Scout

    PSU - Cant remember exactly but its 700W cooler master psu that came with case

    CPU Cooler - ARCTIC Freezer 7 Pro Rev 2 - 150 Watt Multicompatible Low Noise CPU Cooler for AMD and Intel Sockets: Amazon.co.uk: Computers & Accessories

    Last time I replace thermal paste was when I bought the heat sink, which was apparantly 2014....

    Since the pc was first built - new heat sink, new gpu, new HDD and new SSD.

    Have tried to keep an eye on it and it has always run hot, originally when it became too much of a problem I replaced the stock cooler with the above. More recently, now the crashes have been getting worse ive been paying more attention and seen it get over 70oC
      My ComputerSystem Spec
  9.    17 Mar 2017 #9
    Join Date : Mar 2017
    Posts : 7
    Windows 10 Pro N 64-bit
    Thread Starter

    Quote Originally Posted by BSODHunter View Post
    Could be overheating:




    BSOD seemingly caused by hardware fault Diagnostic Test BSOD seemingly caused by hardware fault
     CPU TEST

    Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums



    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
    Forgot to attach dump, 17/03/17 at around 6pm
      My ComputerSystem Spec
  10.    17 Mar 2017 #10
    Join Date : Mar 2017
    Posts : 7
    Windows 10 Pro N 64-bit
    Thread Starter

    Quote Originally Posted by DeclanT View Post
    Hi Shuff,

    As BSODHunter stated this could be an overheating issue so I recommend running prime95 and reporting your temps.

    I would also recommend resetting your Cmos and updating your BIOS.
    Hi, yea have thought about doing both of those but just wanted to see if I was missing anything first. Definitley think it is a heat problem, this cpu has always run a little hot (IIRC it is stock over clocked (AMD Phenom II X4 980 3.7ghz))
      My ComputerSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Solved BSOD seemingly random driver_irql_not_less_or equal (etd.sys)
I have been having BSOD at random times, mostly while playing games, last few have been while i have been playing overwatch. The error it says is driver_irql_not_less_or equal (etd.sys), mini-dump files below
BSOD Crashes and Debugging
Solved Lots of BSOD's Seemingly Without Cause
Well, something must have changed since Windows updated, as I'm now getting very frequent BSOD's again. I once even got a BSOD, restarted and before the computer even started up, I got another BSOD... Here's the requested data:...
BSOD Crashes and Debugging
BSOD Watchdog on Windows 10, Seemingly Random
Hi everyone! This is my first post here. My computer has been fine until I updated it to windows 10 from win 8. I have been getting Watchdog violations randomly every 30 min to 3 hours since the update. One error report analyzed via WhoCrashed...
BSOD Crashes and Debugging
Seemingly random BSOD's on new laptop (ntoskrnl.exe)?
Hi everyone, I'm having an issue with my new laptop running Windows 10. After increasingly short periods of time, I am experiencing a BSOD seemingly at random, with the error message "DRIVER_POWER_STATE_FAILURE". I have looked into my minidump...
BSOD Crashes and Debugging
Solved BSOD Seemingly Random when using PC normally. Variety of BSOD errors
Hi, Over the past couple of days I have been having reasonably frequent BSODs. Some have not created a dump file. I cant pinpoint anything in particular but it seems to be pointing to a driver issue but never identifies the driver from what I can...
BSOD Crashes and Debugging
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 06:24.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums