OCCT ile Power testi yapın.Sistem Özellikleri:
İşlemci: Intel i5-13400F (stok soğutucu)
Ekran kartı: Gigabyte RTX 4070 Windforce (12 GB)
RAM: Crucial DDR5 5600 MHz Pro (2x16)
Anakart: ASUS TUF Z690 Plus.
PSU: Thermaltake TR2 S 750W.
Merhaba, bilgisayarımda Kernel Power 41 (63) hatası ile karşılaşıyorum. Windows 11 kullanırken bu hata daha fazlaydı, bu yüzden Windows 10’a geçiş yaptım ve şu an Windows 11’e göre daha az bu hatayla karşılaşıyorum. Güncel olarak bu hatayla yine de karşılaşıyorum. Yardımcı olursanız sevinirim.
Güncelleme:
Bu sabah karşılaştığım hatada durdurma kodu “Page Fault in Nonpaged Area” olarak gözüküyordu.
Eki Görüntüle 215303
@ST0RM Konuya geri dönüş yapın hocam.Güncelleme:
Bu sabah karşılaştığım hatada durdurma kodu “Page Fault in Nonpaged Area” olarak gözüküyordu.
Sistem Özellikleri:
İşlemci: Intel i5-13400F (stok soğutucu)
Ekran kartı: Gigabyte RTX 4070 Windforce (12 GB)
RAM: Crucial DDR5 5600 MHz Pro (2x16)
Anakart: ASUS TUF Z690 Plus.
PSU: Thermaltake TR2 S 750W.
Merhaba, bilgisayarımda Kernel Power 41 (63) hatası ile karşılaşıyorum. Windows 11 kullanırken bu hata daha fazlaydı bu yüzden Windows 10 geçiş yaptım ve şu an Windows 11'e göre daha az bu hatayla karşılaşıyorum. Güncel olarak bu hatayla yine de karşılaşıyorum. Yardımcı olursanız sevinirim.
Kaç dakika için yapmalıyım? 5 dakika için yaptığımda bir sorun yoktu.OCCT ile Power testi yapın.
Evet.Kernel Power 41 (63) hatası, güç kaynağı veya ekran kartı ile ilgili. "PAGE_FAULT_IN_NONPAGED_AREA" hatası, RAM ile ilgili.
"C:\Windows\Minidump" konumunda .dmp uzantılı dosya var mı?
@ST0RM Konuya geri dönüş yapın hocam.
C:\Windows\Minidump dizinine gidip buradaki dosyaları kopyalayın. Sonrasında ister doğrudan masaüstüne, ister masaüstündeki bir klasöre yapıştırın ve yapıştırdığınız dosyalara sağ tıklayıp "ZIP dosyasına sıkıştır" seçeneğini seçin.MediaFire@ST0RM
Mavi ekran hatası aldığınızda DMP uzantılı Minidump dosyaları oluşur. Bu mini bellek döküm dosyalarının analiziyle mavi ekran hatalarının sebebi genelde tespit edilebilir.
Dosyaları paylaşmak içinC:\Windows\Minidumpdizinine gidip buradaki dosyaları kopyalayın. Sonrasında ister doğrudan masaüstüne, ister masaüstündeki bir klasöre yapıştırın ve yapıştırdığınız dosyalara sağ tıklayıp "ZIP dosyasına sıkıştır" seçeneğini seçin.
Bu aşamadan sonra oluşan ZIP dosyasını güvenilir bir dosya paylaşım servisi aracılığıyla paylaşabilirsiniz. Birkaç popüler servis:
- Techolay
- Mesaj: 0
- Forum: Mavi Ekran Hata Analizi
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.015 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.063 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 46
Microsoft (R) Windows Debugger Version 10.0.29482.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Valerian\Desktop\123125-4343-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
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff802`60800000 PsLoadedModuleList = 0xfffff802`6142a290
Debug session time: Wed Dec 31 20:20:04.554 2025 (UTC + 3:00)
System Uptime: 0 days 0:34:02.168
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`60bf8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffde81`c2b34c90=0000000000000133
9: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* 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: fffff802614fb320, 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: 2203
Key : Analysis.Elapsed.mSec
Value: 10242
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 23
Key : Analysis.Init.CPU.mSec
Value: 953
Key : Analysis.Init.Elapsed.mSec
Value: 30739
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
Key : Analysis.Version.DbgEng
Value: 10.0.29482.1003
Key : Analysis.Version.Description
Value: 10.2509.29.03 amd64fre
Key : Analysis.Version.Ext
Value: 1.2509.29.3
Key : Bugcheck.Code.LegacyAPI
Value: 0x133
Key : Bugcheck.Code.TargetModel
Value: 0x133
Key : Failure.Bucket
Value: 0x133_ISR_nt!KeAccumulateTicks
Key : Failure.Hash
Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Key : Stack.Pointer
Value: ISR
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.System.BIOSRevision
Value: 45.5.0.0
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff802614fb320
BUGCHECK_P4: 0
FILE_IN_CAB: 123125-4343-01.dmp
FAULTING_THREAD: ffff800d0e90b040
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: fffffe0ca16e6e10 -- (.trap 0xfffffe0ca16e6e10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0004000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000192ec85f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80260a46a49 rsp=fffffe0ca16e6fa0 rbp=fffffe0ca16e72e0
r8=0000000000000000 r9=ffffee8000000000 r10=0000000000000004
r11=ffffee8000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiFlushSectionInternal+0x289:
fffff802`60a46a49 498b1c24 mov rbx,qword ptr [r12] ds:00000000`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXSCM: 1 (!blackboxscm)
BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffde81`c2b34c88 fffff802`60c59782 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`614fb320 : nt!KeBugCheckEx
ffffde81`c2b34c90 fffff802`60ad83ed : 000004a8`9598a5b8 ffffde81`c2b1b180 00000000`00000246 00000000`0001fe8a : nt!KeAccumulateTicks+0x1845b2
ffffde81`c2b34cf0 fffff802`60ad8991 : 00000000`0001e000 00000000`0001304e ffffde81`c2b1b180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffffde81`c2b34d40 fffff802`60ad2803 : ffffde81`c2b1b180 00000000`00000000 fffff802`614314c0 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffffde81`c2b34e80 fffff802`60adb1c2 : fffffe0c`a16e6e10 fffffe0c`a16e6e90 fffffe0c`a16e6e00 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffffde81`c2b34f30 fffff802`60a08a45 : 00000004`c15114f5 ffff800d`0013c8a0 ffff800d`0013c950 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
ffffde81`c2b34f60 fffff802`60bfaa4a : fffffe0c`a16e6e90 ffff800d`0013c8a0 ffff988c`3b993148 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffde81`c2b34fb0 fffff802`60bfafb7 : 00000086`4ed758c0 ffff800d`06fc51a0 ffff800d`0bce6010 ffff800d`1a8706e0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffe0c`a16e6e10 fffff802`60a46a49 : 00000000`00000000 00000000`00000000 fffffe0c`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffe0c`a16e6fa0 fffff802`60ae3d7d : fffffe0c`a16e72e0 fffffe0c`a16e7548 ffff800d`1a8706e0 00000000`00000000 : nt!MiFlushSectionInternal+0x289
fffffe0c`a16e7270 fffff802`60a5977e : 00000000`00000000 ffff800d`0e90b040 00000000`00000000 00000000`00000000 : nt!MmFlushSection+0x155
fffffe0c`a16e7320 fffff802`60a6d34f : ffff800d`1a83b5e8 00000000`00000000 ffff988c`00000000 00000000`00000000 : nt!CcFlushCachePriv+0x3fe
fffffe0c`a16e7470 fffff802`6296d435 : 00000000`00000005 00000000`00000000 00000000`00000000 ffff988c`52916170 : nt!CcCoherencyFlushAndPurgeCache+0x6f
fffffe0c`a16e74c0 fffff802`6296d14b : ffff988c`52916170 fffff802`628a81b0 ffff988c`52916001 fffffe0c`a16e7780 : Ntfs!NtfsCoherencyFlushAndPurgeCache+0x55
fffffe0c`a16e7500 fffff802`6288a5af : fffffe0c`a16e7780 ffff988c`52916170 00000000`00000000 ffff988c`52916010 : Ntfs!NtfsFlushUserStream+0xdf
fffffe0c`a16e7590 fffff802`628a84ec : fffffe0c`a16e7780 ffff800d`06fcd180 ffff988c`52916010 fffffe0c`a16e7704 : Ntfs!NtfsFlushVolumeFlushSingleFcb+0x56f
fffffe0c`a16e76d0 fffff802`60a52b65 : ffff800d`0e90b040 ffff800d`0e90b040 ffff800d`000df050 fffff802`00000000 : Ntfs!NtfsFlushVolumeMultiThreadFcbWalkerWorker+0x33c
fffffe0c`a16e7ab0 fffff802`60a71d25 : ffff800d`0e90b040 00000000`00000080 ffff800d`000ae240 002fe47f`bd9bbfff : nt!ExpWorkerThread+0x105
fffffe0c`a16e7b50 fffff802`60c00628 : ffffde81`c26e5180 ffff800d`0e90b040 fffff802`60a71cd0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
fffffe0c`a16e7ba0 00000000`00000000 : fffffe0c`a16e8000 fffffe0c`a16e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: nt!KeAccumulateTicks+1845b2
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.2006
STACK_COMMAND: .process /r /p 0xffff800d000ae240; .thread 0xffff800d0e90b040 ; kb
BUCKET_ID_FUNC_OFFSET: 1845b2
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
---------
Hayır, XMP kapalı.DPC_WATCHDOG_VIOLATION hatası alıyorsun. WinDBG analizi:
Kod:************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.015 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.063 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 46 Microsoft (R) Windows Debugger Version 10.0.29482.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Valerian\Desktop\123125-4343-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 Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff802`60800000 PsLoadedModuleList = 0xfffff802`6142a290 Debug session time: Wed Dec 31 20:20:04.554 2025 (UTC + 3:00) System Uptime: 0 days 0:34:02.168 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ . Loading User Symbols Loading unloaded module list .............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`60bf8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffde81`c2b34c90=0000000000000133 9: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ . Loading User Symbols Loading unloaded module list .............. ******************************************************************************* * * * 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: fffff802614fb320, 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: 2203 Key : Analysis.Elapsed.mSec Value: 10242 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 1 Key : Analysis.IO.Write.Mb Value: 23 Key : Analysis.Init.CPU.mSec Value: 953 Key : Analysis.Init.Elapsed.mSec Value: 30739 Key : Analysis.Memory.CommitPeak.Mb Value: 80 Key : Analysis.Version.DbgEng Value: 10.0.29482.1003 Key : Analysis.Version.Description Value: 10.2509.29.03 amd64fre Key : Analysis.Version.Ext Value: 1.2509.29.3 Key : Bugcheck.Code.LegacyAPI Value: 0x133 Key : Bugcheck.Code.TargetModel Value: 0x133 Key : Failure.Bucket Value: 0x133_ISR_nt!KeAccumulateTicks Key : Failure.Hash Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Key : Stack.Pointer Value: ISR Key : WER.OS.Branch Value: vb_release Key : WER.OS.Version Value: 10.0.19041.1 Key : WER.System.BIOSRevision Value: 45.5.0.0 BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff802614fb320 BUGCHECK_P4: 0 FILE_IN_CAB: 123125-4343-01.dmp FAULTING_THREAD: ffff800d0e90b040 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffffe0ca16e6e10 -- (.trap 0xfffffe0ca16e6e10) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0004000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=0000000192ec85f0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80260a46a49 rsp=fffffe0ca16e6fa0 rbp=fffffe0ca16e72e0 r8=0000000000000000 r9=ffffee8000000000 r10=0000000000000004 r11=ffffee8000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!MiFlushSectionInternal+0x289: fffff802`60a46a49 498b1c24 mov rbx,qword ptr [r12] ds:00000000`00000000=???????????????? Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXSCM: 1 (!blackboxscm) BLACKBOXWINLOGON: 1 (!blackboxwinlogon) CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffde81`c2b34c88 fffff802`60c59782 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`614fb320 : nt!KeBugCheckEx ffffde81`c2b34c90 fffff802`60ad83ed : 000004a8`9598a5b8 ffffde81`c2b1b180 00000000`00000246 00000000`0001fe8a : nt!KeAccumulateTicks+0x1845b2 ffffde81`c2b34cf0 fffff802`60ad8991 : 00000000`0001e000 00000000`0001304e ffffde81`c2b1b180 00000000`00000001 : nt!KiUpdateRunTime+0x5d ffffde81`c2b34d40 fffff802`60ad2803 : ffffde81`c2b1b180 00000000`00000000 fffff802`614314c0 00000000`00000000 : nt!KiUpdateTime+0x4a1 ffffde81`c2b34e80 fffff802`60adb1c2 : fffffe0c`a16e6e10 fffffe0c`a16e6e90 fffffe0c`a16e6e00 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3 ffffde81`c2b34f30 fffff802`60a08a45 : 00000004`c15114f5 ffff800d`0013c8a0 ffff800d`0013c950 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2 ffffde81`c2b34f60 fffff802`60bfaa4a : fffffe0c`a16e6e90 ffff800d`0013c8a0 ffff988c`3b993148 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffde81`c2b34fb0 fffff802`60bfafb7 : 00000086`4ed758c0 ffff800d`06fc51a0 ffff800d`0bce6010 ffff800d`1a8706e0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffffe0c`a16e6e10 fffff802`60a46a49 : 00000000`00000000 00000000`00000000 fffffe0c`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffffe0c`a16e6fa0 fffff802`60ae3d7d : fffffe0c`a16e72e0 fffffe0c`a16e7548 ffff800d`1a8706e0 00000000`00000000 : nt!MiFlushSectionInternal+0x289 fffffe0c`a16e7270 fffff802`60a5977e : 00000000`00000000 ffff800d`0e90b040 00000000`00000000 00000000`00000000 : nt!MmFlushSection+0x155 fffffe0c`a16e7320 fffff802`60a6d34f : ffff800d`1a83b5e8 00000000`00000000 ffff988c`00000000 00000000`00000000 : nt!CcFlushCachePriv+0x3fe fffffe0c`a16e7470 fffff802`6296d435 : 00000000`00000005 00000000`00000000 00000000`00000000 ffff988c`52916170 : nt!CcCoherencyFlushAndPurgeCache+0x6f fffffe0c`a16e74c0 fffff802`6296d14b : ffff988c`52916170 fffff802`628a81b0 ffff988c`52916001 fffffe0c`a16e7780 : Ntfs!NtfsCoherencyFlushAndPurgeCache+0x55 fffffe0c`a16e7500 fffff802`6288a5af : fffffe0c`a16e7780 ffff988c`52916170 00000000`00000000 ffff988c`52916010 : Ntfs!NtfsFlushUserStream+0xdf fffffe0c`a16e7590 fffff802`628a84ec : fffffe0c`a16e7780 ffff800d`06fcd180 ffff988c`52916010 fffffe0c`a16e7704 : Ntfs!NtfsFlushVolumeFlushSingleFcb+0x56f fffffe0c`a16e76d0 fffff802`60a52b65 : ffff800d`0e90b040 ffff800d`0e90b040 ffff800d`000df050 fffff802`00000000 : Ntfs!NtfsFlushVolumeMultiThreadFcbWalkerWorker+0x33c fffffe0c`a16e7ab0 fffff802`60a71d25 : ffff800d`0e90b040 00000000`00000080 ffff800d`000ae240 002fe47f`bd9bbfff : nt!ExpWorkerThread+0x105 fffffe0c`a16e7b50 fffff802`60c00628 : ffffde81`c26e5180 ffff800d`0e90b040 fffff802`60a71cd0 00000000`00000246 : nt!PspSystemThreadStartup+0x55 fffffe0c`a16e7ba0 00000000`00000000 : fffffe0c`a16e8000 fffffe0c`a16e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: nt!KeAccumulateTicks+1845b2 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.2006 STACK_COMMAND: .process /r /p 0xffff800d000ae240; .thread 0xffff800d0e90b040 ; kb BUCKET_ID_FUNC_OFFSET: 1845b2 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 ---------
XMP-EXPO açık mı?
Hata "ntkrnlmp.exe" kaynaklı. Ekran kartı sürücüsünü DDU ile kaldırıp yeniden yükle. Sorun devam ederse yeniden konu açıp etiketlersin. Son durumu haber edersin.
Hata "ntkrnlmp.exe" kaynaklı. Ekran kartı sürücüsünü DDU ile kaldırıp yeniden yükle. Sorun devam ederse yeniden konu açıp etiketlersin. Son durumu haber edersin.
@ST0RM hocam son durum nedir?
Hocam geri dönüş bekliyorum.
Merhaba, bugün internette video izlerken yine benzer bir durum oldu. Bu sefer yine mavi ekran aldım fakat hata kodu farklıydı. Hata kodu critical_process_died olarak verdi.Hata "ntkrnlmp.exe" kaynaklı. Ekran kartı sürücüsünü DDU ile kaldırıp yeniden yükle. Sorun devam ederse yeniden konu açıp etiketlersin. Son durumu haber edersin.
@ST0RM Hocam son durum nedir?
Hocam geri dönüş bekliyorum.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?