LuigisBrother
Herzlich willkommen
Hallo zusammen
Das ist das erste Mal, dass ich in ein solches Forum poste, da ich nun seit einer Woche versuche einen Bluescreen zu beheben und nicht mehr weiter weiß.
Mitten im Spiel bekam ich einen Bluescreen DPC_Watchdog_Violation und versuchte diesen durch Aktualisieren der Treiber und durch Testen von älteren Nvidia Treibern zu beheben. Auch ein Zurücksetzen auf Windows 8.1 und einer Neuinstallation von Windows 10 von einer DVD aus haben nicht geholfen.
Der Fehler tritt auf wenn Ich versuche Nvidia Treiber zu installieren, auch bei älteren Versionen die laufen sollten.
Wenn ich diese Installiere muss ich meine Grafikkarte im Safemode deaktivieren, da der PC sich, falls ich überhaupt auf den Desktop komme, nach kurzer Zeit aufhängt und Ich einen Bluescreen bekomme( Minidump 1 ). Der Taskmanager gibt mit aktivierter Grafikkarte keine Rückmeldung und führt anscheinend auch zum BSod. Ist diese deaktiviert kann ich den PC hochfahren und benutzen.
Nachdem ich mit Driver Verifier die Treiber geprüft habe, wurde eine unterschiedliche Minidump erstellt ( Minidump 2 )
Das ist Minidump 1 :
Ich hoffe das ist hilfreich und dass mir vielleicht jemand weiterhelfen kann
Das ist das erste Mal, dass ich in ein solches Forum poste, da ich nun seit einer Woche versuche einen Bluescreen zu beheben und nicht mehr weiter weiß.
Mitten im Spiel bekam ich einen Bluescreen DPC_Watchdog_Violation und versuchte diesen durch Aktualisieren der Treiber und durch Testen von älteren Nvidia Treibern zu beheben. Auch ein Zurücksetzen auf Windows 8.1 und einer Neuinstallation von Windows 10 von einer DVD aus haben nicht geholfen.
Der Fehler tritt auf wenn Ich versuche Nvidia Treiber zu installieren, auch bei älteren Versionen die laufen sollten.
Wenn ich diese Installiere muss ich meine Grafikkarte im Safemode deaktivieren, da der PC sich, falls ich überhaupt auf den Desktop komme, nach kurzer Zeit aufhängt und Ich einen Bluescreen bekomme( Minidump 1 ). Der Taskmanager gibt mit aktivierter Grafikkarte keine Rückmeldung und führt anscheinend auch zum BSod. Ist diese deaktiviert kann ich den PC hochfahren und benutzen.
Nachdem ich mit Driver Verifier die Treiber geprüft habe, wurde eine unterschiedliche Minidump erstellt ( Minidump 2 )
Das ist Minidump 1 :
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80471d73358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 5
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4THF6MP
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 42
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80471d73358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff804`74475b08 fffff804`719eeb2b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`71d73358 : nt!KeBugCheckEx
fffff804`74475b10 fffff804`7181f61c : 00000f10`b1806647 fffff804`6c8bc180 00000000`00067ecc 00000000`00067ecc : nt!KeAccumulateTicks+0x1cc0cb
fffff804`74475b70 fffff804`7175e4b7 : ffffd202`acb04a80 fffff804`74466f20 fffff804`74466fa0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff804`74475f30 fffff804`71802a25 : 0000000f`7d8f6c49 fffff804`717cc0e0 fffff804`717cc190 ffff8de2`af62664d : hal!HalpTimerClockInterrupt+0xf7
fffff804`74475f60 fffff804`719c2eaa : fffff804`74466fa0 fffff804`717cc0e0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`74475fb0 fffff804`719c3417 : 00000000`00000000 00000000`00000000 00000000`00000003 fffff804`74466fb0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`74466f20 fffff804`8f0e6c11 : fffff804`8f10ec43 ffffd202`a8de3000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`744670b8 fffff804`8f10ec43 : ffffd202`a8de3000 00000000`00000000 00000000`00000000 0ee469df`0000000e : nvlddmkm+0x116c11
fffff804`744670c0 ffffd202`a8de3000 : 00000000`00000000 00000000`00000000 0ee469df`0000000e 5dc19fac`00000020 : nvlddmkm+0x13ec43
fffff804`744670c8 00000000`00000000 : 00000000`00000000 0ee469df`0000000e 5dc19fac`00000020 fffff804`74467100 : 0xffffd202`a8de3000
SYMBOL_NAME: nvlddmkm+116c11
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 116c11
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
Und hier Minidump 2 :
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`36e0c000 PsLoadedModuleList = 0xfffff803`372540b0
Debug session time: Tue Nov 5 17:49:21.070 2019 (UTC + 1:00)
System Uptime: 0 days 0:00:11.041
Loading Kernel Symbols
...............................................................
.................................................
Loading User Symbols
Loading unloaded module list
..
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`36fcd410 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff10c`321b9d70=00000000000000c4
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002002, Code Integrity Issue: The caller specified an executable MDL mapping. (Expected: MdlMappingNoExecute)
Arg2: fffff8010f380d16, The address in the driver's code where the error was detected.
Arg3: 0000000000000010, Page Priority (MM_PAGE_PRIORITY logically OR'd with MdlMapping*).
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4THF6MP
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 23
Key : Analysis.Memory.CommitPeak.Mb
Value: 67
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: c4
BUGCHECK_P1: 2002
BUGCHECK_P2: fffff8010f380d16
BUGCHECK_P3: 10
BUGCHECK_P4: 0
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff10c`321b9d68 fffff803`3777b6e3 : 00000000`000000c4 00000000`00002002 fffff801`0f380d16 00000000`00000010 : nt!KeBugCheckEx
fffff10c`321b9d70 fffff803`371358bb : fffff803`3723987c 00000000`00002002 fffff801`0f380d16 00000000`00000010 : nt!VerifierBugCheckIfAppropriate+0xdf
fffff10c`321b9db0 fffff803`37772a2c : 00000000`00000010 00000000`00000010 fffff803`3723987c 00000001`c3c3c3c3 : nt!VfReportIssueWithOptions+0x103
fffff10c`321b9e00 fffff803`37791523 : ffffcd8e`16dfc540 ffffcd8e`16cc5988 ffffcd8e`16cc5988 fffff803`37f6f8c1 : nt!VfCheckPagePriority+0x70
fffff10c`321b9e40 fffff801`0f380d16 : fffff10c`31a05f70 fffff10c`31a05c01 ffffcd8e`16cc5988 c3c3c3c3`00000000 : nt!VerifierMmMapLockedPagesSpecifyCache+0x43
fffff10c`321b9e90 fffff10c`31a05f70 : fffff10c`31a05c01 ffffcd8e`16cc5988 c3c3c3c3`00000000 00000000`00000000 : aswSnx+0x20d16
fffff10c`321b9e98 fffff10c`31a05c01 : ffffcd8e`16cc5988 c3c3c3c3`00000000 00000000`00000000 ffffc7e3`00000010 : 0xfffff10c`31a05f70
fffff10c`321b9ea0 ffffcd8e`16cc5988 : c3c3c3c3`00000000 00000000`00000000 ffffc7e3`00000010 1a000000`8ce82863 : 0xfffff10c`31a05c01
fffff10c`321b9ea8 c3c3c3c3`00000000 : 00000000`00000000 ffffc7e3`00000010 1a000000`8ce82863 ffffc7f8`86190da0 : 0xffffcd8e`16cc5988
fffff10c`321b9eb0 00000000`00000000 : ffffc7e3`00000010 1a000000`8ce82863 ffffc7f8`86190da0 ffffa001`457e7d90 : 0xc3c3c3c3`00000000
SYMBOL_NAME: aswSnx+20d16
MODULE_NAME: aswSnx
IMAGE_NAME: aswSnx.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 20d16
FAILURE_BUCKET_ID: 0xc4_2002_VRF_aswSnx!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {17df2ca0-1bf5-d266-fff8-431a5f2524cc}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80471d73358, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 5
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4THF6MP
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 42
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80471d73358
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff804`74475b08 fffff804`719eeb2b : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`71d73358 : nt!KeBugCheckEx
fffff804`74475b10 fffff804`7181f61c : 00000f10`b1806647 fffff804`6c8bc180 00000000`00067ecc 00000000`00067ecc : nt!KeAccumulateTicks+0x1cc0cb
fffff804`74475b70 fffff804`7175e4b7 : ffffd202`acb04a80 fffff804`74466f20 fffff804`74466fa0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
fffff804`74475f30 fffff804`71802a25 : 0000000f`7d8f6c49 fffff804`717cc0e0 fffff804`717cc190 ffff8de2`af62664d : hal!HalpTimerClockInterrupt+0xf7
fffff804`74475f60 fffff804`719c2eaa : fffff804`74466fa0 fffff804`717cc0e0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`74475fb0 fffff804`719c3417 : 00000000`00000000 00000000`00000000 00000000`00000003 fffff804`74466fb0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`74466f20 fffff804`8f0e6c11 : fffff804`8f10ec43 ffffd202`a8de3000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`744670b8 fffff804`8f10ec43 : ffffd202`a8de3000 00000000`00000000 00000000`00000000 0ee469df`0000000e : nvlddmkm+0x116c11
fffff804`744670c0 ffffd202`a8de3000 : 00000000`00000000 00000000`00000000 0ee469df`0000000e 5dc19fac`00000020 : nvlddmkm+0x13ec43
fffff804`744670c8 00000000`00000000 : 00000000`00000000 0ee469df`0000000e 5dc19fac`00000020 fffff804`74467100 : 0xffffd202`a8de3000
SYMBOL_NAME: nvlddmkm+116c11
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 116c11
FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}
Followup: MachineOwner
---------
Und hier Minidump 2 :
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`36e0c000 PsLoadedModuleList = 0xfffff803`372540b0
Debug session time: Tue Nov 5 17:49:21.070 2019 (UTC + 1:00)
System Uptime: 0 days 0:00:11.041
Loading Kernel Symbols
...............................................................
.................................................
Loading User Symbols
Loading unloaded module list
..
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`36fcd410 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff10c`321b9d70=00000000000000c4
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000002002, Code Integrity Issue: The caller specified an executable MDL mapping. (Expected: MdlMappingNoExecute)
Arg2: fffff8010f380d16, The address in the driver's code where the error was detected.
Arg3: 0000000000000010, Page Priority (MM_PAGE_PRIORITY logically OR'd with MdlMapping*).
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-4THF6MP
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 23
Key : Analysis.Memory.CommitPeak.Mb
Value: 67
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: c4
BUGCHECK_P1: 2002
BUGCHECK_P2: fffff8010f380d16
BUGCHECK_P3: 10
BUGCHECK_P4: 0
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff10c`321b9d68 fffff803`3777b6e3 : 00000000`000000c4 00000000`00002002 fffff801`0f380d16 00000000`00000010 : nt!KeBugCheckEx
fffff10c`321b9d70 fffff803`371358bb : fffff803`3723987c 00000000`00002002 fffff801`0f380d16 00000000`00000010 : nt!VerifierBugCheckIfAppropriate+0xdf
fffff10c`321b9db0 fffff803`37772a2c : 00000000`00000010 00000000`00000010 fffff803`3723987c 00000001`c3c3c3c3 : nt!VfReportIssueWithOptions+0x103
fffff10c`321b9e00 fffff803`37791523 : ffffcd8e`16dfc540 ffffcd8e`16cc5988 ffffcd8e`16cc5988 fffff803`37f6f8c1 : nt!VfCheckPagePriority+0x70
fffff10c`321b9e40 fffff801`0f380d16 : fffff10c`31a05f70 fffff10c`31a05c01 ffffcd8e`16cc5988 c3c3c3c3`00000000 : nt!VerifierMmMapLockedPagesSpecifyCache+0x43
fffff10c`321b9e90 fffff10c`31a05f70 : fffff10c`31a05c01 ffffcd8e`16cc5988 c3c3c3c3`00000000 00000000`00000000 : aswSnx+0x20d16
fffff10c`321b9e98 fffff10c`31a05c01 : ffffcd8e`16cc5988 c3c3c3c3`00000000 00000000`00000000 ffffc7e3`00000010 : 0xfffff10c`31a05f70
fffff10c`321b9ea0 ffffcd8e`16cc5988 : c3c3c3c3`00000000 00000000`00000000 ffffc7e3`00000010 1a000000`8ce82863 : 0xfffff10c`31a05c01
fffff10c`321b9ea8 c3c3c3c3`00000000 : 00000000`00000000 ffffc7e3`00000010 1a000000`8ce82863 ffffc7f8`86190da0 : 0xffffcd8e`16cc5988
fffff10c`321b9eb0 00000000`00000000 : ffffc7e3`00000010 1a000000`8ce82863 ffffc7f8`86190da0 ffffa001`457e7d90 : 0xc3c3c3c3`00000000
SYMBOL_NAME: aswSnx+20d16
MODULE_NAME: aswSnx
IMAGE_NAME: aswSnx.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 20d16
FAILURE_BUCKET_ID: 0xc4_2002_VRF_aswSnx!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {17df2ca0-1bf5-d266-fff8-431a5f2524cc}
Followup: MachineOwner
---------
Ich hoffe das ist hilfreich und dass mir vielleicht jemand weiterhelfen kann
Zuletzt bearbeitet von einem Moderator: