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

Some info:

1. Computer freezes for 30 seconds before restarting (I dont get crash dumps if i restart manually)

2. Only happens while under load (Benchmark/Games) I can watch videos for hours without a problem

3. It's a new PC

4. I've used Snappy to update my system

:)

 

dpc_watchdog_exception 0x133: hal.dll ntoskrnl.exe

Hi,

BugCheck 133, {1, 1e00, 0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Probably caused by : nvlddmkm.sys ( nvlddmkm+1e46f4 )

nvlddmkm.sys dated 8/1/2016 Nvidia video drivers.

BiosVersion = 1.2.0

BiosReleaseDate = 09/22/2016

SystemManufacturer = Dell Inc.

SystemProductName = Inspiron 7559

SystemFamily = Inspiron

SystemVersion = 1.2.0

SystemSKU = 0706

BaseBoardManufacturer = Dell Inc.

BaseBoardProduct = 0H0CC0

BaseBoardVersion = A00

1. Update the Nvidia Driver and check with Nvidia Support, there online documentation and drivers, and ask in their forums about any known issues.

Nvidia - Drivers - Use OPTION 1 to manually enter your driver info to get most current drivers.

Download Drivers | NVIDIA

Nvidia Support - check with Support as it could be a known issue

Nvidia Support

Nvidia Forums - also check for forums as it could be a known issue and/or others likely to have it

http://forums.nvidia.com/

2. If this is a new computer be sure to check with Dell Support. It would still be under warranty and may be in need of repairs or replacement. Update the BIOS, chipset, and major drivers.

Dell Support

Support | Dell Deutschland

Dell Drivers - Product Manuals & Warranty Info (left side) - Tech Support and more

Support | Dell Deutschland

Dell Forums

Page Not Found - Dell Community

Dell PC Diagnostics

http://www.dell.com/support/Diagnostics/us/en/19/



3. See methods in my previous reply.

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Hope this helps.

--------------------------------------------------------------------------------------------

Rob Brown -
Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

 

dpc_watchdog_exception 0x133: hal.dll ntoskrnl.exe

Thanks,

i write to DELL Support and i'm waiting for an answer.

 

Diagnostic Test

DRIVER VERIFIER


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

 

Driver Verifier is running right now.....

How long does it usually take to check 18 drivers with a good cpu?
using verifier /query i can see this

Raise IRQLs: 15428943
Acquire Spin Locks: 1941145
Synchronize Executions: 0
Trims: 0
Pool Allocations Attempted: 3359964
Pool Allocations Succeeded: 3359964
Pool Allocations Succeeded SpecialPool: 2312
Pool Allocations With No Tag: 40
Pool Allocations Not Tracked: 0
Pool Allocations Failed: 0
Pool Allocations Failed Deliberately: 0

Also should i try to force a bsod by benchmarking while driver verifier is running?

 

48h, as mentioned.

Yes.

 

well...i just ran four Intel Extreme Tuning Benchmarks in a row without a BSOD or any other problem

I've ran it 6 times yesterday and this morning and it froze and BSOD 5/6 times

I'll keep Driver Verifier running and see what happens

 

got a BSOD while running Driver Verifier, What do i do now? use dm log collecter and upload?

 

It looks like your wireless network card driver is causing the crashes.
See if you can find driver updates for it from the manufacturer.
Code: 0: kd> lmvm netr28x Browse full module list start end module name fffff80b`48cf0000 fffff80b`48f64000 netr28x T (no symbols) Loaded symbol image file: netr28x.sys Image path: \SystemRoot\System32\drivers\netr28x.sys Image name: netr28x.sys Browse all global symbols functions data Timestamp: Fri May 29 13:26:59 2015 (55684D03) CheckSum: 0027D7B1 ImageSize: 00274000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Guess its my fault for choosing a cheap wireless card

i've Installed the possible ralink drivers instead of the mediatek ones

Might just buy a decent one if it still crashes

 

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?

 

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

 

That is possible

 

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

 

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