Windows 10: BSOD on different occasions, error 0x00000133

Discus and support BSOD on different occasions, error 0x00000133 in Windows 10 BSOD Crashes and Debugging to solve the problem; 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... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by CortexVacua, Jan 2, 2017.

  1. 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 actual use, not once every day). Most of the times it has happened, I've been surfing the Internet (few times using Youtube, which makes me suspect it has something to do with the GPU), but it has also happened while the PC was idling and I wasn't really doing anything with it.

    I've looked into BlueScreenView and almost all BSODs are caused by hal.dll in combination with ntsokrnl.exe. I am not really good with PCs, I only have basic or little above average knowledge about PCs.

    What I have already tried to fix the Issue:
    I have updated the FW of my SSD. (Crucial_CT250MX200SSD1)
    I have checked and updated the BIOS of my Motherboard (Gigabyte GA-Z170-hd3 HDDR 3) and put everything to default settings.
    I have deleted the drivers of the GPU and reinstalled them, so I would have a clean install.

    So that's about it.

    Would be happy if someone could help.

    :)
     
    CortexVacua, Jan 2, 2017
    #1
  2. Gerry C J Cornell, Jan 2, 2017
    #2
  3. fgalvez Win User
    Frequent BSOD lately with the "Driver overran stack buffer"

    I have been having a number of BSOD lately(one an day). It seems to be going between 2 different types of BSODs, the most recent(which I have crash logs for) is for a "driver overran stack buffer" BSOD. According to the logs ntkrnlmp.exe seems to be the
    culprit on a few occasions. Not really sure what to do at this point, can someone help me out?
     
    fgalvez, Jan 2, 2017
    #3
  4. Blazedbud Win User

    BSOD on different occasions, error 0x00000133

    Hi,

    Do you use Logmein on this pc?

    Thanks
     
    Blazedbud, Jan 2, 2017
    #4
  5. First, thank you for your reply. The anwer is no, I'm not using Logmein and haven't had it installed at any point either.
     
    CortexVacua, Jan 2, 2017
    #5
  6. Blazedbud Win User
    Try this:

    Right-click the Start icon and select Device Manager.


    Expand IDE ATA/ATAPI controllers.


    Select the controller with “SATA AHCI” in its name (such as Standard SATA AHCI Controller). To verify that you’ve selected the right controller, right-click the controller, select Properties, click the Driver tab, and then Driver Details. Verify that iastor.sys is a listed driver, and click OK.


    From the Driver tab, select Update Driver…


    Select Browse my computer for driver software.


    Select Let me pick from a list of device drivers on my computer.


    Select Standard SATA AHCI Controller.

    Click Next then Reboot PC
     
    Blazedbud, Jan 2, 2017
    #6
  7. So in the Device Manager only "Intel(R) 100 Series/C230 Chipset Family SATA-AHCI Controller" pops up. I went to check the driver like you said, but the driver isn't named "iastor.sys". It's named "iaStorA.sys". Can I proceed with your instructions or is this information relevant?

    And many thanks.
     
    CortexVacua, Jan 2, 2017
    #7
  8. Blazedbud Win User

    BSOD on different occasions, error 0x00000133

    Yes that's fine to proceed with.
     
    Blazedbud, Jan 2, 2017
    #8
  9. Ok I proceeded as you suggested. Seeing how I can't provoke a BSOD to test if this worked (it could take a day or even a week), I'm just gonna have to wait. If there is a BSOD in the next days I'll post about it. If there isn't any in 2 weeks, I'll change the thread to solved, if I don't forget (I'll try my best).

    Thank you for your help.
     
    CortexVacua, Jan 2, 2017
    #9
  10. So I just had another BSOD while browsing YT. Meaning the suggested actions didn't work. BlueScreenView again gives me ntsokrnl.exe and hal.dll as the cause. I have reversed all actions taken so far. You'll find the new dump attached. I would really be happy if someone was able to help. Thank you in advance
     
    CortexVacua, Jan 3, 2017
    #10
  11. I just had a freeze on my PC without a BSOD following it like usual. I've been using this PC a lot lately for work and the BSOD's are piling up it seems. That's one a day basically. I am really getting frustrated here. Would be happy for some suggestions. Thanks in advance.
     
    CortexVacua, Jan 4, 2017
    #11
  12. Ztruker Win User
    Most of the dump indicates a problem with athw8x.sys.
    Code: BugCheck 133, {0, 501, 500, 0} *** WARNING: Unable to verify timestamp for athw8x.sys *** ERROR: Module load completed but symbols could not be loaded for athw8x.sys Probably caused by : athw8x.sys ( athw8x+299e6a )[/quote] This belongs to Qualcomm Atheros AR938x Wireless Network Adapter dated 28.01.2016 10:52:54.

    It would be nice to try a newer driver but I don't find one. You can try uninstalling it from Device Manager then reboot and let Windows rediscover it and reinstall the driver, see if that heps.
     
    Ztruker, Jan 4, 2017
    #12
  13. BSOD on different occasions, error 0x00000133

    CortexVacua, Jan 4, 2017
    #13
  14. Ztruker Win User
    That's not really a Qualcomm site, it says: Unofficial Qualcomm Atheros drivers website.

    I downloaded and scanned the zip and it looks okay. Go ahead and try it.

    A different wifi card should fix this specific problem. May not fix all BSOD problems but it sure looks like it will help a lot.
     
    Ztruker, Jan 5, 2017
    #14
  15. Thank you very much, I already went ahead and installed the driver few hours after writing my last post. So far I had no crashes. What other BSOD problems do you mean? Where there other drivers being an issue?
     
    CortexVacua, Jan 5, 2017
    #15
Thema:

BSOD on different occasions, error 0x00000133

Loading...
  1. BSOD on different occasions, error 0x00000133 - Similar Threads - BSOD different occasions

  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. 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...
  4. Numerous BSOD on multiple occasions

    in Windows 10 BSOD Crashes and Debugging
    Numerous BSOD on multiple occasions: Hi there, Over the past several months I've had the BSOD a number of times. I tend to leave my computer running all day and night and have noticed the BSOD tends to happen when I'm not using my computer. However, having said that, it just crashed on me while using my...
  5. 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...
  6. 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,...
  7. BSOD Error 0x00000133 How do I fix Hal.dll error?

    in Windows 10 BSOD Crashes and Debugging
    BSOD Error 0x00000133 How do I fix Hal.dll error?: Hello, Recently upgraded to Windows 10 when free upgrade was offered. Actually I seem to remember being notified that time was running out and my old setup would no longer be supported. After finding PC in BSOD state, I found out my hp model was not tested for the upgrade...
  8. BSOD scanning multipage document, error 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    BSOD scanning multipage document, error 0x00000133: System had been running for a long time without a BSOD to occur. The system is set to standard operation, not in turbo mode (AVG TuneUp). The task of scanning a 20 page document had just completed when the system experienced the crash. Have followed the recommented...
  9. BSOD with stopcode DPC_WATCHDOG_VIOLATION, bug check error 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    BSOD with stopcode DPC_WATCHDOG_VIOLATION, bug check error 0x00000133: Hi, I have encountered multiple BSOD crashes, most often while watching youtube videos. It usually involves my laptop freezing for a few seconds and the sound stuttering loudly before crashing. However, the same crashes have also occured in random occasions (browsing,...
  10. yet another Hal.dll BSOD, error 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    yet another Hal.dll BSOD, error 0x00000133: i was just surfing the net, any ideas why this occurs? report attached. thanks in advance *Confused 75726
Tags: