Windows 10: BSOD Caused by ntoskrnl.exe and hal.dll

Discus and support BSOD Caused by ntoskrnl.exe and hal.dll in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, I am getting a BSOD in my machine. Before this, I also got problems with Windows 10 and my APU (A10-4600M with AMD Radeon HD 7970M). I also fixed... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Mistral, Jun 29, 2017.

  1. Mistral Win User

    BSOD Caused by ntoskrnl.exe and hal.dll


    Hi, I am getting a BSOD in my machine. Before this, I also got problems with
    Windows 10 and my APU (A10-4600M with AMD Radeon HD 7970M). I also fixed that
    by hiding the windows update and use AMD-Catalyst 15.7.1 driver instead of a conflict driver.
    Maybe those cause some problems.

    Thank you in advance for your replies *Smile.


    Attachment 141818

    :)
     
    Mistral, Jun 29, 2017
    #1
  2. AngDean Win User

    hal.dll+35f1f bsod error in Windows 10

    OT- hal.dll+35f1f bsod

    Hello,

    There was a bsod just now, which is the first time I've experienced it - and should I be worrying about it?

    This is what I got from BlueScreenView:

    071816-24656-01.dmp

    18/7/2016 8:23:23 PM

    0x00000124

    00000000`00000000

    ffffe000`2db12028

    00000000`b2000000

    00000000`00100402

    hal.dll

    hal.dll+35f1f

    x64

    ntoskrnl.exe+142940

    C:\WINDOWS\Minidump\071816-24656-01.dmp

    What caused this? Thanks!
     
    AngDean, Jun 29, 2017
    #2
  3. leandronb Win User
    BSOD APC_INDEX_MISMATCH win32full.sys on Windows 10

    I ran Bluescreenview as told in the thread you linked and it says that BSOD was caused by hal.dll bugcheck code was 0x00000001.

    It was also highlighted in red the files ntoskrnl.exe, win32kbase.sys and win32kfull.sys.

    In that thread the BCCode was 0x00000024 so i don't know if it applies to the error i had.
     
    leandronb, Jun 29, 2017
    #3
  4. philc43 Win User

    BSOD Caused by ntoskrnl.exe and hal.dll

    These errors are most likely hardware related. Analysing a x124 WHEA Hardware error requires a lot of testing to track down the culprit. You can do this by following the x124 troubleshooting section in the following tutorial. Please report back all your findings and show screenshots of the result.

    WinDBG - The Basics for Debugging Crash Dumps in Windows 10
     
    philc43, Jun 29, 2017
    #4
  5. Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
    You can upload it to an cloud service like dropbox or onedrive.
     
    BSODHunter, Jun 29, 2017
    #5
  6. Mistral Win User
    Ok, I will post kernel memory dump after I finish running memtest86.
     
    Mistral, Jun 29, 2017
    #6
  7. zbook New Member
    For the memtest86+:
    use version 5.01 : Memtest86+ - Advanced Memory Diagnostic Tool
    make sure it runs for 8 or more runs
    When you have completed 8 or more runs please post an image into the thread.
    http://www.memtest.org/https://answe...f-ecc7b7ff6461

    When testing CPU and GPU please monitor temperatures:

    Speccy - Free Download - Piriform: Speccy - System Information - Free Download


    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID


    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
     
    zbook, Jun 29, 2017
    #7
  8. zbook New Member

    BSOD Caused by ntoskrnl.exe and hal.dll

    Code: WHEA_UNCORRECTABLE_ERROR (124)[/quote] Code: BugCheck 124, {0, ffffc8854f11d028, b0800000, 60151}Probably caused by : AuthenticAMD[/quote] Code: mafia2.exe[/quote] Code: BugCheck 124, {0, ffffc50c60df1028, b0800000, 60151}Probably caused by : AuthenticAMD[/quote] Code: CompatTelRunne[/quote] Code: BugCheck 109, {a3a0215933dcf65d, b3b72ddf865ed3f3, 6, 18}Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/quote] Code: 23/6/2560 2:23 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x1bb8 Faulting application start time: 0x01d2ebc7a2d31783 Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: 144f3837-4097-4751-92fa-5f7ada963871 Faulting package full name: Faulting package-relative application ID:22/6/2560 13:43 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x24e8 Faulting application start time: 0x01d2eb5d8a08cabf Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: 6b96961e-6e0c-4630-9bae-827b0ab5b63a Faulting package full name: Faulting package-relative application ID:22/6/2560 13:43 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0xe0 Faulting application start time: 0x01d2eb5d823d3801 Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: de626716-5141-42af-a6bc-155caec329ae Faulting package full name: Faulting package-relative application ID:22/6/2560 13:42 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x1940 Faulting application start time: 0x01d2eb5d7002b117 Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: ca940a58-9526-4dfd-add1-d9ded06ef1da Faulting package full name: Faulting package-relative application ID:22/6/2560 13:34 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x23f4 Faulting application start time: 0x01d2eb5bf5f3425b Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: 83a40f0c-8a96-4333-bf46-6bebb49c583f Faulting package full name: Faulting package-relative application ID:14/6/2560 2:00 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x15b0 Faulting application start time: 0x01d2e4b209614769 Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: f67d8cd6-285b-4ff7-b080-dfd1f5181f36 Faulting package full name: Faulting package-relative application ID:13/6/2560 11:46 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x1808 Faulting application start time: 0x01d2e43aa4589fb6 Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: 7235e0c8-a7fe-4fe9-8ce1-ce3ef63b1a31 Faulting package full name: Faulting package-relative application ID:13/6/2560 6:03 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x1cac Faulting application start time: 0x01d2e40abf5ccd74 Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: c077013f-72be-4a53-9b48-de8c29fb5fe4 Faulting package full name: Faulting package-relative application ID:13/6/2560 6:00 Application Error Faulting application name: RadeonSettings.exe, version: 10.1.1.1682, time stamp: 0x58fea395 Faulting module name: atiadlxx.dll, version: 7.16.10.1301, time stamp: 0x565b5d82 Exception code: 0xc0000005 Fault offset: 0x000000000008e637 Faulting process id: 0x21f0 Faulting application start time: 0x01d2e40a4cb9c20a Faulting application path: C:\Program Files\AMD\CNext\CNext\RadeonSettings.exe Faulting module path: C:\WINDOWS\SYSTEM32\atiadlxx.dll Report Id: 2504141c-b60a-4916-bce0-5201c099e645 Faulting package full name: Faulting package-relative application ID:[/quote]
    Open administrative command prompt and type or copy and paste:


    1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


    2) sfc /scannow


    3) dism /online /cleanup-image /restorehealth


    4) chkdsk /scan


    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread



    5) uninstall: AMD Radeon
    a) create a restore point
    b) download the new driver from Download Drivers
    to the desktop
    c) download and install: Display driver uninstaller (DDU) Official Display Driver Uninstaller DDU Download
    c) Open AMD install manager
    d) Check AMD display driver (do not check any other boxes)
    e) Reboot into safe mode
    f) In safe mode use Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download
    g) Reboot
    h) Turn off antivirus
    i) install the driver from the desktop

    See this link for text and images: Clean Install AMD Graphics Drivers | Community


    6) Make sure that there is no over clocking while troubleshooting.

    Sometimes there are problems in the bios that produce bsod.

    The bios in your computer: BIOS Version/Date American Megatrends Inc. E16FKAMS.109, DATE UNKNOWN


    Please check to see if this is the most up to date version.

    To ensure that there are no improper bios settings please reset the bios.

    Sometimes there can be failure to boot after resetting the bios.

    So please make sure your files are backed up.
    Please make a backup image with Macrium: Macrium Software | Macrium Reflect Free: Macrium Software | 404
    Please create a restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:3 Ways to Reset Your BIOS - wikiHow
     
    zbook, Jun 29, 2017
    #8
  9. Mistral Win User
    I just finished running memtest86 and it doesn't show any error. But my machine stuck in bad system config info loop bsod. What should i do next.
     
    Mistral, Jul 2, 2017
    #9
  10. zbook New Member
    Please post an image of the Memtest 86+ results and please post an image of what you mean by info loop.

    You should be able to power off.

    Create a bootable windows 10 iso as a backup plan: Download Windows 10
     
    zbook, Jul 2, 2017
    #10
  11. zbook New Member
    zbook, Jul 2, 2017
    #11
  12. Mistral Win User
    Mistral, Jul 2, 2017
    #12
  13. Mistral Win User

    BSOD Caused by ntoskrnl.exe and hal.dll

    My windows 10 version are 1703 (Build 15063.413). I attached the new zipped in this post.
     
    Mistral, Jul 2, 2017
    #13
  14. zbook New Member
    Code: BugCheck 74, {2, ffffe10032d86a70, 1, ffffffffc000014c}Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+a3ce7 )[/quote]
    Code:
     
     The memory test had 20 runs and zero errors. That number of runs is sufficient to rule out RAM/DIMM problems. 
     So far you have removed the Realtek driver and updated the AMD driver.
     The bsod tonight did not give sufficient information to determine the misbehaving driver or application.
     To recover the operating system you performed a registry backup and it was successful.
     
     Open administrative command prompt and run these commands:
     1) sfc /scannow
     2) dism /online /cleanup -image /restorehealth
     3) chkdsk /scan
     
     Post the results into the thread.
     
     The next step is using Windows driver verifier to stimulate drivers and find the misbehaving drivers. Windows driver verifer will repetitively produce bsod until there are no more malfunctioning drivers or until it is turned off.
     
     You must know how to turn it off. That is accomplished by opening the windows recovery or windows advanced troubleshooting menu and navigating to startup options (not startup repair). Once startup options is chosen there is a restart and after restart you will select #6 safe mode with command prompt and type verifier /reset
     
     The command verifier /reset most of the time turns off windows driver verifier. When it is off you will reboot to the desktop. On the desktop you will use two software applications to analyze the dump files. They are Bluescreenview and Whocrashed and they each may add something to the analysis. If you have a driver or application that is identified and can be uninstalled with device manager or control panel you will uninstall it. Then you can either attempt to reinstall another driver or continue finding misbehaving drivers and uninstalling them. It's a personal choice as to which method you prefer. The end result should be the same. All of the misbehaving drivers or applications will be uninstalled and some will be reinstalled and tested again with windows driver verifier to make sure that the new drivers don't misbehave.
     
     To practice navigating the advanced troubleshooting menu open administrative command prompt and copy and paste: 
     shutdown /r /o /f /t 00
     When the windows recovery opens you will navigate to startup repair. If the startup repair stop code fails you will navigate to command prompt with Administrator: X:\windows\system32/cmd.exe and enter 
     verifier /bootmode resetonbootfail to turn off windows driver verifer. If that fails to turn windows driver verifier off you will navigate to restore and perform a restore to the most recent valid restore point. You will make a brand new restore point before using windows driver verifier.
     
     When there is a bsod you will want time to view the window. It typically will display a stop code driver verifier detected violation and sometimes it may display the misbehaving driver in the form *.sys. If you see a driver named please record it.
     
     There are settings to view to make sure you are ready to record bsod and to turn off automatic restart so that you have time to view the bsod window: 
     Keyboard: win + r keys simultaneously > type or copy and paste: sysdm.cpl > click advanced tab > under startup and recover click settings > under system failure un-check automatically restart
     [url='https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/bsod-finding-and-fixing-them/1939df35-283f-4830-a4dd-e95ee5d8669d']BSOD Finding and fixing them - Microsoft Community[/url]
     
     This is information on how to start windwos verifier and the customized settings for the tests and the drivers.
     
     Please make sure that you have files backed up, have made and image using Macrium, and have made a fresh restore point before starting Windows driver verifier.
     
     [url='https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983']Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community[/url]
     
     Once all misbehaving drivers or applications have been fixed you will use windows driver verifier for 36 hours of typical computer use. If there are no more bsod the testing will be completed. The misbehaving drivers/applications will be fixed and preventative maintenance will be accomplished.
     
     During the use of windows driver verifier you may notice that performance is diminished. This is normal while using windows driver verifier.
     
    zbook, Jul 2, 2017
    #14
  15. Mistral Win User
    Here are the result of sfc /scannow
    dism /online /cleanup-image /restorehealth
    chkdsk /scan
    Code: Microsoft Windows [Version 10.0.15063](c) 2017 Microsoft Corporation. All rights reserved.C:\Windows\system32>winverC:\Windows\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\Windows\system32>dism /online/cleanup-image/restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Error: 87The online/cleanup-image/restorehealth option is unknown.For more information, refer to the help by running DISM.exe /?.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32> dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.15063.0Image Version: 10.0.15063.0[==========================100.0%==========================]Error: 0x800f081fThe source files could not be found.Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see MSN France: Hotmail, Outlook, actualités, météo, divertissement DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Windows\system32> chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... Found corrupt basic file structure for "\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-shm <0x7,0x30aa3>" ... repaired online. File "\Windows\System32\LogFiles\Srt\SrtTrail.log <0x2b,0x547c>" and file "\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-shm <0x7,0x30aa3>" both own logical cluster 0x219cb ... queued for offline repair. 702208 file records processed. File verification completed. 21434 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 917142 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found.Stage 3: Examining security descriptors ...Security descriptor verification completed. 107469 data files processed.CHKDSK is verifying Usn Journal...Usn Journal verification completed.Windows has found problems and some were fixed online;the remaining problems must be fixed offline.Please run "chkdsk /spotfix" to fix the issues. 102562598 KB total disk space. 91610848 KB in 463335 files. 258804 KB in 107469 indexes. 0 KB in bad sectors. 792686 KB in use by the system. 65536 KB occupied by the log file. 9900260 KB available on disk. 4096 bytes in each allocation unit. 25640649 total allocation units on disk. 2475065 allocation units available on disk.C:\Windows\system32>[/quote]
     
    Mistral, Jul 2, 2017
    #15
