Monster Turbo moda alınca mavi ekran veriyor

FurkannC dedi:

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...

www.technopat.net

Genişletmek için tıkla...

Yandex

Her şey bulunur

disk.yandex.com.tr

FurkannC dedi:

Minidump Dosyalarını Paylaşın

Minidump dosyaları, bilgisayarınız mavi ekran verdiğinde belleğin ufak bir dökümünü barındıran dosyalardır. Bunları analiz ederek mavi ekran hatalarının nedenini öğrenebiliriz. Minidump dosyaları C:\Windows\Minidump klasöründe bulunur ve DMP uzantılıdır. Bu dosyaları sizden istediğimizde...

www.technopat.net

Genişletmek için tıkla...

gud dedi:

Yandex

Her şey bulunur

disk.yandex.com.tr

Sorun ne bilgisayarımda?

Genişletmek için tıkla...

gud dedi:

Yine herhalde Monster kullanıcılar arasında tek benim karşılaştığım bir olay. Zaten düşük FPS ve ısınma sorunu var iken şimdi Turbo moda alınca mavi ekran veriyor Bunun çözümü nedir neden oluyor bu?

Genişletmek için tıkla...

gud dedi:

gud dedi:

@Yigit Efe Sirin @The G.O.A.T

Genişletmek için tıkla...

Genişletmek için tıkla...

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Minidump\120221-15578-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`36e00000 PsLoadedModuleList = 0xfffff801`37a2a2d0
Debug session time: Thu Dec 2 21:30:53.820 2021 (UTC + 3:00)
System Uptime: 0 days 1:30:32.750
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`371f72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`3c87ee20=0000000000000133
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: 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: fffff80137afb320, 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: 1796

 Key : Analysis.DebugAnalysisManager
 Value: Create

 Key : Analysis.Elapsed.mSec
 Value: 4321

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

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

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

FILE_IN_CAB: 120221-15578-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
 Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80137afb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: GCUService.exe

