Windows 10: BSOD at random times, ntoskrnl.exe or ntfs.sys or hal.dll cause it

I've been having BSODs for a few months now and only now just got around to looking at the memory dumps to find the cause. Unfortunately, it only shows ntoskrnl.exe, ntfs.sys or hal.dll as the causes, which leaves me unsure with what to do since they are system files. It seems that many others are having this same issue and as this computer is a modelling computer, having it running memory tests is not preferable (it is in use 24/7).

My zip should be attached so if someone here can help, I'd greatly appreciate it. It is causing a large headache at my work.

I did a windows update today (first time in a few months) and also a graphics driver update to see if that will stop it in future. I also turned on "verify" in cmd for these three processes. The computer is practically brand new, but it has not always been doing this as far as I know. According to the event log, it has only been doing it this year.

:)

 

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!

 

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.

 

The last dumpfiles are all very different.
Code: BugCheck A, {b0, 2, 0, fffff800862a54a7} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruption Followup: memory_corruption --------- BugCheck 50, {ffffffffffffffe8, 0, ffffd1d622a49d88, 0} Could not read faulting driver name Probably caused by : win32kfull.sys ( win32kfull!TimersProc+88 BugCheck 139, {3, ffffd800fdedfae0, ffffd800fdedfa38, 0} Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 ) BugCheck A, {10200000005, 2, 0, fffff800f46eb844} Probably caused by : memory_corruption Followup: memory_corruption BugCheck 124, {0, ffff8e8ac5cea028, be000000, 800400} Probably caused by : GenuineIntel Followup: MachineOwner --------- 3: 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: ffff8e8ac5cea028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value. BugCheck 3B, {c0000005, 0, ffffa881c7e38a90, 0} Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER:diEscape+de ) Followup: MachineOwner[/quote]
The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- faulting (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. Please stop at least during troubleshooting.
- compatibility issues (3rd party hardware/drivers)
- low-level driver/system problems within windows (SFC/DISM)
- or even malware.

In many dumpfiles the proces was PROCESS_NAME: TUFLOW_iSP_w64. (hopes this give a clue).

A few dumpfiles point to memory corruption, testing your memory could be necessary. Although this is troublesome as you mentioned in your post.

So start first with.

There are newer bios version for your mobo here Access Denied

Looking through your drivermodules i found this older drivers.
And in the unloaded modules there are references to your Kaspersky software and Aladdin/Safenet software ?.

aksdf Thu Oct 17 10:47:38 2013
Driver Description: Data Filter Driver by Aladdin Knowledge Systems
Driver Update Site: Aladdin Knowledge Systems: Support

e1d65x64 Thu Aug 13 11:14:29 2015
Driver Description: Intel Pro/1000 Network Adapter driver
Driver Update Site: Drivers & Software

iocbios2 Thu May 28 22:42:10 2015
Driver Description: Intel Extreme Tuning Utility - Desktop Control
Driver Update Site: Drivers & Software

kl1 Thu Jun 18 20:58:13 2015 (558314
klbackupdisk Tue Jun 02 22:18:33 2015 (556E0F99)
klbackupflt Thu Nov 26 10:59:25 2015 (5656D7FD)
kldisk Tue Nov 10 14:38:35 2015 (5641F35B)
klflt Fri Dec 04 14:27:50 2015
part of Kasparsky

Sentinel64 Mon Jun 02 08:14:55 2008
Driver Description: Rainbow Tech/SafeNet USB Security Device
Driver Update Site: Technical Support | Gemalto Troubleshooting guide: http://www.integratedsoft.com/suppor...ting_Guide.pdf

And install latest version of speedfan.

Also if you use it update to the latest version of the Asus Utilities or uninstal.

First look for updating these driver from your supportpage and also check if all the other drivers have the latest version installed.

 

These Tools are known for causing bluescreens:

- Corsair Link 4
- Intel(R) Extreme Tuning Utility
- ASUS AI Suite

all of them u have installed. I recommend not to overclock your system. We can not support overclocked systems.
Heres some errors from eventlog why these tools are crap:

Code: Task Scheduler service found a misconfiguration in the NT TASK\ASUS\ASUS AISuiteIII definition. Additional Data: Error Value: C:\Program Files (x86)\ASUS\AI Suite III\AISuite3.exe. The Intel(R) Extreme Tuning Utility Service service did not respond on starting.[/quote]

 

Thank you both for your replies. I'll work my way through all of the advice to find the problem.

Thanks again!

 

Is there any news or did you fix the problem?