Thema:

BSOD Caused by ntoskrnl.exe and hal.dll

Loading...
  1. BSOD Caused by ntoskrnl.exe and hal.dll - Similar Threads - BSOD Caused ntoskrnl

  2. Ntoskrnl BSOD

    in Windows 10 Installation and Upgrade
    Ntoskrnl BSOD: I have had this issue for so long its almost like a part of me. I have uploaded the last 3 minidumps but I don't really understand what is going on. But I know the number one culprit is Ntoskrnl.exe https://1drv.ms/u/s!AgeiZ1AnXkV6esFtCX3uiwaGGuA?e=SlXCUk...
  3. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  4. Windows=HAL ?

    in Windows 10 Drivers and Hardware
    Windows=HAL ?: I hope someone can help as Microsoft techs have been unsuccessful at solving this problem. It appears that Windows 10 (in my case) is protecting itself from being updated along with refusing to allow printers (that's plural) to be used. The problem started around 3 months...
  5. BSOD caused by ntoskrnl exceptions

    in Windows 10 BSOD Crashes and Debugging
    BSOD caused by ntoskrnl exceptions: Hello to anyone that is willing to help my name is Glenn, My pc was assembled by professionals but it got really hot so a month ago I took my cpu cooler off and noticed that they left the plastic on the cpu cooling block, So I fixed that issue after emailing the people...
  6. BSOD ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl: I'm having the same issues. It started 2 days ago, computer is crashing randomly with different BSOD errors. I've tried a new SSD, new RAM and multiple fresh installs of Windows 10. I've run out of ideas, I'm starting to think there is a seriously nasty virus or Microsoft...
  7. BSOD ntoskrnl+ 142480

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl+ 142480: Hi *Smile I have problem with BSOD ntoskrnl+ 142480 . previously I used windows 8.1 and got BSOD ntoskrnl+ 142480, and maybe if I change the OS to Windows 10 the problem will be solved but not . I have update all driver but still got bsod . Please help me *Sad I...
  8. BSOD various ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    BSOD various ntoskrnl: Hi guys! Made a fresh Win10 install with just basic software (Like whocrashed) I have tried using the Guru3Ds tool to remove all traces of old video card drivers and installed the newest ones without any extra software or bloatware. Have ran Memtest for 24 hours without a...
  9. Bsod ntoskrnl

    in Windows 10 BSOD Crashes and Debugging
    Bsod ntoskrnl: Hi guys, Any help would be massively appreciated. My computer is BSOD at least two times a day. As far as I can tell, all drivers are up to date including Nvidia. Could somebody take a look at the attached and let me know if you find anything? I've ran a system check...
  10. BSOD - Bad Pool Header caused by NTOSKRNL

    in Windows 10 BSOD Crashes and Debugging
    BSOD - Bad Pool Header caused by NTOSKRNL: Hello, I've been having an issue this past week whenever my computer restarts (seems to be from Windows Updates) I come back to a Bad Pool Header BSOD. I was able to get it stopped by uninstalling Avast and doing a Clean Boot. After about 2 hours of restarting and just adding...