STACK_TEXT:
fffff801`3c87ee18 fffff801`3721f5fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff801`3c87ee20 fffff801`37016953 : 00000b66`8db7c2bb fffff801`33f41180 00000000`00000000 fffff801`33f41180 : nt!KeAccumulateTicks+0x20644a
fffff801`3c87ee80 fffff801`3701643a : fffff801`37af3980 fffff801`3c8774b0 fffff801`4e30d800 00000000`00005301 : nt!KeClockInterruptNotify+0x453
fffff801`3c87ef30 fffff801`370de055 : fffff801`37af3980 fffff801`3c87ef40 00000000`00000010 ffffef13`5c787a96 : nt!HalpTimerClockIpiRoutine+0x1a
fffff801`3c87ef60 fffff801`371f8d4a : fffff801`3c8774b0 fffff801`37af3980 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`3c87efb0 fffff801`371f92b7 : ffffde8a`99e810a8 fffff801`53ff97d8 00000000`00000020 ffffde8a`8c56a270 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`3c877430 fffff801`5408bf3b : ffffde8a`99cc7050 ffffde8a`02810000 ffffde8a`8cfe2f38 ffffde8a`94001d00 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`3c8775c0 ffffde8a`99cc7050 : ffffde8a`02810000 ffffde8a`8cfe2f38 ffffde8a`94001d00 00000000`00000010 : nvlddmkm+0x1fbf3b
fffff801`3c8775c8 ffffde8a`02810000 : ffffde8a`8cfe2f38 ffffde8a`94001d00 00000000`00000010 fffff801`5408c78a : 0xffffde8a`99cc7050
fffff801`3c8775d0 ffffde8a`8cfe2f38 : ffffde8a`94001d00 00000000`00000010 fffff801`5408c78a 00000000`00000010 : 0xffffde8a`02810000
fffff801`3c8775d8 ffffde8a`94001d00 : 00000000`00000010 fffff801`5408c78a 00000000`00000010 ffffde8a`99e97000 : 0xffffde8a`8cfe2f38
fffff801`3c8775e0 00000000`00000010 : fffff801`5408c78a 00000000`00000010 ffffde8a`99e97000 ffffde8a`80000000 : 0xffffde8a`94001d00
fffff801`3c8775e8 fffff801`5408c78a : 00000000`00000010 ffffde8a`99e97000 ffffde8a`80000000 ffffde8a`99e82b38 : 0x10
fffff801`3c8775f0 00000000`00000010 : ffffde8a`99e97000 ffffde8a`80000000 ffffde8a`99e82b38 00000000`00000000 : nvlddmkm+0x1fc78a
fffff801`3c8775f8 ffffde8a`99e97000 : ffffde8a`80000000 ffffde8a`99e82b38 00000000`00000000 fffff801`541fddd0 : 0x10
fffff801`3c877600 ffffde8a`80000000 : ffffde8a`99e82b38 00000000`00000000 fffff801`541fddd0 00000000`80000000 : 0xffffde8a`99e97000
fffff801`3c877608 ffffde8a`99e82b38 : 00000000`00000000 fffff801`541fddd0 00000000`80000000 ffffde8a`99e97000 : 0xffffde8a`80000000
fffff801`3c877610 00000000`00000000 : fffff801`541fddd0 00000000`80000000 ffffde8a`99e97000 00000000`00000002 : 0xffffde8a`99e82b38

SYMBOL_NAME: nvlddmkm+1fbf3b

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1fbf3b

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff801`53e90000 fffff801`5648b000 nvlddmkm T (no symbols)
 Loaded symbol image file: nvlddmkm.sys
 Image path: nvlddmkm.sys
 Image name: nvlddmkm.sys
 Browse all global symbols functions data
 Timestamp: Wed Apr 21 11:17:58 2021 (607FDFB6)
 CheckSum: 0256AFE5
 ImageSize: 025FB000
 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 Information from resource tables:

Yigit Efe Sirin dedi:

Aldığın tüm mavi ekranlar nvlddmkm kısaca ekran kartı sürücüsü ile alakalı bir mavi ekran yaşamışsın, sorun tamamen sürücü ile alakalı olmayabilir RAM'e overclock yaptıysanız bu sorunu yaşayabilirsin, sürücüyü güncellemeyi deneyin sorun çözülmezse birkaç bir şey daha deneyebiliriz. Sistem özellikleriniz nedir?

Kod:Panoya kopyala

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64.
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Minidump\120221-15578-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available.

************* Path validation summary **************
Response Time (ms) Location.
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64.
Product: WinNt, suite: TerminalServer SingleUserTS.
Machine Name:
Kernel base = 0xfffff801`36e00000 PsLoadedModuleList = 0xfffff801`37a2a2d0
Debug session time: Thu Dec 2 21:30:53.820 2021 (UTC + 3:00)
System Uptime: 0 days 1:30:32.750
Loading Kernel Symbols.
...............................................................
................................................................
................................................................
..............................................
Loading User Symbols.
Loading unloaded module list.
.................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`371f72a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`3c87ee20=0000000000000133
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: 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: fffff80137afb320, 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: 1796.

 Key : Analysis.DebugAnalysisManager
 Value: Create.

 Key : Analysis.Elapsed.mSec
 Value: 4321.

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

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

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

FILE_IN_CAB: 120221-15578-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8.
 Kernel Generated Triage Dump.

BUGCHECK_CODE: 133.

BUGCHECK_P1: 0

BUGCHECK_P2: 501.

BUGCHECK_P3: 500.

BUGCHECK_P4: fffff80137afb320.

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: GCUService.exe

STACK_TEXT:
fffff801`3c87ee18 fffff801`3721f5fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff801`3c87ee20 fffff801`37016953 : 00000b66`8db7c2bb fffff801`33f41180 00000000`00000000 fffff801`33f41180 : nt!KeAccumulateTicks+0x20644a
fffff801`3c87ee80 fffff801`3701643a : fffff801`37af3980 fffff801`3c8774b0 fffff801`4e30d800 00000000`00005301 : nt!KeClockInterruptNotify+0x453
fffff801`3c87ef30 fffff801`370de055 : fffff801`37af3980 fffff801`3c87ef40 00000000`00000010 ffffef13`5c787a96 : nt!HalpTimerClockIpiRoutine+0x1a
fffff801`3c87ef60 fffff801`371f8d4a : fffff801`3c8774b0 fffff801`37af3980 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff801`3c87efb0 fffff801`371f92b7 : ffffde8a`99e810a8 fffff801`53ff97d8 00000000`00000020 ffffde8a`8c56a270 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff801`3c877430 fffff801`5408bf3b : ffffde8a`99cc7050 ffffde8a`02810000 ffffde8a`8cfe2f38 ffffde8a`94001d00 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`3c8775c0 ffffde8a`99cc7050 : ffffde8a`02810000 ffffde8a`8cfe2f38 ffffde8a`94001d00 00000000`00000010 : nvlddmkm+0x1fbf3b
fffff801`3c8775c8 ffffde8a`02810000 : ffffde8a`8cfe2f38 ffffde8a`94001d00 00000000`00000010 fffff801`5408c78a : 0xffffde8a`99cc7050
fffff801`3c8775d0 ffffde8a`8cfe2f38 : ffffde8a`94001d00 00000000`00000010 fffff801`5408c78a 00000000`00000010 : 0xffffde8a`02810000
fffff801`3c8775d8 ffffde8a`94001d00 : 00000000`00000010 fffff801`5408c78a 00000000`00000010 ffffde8a`99e97000 : 0xffffde8a`8cfe2f38
fffff801`3c8775e0 00000000`00000010 : fffff801`5408c78a 00000000`00000010 ffffde8a`99e97000 ffffde8a`80000000 : 0xffffde8a`94001d00
fffff801`3c8775e8 fffff801`5408c78a : 00000000`00000010 ffffde8a`99e97000 ffffde8a`80000000 ffffde8a`99e82b38 : 0x10.
fffff801`3c8775f0 00000000`00000010 : ffffde8a`99e97000 ffffde8a`80000000 ffffde8a`99e82b38 00000000`00000000 : nvlddmkm+0x1fc78a
fffff801`3c8775f8 ffffde8a`99e97000 : ffffde8a`80000000 ffffde8a`99e82b38 00000000`00000000 fffff801`541fddd0 : 0x10.
fffff801`3c877600 ffffde8a`80000000 : ffffde8a`99e82b38 00000000`00000000 fffff801`541fddd0 00000000`80000000 : 0xffffde8a`99e97000
fffff801`3c877608 ffffde8a`99e82b38 : 00000000`00000000 fffff801`541fddd0 00000000`80000000 ffffde8a`99e97000 : 0xffffde8a`80000000
fffff801`3c877610 00000000`00000000 : fffff801`541fddd0 00000000`80000000 ffffde8a`99e97000 00000000`00000002 : 0xffffde8a`99e82b38

SYMBOL_NAME: nvlddmkm+1fbf3b

MODULE_NAME: nvlddmkm.

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb.

BUCKET_ID_FUNC_OFFSET: 1fbf3b.

FAILURE_BUCKET_ID: 0x133_DPC_nvlddmkm!unknown_function

OSPLATFORM_TYPE: x64.

OSNAME: Windows 10.

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

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

0: kd> lmvm nvlddmkm.
Browse full module list.
start end module name.
fffff801`53e90000 fffff801`5648b000 nvlddmkm T (no symbols)
 Loaded symbol image file: nvlddmkm.sys
 Image path: nvlddmkm.sys
 Image name: nvlddmkm.sys
 Browse all global symbols functions data.
 Timestamp: Wed Apr 21 11:17:58 2021 (607FDFB6)
 CheckSum: 0256AFE5.
 ImageSize: 025FB000.
 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
 Information from resource tables:

Genişletmek için tıkla...