Çözüldü Mavi Ekran Hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10
Çözüm
Sorun NVIDIA ekran kartınızın sürücüsüyle alakalı. Aşağıdaki sürücüyü indirin ve daha sonra DDU ile eski sürücüyü kaldırın. Eski sürücü kalkıp bilgisayar yeniden başladığındaysa bu indirdiğiniz sürücüyü kurun. DDU kullanım rehberi aşağıda yer alıyor. Ayrıca sorun çözülürse bildirmeyi unutmayın.



[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8046bcfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 105096

Key : Analysis.Init.CPU.mSec
Value: 858

Key : Analysis.Init.Elapsed.mSec
Value: 6573

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8046bcfb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff80471a6cc80 -- (.trap 0xfffff80471a6cc80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffff9588ba4eab02
rdx=fffff80471a6d602 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8046b293272 rsp=fffff80471a6ce10 rbp=fffff80471a6cf79
r8=0000000000000000 r9=fffff80471a6ce80 r10=ffff9588bda92ae0
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!KzLowerIrql+0x2:
fffff804`6b293272 4883ec20 sub rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff804`71a7bc88 fffff804`6b43adbe : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`71a7bc90 fffff804`6b27541d : 00000a43`e91de9ab fffff804`69baf180 00000000`00000246 00000000`00038cf6 : nt!KeAccumulateTicks+0x1c8bbe
fffff804`71a7bcf0 fffff804`6b2759c1 : 00000000`00000000 00000000`00021dc8 fffff804`69baf180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff804`71a7bd40 fffff804`6b26f833 : fffff804`69baf180 00000000`00000000 fffff804`6bc31a38 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff804`71a7be80 fffff804`6b2781f2 : fffff804`71a6cc80 fffff804`71a6cd00 fffff804`71a6cd00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff804`71a7bf30 fffff804`6b327f55 : 00000008`773882a1 fffff804`6bcf3ae0 fffff804`6bcf3b90 ffff8000`7cf26640 : nt!HalpTimerClockInterrupt+0xe2
fffff804`71a7bf60 fffff804`6b3f78ea : fffff804`71a6cd00 fffff804`6bcf3ae0 00000000`00000069 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`71a7bfb0 fffff804`6b3f7e57 : ffff9588`ba4eab70 fffff804`6b3f7e64 ffff9588`bda91098 fffff804`7c06489b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`71a6cc80 fffff804`6b293272 : fffff804`71a6d6e0 fffff804`7c06489b ffff9588`bda90000 fffff804`7c0e53a6 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`71a6ce10 fffff804`7c06489b : ffff9588`bda90000 fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 : nt!KzLowerIrql+0x2
fffff804`71a6ce20 ffff9588`bda90000 : fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 : nvlddmkm+0x9489b
fffff804`71a6ce28 fffff804`7c0e53a6 : ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 : 0xffff9588`bda90000
fffff804`71a6ce30 ffff9588`bda90000 : 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 : nvlddmkm+0x1153a6
fffff804`71a6ce38 00000000`00000000 : fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 00000000`00000001 : 0xffff9588`bda90000


SYMBOL_NAME: nvlddmkm+9489b

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9489b

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup: MachineOwner
---------[/CODE]
Sorun NVIDIA ekran kartınızın sürücüsüyle alakalı. Aşağıdaki sürücüyü indirin ve daha sonra DDU ile eski sürücüyü kaldırın. Eski sürücü kalkıp bilgisayar yeniden başladığındaysa bu indirdiğiniz sürücüyü kurun. DDU kullanım rehberi aşağıda yer alıyor. Ayrıca sorun çözülürse bildirmeyi unutmayın.



[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8046bcfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 105096

Key : Analysis.Init.CPU.mSec
Value: 858

Key : Analysis.Init.Elapsed.mSec
Value: 6573

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8046bcfb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff80471a6cc80 -- (.trap 0xfffff80471a6cc80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffff9588ba4eab02
rdx=fffff80471a6d602 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8046b293272 rsp=fffff80471a6ce10 rbp=fffff80471a6cf79
r8=0000000000000000 r9=fffff80471a6ce80 r10=ffff9588bda92ae0
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!KzLowerIrql+0x2:
fffff804`6b293272 4883ec20 sub rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff804`71a7bc88 fffff804`6b43adbe : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`71a7bc90 fffff804`6b27541d : 00000a43`e91de9ab fffff804`69baf180 00000000`00000246 00000000`00038cf6 : nt!KeAccumulateTicks+0x1c8bbe
fffff804`71a7bcf0 fffff804`6b2759c1 : 00000000`00000000 00000000`00021dc8 fffff804`69baf180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff804`71a7bd40 fffff804`6b26f833 : fffff804`69baf180 00000000`00000000 fffff804`6bc31a38 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff804`71a7be80 fffff804`6b2781f2 : fffff804`71a6cc80 fffff804`71a6cd00 fffff804`71a6cd00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff804`71a7bf30 fffff804`6b327f55 : 00000008`773882a1 fffff804`6bcf3ae0 fffff804`6bcf3b90 ffff8000`7cf26640 : nt!HalpTimerClockInterrupt+0xe2
fffff804`71a7bf60 fffff804`6b3f78ea : fffff804`71a6cd00 fffff804`6bcf3ae0 00000000`00000069 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`71a7bfb0 fffff804`6b3f7e57 : ffff9588`ba4eab70 fffff804`6b3f7e64 ffff9588`bda91098 fffff804`7c06489b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`71a6cc80 fffff804`6b293272 : fffff804`71a6d6e0 fffff804`7c06489b ffff9588`bda90000 fffff804`7c0e53a6 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`71a6ce10 fffff804`7c06489b : ffff9588`bda90000 fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 : nt!KzLowerIrql+0x2
fffff804`71a6ce20 ffff9588`bda90000 : fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 : nvlddmkm+0x9489b
fffff804`71a6ce28 fffff804`7c0e53a6 : ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 : 0xffff9588`bda90000
fffff804`71a6ce30 ffff9588`bda90000 : 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 : nvlddmkm+0x1153a6
fffff804`71a6ce38 00000000`00000000 : fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 00000000`00000001 : 0xffff9588`bda90000


SYMBOL_NAME: nvlddmkm+9489b

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9489b

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup: MachineOwner
---------[/CODE]
 
Çözüm
Sorun NVIDIA ekran kartınızın sürücüsüyle alakalı. Aşağıdaki sürücüyü indirin ve daha sonra DDU ile eski sürücüyü kaldırın. Eski sürücü kalkıp bilgisayar yeniden başladığındaysa bu indirdiğiniz sürücüyü kurun. DDU kullanım rehberi aşağıda yer alıyor. Ayrıca sorun çözülürse bildirmeyi unutmayın.



[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8046bcfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 105096

Key : Analysis.Init.CPU.mSec
Value: 858

Key : Analysis.Init.Elapsed.mSec
Value: 6573

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8046bcfb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff80471a6cc80 -- (.trap 0xfffff80471a6cc80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffff9588ba4eab02
rdx=fffff80471a6d602 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8046b293272 rsp=fffff80471a6ce10 rbp=fffff80471a6cf79
r8=0000000000000000 r9=fffff80471a6ce80 r10=ffff9588bda92ae0
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!KzLowerIrql+0x2:
fffff804`6b293272 4883ec20 sub rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff804`71a7bc88 fffff804`6b43adbe : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`71a7bc90 fffff804`6b27541d : 00000a43`e91de9ab fffff804`69baf180 00000000`00000246 00000000`00038cf6 : nt!KeAccumulateTicks+0x1c8bbe
fffff804`71a7bcf0 fffff804`6b2759c1 : 00000000`00000000 00000000`00021dc8 fffff804`69baf180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff804`71a7bd40 fffff804`6b26f833 : fffff804`69baf180 00000000`00000000 fffff804`6bc31a38 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff804`71a7be80 fffff804`6b2781f2 : fffff804`71a6cc80 fffff804`71a6cd00 fffff804`71a6cd00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff804`71a7bf30 fffff804`6b327f55 : 00000008`773882a1 fffff804`6bcf3ae0 fffff804`6bcf3b90 ffff8000`7cf26640 : nt!HalpTimerClockInterrupt+0xe2
fffff804`71a7bf60 fffff804`6b3f78ea : fffff804`71a6cd00 fffff804`6bcf3ae0 00000000`00000069 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`71a7bfb0 fffff804`6b3f7e57 : ffff9588`ba4eab70 fffff804`6b3f7e64 ffff9588`bda91098 fffff804`7c06489b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`71a6cc80 fffff804`6b293272 : fffff804`71a6d6e0 fffff804`7c06489b ffff9588`bda90000 fffff804`7c0e53a6 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`71a6ce10 fffff804`7c06489b : ffff9588`bda90000 fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 : nt!KzLowerIrql+0x2
fffff804`71a6ce20 ffff9588`bda90000 : fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 : nvlddmkm+0x9489b
fffff804`71a6ce28 fffff804`7c0e53a6 : ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 : 0xffff9588`bda90000
fffff804`71a6ce30 ffff9588`bda90000 : 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 : nvlddmkm+0x1153a6
fffff804`71a6ce38 00000000`00000000 : fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 00000000`00000001 : 0xffff9588`bda90000


SYMBOL_NAME: nvlddmkm+9489b

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9489b

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup: MachineOwner
---------[/CODE]
Ne yazıyordu? Arama kısmına ''Mavi ekran sorunlarını düzelt'' yazar mısın?
Sorun NVIDIA ekran kartınızın sürücüsüyle alakalı. Aşağıdaki sürücüyü indirin ve daha sonra DDU ile eski sürücüyü kaldırın. Eski sürücü kalkıp bilgisayar yeniden başladığındaysa bu indirdiğiniz sürücüyü kurun. DDU kullanım rehberi aşağıda yer alıyor. Ayrıca sorun çözülürse bildirmeyi unutmayın.



[CODE title="Dökümler"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8046bcfb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 9499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 105096

Key : Analysis.Init.CPU.mSec
Value: 858

Key : Analysis.Init.Elapsed.mSec
Value: 6573

Key : Analysis.Memory.CommitPeak.Mb
Value: 77

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8046bcfb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff80471a6cc80 -- (.trap 0xfffff80471a6cc80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffff9588ba4eab02
rdx=fffff80471a6d602 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8046b293272 rsp=fffff80471a6ce10 rbp=fffff80471a6cf79
r8=0000000000000000 r9=fffff80471a6ce80 r10=ffff9588bda92ae0
r11=000000000000000c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac pe cy
nt!KzLowerIrql+0x2:
fffff804`6b293272 4883ec20 sub rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff804`71a7bc88 fffff804`6b43adbe : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`71a7bc90 fffff804`6b27541d : 00000a43`e91de9ab fffff804`69baf180 00000000`00000246 00000000`00038cf6 : nt!KeAccumulateTicks+0x1c8bbe
fffff804`71a7bcf0 fffff804`6b2759c1 : 00000000`00000000 00000000`00021dc8 fffff804`69baf180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff804`71a7bd40 fffff804`6b26f833 : fffff804`69baf180 00000000`00000000 fffff804`6bc31a38 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff804`71a7be80 fffff804`6b2781f2 : fffff804`71a6cc80 fffff804`71a6cd00 fffff804`71a6cd00 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
fffff804`71a7bf30 fffff804`6b327f55 : 00000008`773882a1 fffff804`6bcf3ae0 fffff804`6bcf3b90 ffff8000`7cf26640 : nt!HalpTimerClockInterrupt+0xe2
fffff804`71a7bf60 fffff804`6b3f78ea : fffff804`71a6cd00 fffff804`6bcf3ae0 00000000`00000069 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`71a7bfb0 fffff804`6b3f7e57 : ffff9588`ba4eab70 fffff804`6b3f7e64 ffff9588`bda91098 fffff804`7c06489b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`71a6cc80 fffff804`6b293272 : fffff804`71a6d6e0 fffff804`7c06489b ffff9588`bda90000 fffff804`7c0e53a6 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`71a6ce10 fffff804`7c06489b : ffff9588`bda90000 fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 : nt!KzLowerIrql+0x2
fffff804`71a6ce20 ffff9588`bda90000 : fffff804`7c0e53a6 ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 : nvlddmkm+0x9489b
fffff804`71a6ce28 fffff804`7c0e53a6 : ffff9588`bda90000 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 : 0xffff9588`bda90000
fffff804`71a6ce30 ffff9588`bda90000 : 00000000`00000000 fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 : nvlddmkm+0x1153a6
fffff804`71a6ce38 00000000`00000000 : fffff804`71a6d730 fffff804`7c065b37 00000000`00000000 00000000`00000001 : 0xffff9588`bda90000


SYMBOL_NAME: nvlddmkm+9489b

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 9489b

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {15c3af0e-5564-7a80-2e26-65b5115ecc4d}

Followup: MachineOwner
---------[/CODE]
Hocam dediklerini yaptım tekrardan mavi ekran verirse haberdar ederim
 
Son düzenleme:
Hocam şu anlık bir sorun vermedi daha ama bir sorum olacaktı GeForce Experience de sürücü güncellemesi gösteriyor. Onu aynı şekilde DDU ile ekran kartı sürücülerini temizledikten sonra mı kurmam gerekiyor?

Yeni sürücünün sürücü numarası nedir bilmiyorum ama güncelleme notlarına bakın ve mavi ekran hatası düzeltilmişse onu kurun. Sorun o sürümlü sürücüdeydi anlayacağınız. Eski sürümlü sürücüyü kurmadığınız sürece her şeyi yapmakta serbestsiniz.
 
Yeni sürücünün sürücü numarası nedir bilmiyorum ama güncelleme notlarına bakın ve mavi ekran hatası düzeltilmişse onu kurun. Sorun o sürümlü sürücüdeydi anlayacağınız. Eski sürümlü sürücüyü kurmadığınız sürece her şeyi yapmakta serbestsiniz.
Screenshot_4.png

Bu şekilde hocam, tekrardan yardımın için teşekkür ederim. Çalıştığım için biraz geç yazıyorum kusura bakmayın
 
Ne demek, sorunun çözülmesine sevindim. Bu arada aylar sonra geri dönenler dahi oluyor, takmayın hemen yanıt verip vermemeye. İyi çalışmalar ve iyi geceler dilerim :)
 

Geri
Yukarı