Hey, heute ist schon 3 mal mein XPS 15 9530 abgeschmiert, mit dem Fehler "DPC_watchdogs_violation". Keine Ahnung was das heißt, google ist da auch nicht wirklich eindeutig. Hab aber rausgefunden dass es dumps von windows gibt. Hab die mal mit "WhoCrashed" ausgelesen, mir als Leien hilft das Ergebnis aber leider auch nicht viel weiter:
System Information (local)
--------------------------------------------------------------------------------computer name: XPS15
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: XPS 15 9530, Dell Inc.
CPU: GenuineIntel Intel(R) Core(TM) i7-4712HQ CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17078222848 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 01.08.2014 19:40:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080114-9218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 01.08.2014 19:40:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x6F)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 01.08.2014 05:36:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080114-13203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 01.08.2014 01:21:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080114-20406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.