Windows 10: BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe

Discus and support BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe in Windows 10 BSOD Crashes and Debugging to solve the problem; Doesn't look like an accident Code: #5ar's hosts # ...... xxxxxx[/quote] Discussion in 'Windows 10 BSOD Crashes and Debugging' started by 5ar, May 31, 2017.

  1. axe0 New Member

    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe


    Doesn't look like an accident
    Code: #5ar's hosts # ...... xxxxxx[/quote]
     
  2. 5AR
    5ar Win User

    No Malwarebytes. *SmileAttachment 137608
     
  3. axe0 New Member
    What about KMSAutoS, you've had it installed and used it.
     
  4. 5AR
    5ar Win User

    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe

    Well, maybe for Office, but that was long time ago. I don't have it now. *Smile
    Attachment 137609
     
  5. axe0 New Member
    Alright, please check every program one pays for if it is genuinely activated.
    Piracy doesn't just costs unnecessary time, but also could be somehow related to this issue.
    This time it was 'just' blocking access to a server, but with a little bit surfing the internet there are enough issues caused by this kind of stuff.

    This specific BSOD is a new one for me, the 0x133 I've seen are about a driver exceeding its allowed time to spend in a DPC routine.
    DPC is basically delaying execution because the current task has not yet been finished. In a DPC routine a driver is finishing the task.
    This BSOD is about something being in a DPC routine for an extensive period, according to the 2nd parameter it is 7680ms.
    Code: 0: kd> ? 0000000000001e00 Evaluate expression: 7680 = 00000000`00001e00[/quote] The official time is 100ms for DPCs, and 25ms for ISR, but the actual times are much higher.
    DPC and ISR are basically the same, DPC is for software and ISR for hardware.
    DPC stands for Deferred Procedure Call
    ISR stands for Interrupt Service Routine.
    Ms is microseconds.


    Please remove Avast temporary and use Windows Defender as alternative.
    Please run driver verifier, do NOT check the options in the tutorial, select 'deadlock detection'.





    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe [​IMG]
    Diagnostic Test
    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe [​IMG]
    DRIVER VERIFIER

    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe [​IMG]
    Warning Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.
    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.


    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe [​IMG]
    Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
     
  6. 5AR
    5ar Win User
    I did like you said, and it crashed(BSOD) a few minutes after boot up. I think, now is different error.Attachment 137618
     
  7. axe0 New Member
    Could you please upload a kernel dump (C:\Windows\Memory.dmp) to a 3rd party uploader (dropbox, onedrive, google drive) and post a share link in your next reply. This time only.
     
  8. 5AR
    5ar Win User

    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe

  9. axe0 New Member
    There appear to be 2 crashes, different drivers but both related to AMD.

    Please remove AMD Quick Stream.

    Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from Lenovo. Be sure to install as less as possible software using custom/advanced options, you can use this tutorial for the installation part *Arrow AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums

    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe [​IMG]

    Code: 1: kd> lmvm appexDrv Browse full module list start end module name fffff80e`fd960000 fffff80e`fd9ab000 appexDrv T (no symbols) Loaded symbol image file: appexDrv.sys Image path: \SystemRoot\system32\DRIVERS\appexDrv.sys Image name: appexDrv.sys Browse all global symbols functions data Timestamp: Wed Mar 25 21:41:52 2015 (55131D90) CheckSum: 00043B1A ImageSize: 0004B000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 1: kd> lmvm atikmdag Browse full module list start end module name fffff803`847c0000 fffff803`85cc7000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Browse all global symbols functions data Timestamp: Tue Jun 23 03:34:51 2015 (5588B7BB) CheckSum: 014A1E54 ImageSize: 01507000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]
     
  10. 5AR
    5ar Win User
    Thank you very much! I'll do everything you said and I hope it will help.
    P.C.
    I'm not fan of piracy. I use Linux as my primary OS where is everything I need open source; Windows very rarely. Only when I need Visual Studio because there is no good alternative for Linux by now.

    Again, sorry for bothering you and than you for your time! *Smile
     
  11. 5AR
    5ar Win User
    I did everything like you said, but the same error occurs..
     
  12. axe0 New Member
  13. axe0 New Member

    BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe

    Could you check Lenovo for BIOS updates *Smile
     
  14. Ztruker Win User
    He has V3.0 which is the latest on the Lenovo site for this computer.
     
    Ztruker, Jun 3, 2017
    #29
  15. axe0 New Member
Thema:

BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe

Loading...
  1. BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe - Similar Threads - BSOD happens randomly

  2. BSOD errors PSHED.dll and ntoskrnl

    in Windows 10 Software and Apps
    BSOD errors PSHED.dll and ntoskrnl: Continue to receive these ... rand system file checker and also updated all drivers from Dells site.I have the dump files how can i attach them? https://answers.microsoft.com/en-us/windows/forum/all/bsod-errors-psheddll-and-ntoskrnl/e28e8852-6a2f-47ea-a539-2551c8c718e8
  3. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...
  4. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...
  5. Random BSOD with Wathcdog Violation : 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD with Wathcdog Violation : 0x00000133: I'm running a pre_release version of Win10 and getting sporadic BSOD's when gaming, at first I thought it was the build and so have raised a report there, but then I started to think it was my video card and my PC getting old, so I have replaced my video card with a RTX2060...
  6. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  7. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  8. BSoD randomly happening, Mostly Bug check 0x00000133

    in Windows 10 BSOD Crashes and Debugging
    BSoD randomly happening, Mostly Bug check 0x00000133: Just put together an Asus P5Q-E with a nVidia GeForce GT 730 video card. Constantly getting black screens eventualy ending in a BSoD with a DPC Watchdog Violation with a Bug check code: 0x00000133 with hal.dll & ntoskrnl.exe being the main culprits. Any help would be...
  9. Random BSOD, 0x00000133, caused by hal.dll

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD, 0x00000133, caused by hal.dll: It started with keyboard and mouse becoming non responsive within a minute or so of boot. Then got my first bsod while playing a video in vlc. Some googling pointed to outdated GPU drivers. So I updated but it didn't fix the bsod. Any help will be appreciated. I've...
  10. Random BSODs (ntoskrnl,memory_management)

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs (ntoskrnl,memory_management): Hello, first timer here. Long story short, after i updated to windows 10 from 8.1 i started experiencing some randomly BSODs. So i downloaded the ISO and made a clean install.Immidiatelly after my newly formated pc i installed Avast,mozilla and Asrock's Suite to check for...

Users found this page by searching for:

  1. dpc watchdog deleting hal.dll

    ,
  2. windows 10 BSOD 0x00000133 cause by address hal.dll 17a9 crash address ntoskrnl.exe 1b35e0