Windows 10: Daily BSOD in hal.dll with bugcheck code 133 since last windows update

I need help identifying the driver causing the BSOD in Windows 10.0.14393.206.

It seems that every other set of MS updates causes this BSOD after I upgraded to Windows 10 about a year ago. My computer was stable for a few months, then an update would cause random crashes, then a few weeks later another update would stabilize my system, then update/crashes. Haven't changed hardware at all.

Currently, I have a BSOD every day since the last windows update about 3 weeks ago. I haven't been able to identify which driver is causing the issue.

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.

 

Windows 10 BSOD hal.dll

Hey all,

I have a problem nowadays, the Windows 10 crashes to desktop mainly when using Skype, but not only. A crash analyzer says:

This was probably caused by the following module:
hal.dll (hal+0x1A39E)

Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF802AAF0539E, 0xFFFFF802AAA2E380, 0x0)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\hal.dll

This was probably caused by the following module:
hal.dll (hal!HalAcpiGetTableEx+0x223E)

Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF802AAF0539E, 0xFFFFF802AAA2E380, 0x0)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\WINDOWS\system32\hal.dll

PC: Windows version: Windows 10 , 10.0, build: 16299

Windows dir: C:\WINDOWS

Hardware: MS-7918, MSI, H97 GAMING 3 (MS-7918)

CPU: GenuineIntel Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz Intel586, level: 6

4 logical processors, active mask: 15

RAM: 17109258240 bytes total

Anyone knows how to solve this?

Thank you,

Gery

 

All 5 dumpfiles from december blame:
Code: BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for nvstor.sys *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys Probably caused by : nvstor.sys ( nvstor+7468 )[/quote] Timestamp: Mon Apr 21 20:34:03 2014
Driver Description: nVidia Storage Drivers
Driver Update Site: Download Drivers | NVIDIA
First look on the supportpage of your mobo.

 

Thanks, lifetec.
NVidia does not update their legacy drivers like nvstor.sys. Using Device Manager, I updated two instances of NVidia nForce SATA controller to use standard IDE/ATA drivers instead of nvstor.sys. I am optimistic as my computer hasn't BSOD in 9 days but before the change, it was BSOD every day.