Windows 11 "Kernel Power 41" hatası

Carlsberg

Kilopat
Katılım
5 Mart 2015
Mesajlar
3.328
Makaleler
9
Çözümler
12
RAM
G.SKILL TridentZ RGB 4x8 3600MHz CL18
SSD veya HDD modeli
Samsung 970 Plus
Ekran kartı
ASUS ROG Strix RTX 3060
Anakart
ASUS ROG Strix Z490-F
İşlemci
İntel 10700K
Bilgisayar random zamanlarda kendini resetliyor artık can sıkmaya başladı. Format atmayı, DDU ile güvenli modda grafik sürücüsünü silip yüklemeyi, ramlere memtest yapmayı, ram slot yerlerini değiştirmeyi ve daha bir çok şeyi denedim.

Kernel hatası için hata kodu şöyle;


- <Event xmlns="[B]http://schemas.microsoft.com/win/2004/08/events/event[/B]"> - <System> <Provider Name="[B]Microsoft-Windows-Kernel-Power[/B]" Guid="[B]{331c3b3a-2005-44c2-ac5e-77220c37d6b4}[/B]" /> <EventID>41</EventID> <Version>8</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="[B]2022-01-16T09:18:16.4084831Z[/B]" /> <EventRecordID>2577</EventRecordID> <Correlation /> <Execution ProcessID="[B]4[/B]" ThreadID="[B]8[/B]" /> <Channel>System</Channel> <Computer>EA</Computer> <Security UserID="[B]S-1-5-18[/B]" /> </System> - <EventData> <Data Name="[B]BugcheckCode[/B]">313</Data> <Data Name="[B]BugcheckParameter1[/B]">0x3</Data> <Data Name="[B]BugcheckParameter2[/B]">0xffff90007ceb7170</Data> <Data Name="[B]BugcheckParameter3[/B]">0xffff90007ceb70c8</Data> <Data Name="[B]BugcheckParameter4[/B]">0x0</Data> <Data Name="[B]SleepInProgress[/B]">0</Data> <Data Name="[B]PowerButtonTimestamp[/B]">0</Data> <Data Name="[B]BootAppStatus[/B]">0</Data> <Data Name="[B]Checkpoint[/B]">0</Data> <Data Name="[B]ConnectedStandbyInProgress[/B]">false</Data> <Data Name="[B]SystemSleepTransitionsToOn[/B]">0</Data> <Data Name="[B]CsEntryScenarioInstanceId[/B]">0</Data> <Data Name="[B]BugcheckInfoFromEFI[/B]">false</Data> <Data Name="[B]CheckpointStatus[/B]">0</Data> <Data Name="[B]CsEntryScenarioInstanceIdV2[/B]">0</Data> <Data Name="[B]LongPowerButtonPressDetected[/B]">false</Data> </EventData> </Event>

