şahin123456
Hectopat
- Katılım
- 10 Mayıs 2021
- Mesajlar
- 1.524
- Çözümler
- 1
Daha fazla
- Cinsiyet
- Erkek
Sistem CS:GO'da mavi ekran veriyor
- Konuyu başlatan şahin123456
- Başlangıç Tarihi
- Mesaj 20
- Görüntüleme 783
Öncelikle Google hesabınıza giriş yapın. Daha sonra hesabınızın Drive kısmına gidin. Dosyalarınızı zipledikten sonra Drive'da dosyalarım kısmına sürükleyip bırakın. Dosyalar yüklendikten sonra Drive içinde dosyaya sağ tıklayın Paylaş kısmına tıklayın ve açılan ekranda aşağıdaki 1. resimde gösterildiği gibi bağlantıyı herkese açın. Daha sonra 2. resimdeki gibi bağlantıya sahip olan herkes seçeneğinin işaretli olduğundan emin olun ve bağlantıyı buraya gönderin.
KS
KS
şahin123456
Hectopat
- Katılım
- 10 Mayıs 2021
- Mesajlar
- 1.524
- Çözümler
- 1
Daha fazla
- Cinsiyet
- Erkek
Gönderdim nasıl bakacaksınız siz buna ?
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
KS
KS
şahin123456
Hectopat
- Katılım
- 10 Mayıs 2021
- Mesajlar
- 1.524
- Çözümler
- 1
Daha fazla
- Cinsiyet
- Erkek
DDU ile ekran kartı sürücüsünü silip yenisini yüklemeniz faydalı olabilir. Ve sistem dosyalarını kontrol etmek için şunu uygulamanızda aynı şekilde. VIDEO_TDR_FAILURE ve DPC_WATCHDOG_VIOLATION olarak gözüküyor hata adları. Tabii ben bu işlerde biraz acemiyim. Diğer hocalarımın da öncelikle incelemesi daha uygun olacaktır sanırım. @PanzerTR @Murat5038 @Er73748
[CODE title="Minidump Dosyası 1"]VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffbb0a3469d460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80253ddcc54, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 113257
Key : Analysis.Init.CPU.mSec
Value: 874
Key : Analysis.Init.Elapsed.mSec
Value: 53733
Key : Analysis.Memory.CommitPeak.Mb
Value: 88
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: 116
BUGCHECK_P1: ffffbb0a3469d460
BUGCHECK_P2: fffff80253ddcc54
BUGCHECK_P3: 0
BUGCHECK_P4: d
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffbb0a3469d460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 000000000000000d
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd58c`f14ffeb8 fffff802`547d1cce : 00000000`00000116 ffffbb0a`3469d460 fffff802`53ddcc54 00000000`00000000 : nt!KeBugCheckEx
ffffd58c`f14ffec0 fffff802`547d1331 : fffff802`53ddcc54 ffffbb0a`3469d460 ffffd58c`f14fffc9 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffd58c`f14fff00 fffff802`54255ba6 : ffffbb0a`3469d460 00000000`0000526a ffffd58c`f14fffc9 00000000`0000526a : dxgkrnl!TdrIsRecoveryRequired+0x1b1
ffffd58c`f14fff30 fffff802`5427e2cf : ffffd58c`f1500110 ffffbb0a`3189a000 ffffd58c`f1500110 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x662
ffffd58c`f1500030 fffff802`5427d240 : ffffbb0a`316f76f0 ffffbb0a`3189a000 00000000`00000000 ffffbb0a`318a5190 : dxgmms1!VidSchWaitForCompletionEvent+0x29f
ffffd58c`f15000f0 fffff802`5427fd76 : ffffbb0a`316f76f0 00000000`00000000 ffffbb0a`2edfb100 fffff802`54254557 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0x120
ffffd58c`f15001d0 fffff802`5427f35e : 00000000`0000007a ffffd58c`f1500300 00000000`0000007a ffffd58c`f1500311 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x206
ffffd58c`f1500220 fffff802`5427c900 : ffffbb0a`00000000 fffff802`00000003 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x3de
ffffd58c`f1500360 fffff802`542791d7 : ffffbb0a`31933000 00000000`00000000 ffffbb0a`2e30b3d0 ffffd58c`f1500460 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x500
ffffd58c`f1500410 fffff802`54278d70 : ffff820a`c01e0001 00000000`00000000 ffffbb0a`316f8aa0 00000000`00001000 : dxgmms1!VIDMM_GLOBAL::MemoryTransferInternal+0x2c7
ffffd58c`f15005f0 fffff802`542795f5 : 00000000`00000000 00000000`00000008 ffffbb0a`2e30b3d0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::MemoryTransfer+0xb8
ffffd58c`f1500690 fffff802`54274740 : 00000000`00000002 00000000`00000008 00000000`00000003 00000000`00000007 : dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x1c5
ffffd58c`f1500790 fffff802`54282b79 : ffffbb0a`31933000 ffffbb0a`31933000 00000000`00000000 ffffbb0a`34765000 : dxgmms1!VIDMM_GLOBAL:
ageInAllocations+0xc0
ffffd58c`f1500810 fffff802`54280936 : ffffbb0a`3189a000 ffff820a`c363fe90 ffffd58c`00000000 ffffbb0a`3467fa90 : dxgmms1!VIDMM_GLOBAL:repareDmaBuffer+0x1809
ffffd58c`f1500940 fffff802`54280060 : ffffbb0a`33d929b0 ffffbb0a`33d6b350 ffffbb0a`3189a000 ffffbb0a`3471a7d0 : dxgmms1!VidSchiSubmitRenderCommand+0x1f6
ffffd58c`f1500b90 fffff802`542a68bf : 00000000`00000080 ffffbb0a`3189a000 ffffbb0a`2c886040 00000000`00000000 : dxgmms1!VidSchiRun_PriorityTable+0xf0
ffffd58c`f1500bd0 fffff802`4c8f53b5 : ffffbb0a`31632080 fffff802`542a6820 ffffbb0a`3189a000 00078405`b59bbfff : dxgmms1!VidSchiWorkerThread+0x9f
ffffd58c`f1500c10 fffff802`4c9fe2e8 : ffffdc00`d4548180 ffffbb0a`31632080 fffff802`4c8f5360 00730065`00630072 : nt!PspSystemThreadStartup+0x55
ffffd58c`f1500c60 00000000`00000000 : ffffd58c`f1501000 ffffd58c`f14fb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: atikmpag+cc54
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}
Followup: MachineOwner
---------[/CODE]
[CODE title="Minidump dosyası 2"]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: fffff80051cfb320, 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: 4421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 49259
Key : Analysis.Init.CPU.mSec
Value: 296
Key : Analysis.Init.Elapsed.mSec
Value: 2722
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
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: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80051cfb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff80055874830 -- (.trap 0xfffff80055874830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff80051d25440
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80051310553 rsp=fffff800558749c0 rbp=0000000000aba000
r8=0000000000000002 r9=000000000000000f r10=000000000000000f
r11=fffff8004daf6180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po cy
nt!KiDeferredReadySingleThread+0x383:
fffff800`51310553 488b8658840000 mov rax,qword ptr [rsi+8458h] ds:00000000`00008458=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: dwm.exe
DPC_STACK_BASE: FFFFF80055874FB0
STACK_TEXT:
fffff800`5587bc88 fffff800`5141eeb6 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`51cfb320 : nt!KeBugCheckEx
fffff800`5587bc90 fffff800`5121c53d : 00000051`934e65da fffff800`4daf6180 00000000`00000246 00000000`00002072 : nt!KeAccumulateTicks+0x205b96
fffff800`5587bcf0 fffff800`5121cae1 : ffffe08e`2efc7000 00000000`00001357 fffff800`4daf6180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff800`5587bd40 fffff800`51216953 : fffff800`4daf6180 00000000`00000000 fffff800`51c315d0 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff800`5587be80 fffff800`5121f312 : fffff800`55874830 fffff800`558748b0 fffff800`55874800 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff800`5587bf30 fffff800`5127e795 : 00000000`4d737006 fffff800`51cf3a20 fffff800`51cf3ad0 ffff689d`b8c6d600 : nt!HalpTimerClockInterrupt+0xe2
fffff800`5587bf60 fffff800`513f873a : fffff800`558748b0 fffff800`51cf3a20 00000000`00000002 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`5587bfb0 fffff800`513f8ca7 : fffff800`4daf6180 fffff800`51d25440 fffff800`55874e70 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`55874830 fffff800`51310553 : 00000000`00000000 ffffe08e`2e73d1a0 00000000`00000000 fffff800`512c31d0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`558749c0 fffff800`5130a30d : 00000000`00000004 ffffe08e`2cad5000 00000000`00000000 fffff800`00000002 : nt!KiDeferredReadySingleThread+0x383
fffff800`55874bb0 fffff800`51309b3b : ffffe08e`319d9080 00000000`00000000 ffffe08e`319ef220 00000000`00000000 : nt!KiReadyThread+0x4d
fffff800`55874be0 fffff800`5130a77d : ffffe08e`2e351540 00000000`00000005 fffff800`4daf6180 fffff800`00000002 : nt!KiProcessThreadWaitList+0xcb
fffff800`55874c30 fffff800`5132279d : 00000000`00000000 00000000`00000000 00000000`0000002a 00000000`0000018f : nt!KiProcessExpiredTimerList+0x31d
fffff800`55874d20 fffff800`513fdcd5 : 00000000`00000000 fffff800`4daf6180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0x5dd
fffff800`55874fb0 fffff800`513fdac0 : 00000000`01000010 00000000`00000286 ffffe08e`3230e080 fffff800`513fd375 : nt!KxRetireDpcList+0x5
ffffda89`e73e2940 fffff800`513fd18e : ffffe08e`3230e080 00000000`00000001 ffffda89`00000000 00001f80`00000200 : nt!KiDispatchInterruptContinue
ffffda89`e73e2970 fffff800`51408571 : 000001c8`00000000 00000000`00000001 000001c8`77600ca0 ffffda89`e73e2b80 : nt!KiDpcInterrupt+0x2ee
ffffda89`e73e2b00 00007ffd`79f8e014 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceRepeat+0x3d
0000001f`6661f258 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`79f8e014
SYMBOL_NAME: nt!KeAccumulateTicks+205b96
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1023
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 205b96
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
---------
[/CODE]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffbb0a3469d460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80253ddcc54, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 113257
Key : Analysis.Init.CPU.mSec
Value: 874
Key : Analysis.Init.Elapsed.mSec
Value: 53733
Key : Analysis.Memory.CommitPeak.Mb
Value: 88
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: 116
BUGCHECK_P1: ffffbb0a3469d460
BUGCHECK_P2: fffff80253ddcc54
BUGCHECK_P3: 0
BUGCHECK_P4: d
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffbb0a3469d460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 000000000000000d
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd58c`f14ffeb8 fffff802`547d1cce : 00000000`00000116 ffffbb0a`3469d460 fffff802`53ddcc54 00000000`00000000 : nt!KeBugCheckEx
ffffd58c`f14ffec0 fffff802`547d1331 : fffff802`53ddcc54 ffffbb0a`3469d460 ffffd58c`f14fffc9 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffd58c`f14fff00 fffff802`54255ba6 : ffffbb0a`3469d460 00000000`0000526a ffffd58c`f14fffc9 00000000`0000526a : dxgkrnl!TdrIsRecoveryRequired+0x1b1
ffffd58c`f14fff30 fffff802`5427e2cf : ffffd58c`f1500110 ffffbb0a`3189a000 ffffd58c`f1500110 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x662
ffffd58c`f1500030 fffff802`5427d240 : ffffbb0a`316f76f0 ffffbb0a`3189a000 00000000`00000000 ffffbb0a`318a5190 : dxgmms1!VidSchWaitForCompletionEvent+0x29f
ffffd58c`f15000f0 fffff802`5427fd76 : ffffbb0a`316f76f0 00000000`00000000 ffffbb0a`2edfb100 fffff802`54254557 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0x120
ffffd58c`f15001d0 fffff802`5427f35e : 00000000`0000007a ffffd58c`f1500300 00000000`0000007a ffffd58c`f1500311 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x206
ffffd58c`f1500220 fffff802`5427c900 : ffffbb0a`00000000 fffff802`00000003 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x3de
ffffd58c`f1500360 fffff802`542791d7 : ffffbb0a`31933000 00000000`00000000 ffffbb0a`2e30b3d0 ffffd58c`f1500460 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x500
ffffd58c`f1500410 fffff802`54278d70 : ffff820a`c01e0001 00000000`00000000 ffffbb0a`316f8aa0 00000000`00001000 : dxgmms1!VIDMM_GLOBAL::MemoryTransferInternal+0x2c7
ffffd58c`f15005f0 fffff802`542795f5 : 00000000`00000000 00000000`00000008 ffffbb0a`2e30b3d0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::MemoryTransfer+0xb8
ffffd58c`f1500690 fffff802`54274740 : 00000000`00000002 00000000`00000008 00000000`00000003 00000000`00000007 : dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x1c5
ffffd58c`f1500790 fffff802`54282b79 : ffffbb0a`31933000 ffffbb0a`31933000 00000000`00000000 ffffbb0a`34765000 : dxgmms1!VIDMM_GLOBAL:
ageInAllocations+0xc0ffffd58c`f1500810 fffff802`54280936 : ffffbb0a`3189a000 ffff820a`c363fe90 ffffd58c`00000000 ffffbb0a`3467fa90 : dxgmms1!VIDMM_GLOBAL:
repareDmaBuffer+0x1809ffffd58c`f1500940 fffff802`54280060 : ffffbb0a`33d929b0 ffffbb0a`33d6b350 ffffbb0a`3189a000 ffffbb0a`3471a7d0 : dxgmms1!VidSchiSubmitRenderCommand+0x1f6
ffffd58c`f1500b90 fffff802`542a68bf : 00000000`00000080 ffffbb0a`3189a000 ffffbb0a`2c886040 00000000`00000000 : dxgmms1!VidSchiRun_PriorityTable+0xf0
ffffd58c`f1500bd0 fffff802`4c8f53b5 : ffffbb0a`31632080 fffff802`542a6820 ffffbb0a`3189a000 00078405`b59bbfff : dxgmms1!VidSchiWorkerThread+0x9f
ffffd58c`f1500c10 fffff802`4c9fe2e8 : ffffdc00`d4548180 ffffbb0a`31632080 fffff802`4c8f5360 00730065`00630072 : nt!PspSystemThreadStartup+0x55
ffffd58c`f1500c60 00000000`00000000 : ffffd58c`f1501000 ffffd58c`f14fb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: atikmpag+cc54
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}
Followup: MachineOwner
---------[/CODE]
[CODE title="Minidump dosyası 2"]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: fffff80051cfb320, 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: 4421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 49259
Key : Analysis.Init.CPU.mSec
Value: 296
Key : Analysis.Init.Elapsed.mSec
Value: 2722
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
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: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80051cfb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff80055874830 -- (.trap 0xfffff80055874830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff80051d25440
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80051310553 rsp=fffff800558749c0 rbp=0000000000aba000
r8=0000000000000002 r9=000000000000000f r10=000000000000000f
r11=fffff8004daf6180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po cy
nt!KiDeferredReadySingleThread+0x383:
fffff800`51310553 488b8658840000 mov rax,qword ptr [rsi+8458h] ds:00000000`00008458=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: dwm.exe
DPC_STACK_BASE: FFFFF80055874FB0
STACK_TEXT:
fffff800`5587bc88 fffff800`5141eeb6 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`51cfb320 : nt!KeBugCheckEx
fffff800`5587bc90 fffff800`5121c53d : 00000051`934e65da fffff800`4daf6180 00000000`00000246 00000000`00002072 : nt!KeAccumulateTicks+0x205b96
fffff800`5587bcf0 fffff800`5121cae1 : ffffe08e`2efc7000 00000000`00001357 fffff800`4daf6180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff800`5587bd40 fffff800`51216953 : fffff800`4daf6180 00000000`00000000 fffff800`51c315d0 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff800`5587be80 fffff800`5121f312 : fffff800`55874830 fffff800`558748b0 fffff800`55874800 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff800`5587bf30 fffff800`5127e795 : 00000000`4d737006 fffff800`51cf3a20 fffff800`51cf3ad0 ffff689d`b8c6d600 : nt!HalpTimerClockInterrupt+0xe2
fffff800`5587bf60 fffff800`513f873a : fffff800`558748b0 fffff800`51cf3a20 00000000`00000002 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`5587bfb0 fffff800`513f8ca7 : fffff800`4daf6180 fffff800`51d25440 fffff800`55874e70 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`55874830 fffff800`51310553 : 00000000`00000000 ffffe08e`2e73d1a0 00000000`00000000 fffff800`512c31d0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`558749c0 fffff800`5130a30d : 00000000`00000004 ffffe08e`2cad5000 00000000`00000000 fffff800`00000002 : nt!KiDeferredReadySingleThread+0x383
fffff800`55874bb0 fffff800`51309b3b : ffffe08e`319d9080 00000000`00000000 ffffe08e`319ef220 00000000`00000000 : nt!KiReadyThread+0x4d
fffff800`55874be0 fffff800`5130a77d : ffffe08e`2e351540 00000000`00000005 fffff800`4daf6180 fffff800`00000002 : nt!KiProcessThreadWaitList+0xcb
fffff800`55874c30 fffff800`5132279d : 00000000`00000000 00000000`00000000 00000000`0000002a 00000000`0000018f : nt!KiProcessExpiredTimerList+0x31d
fffff800`55874d20 fffff800`513fdcd5 : 00000000`00000000 fffff800`4daf6180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0x5dd
fffff800`55874fb0 fffff800`513fdac0 : 00000000`01000010 00000000`00000286 ffffe08e`3230e080 fffff800`513fd375 : nt!KxRetireDpcList+0x5
ffffda89`e73e2940 fffff800`513fd18e : ffffe08e`3230e080 00000000`00000001 ffffda89`00000000 00001f80`00000200 : nt!KiDispatchInterruptContinue
ffffda89`e73e2970 fffff800`51408571 : 000001c8`00000000 00000000`00000001 000001c8`77600ca0 ffffda89`e73e2b80 : nt!KiDpcInterrupt+0x2ee
ffffda89`e73e2b00 00007ffd`79f8e014 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceRepeat+0x3d
0000001f`6661f258 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`79f8e014
SYMBOL_NAME: nt!KeAccumulateTicks+205b96
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1023
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 205b96
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
---------
[/CODE]
KS
KS
şahin123456
Hectopat
- Katılım
- 10 Mayıs 2021
- Mesajlar
- 1.524
- Çözümler
- 1
Daha fazla
- Cinsiyet
- Erkek
@PanzerTR @Murat5038 nasıl ulaşırım peki? Onlar görür mü bu yazılanları ?DDU ile ekran kartı sürücüsünü silip yenisini yüklemeniz faydalı olabilir. Ve sistem dosyalarını kontrol etmek için şunu uygulamanızda aynı şekilde. VIDEO_TDR_FAILURE ve DPC_WATCHDOG_VIOLATION olarak gözüküyor hata adları. Tabii ben bu işlerde biraz acemiyim. Diğer hocalarımın da öncelikle incelemesi daha uygun olacaktır sanırım. @PanzerTR @Murat5038
[CODE title="Minidump Dosyası 1"]VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffbb0a3469d460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80253ddcc54, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 113257
Key : Analysis.Init.CPU.mSec
Value: 874
Key : Analysis.Init.Elapsed.mSec
Value: 53733
Key : Analysis.Memory.CommitPeak.Mb
Value: 88
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: 116
BUGCHECK_P1: ffffbb0a3469d460
BUGCHECK_P2: fffff80253ddcc54
BUGCHECK_P3: 0
BUGCHECK_P4: d
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffbb0a3469d460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 000000000000000d
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd58c`f14ffeb8 fffff802`547d1cce : 00000000`00000116 ffffbb0a`3469d460 fffff802`53ddcc54 00000000`00000000 : nt!KeBugCheckEx
ffffd58c`f14ffec0 fffff802`547d1331 : fffff802`53ddcc54 ffffbb0a`3469d460 ffffd58c`f14fffc9 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffd58c`f14fff00 fffff802`54255ba6 : ffffbb0a`3469d460 00000000`0000526a ffffd58c`f14fffc9 00000000`0000526a : dxgkrnl!TdrIsRecoveryRequired+0x1b1
ffffd58c`f14fff30 fffff802`5427e2cf : ffffd58c`f1500110 ffffbb0a`3189a000 ffffd58c`f1500110 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x662
ffffd58c`f1500030 fffff802`5427d240 : ffffbb0a`316f76f0 ffffbb0a`3189a000 00000000`00000000 ffffbb0a`318a5190 : dxgmms1!VidSchWaitForCompletionEvent+0x29f
ffffd58c`f15000f0 fffff802`5427fd76 : ffffbb0a`316f76f0 00000000`00000000 ffffbb0a`2edfb100 fffff802`54254557 : dxgmms1!VIDMM_DMA_POOL::WaitDmaBufferNotBusy+0x120
ffffd58c`f15001d0 fffff802`5427f35e : 00000000`0000007a ffffd58c`f1500300 00000000`0000007a ffffd58c`f1500311 : dxgmms1!VIDMM_DMA_POOL::AcquireBuffer+0x206
ffffd58c`f1500220 fffff802`5427c900 : ffffbb0a`00000000 fffff802`00000003 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::FlushPagingBufferInternal+0x3de
ffffd58c`f1500360 fffff802`542791d7 : ffffbb0a`31933000 00000000`00000000 ffffbb0a`2e30b3d0 ffffd58c`f1500460 : dxgmms1!VIDMM_GLOBAL::CompleteBuildPagingBufferIteration+0x500
ffffd58c`f1500410 fffff802`54278d70 : ffff820a`c01e0001 00000000`00000000 ffffbb0a`316f8aa0 00000000`00001000 : dxgmms1!VIDMM_GLOBAL::MemoryTransferInternal+0x2c7
ffffd58c`f15005f0 fffff802`542795f5 : 00000000`00000000 00000000`00000008 ffffbb0a`2e30b3d0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::MemoryTransfer+0xb8
ffffd58c`f1500690 fffff802`54274740 : 00000000`00000002 00000000`00000008 00000000`00000003 00000000`00000007 : dxgmms1!VIDMM_MEMORY_SEGMENT::CommitResource+0x1c5
ffffd58c`f1500790 fffff802`54282b79 : ffffbb0a`31933000 ffffbb0a`31933000 00000000`00000000 ffffbb0a`34765000 : dxgmms1!VIDMM_GLOBAL:
ffffd58c`f1500810 fffff802`54280936 : ffffbb0a`3189a000 ffff820a`c363fe90 ffffd58c`00000000 ffffbb0a`3467fa90 : dxgmms1!VIDMM_GLOBAL:
ffffd58c`f1500940 fffff802`54280060 : ffffbb0a`33d929b0 ffffbb0a`33d6b350 ffffbb0a`3189a000 ffffbb0a`3471a7d0 : dxgmms1!VidSchiSubmitRenderCommand+0x1f6
ffffd58c`f1500b90 fffff802`542a68bf : 00000000`00000080 ffffbb0a`3189a000 ffffbb0a`2c886040 00000000`00000000 : dxgmms1!VidSchiRun_PriorityTable+0xf0
ffffd58c`f1500bd0 fffff802`4c8f53b5 : ffffbb0a`31632080 fffff802`542a6820 ffffbb0a`3189a000 00078405`b59bbfff : dxgmms1!VidSchiWorkerThread+0x9f
ffffd58c`f1500c10 fffff802`4c9fe2e8 : ffffdc00`d4548180 ffffbb0a`31632080 fffff802`4c8f5360 00730065`00630072 : nt!PspSystemThreadStartup+0x55
ffffd58c`f1500c60 00000000`00000000 : ffffd58c`f1501000 ffffd58c`f14fb000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: atikmpag+cc54
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e300aa8c-6915-3f37-7957-d2e4fc30a6fd}
Followup: MachineOwner
---------[/CODE]
[CODE title="Minidump dosyası 2"]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: fffff80051cfb320, 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: 4421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 49259
Key : Analysis.Init.CPU.mSec
Value: 296
Key : Analysis.Init.Elapsed.mSec
Value: 2722
Key : Analysis.Memory.CommitPeak.Mb
Value: 72
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: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff80051cfb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff80055874830 -- (.trap 0xfffff80055874830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff80051d25440
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80051310553 rsp=fffff800558749c0 rbp=0000000000aba000
r8=0000000000000002 r9=000000000000000f r10=000000000000000f
r11=fffff8004daf6180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po cy
nt!KiDeferredReadySingleThread+0x383:
fffff800`51310553 488b8658840000 mov rax,qword ptr [rsi+8458h] ds:00000000`00008458=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: dwm.exe
DPC_STACK_BASE: FFFFF80055874FB0
STACK_TEXT:
fffff800`5587bc88 fffff800`5141eeb6 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`51cfb320 : nt!KeBugCheckEx
fffff800`5587bc90 fffff800`5121c53d : 00000051`934e65da fffff800`4daf6180 00000000`00000246 00000000`00002072 : nt!KeAccumulateTicks+0x205b96
fffff800`5587bcf0 fffff800`5121cae1 : ffffe08e`2efc7000 00000000`00001357 fffff800`4daf6180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff800`5587bd40 fffff800`51216953 : fffff800`4daf6180 00000000`00000000 fffff800`51c315d0 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff800`5587be80 fffff800`5121f312 : fffff800`55874830 fffff800`558748b0 fffff800`55874800 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff800`5587bf30 fffff800`5127e795 : 00000000`4d737006 fffff800`51cf3a20 fffff800`51cf3ad0 ffff689d`b8c6d600 : nt!HalpTimerClockInterrupt+0xe2
fffff800`5587bf60 fffff800`513f873a : fffff800`558748b0 fffff800`51cf3a20 00000000`00000002 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`5587bfb0 fffff800`513f8ca7 : fffff800`4daf6180 fffff800`51d25440 fffff800`55874e70 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`55874830 fffff800`51310553 : 00000000`00000000 ffffe08e`2e73d1a0 00000000`00000000 fffff800`512c31d0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`558749c0 fffff800`5130a30d : 00000000`00000004 ffffe08e`2cad5000 00000000`00000000 fffff800`00000002 : nt!KiDeferredReadySingleThread+0x383
fffff800`55874bb0 fffff800`51309b3b : ffffe08e`319d9080 00000000`00000000 ffffe08e`319ef220 00000000`00000000 : nt!KiReadyThread+0x4d
fffff800`55874be0 fffff800`5130a77d : ffffe08e`2e351540 00000000`00000005 fffff800`4daf6180 fffff800`00000002 : nt!KiProcessThreadWaitList+0xcb
fffff800`55874c30 fffff800`5132279d : 00000000`00000000 00000000`00000000 00000000`0000002a 00000000`0000018f : nt!KiProcessExpiredTimerList+0x31d
fffff800`55874d20 fffff800`513fdcd5 : 00000000`00000000 fffff800`4daf6180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0x5dd
fffff800`55874fb0 fffff800`513fdac0 : 00000000`01000010 00000000`00000286 ffffe08e`3230e080 fffff800`513fd375 : nt!KxRetireDpcList+0x5
ffffda89`e73e2940 fffff800`513fd18e : ffffe08e`3230e080 00000000`00000001 ffffda89`00000000 00001f80`00000200 : nt!KiDispatchInterruptContinue
ffffda89`e73e2970 fffff800`51408571 : 000001c8`00000000 00000000`00000001 000001c8`77600ca0 ffffda89`e73e2b80 : nt!KiDpcInterrupt+0x2ee
ffffda89`e73e2b00 00007ffd`79f8e014 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceRepeat+0x3d
0000001f`6661f258 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`79f8e014
SYMBOL_NAME: nt!KeAccumulateTicks+205b96
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.1023
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 205b96
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
---------
[/CODE]
Son düzenleyen: Moderatör:
Bakıyorum hocam şimdi. Bu arada beni etiketlediğiniz için teşekkürler.
Memtest86 ile RAM testi yapın.
AMD'ye ait crash report service ait olan programları kaldırın.
sfc/scannow ve DISM komutlarını uygulayın.
Yeni hata olursa paylaşın.
KS
KS
şahin123456
Hectopat
- Katılım
- 10 Mayıs 2021
- Mesajlar
- 1.524
- Çözümler
- 1
Daha fazla
- Cinsiyet
- Erkek
Gokberk_DRY
Hectopat
Ekran kartı sürücünü DDU ile kaldır.
DISM ve SFC /scannow rehberini uygula.
Ve RAM'leri Memtest 86 ile test et.
www.technopat.net
www.technopat.net
www.technopat.net
DISM ve SFC /scannow rehberini uygula.
Ve RAM'leri Memtest 86 ile test et.
Rehber: DDU ile Sürücü Kaldırma Rehberi
Display Driver Uninstaller (DDU), zamanla bilgisayara takılan farklı monitörler, üst üste güncellenen sürücüler ve Windows güncellemeleri sonrası biriken kayıt defteri ve sürücü dosyalarını silerek temiz bir sürücü kurulumunun yolunu açan kullanışlı bir araçtır. Adım adım sürücü temizliği...
Rehber: DISM aracı nedir ve nasıl kullanılır?
Herkese iyi günler. Bu rehberde sizlere DISM komutunun ne işe yaradığını, ne tarz durumlarda kullanılacağını ve nasıl kullanılacağını göstereceğim. İlk önce DISM nedir onu öğrenelim. DISM aracı yani “Deployment Image Servicing and Management” aracı sistemde tıpkı SFC komutunun yaptığı işlev...
Memtest86 ile Bozuk RAM Testi
Bu rehberimizde Memtes86 ile RAM testi yaparak bozuk RAM modüllerini nasıl tespit edeceğinize bakıyoruz. Bilgisayarda karşılaşılan mavi ekran hataları
www.technopat.net
Benzer konular
- Çözüldü
Yeni konular
-
-
-
-
-
Yurt dışı iPhone 13 Pro Max'in ön kamerasını yetkili servis temizler mi?- Ali Bozkurtlar
- Mesaj: 2
-
-
-
-
-
-
-
-
-
RX 5700 XT GPU hotspot sıcaklığı aniden 110 dereceye çıkıyor- Furkan Fer
- Mesaj: 7
