BSOD caused by hal.dll

Page 1 of 2 12 LastLast

  1. Posts : 11
    Windows 10
       #1

    BSOD caused by hal.dll


    Hello!
    So this Night my pc, Got a bsod and ever since then i try to start my pc, it will come again after sometime(not that long) so what i have tried to do is:
    Run the system, with both of my ram(1 at a time), same issue.
    Unplug my ssd with Windows and install Windows On my other ssd and while i was installing my gpu driver, same issue..

    Bluescreenview: https://gyazo.com/ff258e10820610016daab404083f5e97

    My specs:
    I7 6700k
    Corsair Vengeance LED DDR4 3200MHz 2x8GB
    ASUS Z170 PRO GAMING/AURA
    Cooler Master B700 VER.2, 700W PSU
    Gigabyte GeForce GTX 970 4GB
    Samsung 850 evo 250gb
    NZXT Kraken x61

    Thanks in advance!
    Last edited by Apisathan; 09 Jan 2017 at 17:11. Reason: Wanted to upload the file fast since my pc close to instant bsod after startup
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    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: ffffda84e4118028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000f6101400, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040150, Low order 32-bits of the MCi_STATUS value
    Code:
    7: kd> !errrec ffffda84e4118028
    ===============================================================================
    Common Platform Error Record @ ffffda84e4118028
    -------------------------------------------------------------------------------
    Record Id     : 01d26ac43e4b7058
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 1/9/2017 22:04:31 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffda84e41180a8
    Section       @ ffffda84e4118180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Instruction Execute
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x00000000000506e3
    Processor ID  : 0x0000000000000007
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffda84e41180f0
    Section       @ ffffda84e4118240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000007
    CPU Id        : e3 06 05 00 00 08 10 07 - bf fb fa 7f 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  @ ffffda84e4118240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffda84e4118138
    Section       @ ffffda84e41182c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : ICACHEL0_IRD_ERR (Proc 7 Bank 0)
      Status      : 0xf610140000040150
      Address     : 0x00007ffec43ad130
      Misc.       : 0x0000000000000000
    ICACHEL0_IRD_ERR (Proc 7 Bank 0) - cache read error, processor 7 bank 0.

    Overclocking:
    If you are overclocking, set all the hardware components to their defaults.

    Test your RAM modules for possible errors.
    MemTest86+ - Test RAM
    Run memtest86+ for at least 8 consecutive passes.

    If it starts showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

    Take a camera snap of the memtest86+ window before closing the program. Let us see it.
    Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums

    Stress test the Graphics Card using Furmark.
    FurMark - GPU Stress Test
    Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

    Stress test the CPU.
    Prime95 - Stress Test Your CPU
    It saves the result as a .txt file in the prime95's folder. Upload the file for us.

    Also, check that all fans are working and none are clogged. Check temperatures with a program like Speedfan or CPUZ or HWMonitor. If the PC has been running hot that can damage the CPU.
      My Computers


  3. Posts : 11
    Windows 10
    Thread Starter
       #3

    Should i run memtest86+ even then i use ddr4 or should i use the free version of memtest86? And also How long should i run furmark for? If it doesnt overheat?

    Update:
    I decide to use memtest86 since it has ddr4 support
    Last edited by Apisathan; 10 Jan 2017 at 13:04.
      My Computer


  4. Posts : 11
    Windows 10
    Thread Starter
       #4

    I did the cpu stress test, and after 2 hours and 30 min~ my pc got a bsod, and after that it the pc got weird, and slow.
      My Computer


  5. Posts : 11
    Windows 10
    Thread Starter
       #5

    My cpu is acting weird and my pc freezes every 3 second.
    Imgur: The most awesome images on the Internet

    Probarly my flaut because i ran furmark, with another GPU then i normally use, and didn't install the right driver, but i still think you should know it since, it looked weird.

    I'm still doing the memtest, its on 5 passes after 9 hours and 30 minutes.
    Last edited by Apisathan; 10 Jan 2017 at 19:10.
      My Computer


  6. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #6

    Apisathan said:
    I did the cpu stress test, and after 2 hours and 30 min~ my pc got a bsod, and after that it the pc got weird, and slow.
    Were you monitoring temperatures? Sounds suspiciously like a over heating problem.

    Run dm_log_collector again ang upload the zip file, lets see if anything has changed.
      My Computers


  7. Posts : 11
    Windows 10
    Thread Starter
       #7

    Memtest just got done: Imgur: The most awesome images on the Internet
    Then i was cpu stress testing was 12:36 10/01, and i was looking the 2 hours and 25~ min, and all the time it was on 69c, but i don't know the last 5-10 minutes, since i was about and make food.
    Last edited by Apisathan; 11 Jan 2017 at 04:24.
      My Computer


  8. Posts : 11
    Windows 10
    Thread Starter
       #8

    I took my GPU out of my machine, and plugged a old in GTX 660 TI, and was able to run the CPU stress test fully, and for more then 3 hours, and so far there have been no issues with BSOD. And for testing i plugged my GTX 970 into my brothers pc, to see if there will be any issue there. Going to update about that later.
      My Computer


  9. Posts : 654
    windows 10 Pro
       #9

    Have you tried this CPU Test from Intel.

    Intel Processor Diagnostic Tool (works in Windows)
    Only need to run 1 or 2 of the tests under most circumstances.
    https://downloadcenter.intel.com/dow...iagnostic-Tool

    Although i do not think it is is the cause of the WHEA_UNCORRECTABLE_ERROR (124), update your Razer drivers many references in WER= windows error report.
    Also your logitech webcamera has drivers from 2012, update to windows 10 drivers or if not avaliable as a test uninstall and remove them.
      My Computer


  10. Posts : 11
    Windows 10
    Thread Starter
       #10

    Okay, even when i switch graphics card, it still crashs and shouldn't be due to cpu overheat because i was looking at speccy while the bsod come and my CPU was on 28c. (And my brother with my graphics card runs just fine)
      My Computer


 

  Related Discussions
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 02:37.
Find Us




Windows 10 Forums