Daily BSOD in hal.dll with bugcheck code 133 since last windows update Solved

  1.    06 Dec 2016 #1

    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.

      My ComputerSystem Spec

  2.    06 Dec 2016 #2

    All 5 dumpfiles from december blame:
      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 )
    Timestamp: Mon Apr 21 20:34:03 2014
    Driver Description: nVidia Storage Drivers
    Driver Update Site: http://www.nvidia.com/Download/index.aspx
    First look on the supportpage of your mobo.
      My ComputerSystem Spec

  3.    03 Jan 2017 #3

    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.
      My ComputerSystem Spec


Related Threads
Windows 10 Pro bsod d1 bugcheck in BSOD Crashes and Debugging
My system rebooted from a bug check. Actual error is this - The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000008, 0x0000000000000000). A dump was saved in:...
Been getting infrequent BSOD errors on my Windows 10 PC (Home edition). I had a look on BlueScreenView, seems like a lot of the bugcheck BSOD is ntoskrnl related but I can't work out if it's hardware related or some bad driver somewhere. ...
Partial workaround for Bugcheck code: 0x116 in module nvlddmkm.sys, VIDEO_TDR_ERROR As many other people, I too faced this problem after upgrading my desktop system to Windows 10. Did some research and testing, now I'd like to share my knowledge....
Started getting these bugchecks ever since I went back to 8.1 (via restoring an old image) then going back to 10 1511. Seems to occur after connected standby, a string of DCOM errors then it bugchecks 7F. Always occurs when I just leave the...
My problem is very similar to one described by tomzino earlier this month in this forum. Since upgrading from windows 7 home premium to windows 10, my computer gets a BSOD and reboots daily; so far in November it has crashed 20 times. The only...
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 10:58.
Find Us