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

**Kronox001** · 02 Sep 2017

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?

**zbook** · 02 Sep 2017

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

**axe0** · 03 Sep 2017

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

**Kronox001** · 03 Sep 2017

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

**zbook** · 03 Sep 2017

...

**Kronox001** · 04 Sep 2017

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

**axe0** · 04 Sep 2017

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.

**Kronox001** · 04 Sep 2017

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)

**Kronox001** · 05 Sep 2017

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

**Kronox001** · 05 Sep 2017

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

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

Posting Permissions