Dump dosyası detayları ise şu şekilde;

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Emir_\Desktop\011622-4875-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22000 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22000.1.amd64fre.co_release.210604-1628 Machine Name: Kernel base = 0xfffff803`15000000 PsLoadedModuleList = 0xfffff803`15c29640 Debug session time: Sun Jan 16 12:17:52.241 2022 (UTC + 3:00) System Uptime: 0 days 0:42:08.903 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................. Loading User Symbols Loading unloaded module list .......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`15415b00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9000`7ceb6e50=0000000000000139 14: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_SECURITY_CHECK_FAILURE (139) A kernel component has corrupted a critical data structure. The corruption could potentially allow a malicious user to gain control of this machine. Arguments: Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove). Arg2: ffff90007ceb7170, Address of the trap frame for the exception that caused the BugCheck Arg3: ffff90007ceb70c8, Address of the exception record for the exception that caused the BugCheck Arg4: 0000000000000000, Reserved Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for dxgmms2.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2999 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 71610 Key : Analysis.Init.CPU.mSec Value: 405 Key : Analysis.Init.Elapsed.mSec Value: 29009 Key : Analysis.Memory.CommitPeak.Mb Value: 123 Key : FailFast.Name Value: CORRUPT_LIST_ENTRY Key : FailFast.Type Value: 3 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 FILE_IN_CAB: 011622-4875-01.dmp BUGCHECK_CODE: 139 BUGCHECK_P1: 3 BUGCHECK_P2: ffff90007ceb7170 BUGCHECK_P3: ffff90007ceb70c8 BUGCHECK_P4: 0 TRAP_FRAME: ffff90007ceb7170 -- (.trap 0xffff90007ceb7170) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffc603ea7ae018 rbx=0000000000000000 rcx=0000000000000003 rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8032de077a9 rsp=ffff90007ceb7300 rbp=0000000000000cc0 r8=ffffc603ef7fbb98 r9=0000000000000070 r10=0000000000000000 r11=ffff90007ceb74a8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac po cy dxgmms2+0x77a9: fffff803`2de077a9 cd29 int 29h Resetting default scope EXCEPTION_RECORD: ffff90007ceb70c8 -- (.exr 0xffff90007ceb70c8) ExceptionAddress: fffff8032de077a9 (dxgmms2+0x00000000000077a9) ExceptionCode: c0000409 (Security check failure or stack buffer overrun) ExceptionFlags: 00000001 NumberParameters: 1 Parameter[0]: 0000000000000003 Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: BF2042.exe ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y n tabanl bir arabelle in ta t n alg lad . Bu ta ma, k t niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir. EXCEPTION_CODE_STR: c0000409 EXCEPTION_PARAMETER1: 0000000000000003 EXCEPTION_STR: 0xc0000409 STACK_TEXT: ffff9000`7ceb6e48 fffff803`154286a9 : 00000000`00000139 00000000`00000003 ffff9000`7ceb7170 ffff9000`7ceb70c8 : nt!KeBugCheckEx ffff9000`7ceb6e50 fffff803`15428af2 : fffff803`3093f7c8 ffffc603`dfc22000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 ffff9000`7ceb6f90 fffff803`15426dd2 : 00000000`00000000 ffffc603`e1c696c0 ffffc603`f11f5010 00000000`0294056b : nt!KiFastFailDispatch+0xb2 ffff9000`7ceb7170 fffff803`2de077a9 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffc603`e1c5b720 : nt!KiRaiseSecurityCheckFailure+0x312 ffff9000`7ceb7300 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffc603`e1c5b720 fffff803`19a7e020 : dxgmms2+0x77a9 SYMBOL_NAME: dxgmms2+77a9 MODULE_NAME: dxgmms2 IMAGE_NAME: dxgmms2.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 77a9 FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_dxgmms2!unknown_function OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {5700d7bc-3b8a-8710-5866-32d56930b2ac} Followup: MachineOwner ---------
 
Genellikle PSU kaynaklı oluyor. Bende de vardı, PSU değiştikten sonra düzeldi. OCCT testi ile PSU'nuzu zorlayın. 5-10 dakika içinde yine resetlenirse büyük ihtimalle PSU kaynaklıdır hocam.
 
Artı -1 Eksi
Genellikle PSU kaynaklı oluyor. Bende de vardı, PSU değiştikten sonra düzeldi. OCCT testi ile PSU'nuzu zorlayın. 5-10 dakika içinde yine resetlenirse büyük ihtimalle PSU kaynaklıdır hocam.
İlk aklıma gelen durumlardan biri olduğu için haftalar öncesinde denemiştim zaten ancak PSU bir süredir bende ve herhangi bir kusurunu görmedim.
Siz söyleyince yine de havada kalmasın kanıt bulunsun diye tekrar yaptım.

OCCT-20220116-140307-PowerSupply.png


Kısaca, sorun PSU değil ne yazık ki.
Sadece bir tane mi dump dosyası var? Mevcut ise diğerlerini de atabilir misiniz?
Sistemi henüz geçen gün tekrar formatladığımdan 2 adet mevcut. Diğer minidump içeriği ise şu şekilde;
(Yalnız, bu önceki. Güncel olan, en son aldığım minidump konunun ilk mesajındaki, onu da belirteyim.)

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Emir_\Desktop\010722-4703-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22000 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22000.1.amd64fre.co_release.210604-1628 Machine Name: Kernel base = 0xfffff801`52a00000 PsLoadedModuleList = 0xfffff801`53629750 Debug session time: Fri Jan 7 20:15:36.619 2022 (UTC + 3:00) System Uptime: 0 days 0:33:36.281 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................ Loading User Symbols Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`52e159c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`4fb6dde0=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: 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: fffff80153705330, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4359 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 92335 Key : Analysis.Init.CPU.mSec Value: 546 Key : Analysis.Init.Elapsed.mSec Value: 376026 Key : Analysis.Memory.CommitPeak.Mb Value: 137 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 FILE_IN_CAB: 010722-4703-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff80153705330 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff8014fb5d7a0 -- (.trap 0xfffff8014fb5d7a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000ff358ff rbx=0000000000000000 rcx=000000000004035d rdx=0000000000100d74 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8016cd4e420 rsp=fffff8014fb5d930 rbp=fffff8014fb5d9b0 r8=fffff8014fb5d978 r9=0000000000100d74 r10=ffffe58d98a6b2c0 r11=000000000000000c r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nvlddmkm+0x8e420: fffff801`6cd4e420 488b5c2430 mov rbx,qword ptr [rsp+30h] ss:0018:fffff801`4fb5d960=ffffe58d98a69000 Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff801`4fb6ddd8 fffff801`52cdb50f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`53705330 : nt!KeBugCheckEx fffff801`4fb6dde0 fffff801`52cdb121 : 000006fc`6a57b638 fffff801`00000500 00000000`00000002 fffff801`52cd68ae : nt!KeAccumulateTicks+0x20f fffff801`4fb6de50 fffff801`52cd930a : fffff801`4f908200 fffff801`4fb5d7a0 fffff801`4f908450 00000000`00000688 : nt!KiUpdateRunTime+0x61 fffff801`4fb6deb0 fffff801`52cd90f6 : fffff801`536f7c90 fffff801`536f7d40 ffff8281`00000000 fffff801`4fb6dfc0 : nt!KeClockInterruptNotify+0x11a fffff801`4fb6df40 fffff801`52c8d6a0 : 00000000`0000000c ffffd5e2`62024afe ffffe58d`98a69a10 fffff801`52e1736b : nt!HalpTimerClockIpiRoutine+0x16 fffff801`4fb6df70 fffff801`52e175ca : fffff801`4fb5d820 fffff801`536f7c90 000006fc`557b6e0e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa0 fffff801`4fb6dfb0 fffff801`52e17b97 : 00000000`00000020 ffffe58d`98a69000 ffffe58d`98a6a9c8 fffff801`6ce3e53f : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff801`4fb5d7a0 fffff801`6cd4e420 : 00000000`00100d74 00000000`00000020 ffffe58d`98a6c000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff801`4fb5d930 00000000`00100d74 : 00000000`00000020 ffffe58d`98a6c000 00000000`00000000 00000000`00100d74 : nvlddmkm+0x8e420 fffff801`4fb5d938 00000000`00000020 : ffffe58d`98a6c000 00000000`00000000 00000000`00100d74 fffff801`6ce3db95 : 0x100d74 fffff801`4fb5d940 ffffe58d`98a6c000 : 00000000`00000000 00000000`00100d74 fffff801`6ce3db95 ffffe58d`98a69000 : 0x20 fffff801`4fb5d948 00000000`00000000 : 00000000`00100d74 fffff801`6ce3db95 ffffe58d`98a69000 fffff801`4fb5d9b0 : 0xffffe58d`98a6c000 SYMBOL_NAME: nvlddmkm+8e420 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 8e420 FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86} Followup: MachineOwner ---------
 
İlk aklıma gelen durumlardan biri olduğu için haftalar öncesinde denemiştim zaten ancak PSU bir süredir bende ve herhangi bir kusurunu görmedim.
Siz söyleyince yine de havada kalmasın kanıt bulunsun diye tekrar yaptım.

Eki Görüntüle 1271726

Kısaca, sorun PSU değil ne yazık ki.

Sistemi henüz geçen gün tekrar formatladığımdan 2 adet mevcut. Diğer minidump içeriği ise şu şekilde;
(Yalnız, bu önceki. Güncel olan, en son aldığım minidump konunun ilk mesajındaki, onu da belirteyim.)

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Emir_\Desktop\010722-4703-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22000 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22000.1.amd64fre.co_release.210604-1628 Machine Name: Kernel base = 0xfffff801`52a00000 PsLoadedModuleList = 0xfffff801`53629750 Debug session time: Fri Jan 7 20:15:36.619 2022 (UTC + 3:00) System Uptime: 0 days 0:33:36.281 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................................ Loading User Symbols Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`52e159c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`4fb6dde0=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: 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: fffff80153705330, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4359 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 92335 Key : Analysis.Init.CPU.mSec Value: 546 Key : Analysis.Init.Elapsed.mSec Value: 376026 Key : Analysis.Memory.CommitPeak.Mb Value: 137 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 FILE_IN_CAB: 010722-4703-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff80153705330 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff8014fb5d7a0 -- (.trap 0xfffff8014fb5d7a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000ff358ff rbx=0000000000000000 rcx=000000000004035d rdx=0000000000100d74 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8016cd4e420 rsp=fffff8014fb5d930 rbp=fffff8014fb5d9b0 r8=fffff8014fb5d978 r9=0000000000100d74 r10=ffffe58d98a6b2c0 r11=000000000000000c r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nvlddmkm+0x8e420: fffff801`6cd4e420 488b5c2430 mov rbx,qword ptr [rsp+30h] ss:0018:fffff801`4fb5d960=ffffe58d98a69000 Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff801`4fb6ddd8 fffff801`52cdb50f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`53705330 : nt!KeBugCheckEx fffff801`4fb6dde0 fffff801`52cdb121 : 000006fc`6a57b638 fffff801`00000500 00000000`00000002 fffff801`52cd68ae : nt!KeAccumulateTicks+0x20f fffff801`4fb6de50 fffff801`52cd930a : fffff801`4f908200 fffff801`4fb5d7a0 fffff801`4f908450 00000000`00000688 : nt!KiUpdateRunTime+0x61 fffff801`4fb6deb0 fffff801`52cd90f6 : fffff801`536f7c90 fffff801`536f7d40 ffff8281`00000000 fffff801`4fb6dfc0 : nt!KeClockInterruptNotify+0x11a fffff801`4fb6df40 fffff801`52c8d6a0 : 00000000`0000000c ffffd5e2`62024afe ffffe58d`98a69a10 fffff801`52e1736b : nt!HalpTimerClockIpiRoutine+0x16 fffff801`4fb6df70 fffff801`52e175ca : fffff801`4fb5d820 fffff801`536f7c90 000006fc`557b6e0e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa0 fffff801`4fb6dfb0 fffff801`52e17b97 : 00000000`00000020 ffffe58d`98a69000 ffffe58d`98a6a9c8 fffff801`6ce3e53f : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff801`4fb5d7a0 fffff801`6cd4e420 : 00000000`00100d74 00000000`00000020 ffffe58d`98a6c000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff801`4fb5d930 00000000`00100d74 : 00000000`00000020 ffffe58d`98a6c000 00000000`00000000 00000000`00100d74 : nvlddmkm+0x8e420 fffff801`4fb5d938 00000000`00000020 : ffffe58d`98a6c000 00000000`00000000 00000000`00100d74 fffff801`6ce3db95 : 0x100d74 fffff801`4fb5d940 ffffe58d`98a6c000 : 00000000`00000000 00000000`00100d74 fffff801`6ce3db95 ffffe58d`98a69000 : 0x20 fffff801`4fb5d948 00000000`00000000 : 00000000`00100d74 fffff801`6ce3db95 ffffe58d`98a69000 fffff801`4fb5d9b0 : 0xffffe58d`98a6c000 SYMBOL_NAME: nvlddmkm+8e420 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 8e420 FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86} Followup: MachineOwner ---------
Hocam aynı dediğiniz sorun bende de vardı ve OCCT'de gram sorun çıkmadı. PSU garantiye gittiğinde değişim yapıldı (orada elektronik ölçümlerde tutarsızlıklar çıkmış). Yine de yollamanızı öneririm garantiniz var ise.
 
Sürücü sorunu olarak gördüm. Format sonrası ve DDU ile temizleme sonrası aynı sürücüyü mü yüklediniz?
Hayır, direkt ekran kartının Asus Destek sayfasından Windows 11 için tavsiye edilen 472.XX sürümünü yükleyip, GeForce Experience'ı güncellemedim.
Sitesinde tavsiye edilen driver da çözüm sağlamadı.
Sonrasında tekrar formatlayıp temiz olarak o driver'ı kurdum yine çözüm olmadı. Az önce tekrardan son sürüme güncelledim temiz Windows'ta bakalım.
Hocam aynı dediğiniz sorun bende de vardı ve OCCT'de gram sorun çıkmadı. PSU garantiye gittiğinde değişim yapıldı (orada elektronik ölçümlerde tutarsızlıklar çıkmış). Yine de yollamanızı öneririm garantiniz var ise.
Dediğim gibi bir süredir bende PSU, daha önce kullanırken böyle bir hata yoktu. Durduk yerde bozulacağını pek sanmıyorum. Ancak son çare olarak söylediğiniz aklımda.
Garantisi var olmasına da, PSU'nun garantiye gidip gelmesi minimum 3-4 hafta kayıp demek. Sorunun kesin PSU'dan kaynaklandığını bilsem zaten yaparım önemli değil ancak, eğer ki PSU'dan değil ise boşu boşuna uğraşmış, yorulmuş, 1 ay PC'siz kalmış ve hiçbir sonuç elde edememiş olacağım.
 
Hayır, direkt ekran kartının Asus Destek sayfasından Windows 11 için tavsiye edilen 472.XX sürümünü yükleyip, GeForce Experience'ı güncellemedim.
Sitesinde tavsiye edilen driver da çözüm sağlamadı.

Dediğim gibi bir süredir bende PSU, daha önce kullanırken böyle bir hata yoktu. Durduk yerde bozulacağını pek sanmıyorum. Ancak son çare olarak söylediğiniz aklımda.
Garantisi var olmasına da, PSU'nun garantiye gidip gelmesi minimum 3-4 hafta kayıp demek. Sorunun kesin PSU'dan kaynaklandığını bilsem zaten yaparım önemli değil ancak, eğer ki PSU'dan değil ise boşu boşuna uğraşmış, yorulmuş, 1 ay PC'siz kalmış ve hiçbir sonuç elde edememiş olacağım.
Siz bilirsiniz, ama benim bilgisayarım 6 aylıktı ve 3 hafta mecbur bekledim çünkü diğer denediğim hiçbir şeyden sonuç alamamıştım. Hatta aldığım firma olan Sinerji Bilgisayar parçaların hiçbirinde sorun olmadığını, yapılabilecek bütün testleri yaptıklarını söylemişlerdi. İkna edip PSU'yu özellikle kendim yollattım. Bilgisayar elime ulaşalı 5 gün oluyor. Şimdi düzeldi ve kafam rahat.
 
Siz bilirsiniz, ama benim bilgisayarım 6 aylıktı ve 3 hafta mecbur bekledim çünkü diğer denediğim hiçbir şeyden sonuç alamamıştım. Hatta aldığım firma olan Sinerji Bilgisayar parçaların hiçbirinde sorun olmadığını, yapılabilecek bütün testleri yaptıklarını söylemişlerdi. İkna edip PSU'yu özellikle kendim yollattım. Bilgisayar elime ulaşalı 5 gün oluyor. Şimdi düzeldi ve kafam rahat.
Teşekkürler, dediğim gibi son çare olarak artık aklımda. Bakacağım artık, yazılımsal müdahaleler ile çözülebilecek gibiyse o şekilde denemediğim şey kalmasın istiyorum.
 

Geri
Yukarı