Bilgisayar mavi ekran hatası veriyor

İşletim sistemi
Windows 10
C

cscs1903

Hectopat
Katılım
19 Temmuz 2017
Mesajlar
28
Çözümler
1
Daha fazla  
Cinsiyet
Erkek
RAM
16 GB 3200MHz Team Force RAM.
SSD veya HDD modeli
corsair mp510 240 gb
Ekran kartı
rx 570 armor oc
Anakart
asus tuf b450 pro gaming
İşlemci
ryzen 5 3600
Arkadaşlar 2 gündür mavi ekran yiyorum. DMP dosyalarını bırakıyorum, yardımcı olursanız sevinirim.

minidump - Google Drive

drive.google.com drive.google.com
 
Son düzenleyen: Moderatör:
Tarihe göre sırala Puana göre sırala
Mavi ekran sanırsam oyun oynarken aldın rapor sonucunu bırakıyorum;

Kod: 
*******************************************************************************
* *
* 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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8067f4fb320, 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.mSec
 Value: 2952

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 17163

 Key : Analysis.IO.Other.Mb
 Value: 17

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 20

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x133

 Key : Bugcheck.Code.Register
 Value: 0x133

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

FILE_IN_CAB: 041823-5859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
 Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8067f4fb320

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: AMDRSServ.exe

STACK_TEXT:
ffffab80`c44b7e18 fffff806`7ec43714 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`7f4fb320 : nt!KeBugCheckEx
ffffab80`c44b7e20 fffff806`7ea813c3 : 0000339c`ac10b4fd ffffab80`c449e180 00000000`00000000 ffffab80`c449e180 : nt!KeAccumulateTicks+0x1bfaf4
ffffab80`c44b7e80 fffff806`7ea80eaa : ffffc30a`1dca89a0 ffffaa83`6af48300 ffffc30a`27ded000 ffffc30a`27af0000 : nt!KeClockInterruptNotify+0x453
ffffab80`c44b7f30 fffff806`7eb3e965 : ffffc30a`1dca89a0 00000000`00000000 00000000`00000000 ffff7dd8`ce129212 : nt!HalpTimerClockIpiRoutine+0x1a
ffffab80`c44b7f60 fffff806`7ebfdb8a : ffffaa83`6af48300 ffffc30a`1dca89a0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffab80`c44b7fb0 fffff806`7ebfe357 : 00000000`bb6144ba 00000000`00000000 ffff7cdb`60ad6d12 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffaa83`6af48280 fffff806`7eb405bf : ffffaa83`6af48480 00000000`00000008 ffff82f6`e0c16ae8 ffff9587`00000004 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffaa83`6af48410 fffff806`7ea1e6dc : ffffc30a`204ffd90 ffffc30a`204ffd90 ffffaa83`6af48499 ffff9587`f836fd20 : nt!KxWaitForSpinLockAndAcquire+0x2f
ffffaa83`6af48440 fffff806`7ebfd206 : ffffc30a`337e0a20 00000000`000b883a ffffc30a`337e0a20 00000000`00000000 : nt!KeAcquireSpinLockAtDpcLevel+0x5c
ffffaa83`6af48470 fffff806`8205d75c : ffffc30a`24da3d90 fffff806`ac2f42c0 ffffc30a`2bf52b70 00000000`00000000 : nt!KeSynchronizeExecution+0x36
ffffaa83`6af484b0 fffff806`ac2e78e5 : 00000000`00000000 ffffc30a`2bf52b70 ffffaa83`6af485b9 ffffc30a`27ded000 : dxgkrnl!DpSynchronizeExecution+0xac
ffffaa83`6af48500 fffff806`ac2e65dd : ffffc30a`337e0a00 00000000`00000000 ffffc30a`2bf52b70 ffffc30a`337e0a20 : dxgmms2!VidSchiInsertCommandToSoftwareQueue+0x2b5
ffffaa83`6af48560 fffff806`ac2e5661 : ffffc30a`00000000 ffffc30a`337e0a20 ffffc30a`2e0759e0 ffffc30a`2bf52b70 : dxgmms2!VidSchiSubmitCommandPacketToQueue+0xed
ffffaa83`6af48620 fffff806`8213c680 : ffff9587`f836fd20 00000000`00000000 ffff9587`f836fd20 ffffaa83`6af48878 : dxgmms2!VidSchWaitForSingleSyncObject+0x351
ffffaa83`6af486e0 fffff806`8213aa66 : ffffc30a`2f01f080 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!WaitForSynchronizationObjectFromGpu+0x1b70
ffffaa83`6af48990 fffff806`8213a656 : 00000000`00000020 fffff806`8219dc40 00000000`00000003 ffffc30a`00000001 : dxgkrnl!DxgkWaitForSynchronizationObjectFromGpuInternal+0x3f6
ffffaa83`6af48ac0 fffff806`7ec0f3f8 : ffffc30a`2f01f080 ffffc30a`00000000 00000000`00000000 ffffc30a`2e0abef0 : dxgkrnl!DxgkWaitForSynchronizationObjectFromGpu+0x16
ffffaa83`6af48b00 00007ffb`ba805ca4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000af`733fc328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ba805ca4

