The PC appears to power down when under stress, kernel power at level 41.
The PC appears to power down when under stress, kernel power at level 41.
63) Niveau: Kritisk Nøgleord: (70368744177664),(2) Bruger: SYSTEM Computer: Draysh Beskrivelse: Systemet har genstartet uden først at lukke korrekt ned. Denne fejl kan skyldes, at systemet er holdt op med at svare, er gået ned, eller at strømmen forsvandt uventet. Hændelses-Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> <EventID>41</EventID> <Version>9</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2023-12-12T14:44:01.5012424Z" /> <EventRecordID>151068</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Draysh</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">80</Data> <Data Name="BugcheckParameter1">0xffffc004748288d0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0xfffff807669b26c9</Data> <Data Name="BugcheckParameter4">0x2</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> <Data Name="BugcheckInfoFromEFI">false</Data> <Data Name="CheckpointStatus">0</Data> <Data Name="CsEntryScenarioInstanceIdV2">0</Data> <Data Name="LongPowerButtonPressDetected">false</Data> <Data Name="LidReliability">false</Data> <Data Name="InputSuppressionState">0</Data> <Data Name="PowerButtonSuppressionState">0</Data> <Data Name="LidState">3</Data> </EventData> </Event> Minidump: 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffc004748288d0, memory referenced. Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE. bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the processor decided the fault was due to a corrupted PTE. bit 4 is set if the fault was due to attempted execute of a no-execute PTE. - ARM64: bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the fault was due to attempted execute of a no-execute PTE. Arg3: fffff807669b26c9, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Type Value: Read Key : Analysis.CPU.mSec Value: 2343 Key : Analysis.Elapsed.mSec Value: 6864 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: 421 Key : Analysis.Init.Elapsed.mSec Value: 3891 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : Bugcheck.Code.LegacyAPI Value: 0x50 Key : Failure.Bucket Value: AV_R_(null)_nt!RtlCompressBufferXpressLzStandard Key : Failure.Hash Value: {2eaf1604-dd87-7d64-b274-d3b552f8b4b3} Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: 50 BUGCHECK_P1: ffffc004748288d0 BUGCHECK_P2: 0 BUGCHECK_P3: fffff807669b26c9 BUGCHECK_P4: 2 FILE_IN_CAB: 121223-15593-01.dmp READ_ADDRESS: fffff8076731c468: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffc004748288d0 MM_INTERNAL_CODE: 2 BLACKBOXBSD: 1 ( !blackboxbsd ) BLACKBOXNTFS: 1 ( !blackboxntfs ) BLACKBOXPNP: 1 ( !blackboxpnp ) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: MemCompression TRAP_FRAME: ffffd189ab8bf7a0 -- (.trap 0xffffd189ab8bf7a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000002da rbx=0000000000000000 rcx=0000000000000041 rdx=ffffc00425303230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff807669b26c9 rsp=ffffd189ab8bf930 rbp=ffffc00425b286c5 r8=ffffc004748288d0 r9=ffffc00425312f29 r10=ffffc00425b286c5 r11=ffffc00425312f4f r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe nc nt!RtlCompressBufferXpressLzStandard+0x139: fffff807`669b26c9 413808 cmp byte ptr [r8],cl ds:ffffc004`748288d0=?? Resetting default scope STACK_TEXT: ffffd189`ab8bf578 fffff807`66a8152f : 00000000`00000050 ffffc004`748288d0 00000000`00000000 ffffd189`ab8bf7a0 : nt!KeBugCheckEx ffffd189`ab8bf580 fffff807`66853cac : ffffd189`ab8bf978 00000000`00000000 ffffd189`ab8bf739 00000000`00000000 : nt!MiSystemFault+0x23079f ffffd189`ab8bf680 fffff807`66a39529 : 00000000`0000000a fffff807`66bb13a9 ffffc004`25312f29 ffffc004`1f1b5000 : nt!MmAccessFault+0x29c ffffd189`ab8bf7a0 fffff807`669b26c9 : ffffd189`ab8bf958 00000000`00000000 00000000`00000000 00000008`00000003 : nt!KiPageFault+0x369 ffffd189`ab8bf930 fffff807`669b2581 : ffffc004`25312f29 00000000`00000000 ffffc004`25b28070 ffffc004`25311f4f : nt!RtlCompressBufferXpressLzStandard+0x139 ffffd189`ab8bf9e0 fffff807`6697532f : ffffc004`083e5570 fffff807`6687d05a ffffc004`255f9000 ffffc004`2511e930 : nt!RtlCompressBufferXpressLz+0x61 ffffd189`ab8bfa40 fffff807`66bacf8e : ffffc004`083e5500 00000000`255f9070 ffffc004`255f9028 fffff807`66bad163 : nt!RtlCompressBuffer+0x6f ffffd189`ab8bfaa0 fffff807`66aee69b : ffffc004`083e5500 ffffc004`083e5010 ffffc004`083e5500 ffffc004`1bdbd1c0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxProcessEntry+0x92 ffffd189`ab8bfb30 fffff807`669089b7 : ffffffff`fd050f80 ffffc004`20243080 fffff807`669e6ee0 ffffc004`25303000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxWorkerThread+0x1077bb ffffd189`ab8bfbb0 fffff807`66a2d854 : ffff9800`76e51180 ffffc004`20243080 fffff807`66908960 00000000`00000246 : nt!PspSystemThreadStartup+0x57 ffffd189`ab8bfc00 00000000`00000000 : ffffd189`ab8c0000 ffffd189`ab8b9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!RtlCompressBufferXpressLzStandard+139 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.1020 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 139 FAILURE_BUCKET_ID: AV_R_(null)_nt!RtlCompressBufferXpressLzStandard OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {2eaf1604-dd87-7d64-b274-d3b552f8b4b3} Followup: MachineOwner ---------
FreeThroatHugz
09-12-2025, 05:12 PM #11I will try running the test again and see if it happens. For now here are all the entries and dumps i could find. Error from prime95: [Tue Dec 12 15:43:31 2023] FATAL ERROR: Rounding was 0.5, expected less than 0.4 Entry: Lognavn: System Kilde: Microsoft-Windows-Kernel-Power Dato: 12-12-2023 15:44:01 Hændelses-id: 41 Opgavekategori63) Niveau: Kritisk Nøgleord: (70368744177664),(2) Bruger: SYSTEM Computer: Draysh Beskrivelse: Systemet har genstartet uden først at lukke korrekt ned. Denne fejl kan skyldes, at systemet er holdt op med at svare, er gået ned, eller at strømmen forsvandt uventet. Hændelses-Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> <EventID>41</EventID> <Version>9</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2023-12-12T14:44:01.5012424Z" /> <EventRecordID>151068</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>Draysh</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">80</Data> <Data Name="BugcheckParameter1">0xffffc004748288d0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0xfffff807669b26c9</Data> <Data Name="BugcheckParameter4">0x2</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> <Data Name="BugcheckInfoFromEFI">false</Data> <Data Name="CheckpointStatus">0</Data> <Data Name="CsEntryScenarioInstanceIdV2">0</Data> <Data Name="LongPowerButtonPressDetected">false</Data> <Data Name="LidReliability">false</Data> <Data Name="InputSuppressionState">0</Data> <Data Name="PowerButtonSuppressionState">0</Data> <Data Name="LidState">3</Data> </EventData> </Event> Minidump: 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. This cannot be protected by try-except. Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: ffffc004748288d0, memory referenced. Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE. bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the processor decided the fault was due to a corrupted PTE. bit 4 is set if the fault was due to attempted execute of a no-execute PTE. - ARM64: bit 1 is set if the fault was due to a write, clear if a read. bit 3 is set if the fault was due to attempted execute of a no-execute PTE. Arg3: fffff807669b26c9, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Type Value: Read Key : Analysis.CPU.mSec Value: 2343 Key : Analysis.Elapsed.mSec Value: 6864 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: 421 Key : Analysis.Init.Elapsed.mSec Value: 3891 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : Bugcheck.Code.LegacyAPI Value: 0x50 Key : Failure.Bucket Value: AV_R_(null)_nt!RtlCompressBufferXpressLzStandard Key : Failure.Hash Value: {2eaf1604-dd87-7d64-b274-d3b552f8b4b3} Key : WER.OS.Branch Value: ni_release Key : WER.OS.Version Value: 10.0.22621.1 BUGCHECK_CODE: 50 BUGCHECK_P1: ffffc004748288d0 BUGCHECK_P2: 0 BUGCHECK_P3: fffff807669b26c9 BUGCHECK_P4: 2 FILE_IN_CAB: 121223-15593-01.dmp READ_ADDRESS: fffff8076731c468: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse ffffc004748288d0 MM_INTERNAL_CODE: 2 BLACKBOXBSD: 1 ( !blackboxbsd ) BLACKBOXNTFS: 1 ( !blackboxntfs ) BLACKBOXPNP: 1 ( !blackboxpnp ) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: MemCompression TRAP_FRAME: ffffd189ab8bf7a0 -- (.trap 0xffffd189ab8bf7a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000002da rbx=0000000000000000 rcx=0000000000000041 rdx=ffffc00425303230 rsi=0000000000000000 rdi=0000000000000000 rip=fffff807669b26c9 rsp=ffffd189ab8bf930 rbp=ffffc00425b286c5 r8=ffffc004748288d0 r9=ffffc00425312f29 r10=ffffc00425b286c5 r11=ffffc00425312f4f r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe nc nt!RtlCompressBufferXpressLzStandard+0x139: fffff807`669b26c9 413808 cmp byte ptr [r8],cl ds:ffffc004`748288d0=?? Resetting default scope STACK_TEXT: ffffd189`ab8bf578 fffff807`66a8152f : 00000000`00000050 ffffc004`748288d0 00000000`00000000 ffffd189`ab8bf7a0 : nt!KeBugCheckEx ffffd189`ab8bf580 fffff807`66853cac : ffffd189`ab8bf978 00000000`00000000 ffffd189`ab8bf739 00000000`00000000 : nt!MiSystemFault+0x23079f ffffd189`ab8bf680 fffff807`66a39529 : 00000000`0000000a fffff807`66bb13a9 ffffc004`25312f29 ffffc004`1f1b5000 : nt!MmAccessFault+0x29c ffffd189`ab8bf7a0 fffff807`669b26c9 : ffffd189`ab8bf958 00000000`00000000 00000000`00000000 00000008`00000003 : nt!KiPageFault+0x369 ffffd189`ab8bf930 fffff807`669b2581 : ffffc004`25312f29 00000000`00000000 ffffc004`25b28070 ffffc004`25311f4f : nt!RtlCompressBufferXpressLzStandard+0x139 ffffd189`ab8bf9e0 fffff807`6697532f : ffffc004`083e5570 fffff807`6687d05a ffffc004`255f9000 ffffc004`2511e930 : nt!RtlCompressBufferXpressLz+0x61 ffffd189`ab8bfa40 fffff807`66bacf8e : ffffc004`083e5500 00000000`255f9070 ffffc004`255f9028 fffff807`66bad163 : nt!RtlCompressBuffer+0x6f ffffd189`ab8bfaa0 fffff807`66aee69b : ffffc004`083e5500 ffffc004`083e5010 ffffc004`083e5500 ffffc004`1bdbd1c0 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxProcessEntry+0x92 ffffd189`ab8bfb30 fffff807`669089b7 : ffffffff`fd050f80 ffffc004`20243080 fffff807`669e6ee0 ffffc004`25303000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxWorkerThread+0x1077bb ffffd189`ab8bfbb0 fffff807`66a2d854 : ffff9800`76e51180 ffffc004`20243080 fffff807`66908960 00000000`00000246 : nt!PspSystemThreadStartup+0x57 ffffd189`ab8bfc00 00000000`00000000 : ffffd189`ab8c0000 ffffd189`ab8b9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!RtlCompressBufferXpressLzStandard+139 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.1020 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 139 FAILURE_BUCKET_ID: AV_R_(null)_nt!RtlCompressBufferXpressLzStandard OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {2eaf1604-dd87-7d64-b274-d3b552f8b4b3} Followup: MachineOwner ---------
I just executed the default test and noticed a "hardware failure" on 3 cores, while the remaining 3 cores completed without issues. Results show multiple fatal errors related to rounding and FFT size, referencing stress.txt for details. This time the self-test for 960K succeeded! How would you proceed with the memory test?
Cableperson
09-21-2025, 10:20 PM #15For the memory test, the easiest way is to type "Windows Memory Diagnostic" in the search bar and run it. Have you tried adjusting AMD Precision Boost Overdrive to lower or increase your CPU voltage? That often causes the issue if there’s an unstable overclock.
killer69990
09-22-2025, 12:01 AM #16Sure, try reverting everything to the default configuration. If it still works without problems, you're good to go.
martims098
09-22-2025, 05:52 PM #17I adjusted it to the standard setting, yes. I checked your Prime95 logs and it looks like the issue is user-related.
WoobzyWoobz
10-10-2025, 07:59 AM #19If the OC is removed, or not, you might attempt using the core at 0.05v+ and re-running the test to check for stability. This approach helps maintain performance.