Windows 10: Experiencing BSOD's about once a week - 0x00000133 - hal.dll

Discus and support Experiencing BSOD's about once a week - 0x00000133 - hal.dll in Windows 10 BSOD Crashes and Debugging to solve the problem; Hey guys So about 8 months ago i upgraded my MOBO to a Gigabyte gigabyte z170x-ud3 ultra, upgraded my CPU to a i7 6700K and also upgraded my RAM to... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by terrorc0n, Apr 4, 2017.

  1. terrorc0n Win User

    Experiencing BSOD's about once a week - 0x00000133 - hal.dll


    Hey guys

    So about 8 months ago i upgraded my MOBO to a Gigabyte gigabyte z170x-ud3 ultra, upgraded my CPU to a i7 6700K and also upgraded my RAM to 16GB DDR4 at 2400Mhz.
    I kept the same GPU a EVGA GTX 970 FTW and also kept the same PSU ( I cant recall the exact specs of the PSU at this point in time).

    Previously I was using an AMD CPU and a different MOBO & I never ran into any issues at all, everything just worked.
    Though since upgrading, I have had constant BSOD's at least once a week, if not sometimes twice.

    Now I'm not good at deciphering the BSOD dumps, it doesnt quite mean anything to me.

    I have run Memtest86 overnight and it passed 100%.
    I believe that all my drivers are up to date (I could be wrong of course).
    I did do a CPU burn in test, (prime95?) when I first built the PC to actually check that everything worked and I have not done one since.

    I am really at a loss with what this could be and I would really appreciate some help with getting this resolved some what.


    PC Specs
    CPU - Intel i7 6700k
    Motherboard - Gigabyte gigabyte z170x-ud3 ultra
    RAM - 2X DDR4 8GB Ballistic 2400Mhz
    GPU - EVGA GTX 970 FTW
    PSU -


    Attachment 128314

    :)
     
    terrorc0n, Apr 4, 2017
    #1
  2. _JacobG Win User

    BSOD, Bug check code 0x00000133, caused by driver hal.dll

    Lenovo ThinkPad with Intel i-7 processor, 8GB RAM, Windows 10 professional edition, suddenly crashed with BSOD, Bug check code 0x00000133, caused by driver hal.dll

    Attached is the minidump file.

    Any hints an to what might have caused the problem ?
     
    _JacobG, Apr 4, 2017
    #2
  3. 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, Apr 4, 2017
    #3
  4. philc43 Win User

    Experiencing BSOD's about once a week - 0x00000133 - hal.dll

    Hello and welcome to TenForums *Smile

    There is only one crashdump file from today in your logs. I suspect you are using CCleaner which is deleting all your older crashdump files. For future help please change the settings so that it does not delete memory dump files.

    So there is not a lot to examine. However there was a problem with one of the drivers:
    Code: fffff801`ac3d2508 fffff802`c84e9d64Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for iaStorA.sys *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys iaStorA+0xb9d64[/quote] This would suggest that the Intel Rapid Storage Technology drivers should be updated. I think there are newer versions on your Motherboard website dated 29/11/2016 that would be worth installing.
     
    philc43, Apr 4, 2017
    #4
  5. terrorc0n Win User
    Hey philc43!

    Thanks for your quick reply! I have updated this driver and i will stop using Ccleaner until I have somewhat figured out what may be causing the BSOD's. When I have had a few more I will post another dump file *Smile
    Fingers crossed it was just the Intel Rapid Storage driver!

    Cheers! *Smile
     
    terrorc0n, Apr 4, 2017
    #5
  6. terrorc0n Win User
    Well its been a while since I have had a BSOD, so I feel that I can safely say that this is solved! Experiencing BSOD's about once a week - 0x00000133 - hal.dll :)
    Thank you so much for your help philc43!
     
    terrorc0n, Apr 5, 2018
    #6
Thema:

Experiencing BSOD's about once a week - 0x00000133 - hal.dll

Loading...
  1. Experiencing BSOD's about once a week - 0x00000133 - hal.dll - Similar Threads - Experiencing BSOD's once

  2. radom BSOD (0x00000133)

    in Windows 10 BSOD Crashes and Debugging
    radom BSOD (0x00000133): 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8037b58a350, 0x0000000000000000) is the bugcheck error code. Strange thing is my system is stable and this if the first instance I've ever encountered this issue on this system. Ran BlueScreenView by Nirsoft and it...
  3. BSOD once a day for the past week

    in Windows 10 BSOD Crashes and Debugging
    BSOD once a day for the past week: For at least a week now, my computer has had a BSOD once a day, but after that it's fine for the rest of the day until the next day when I boot my PC up again. Today, however, it crashed twice in one day. I've had help from my friend to try and solve this but he can't come up...
  4. facing BSOD once or twice a week in about a month with many different bugchecks

    in Windows 10 BSOD Crashes and Debugging
    facing BSOD once or twice a week in about a month with many different bugchecks: Hi, i tried to fix the problem by myself after doing a little research online but it didn't help. i tried to run check disk, memory diagnostic tool, sfc but it still keep occurring with new bugcheck. they were, from oldest to newest, 0x0000007e, 0x0000001a, 0x0000009f,...
  5. Getting BSOD with error code 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    Getting BSOD with error code 0x00000133: This keeps happening for several times when I was playing games (PUBG and Rainbow Six) even when the system is idling. I have checked the BlueScreen info and it is caused by ntoskrnl.exe and hal.dll. Here is the info about my system. Z-2018-12-27__05857_47.zip Thanks for...
  6. DPC_Watchdog_Violation BSOD, The bugcheck was: 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    DPC_Watchdog_Violation BSOD, The bugcheck was: 0x00000133: Hi Guys, Installing windows and drivers onto a new system today and everything went smoothly. Unfortunately, whenever audio should emit the system will BSOD. This is not straight away but after about 10 seconds. This even happens when playing a music CD. I...
  7. Silent BSOD: bugcheck was: 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    Silent BSOD: bugcheck was: 0x00000133: Computer freezed twice today, ran 4 weeks without issue. No new software or drivers installed. Screen froze and then computer restart without BSOD message. Event log message: bugcheck was: 0x00000133 (0x0000000000000000, 0x0000000000000501, 0x0000000000000500,...
  8. IRQL_NOT_LESS_OR_EQUAL once a week

    in Windows 10 BSOD Crashes and Debugging
    IRQL_NOT_LESS_OR_EQUAL once a week: Keep having this blue screen. In parallel have a problem in all of the browsers: pages keep crashing, most often happens in Chrome. eBay is heavily used and hugely affected by this problem. it could crash before the page loaded. Not sure if it has any connection to the blue...
  9. BSOD on different occasions, error 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    BSOD on different occasions, error 0x00000133: Hi, I have a new rig. It got assembled by an online retailer in Germany (Alternate) and I live in Switzerland, so I'd be happy if I could fix this issue myself. I noticed that from time to time I get BSODs with the error 0x00000133 (more or less once every 24 hours of...
  10. BSOD once a week

    in Windows 10 BSOD Crashes and Debugging
    BSOD once a week: After upgrading from Windows 7 to 10 Iexperienced ”Video TDR Failures” about every other week. Theynever happened with Windows 7. I see no relation to heavy graphicuses. It seems to me that they happen more frequently when I startagain after putting the computer to sleep and...