SYMBOL_NAME: dxgkrnl!DpSynchronizeExecution+ac

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.2311

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: ac

FAILURE_BUCKET_ID: 0x133_ISR_dxgkrnl!DpSynchronizeExecution

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {558c278d-5c04-0e1d-c3fd-1cbb6a5abeff}

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: 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: fffff807798fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
 additional information regarding this single DPC timeout

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.mSec
 Value: 2656

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 4680

 Key : Analysis.IO.Other.Mb
 Value: 16

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 18

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x133

 Key : Bugcheck.Code.Register
 Value: 0x133

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

FILE_IN_CAB: 041723-5937-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
 Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff807798fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa480`7c792c88 fffff807`79043690 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffa480`7c792c90 fffff807`78e86e3d : 0001e82d`13abb27f ffffa480`7c740180 00000000`00000246 00000000`00c94d2d : nt!KeAccumulateTicks+0x1bfa70
ffffa480`7c792cf0 fffff807`78e7dec1 : fffff807`78f65000 00000000`0077fc2a ffffa480`7c740180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffa480`7c792d40 fffff807`78e81253 : ffffa480`7c740180 00000000`00000000 fffff807`79831598 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffa480`7c792e80 fffff807`78e88ae2 : fffffa8c`af037580 fffffa8c`af037600 fffffa8c`af037600 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffa480`7c792f30 fffff807`78f3e965 : 000001df`f1e2bd32 ffffd10f`410a8200 ffffd10f`410a82b0 ffff142f`70868916 : nt!HalpTimerClockInterrupt+0xe2
ffffa480`7c792f60 fffff807`78ffdbaa : fffffa8c`af037600 ffffd10f`410a8200 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffa480`7c792fb0 fffff807`78ffe377 : 00000000`00000000 00000000`00000000 fffffa8c`af0377c0 fffff807`78ffe384 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffa8c`af037580 fffff807`78ede397 : 00000000`00000010 00000000`00000286 fffffa8c`af037738 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffa8c`af037710 fffff807`78e950ca : 00000001`ffffffff fffffff6`0000000d fffffa8c`af0378e8 00000000`00000006 : nt!KeYieldProcessorEx+0x17
fffffa8c`af037740 fffff807`78e96dd3 : 00000000`46c24a66 fffff807`78ee10ea 00000000`00000000 00000000`00000006 : nt!KxWaitForLockOwnerShip+0x2a
fffffa8c`af037770 fffff807`a5cc4be6 : ffffd10f`49ebc000 00000000`00989680 ffffd10f`49ebc000 ffffd10f`49ebc000 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x73
fffffa8c`af0377a0 fffff807`78ee0619 : ffffd10f`492f38c0 fffff807`a5cc4ba0 00000000`00989680 fffffa8c`af0378a9 : dxgmms2!VidSchiWorkerThreadTimerCallback+0x46
fffffa8c`af037800 fffff807`78e8d925 : ffffd10f`4b4f1a38 00000000`00000001 fffffa8c`af037b10 ffffd10f`4b4f1a38 : nt!KiExpireTimer2+0x429
fffffa8c`af037910 fffff807`78e8aee4 : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`0077f947 : nt!KiTimer2Expiration+0x165
fffffa8c`af0379d0 fffff807`7900050e : ffffffff`00000000 ffffa480`7c740180 ffffa480`7c74b340 ffffd10f`4d4df080 : nt!KiRetireDpcList+0x874
fffffa8c`af037c60 00000000`00000000 : fffffa8c`af038000 fffffa8c`af032000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: dxgmms2!VidSchiWorkerThreadTimerCallback+46

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.2311

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 46

FAILURE_BUCKET_ID: 0x133_DPC_dxgmms2!VidSchiWorkerThreadTimerCallback

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7c8b50ff-53da-11c4-a8b3-cef8f5e196be}

Followup: MachineOwner
---------

İlk önce ekran kartını overclock undervolt işlemleri yaptıysan geri alıp, sürücüyü " AMD Cleanup Utility " ile silip temiz bir kurulum ile en güncel driverı yeniden yükleyip test edin.
 
Artı 0 Eksi
lazye dedi:
Mavi ekran sanırsam oyun oynarken aldın rapor sonucunu bırakıyorum;

Kod: 
*******************************************************************************
* *
* 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.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8067f4fb320, 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.mSec
 Value: 2952

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 17163

 Key : Analysis.IO.Other.Mb
 Value: 17

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 20

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x133

 Key : Bugcheck.Code.Register
 Value: 0x133

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

FILE_IN_CAB: 041823-5859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
 Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8067f4fb320

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: AMDRSServ.exe

STACK_TEXT:
ffffab80`c44b7e18 fffff806`7ec43714 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`7f4fb320 : nt!KeBugCheckEx
ffffab80`c44b7e20 fffff806`7ea813c3 : 0000339c`ac10b4fd ffffab80`c449e180 00000000`00000000 ffffab80`c449e180 : nt!KeAccumulateTicks+0x1bfaf4
ffffab80`c44b7e80 fffff806`7ea80eaa : ffffc30a`1dca89a0 ffffaa83`6af48300 ffffc30a`27ded000 ffffc30a`27af0000 : nt!KeClockInterruptNotify+0x453
ffffab80`c44b7f30 fffff806`7eb3e965 : ffffc30a`1dca89a0 00000000`00000000 00000000`00000000 ffff7dd8`ce129212 : nt!HalpTimerClockIpiRoutine+0x1a
ffffab80`c44b7f60 fffff806`7ebfdb8a : ffffaa83`6af48300 ffffc30a`1dca89a0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffab80`c44b7fb0 fffff806`7ebfe357 : 00000000`bb6144ba 00000000`00000000 ffff7cdb`60ad6d12 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffaa83`6af48280 fffff806`7eb405bf : ffffaa83`6af48480 00000000`00000008 ffff82f6`e0c16ae8 ffff9587`00000004 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffaa83`6af48410 fffff806`7ea1e6dc : ffffc30a`204ffd90 ffffc30a`204ffd90 ffffaa83`6af48499 ffff9587`f836fd20 : nt!KxWaitForSpinLockAndAcquire+0x2f
ffffaa83`6af48440 fffff806`7ebfd206 : ffffc30a`337e0a20 00000000`000b883a ffffc30a`337e0a20 00000000`00000000 : nt!KeAcquireSpinLockAtDpcLevel+0x5c
ffffaa83`6af48470 fffff806`8205d75c : ffffc30a`24da3d90 fffff806`ac2f42c0 ffffc30a`2bf52b70 00000000`00000000 : nt!KeSynchronizeExecution+0x36
ffffaa83`6af484b0 fffff806`ac2e78e5 : 00000000`00000000 ffffc30a`2bf52b70 ffffaa83`6af485b9 ffffc30a`27ded000 : dxgkrnl!DpSynchronizeExecution+0xac
ffffaa83`6af48500 fffff806`ac2e65dd : ffffc30a`337e0a00 00000000`00000000 ffffc30a`2bf52b70 ffffc30a`337e0a20 : dxgmms2!VidSchiInsertCommandToSoftwareQueue+0x2b5
ffffaa83`6af48560 fffff806`ac2e5661 : ffffc30a`00000000 ffffc30a`337e0a20 ffffc30a`2e0759e0 ffffc30a`2bf52b70 : dxgmms2!VidSchiSubmitCommandPacketToQueue+0xed
ffffaa83`6af48620 fffff806`8213c680 : ffff9587`f836fd20 00000000`00000000 ffff9587`f836fd20 ffffaa83`6af48878 : dxgmms2!VidSchWaitForSingleSyncObject+0x351
ffffaa83`6af486e0 fffff806`8213aa66 : ffffc30a`2f01f080 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!WaitForSynchronizationObjectFromGpu+0x1b70
ffffaa83`6af48990 fffff806`8213a656 : 00000000`00000020 fffff806`8219dc40 00000000`00000003 ffffc30a`00000001 : dxgkrnl!DxgkWaitForSynchronizationObjectFromGpuInternal+0x3f6
ffffaa83`6af48ac0 fffff806`7ec0f3f8 : ffffc30a`2f01f080 ffffc30a`00000000 00000000`00000000 ffffc30a`2e0abef0 : dxgkrnl!DxgkWaitForSynchronizationObjectFromGpu+0x16
ffffaa83`6af48b00 00007ffb`ba805ca4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000af`733fc328 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ba805ca4

SYMBOL_NAME: dxgkrnl!DpSynchronizeExecution+ac

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.2311

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: ac

FAILURE_BUCKET_ID: 0x133_ISR_dxgkrnl!DpSynchronizeExecution

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {558c278d-5c04-0e1d-c3fd-1cbb6a5abeff}

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: 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: fffff807798fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
 additional information regarding this single DPC timeout

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.mSec
 Value: 2656

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 4680

 Key : Analysis.IO.Other.Mb
 Value: 16

 Key : Analysis.IO.Read.Mb
 Value: 0

 Key : Analysis.IO.Write.Mb
 Value: 18

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

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

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

 Key : Bugcheck.Code.DumpHeader
 Value: 0x133

 Key : Bugcheck.Code.Register
 Value: 0x133

 Key : Dump.Attributes.AsUlong
 Value: 8

 Key : Dump.Attributes.KernelGeneratedTriageDump
 Value: 1

FILE_IN_CAB: 041723-5937-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
 Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff807798fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa480`7c792c88 fffff807`79043690 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffa480`7c792c90 fffff807`78e86e3d : 0001e82d`13abb27f ffffa480`7c740180 00000000`00000246 00000000`00c94d2d : nt!KeAccumulateTicks+0x1bfa70
ffffa480`7c792cf0 fffff807`78e7dec1 : fffff807`78f65000 00000000`0077fc2a ffffa480`7c740180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffa480`7c792d40 fffff807`78e81253 : ffffa480`7c740180 00000000`00000000 fffff807`79831598 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffa480`7c792e80 fffff807`78e88ae2 : fffffa8c`af037580 fffffa8c`af037600 fffffa8c`af037600 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffa480`7c792f30 fffff807`78f3e965 : 000001df`f1e2bd32 ffffd10f`410a8200 ffffd10f`410a82b0 ffff142f`70868916 : nt!HalpTimerClockInterrupt+0xe2
ffffa480`7c792f60 fffff807`78ffdbaa : fffffa8c`af037600 ffffd10f`410a8200 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffa480`7c792fb0 fffff807`78ffe377 : 00000000`00000000 00000000`00000000 fffffa8c`af0377c0 fffff807`78ffe384 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffa8c`af037580 fffff807`78ede397 : 00000000`00000010 00000000`00000286 fffffa8c`af037738 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffa8c`af037710 fffff807`78e950ca : 00000001`ffffffff fffffff6`0000000d fffffa8c`af0378e8 00000000`00000006 : nt!KeYieldProcessorEx+0x17
fffffa8c`af037740 fffff807`78e96dd3 : 00000000`46c24a66 fffff807`78ee10ea 00000000`00000000 00000000`00000006 : nt!KxWaitForLockOwnerShip+0x2a
fffffa8c`af037770 fffff807`a5cc4be6 : ffffd10f`49ebc000 00000000`00989680 ffffd10f`49ebc000 ffffd10f`49ebc000 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x73
fffffa8c`af0377a0 fffff807`78ee0619 : ffffd10f`492f38c0 fffff807`a5cc4ba0 00000000`00989680 fffffa8c`af0378a9 : dxgmms2!VidSchiWorkerThreadTimerCallback+0x46
fffffa8c`af037800 fffff807`78e8d925 : ffffd10f`4b4f1a38 00000000`00000001 fffffa8c`af037b10 ffffd10f`4b4f1a38 : nt!KiExpireTimer2+0x429
fffffa8c`af037910 fffff807`78e8aee4 : 00000000`00000000 00000000`00000000 00000000`00000008 00000000`0077f947 : nt!KiTimer2Expiration+0x165
fffffa8c`af0379d0 fffff807`7900050e : ffffffff`00000000 ffffa480`7c740180 ffffa480`7c74b340 ffffd10f`4d4df080 : nt!KiRetireDpcList+0x874
fffffa8c`af037c60 00000000`00000000 : fffffa8c`af038000 fffffa8c`af032000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: dxgmms2!VidSchiWorkerThreadTimerCallback+46

MODULE_NAME: dxgmms2

IMAGE_NAME: dxgmms2.sys

IMAGE_VERSION: 10.0.19041.2311

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 46

FAILURE_BUCKET_ID: 0x133_DPC_dxgmms2!VidSchiWorkerThreadTimerCallback

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7c8b50ff-53da-11c4-a8b3-cef8f5e196be}

Followup: MachineOwner
---------

İlk önce ekran kartını overclock undervolt işlemleri yaptıysan geri alıp, sürücüyü " AMD Cleanup Utility " ile silip temiz bir kurulum ile en güncel driverı yeniden yükleyip test edin.
Genişletmek için tıkla...
Evet oyunda iken aniden donuyor ve mavi ekran veriyor
 
Artı 0 Eksi
Artı 0 Eksi
Artı 0 Eksi
Artı 0 Eksi
Sorun ekran kartınızda görünüyor, OC yaptınız mı? Öyleyse o işlemi sıfırlayın.

Ayrıca çipset sürücünüzü ve BIOS'u güncelleyin.

TUF B450-PRO GAMING｜Anakart｜ASUS Türkiye

TUF Gaming serisi, en yeni AMD ve Intel® platformlarının temel unsurlarını saflaÅtırır ve bunları oyuna hazır özellikler ve kanıtlanmıŠdayanıklılıkla birleÅtirir. Askeri sınıf bileÅenler, yükseltilmiÅ bir güç çözümü ve kapsamlı soÄutma seçenekleri ile tasarlanan bu...
www.asus.com www.asus.com
 
Artı 0 Eksi

Benzer konular

Ömer Yücebaş
  • Soru
Bilgisayar mavi ekran hatası veriyor
Mesaj
2
Görüntüleme
79
684918
684918
Hielaph
  • Soru
Bilgisayar mavi ekran hatası veriyor
Mesaj
6
Görüntüleme
416
Hielaph
Hielaph
0merfaruk
  • Soru
Bilgisayar mavi ekran hatası veriyor
Mesaj
1
Görüntüleme
135
xtreamen
xtreamen
ismailsakinn
  • Soru
Bilgisayar mavi ekran hatası veriyor
Mesaj
2
Görüntüleme
277
phan metal
P
A
  • Çözüldü
Çözüldü  Bilgisayar mavi ekran hatası veriyor
2
Mesaj
14
Görüntüleme
825
Aslan193
A

Yeni konular

Yeni mesajlar

Geri
Yukarı