Merhabalar ısı sorunu yaşıyor olabilir misiniz? İlk fotoğraftaki hata ısıdan veya işlemciden dolayı olabilir. Ek olarak dump dosyası veya cihaz bilgisini eksiksiz olarak paylaşın.
23.06.2025 tarihinde yapılan güncel rehbere aşağıdaki linkten erişebilirsiniz: https://www.technopat.net/sosyal/konu/minidump-nedir-nasil-paylasilir.3817531/ 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...
www.technopat.net
Isı sorunu yaşamıyorum. Ekran kartımın ve işlemcimin ısısı çok düşük seviyelerde. Sıvı soğutucum var. dump dosyasını da atıyorum hocam.
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Bahadır\Desktop\Yeni klasör\022023-3937-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 (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`04a00000 PsLoadedModuleList = 0xfffff805`0562a210
Debug session time: Mon Feb 20 00:40:43.421 2023 (UTC + 3:00)
System Uptime: 0 days 0:00:31.047
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`04dfa090 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd401`d45f9c90=0000000000000101
8: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd401d4540180, The PRCB address of the hung processor.
Arg4: 0000000000000007, The index of the hung processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2281
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 5299
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 390
Key : Analysis.Init.Elapsed.mSec
Value: 4481
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
Key : Bugcheck.Code.DumpHeader
Value: 0x101
Key : Bugcheck.Code.Register
Value: 0x101
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
FILE_IN_CAB: 022023-3937-01.dmp
BUGCHECK_CODE: 101
BUGCHECK_P1: 10
BUGCHECK_P2: 0
BUGCHECK_P3: ffffd401d4540180
BUGCHECK_P4: 7
FAULTING_PROCESSOR: 7
PROCESS_NAME: opera.exe
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
STACK_TEXT:
ffffd401`d45f9c88 fffff805`04e94ae4 : 00000000`00000101 00000000`00000010 00000000`00000000 ffffd401`d4540180 : nt!KeBugCheckEx
ffffd401`d45f9c90 fffff805`04d2ddad : 00000000`00000000 ffffd401`d4600180 00000000`00000246 00000000`000007c3 : nt!KeAccumulateTicks+0x169f54
ffffd401`d45f9cf0 fffff805`04d2e351 : 00000000`00000500 00000000`000004a0 ffffd401`d4600180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffd401`d45f9d40 fffff805`04d281c3 : ffffd401`d4600180 00000000`00000000 fffff805`05631540 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffd401`d45f9e80 fffff805`04d30b42 : ffffe500`b2afe1b0 ffffe500`b2afe230 ffffe500`b2afe200 00000000`0000000c : nt!KeClockInterruptNotify+0x2e3
ffffd401`d45f9f30 fffff805`04c73e05 : 00000000`1298371a ffffc387`6dad7c40 ffffc387`6dad7cf0 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffd401`d45f9f60 fffff805`04dfc02a : ffffe500`b2afe230 ffffc387`6dad7c40 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd401`d45f9fb0 fffff805`04dfc7f7 : 00000000`0da0f5ea ffffd401`d40f9088 ffffe500`b2afe2e1 fff28059`57f1c804 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffe500`b2afe1b0 fffff805`04d11fc0 : 00000000`00000000 00000000`00000001 00000000`00000002 ffffe500`b2afe399 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffe500`b2afe340 fffff805`04d11dd8 : ffffeb00`00000000 ffffe500`b2afe600 ffffc387`7f12b700 ffffeb00`00000000 : nt!KeFlushMultipleRangeTb+0x160
ffffe500`b2afe3e0 fffff805`04d19ab3 : ffffc387`7f12b700 1a000001`a11fc867 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x88
ffffe500`b2afe410 fffff805`04cb64a0 : ffffe500`b2afe6c0 00000000`00000000 00000000`00000000 ffff85c2`c5f80018 : nt!MiTerminateWsleCluster+0x363
ffffe500`b2afe5c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDecommitPages+0x1200
SYMBOL_NAME: nt!KeAccumulateTicks+169f54
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2604
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 169f54
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}
Followup: MachineOwner
---------
