BSOD (hal.dll ntoskrnl.exe DPC 0x133) Only while under load

Page 2 of 3 FirstFirst 123 LastLast

  1. Kronox001
    Posts : 14
    Windows 10
    Thread Starter
       New #11

    still crashing...i might just buy another wireless card

    I also needed to repair my C:/ drive while windows was starting after a BSOD

    Is that caused by crashing at a bad time?
      My Computer
    Quote Quote

  3. zbook
    Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       New #12

    Please post an updated zip:
    BSOD - Posting Instructions - Windows 10 Forums
      My Computer
    Quote Quote

  4. axe0
    Posts : 14,903
    Windows 10 Pro
       New #13

    Kronox001 said:
    still crashing...i might just buy another wireless card

    I also needed to repair my C:/ drive while windows was starting after a BSOD

    Is that caused by crashing at a bad time?
    That is possible
      My Computers
    Quote Quote

  6. Kronox001
    Posts : 14
    Windows 10
    Thread Starter
       New #14

    i got a CLOCK_WATCHDOG_TIMEOUT BSOD(didn't get the dump file because it was stuck on 0%), can that also happen because of the bad wireless driver?

    I'll have a new wireless card tommorow
      My Computer
    Quote Quote

  7. zbook
    Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       New #15

    ...
      My Computer
    Quote Quote

  8. Kronox001
    Posts : 14
    Windows 10
    Thread Starter
       New #16

    I'm still freezing and getting the same bsod

    I uninstalled my wireless pci card(netr28x is gone) and removed it from my pc
    I'm using a TP-Link wireless usb now

    This is the new crash dump
      My Computer
    Quote Quote

  9. axe0
    Posts : 14,903
    Windows 10 Pro
       New #17

    0x133 with first param being 1 means something ran an extended period of time in an IRQL level of 2 or higher (IRQL = importance order in which the CPU processes things, the higher the earlier with a max of 13)
    Since it looks like multiple drivers are internally delaying execution, and a minidump isn't sufficient to identify which drivers cause this issue, I'm taking a different approach than normally.

    Please follow below instructions
    - Download the Windows Software Development Kit (SDK) executable from Windows 10 SDK - Windows app development,
    - Run in, when you get at the part where you can choose what to install, select only Windows Performance Toolkit,
    - Open an elevated command prompt,
    - Enter following command, this makes it easier to access the tool we need
    Code:
    SET PATH=%PATH%;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\
    If your SDK is installed on a different location, please change the path to specify the right path
    - Enter following command
    Code:
    xperf -on DiagEasy
    - Wait an extensive period and then run following command, preferable after you noticed some performance issues
    Code:
    xperf -d "%userprofile%\Desktop\trace.etl"
    Please upload the trace.etl to onedrive, google drive or dropbox and post a share link. Trace.etl will be too large to upload directly.
      My Computers
    Quote Quote

  10. Kronox001
    Posts : 14
    Windows 10
    Thread Starter
       New #18

    After i posted the new crash dump i noticed an older version of the wireless pci card driver in hidden devices in my Network adapter list in Device Manager and uninstalled it

    If i still crash now il do the Performance toolkit

    (I also did a Intel Processor Diagnostic without any problems)
      My Computer
    Quote Quote

  12. Kronox001
    Posts : 14
    Windows 10
    Thread Starter
       New #19

    Ran it for about 4 hours: trace.etl - Google Drive

    Some more info: Got another CLOCK_WATCHDOG crash yesterday night, it happenend while i was clicking through different times on a youtube video

    Since CLOCK_WATCHDOG can be caused by overclocking I've also defaulted my bios

    I've used "Show and hide updates" to try and stop windows from installing drivers for usb devices

    I told the place i bought the pc from that i was getting Watchdog errors and they just linked me this to solve it: How to fix my CLOCK_WATCHDOG_TIMEOUT error - [Solved] - CPUs
      My Computer
    Quote Quote

  13. Kronox001
    Posts : 14
    Windows 10
    Thread Starter
       New #20

    I've also just had a problem where a program wouldn't start and the process in Task Manager couldn't be ended, I read somewhere it could be a anti virus problem so i uninstalled the BullGuard AV 30 day trial that came with the PC and the program started while i was uninstalling it. Dont know if that could also cause those BSOD's
      My Computer
    Quote Quote

 

  Related Discussions
BSOD, Watch Dog Violation 0x133
in BSOD Crashes and Debugging

Since building my new PC around August 2019 I have been getting random reboots and the occasional BSOD, each of these result in my 2nd Samsung 970 Evo Plus (2TB) disappearing from Windows. Originally the PC would instantly restart, more recently...
So I was browsing stuff on the web and this happens. Anyway, since then I've tried to update some certain drivers related to the issue, however, most of them were already up-to-date. I've ran an SFC scan and nothing came up in there either. Anyhow,...
BSOD 0x133 and 0xa during the reboot
in BSOD Crashes and Debugging

As title, the dut have bsod symptom during reboot the system. Could anyone know which cause the BSOD?? 161338
Hello! I'm having BSOD problems like DPC_WATCHDOG_VIOLATION and WHEA_UNCORRECTABLE_ERROR caused by hal.dll and ntoskrnl.exe. I'm using an Alienware 15 R1 with Intel i7 4710HQ with GTX980M and 16GB DDR3 RAM. This started somewhere around the middle...
I'm running a genuine MSDN copy of Windows 10 Enterprise. Recently from past month, the laptop has started behaving weirdly. Earlier the issue was that it would hang and after waiting hours I had to shut it down forcibly and then when re-starting,...
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 00:08.
Find Us




Windows 10 Forums