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

Page 2 of 3 FirstFirst 123 LastLast
  1.    01 Jun 2017 #11

    Which one? I'll delete it momentarily.
      My ComputerSystem Spec

  2. Posts : 13,312
    Windows 10 Pro
       01 Jun 2017 #12

    I'll have another look at the logs to see if I didn't miss anything when I'm home
      My ComputersSystem Spec

  3. Posts : 13,312
    Windows 10 Pro
       01 Jun 2017 #13

    Although it's old, have you dealt with this program and reinstalled the affected software?
      Log Name: System
      Source: Service Control Manager
      Date: 2017-02-21T10:14:19.892
      Event ID: 7045
      Task: N/A
      Level: Information
      Opcode: N/A
      Keyword: Classic
      User: S-1-5-21-3449498139-531481687-1691142593-1002
      User Name: DESKTOP-FM6FKJ2\5ar
      Computer: DESKTOP-FM6FKJ2
    A service was installed in the system.
    Service Name:  WinDivert1.1
    Service File Name:  C:\ProgramData\KMSAutoS\bin\driver\x64WDV\WinDivert.sys
    Service Type:  kernel mode driver
    Service Start Type:  demand start
    Service Account:
    I see you've altered the hosts file to block Malwarebytes from accessing their activation server.
      My ComputersSystem Spec

  4.    01 Jun 2017 #14

    Must be accidentally. But I've deleted it in any case.
      My ComputerSystem Spec

  5. Posts : 13,312
    Windows 10 Pro
       01 Jun 2017 #15

    Doesn't look like an accident
    #5ar's hosts
    ...... xxxxxx
      My ComputersSystem Spec

  6.    01 Jun 2017 #16

    No Malwarebytes. Attachment 137608
      My ComputerSystem Spec

  7. Posts : 13,312
    Windows 10 Pro
       01 Jun 2017 #17

    What about KMSAutoS, you've had it installed and used it.
    have you dealt with this program and reinstalled the affected software?
      My ComputersSystem Spec

  •    01 Jun 2017 #18

    Well, maybe for Office, but that was long time ago. I don't have it now.
    Attachment 137609
      My ComputerSystem Spec

  • Posts : 13,312
    Windows 10 Pro
       01 Jun 2017 #19

    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.
    0: kd> ? 0000000000001e00
    Evaluate expression: 7680 = 00000000`00001e00
    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 Diagnostic Test BSOD happens randomly, error 0x00000133 hal.dll + ntoskrnl.exe

    warning   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.

    Note   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.
      My ComputersSystem Spec

  •    01 Jun 2017 #20

    I did like you said, and it crashed(BSOD) a few minutes after boot up. I think, now is different error.Attachment 137618
      My ComputerSystem Spec

    Page 2 of 3 FirstFirst 123 LastLast

    Related Threads
    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....
    yet another Hal.dll BSOD, error 0x00000133 in BSOD Crashes and Debugging
    i was just surfing the net, any ideas why this occurs? report attached. thanks in advance :confused:
    Solved BSOD on different occasions, error 0x00000133 in BSOD Crashes and Debugging
    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...
    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...
    Randomly recurring BSOD ntoskrnl.exe in BSOD Crashes and Debugging
    I recently got this HP Pavilion x2 - 10-n107na and it has been crashing constantly at random times. after using Bluescreenview under "Caused by address" is see ntoskrnl.exe+ 14cc20 I have reinstalled the operating system which is windows 10 pro...
    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 05:55.
    Find Us