How can I continue tracking this data from LatencyMon?
How can I continue tracking this data from LatencyMon?
My system has been stuttering like crazy, so I started digging into it with LatencyMon.
I've made good progress reducing my numbers through a combination of windows reinstall, software updates, power tweaks, ditching my RAM overclock (it stable according to prime95 but major latency spikes went away when I went back to XMP II), and unplugging my front port with broken USB from the motherboard.
Good progress. Not great.
It's weirdly consistent, almost like there's a timeout in play. After30 seconds to a few minutes running, the "Highest measured interrupt to process latency" jumps to about 730 microseconds. 728, 731. Very close to 730.
LatencyMon stays green, but I'm on a tear. The microstutters have driven me crazy. I knew something was way wrong when 20-year old Half-Life was stuttering consistently. Spider-Man 2 performed better, actually, probably because it ran the CPU too much for it to park.
I think my current spike has something to do with my graphics drivers" dxgkrnl.sys is usually the worst offender in ISR and DPC execution time. nvlddmkm.sys also makes appearances.
Almost all of my ISRs are on CPU 0, even after running for a while. I tried the process affinity tool and just got some error message about wrong data type in the regkey.
I'm about to play HL2 again, see if this >1ms spike every few minutes is even something I want to worry about, but I would like to track this down and figure out what's actually happening, why it's so consistent.
I'm wondering if it represents a hardware problem. I've got my CPU running with the OC voltages, worst-case-scenario just to maintain stock clocks, basically. Two cores (including core 0) won't OC at all, 53x is the best I can do (vs. base 51x). Seems more like software, though, right?
Should I just move on, call this good enough? I feel like I have seen much better results.
Edit: HL2 still running bad, though my process latencies do not exceed 1ms during those frame drops.
Here's my stats
CPU: 13600k
Cooler: BeQuiet 280 AIO
Mobo: Asus z690-p (new microcode, which did tank performance, thermal throttling or limiting my ecores under load, unless I do worst-case SVID, ignore all limits (90c), LLC 4)
Ram: T-Force DDR5 6000MTs, 30-36-36-76 (slight voltage boost for stability in XMP I)
SSD: Samsung 990 Pro 1TB, also a WD Blue and P310 on M2_2/3
GPU: PNY 5070Ti
PSU: TOUGHPOWER GT 1000 Watt 80 Plus Gold ATX
Chassis: Lian Li 205 (some improvement after disconnecting broken front usb)
OS: Windows 11 v 10.0.26200
Monitor: LG32GP750
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:17:58 (h:mm
s) on all processors._________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-V92K8VD
OS version: Windows 11, 10.0, version 2009, build: 26200 (x64)
Hardware: System Product Name, ASUS
BIOS: 3811
CPU: GenuineIntel 13th Gen Intel® Core™ i5-13600KF
Logical processors: 14
Processor groups: 1
Processor group size: 14
RAM: 32581 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 350 MHz
Reported CPU speed (registry): 3494 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step
and AMD Cool N Quiet in the BIOS setup for more accurate results.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the
moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an
event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 728.80
Average measured interrupt to process latency (µs): 9.135067
Highest measured interrupt to DPC latency (µs): 717.0
Average measured interrupt to DPC latency (µs): 3.240217
_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 207.471666
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.081443
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.117777
ISR count (execution time <250 µs): 5110625
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it
is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 407.631654
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0.124009
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.179826
DPC count (execution time <250 µs): 5751647
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 2
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped
file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and
blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream
resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: firefox.exe
Total number of hard pagefaults 21657
Hard pagefault count of hardest hit process: 3110
Number of processes hit: 84
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 67.788690
CPU 0 ISR highest execution time (µs): 207.471666
CPU 0 ISR total execution time (s): 17.277123
CPU 0 ISR count: 5095556
CPU 0 DPC highest execution time (µs): 271.565255
CPU 0 DPC total execution time (s): 26.147398
CPU 0 DPC count: 5628316
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 15.001665
CPU 1 ISR highest execution time (µs): 159.017172
CPU 1 ISR total execution time (s): 0.508581
CPU 1 ISR count: 15068
CPU 1 DPC highest execution time (µs): 169.356611
CPU 1 DPC total execution time (s): 0.666666
CPU 1 DPC count: 58125
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 9.380641
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 407.631654
CPU 2 DPC total execution time (s): 0.060656
CPU 2 DPC count: 15173
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 9.37090
CPU 3 ISR highest execution time (µs): 34.586148
CPU 3 ISR total execution time (s): 0.000035
CPU 3 ISR count: 1
CPU 3 DPC highest execution time (µs): 104.124213
CPU 3 DPC total execution time (s): 0.059626
CPU 3 DPC count: 14758
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 9.729669
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 87.893532
CPU 4 DPC total execution time (s): 0.055155
CPU 4 DPC count: 11068
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 9.141767
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 102.014596
CPU 5 DPC total execution time (s): 0.050389
CPU 5 DPC count: 9455
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 7.003285
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 117.691185
CPU 6 DPC total execution time (s): 0.017577
CPU 6 DPC count: 2145
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 6.901803
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 166.289926
CPU 7 DPC total execution time (s): 0.014211
CPU 7 DPC count: 1927
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 6.846257
CPU 8 ISR highest execution time (µs): 0.0
CPU 8 ISR total execution time (s): 0.0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 167.200630
CPU 8 DPC total execution time (s): 0.011287
CPU 8 DPC count: 1367
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 6.931584
CPU 9 ISR highest execution time (µs): 0.0
CPU 9 ISR total execution time (s): 0.0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 136.637665
CPU 9 DPC total execution time (s): 0.012752
CPU 9 DPC count: 1418
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 6.882736
CPU 10 ISR highest execution time (µs): 0.0
CPU 10 ISR total execution time (s): 0.0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 116.024327
CPU 10 DPC total execution time (s): 0.012979
CPU 10 DPC count: 1552
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 6.826734
CPU 11 ISR highest execution time (µs): 0.0
CPU 11 ISR total execution time (s): 0.0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 94.202919
CPU 11 DPC total execution time (s): 0.010752
CPU 11 DPC count: 1198
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 6.905321
CPU 12 ISR highest execution time (µs): 0.0
CPU 12 ISR total execution time (s): 0.0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 134.059244
CPU 12 DPC total execution time (s): 0.019599
CPU 12 DPC count: 3514
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 6.921292
CPU 13 ISR highest execution time (µs): 0.0
CPU 13 ISR total execution time (s): 0.0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 108.524327
CPU 13 DPC total execution time (s): 0.016881
CPU 13 DPC count: 1633
_________________________________________________________________________________________________________
Bananabut12
11-24-2022, 07:03 PM #1Edit: AIDA64 showed me what I needed to know. Info in reply below.
My system has been stuttering like crazy, so I started digging into it with LatencyMon.
I've made good progress reducing my numbers through a combination of windows reinstall, software updates, power tweaks, ditching my RAM overclock (it stable according to prime95 but major latency spikes went away when I went back to XMP II), and unplugging my front port with broken USB from the motherboard.
Good progress. Not great.
It's weirdly consistent, almost like there's a timeout in play. After30 seconds to a few minutes running, the "Highest measured interrupt to process latency" jumps to about 730 microseconds. 728, 731. Very close to 730.
LatencyMon stays green, but I'm on a tear. The microstutters have driven me crazy. I knew something was way wrong when 20-year old Half-Life was stuttering consistently. Spider-Man 2 performed better, actually, probably because it ran the CPU too much for it to park.
I think my current spike has something to do with my graphics drivers" dxgkrnl.sys is usually the worst offender in ISR and DPC execution time. nvlddmkm.sys also makes appearances.
Almost all of my ISRs are on CPU 0, even after running for a while. I tried the process affinity tool and just got some error message about wrong data type in the regkey.
I'm about to play HL2 again, see if this >1ms spike every few minutes is even something I want to worry about, but I would like to track this down and figure out what's actually happening, why it's so consistent.
I'm wondering if it represents a hardware problem. I've got my CPU running with the OC voltages, worst-case-scenario just to maintain stock clocks, basically. Two cores (including core 0) won't OC at all, 53x is the best I can do (vs. base 51x). Seems more like software, though, right?
Should I just move on, call this good enough? I feel like I have seen much better results.
Edit: HL2 still running bad, though my process latencies do not exceed 1ms during those frame drops.
Here's my stats
CPU: 13600k
Cooler: BeQuiet 280 AIO
Mobo: Asus z690-p (new microcode, which did tank performance, thermal throttling or limiting my ecores under load, unless I do worst-case SVID, ignore all limits (90c), LLC 4)
Ram: T-Force DDR5 6000MTs, 30-36-36-76 (slight voltage boost for stability in XMP I)
SSD: Samsung 990 Pro 1TB, also a WD Blue and P310 on M2_2/3
GPU: PNY 5070Ti
PSU: TOUGHPOWER GT 1000 Watt 80 Plus Gold ATX
Chassis: Lian Li 205 (some improvement after disconnecting broken front usb)
OS: Windows 11 v 10.0.26200
Monitor: LG32GP750
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:17:58 (h:mms) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-V92K8VD
OS version: Windows 11, 10.0, version 2009, build: 26200 (x64)
Hardware: System Product Name, ASUS
BIOS: 3811
CPU: GenuineIntel 13th Gen Intel® Core™ i5-13600KF
Logical processors: 14
Processor groups: 1
Processor group size: 14
RAM: 32581 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 350 MHz
Reported CPU speed (registry): 3494 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step
and AMD Cool N Quiet in the BIOS setup for more accurate results.
_________________________________________________________________________________________________________
MEASURED INTERRUPT TO USER PROCESS LATENCIES
_________________________________________________________________________________________________________
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the
moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an
event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 728.80
Average measured interrupt to process latency (µs): 9.135067
Highest measured interrupt to DPC latency (µs): 717.0
Average measured interrupt to DPC latency (µs): 3.240217
_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 207.471666
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.081443
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in ISRs (%) 0.117777
ISR count (execution time <250 µs): 5110625
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it
is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 407.631654
Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation
Highest reported total DPC routine time (%): 0.124009
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.179826
DPC count (execution time <250 µs): 5751647
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 2
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0
_________________________________________________________________________________________________________
REPORTED HARD PAGEFAULTS
_________________________________________________________________________________________________________
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped
file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and
blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream
resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: firefox.exe
Total number of hard pagefaults 21657
Hard pagefault count of hardest hit process: 3110
Number of processes hit: 84
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 67.788690
CPU 0 ISR highest execution time (µs): 207.471666
CPU 0 ISR total execution time (s): 17.277123
CPU 0 ISR count: 5095556
CPU 0 DPC highest execution time (µs): 271.565255
CPU 0 DPC total execution time (s): 26.147398
CPU 0 DPC count: 5628316
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 15.001665
CPU 1 ISR highest execution time (µs): 159.017172
CPU 1 ISR total execution time (s): 0.508581
CPU 1 ISR count: 15068
CPU 1 DPC highest execution time (µs): 169.356611
CPU 1 DPC total execution time (s): 0.666666
CPU 1 DPC count: 58125
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 9.380641
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 407.631654
CPU 2 DPC total execution time (s): 0.060656
CPU 2 DPC count: 15173
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 9.37090
CPU 3 ISR highest execution time (µs): 34.586148
CPU 3 ISR total execution time (s): 0.000035
CPU 3 ISR count: 1
CPU 3 DPC highest execution time (µs): 104.124213
CPU 3 DPC total execution time (s): 0.059626
CPU 3 DPC count: 14758
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 9.729669
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 87.893532
CPU 4 DPC total execution time (s): 0.055155
CPU 4 DPC count: 11068
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 9.141767
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 102.014596
CPU 5 DPC total execution time (s): 0.050389
CPU 5 DPC count: 9455
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 7.003285
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 117.691185
CPU 6 DPC total execution time (s): 0.017577
CPU 6 DPC count: 2145
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 6.901803
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 166.289926
CPU 7 DPC total execution time (s): 0.014211
CPU 7 DPC count: 1927
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 6.846257
CPU 8 ISR highest execution time (µs): 0.0
CPU 8 ISR total execution time (s): 0.0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 167.200630
CPU 8 DPC total execution time (s): 0.011287
CPU 8 DPC count: 1367
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 6.931584
CPU 9 ISR highest execution time (µs): 0.0
CPU 9 ISR total execution time (s): 0.0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 136.637665
CPU 9 DPC total execution time (s): 0.012752
CPU 9 DPC count: 1418
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 6.882736
CPU 10 ISR highest execution time (µs): 0.0
CPU 10 ISR total execution time (s): 0.0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 116.024327
CPU 10 DPC total execution time (s): 0.012979
CPU 10 DPC count: 1552
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 6.826734
CPU 11 ISR highest execution time (µs): 0.0
CPU 11 ISR total execution time (s): 0.0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 94.202919
CPU 11 DPC total execution time (s): 0.010752
CPU 11 DPC count: 1198
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 6.905321
CPU 12 ISR highest execution time (µs): 0.0
CPU 12 ISR total execution time (s): 0.0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 134.059244
CPU 12 DPC total execution time (s): 0.019599
CPU 12 DPC count: 3514
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 6.921292
CPU 13 ISR highest execution time (µs): 0.0
CPU 13 ISR total execution time (s): 0.0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 108.524327
CPU 13 DPC total execution time (s): 0.016881
CPU 13 DPC count: 1633
_________________________________________________________________________________________________________
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
Include the age of the PSU along with its make and model. BIOS version for your motherboard at this time.
In your first message, I saw you're using BIOS version 3811 with an i5-13600KF. I hope you're running a BIOS version that includes microcode 0x12F or newer. Be cautious—later microcodes aimed at preventing Intel degradation have negatively impacted performance on the platform Overfall. Asus, Gigabyte, and MSI have all seen reduced support, but Asus was the most affected.
I've made significant improvements by combining several steps: reinstalling Windows, applying software updates, adjusting power settings, stopping RAM overclocking (stable per Prime95, though major latency spikes disappeared when I re-enabled XMP II), and unplugging the front port with a faulty USB cable from the motherboard.
Where did you obtain the OS installer? Did you install the operating system in offline mode, disconnecting all drives except the one you intended to install it on? Were you installing all required drivers manually using the latest versions while in offline mode with elevated command privileges?
___Alex___
12-12-2022, 05:34 PM #2When sharing a troubleshooting thread, it's important to provide complete system details. Please format your specs as follows:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
Include the age of the PSU along with its make and model. BIOS version for your motherboard at this time.
In your first message, I saw you're using BIOS version 3811 with an i5-13600KF. I hope you're running a BIOS version that includes microcode 0x12F or newer. Be cautious—later microcodes aimed at preventing Intel degradation have negatively impacted performance on the platform Overfall. Asus, Gigabyte, and MSI have all seen reduced support, but Asus was the most affected.
I've made significant improvements by combining several steps: reinstalling Windows, applying software updates, adjusting power settings, stopping RAM overclocking (stable per Prime95, though major latency spikes disappeared when I re-enabled XMP II), and unplugging the front port with a faulty USB cable from the motherboard.
Where did you obtain the OS installer? Did you install the operating system in offline mode, disconnecting all drives except the one you intended to install it on? Were you installing all required drivers manually using the latest versions while in offline mode with elevated command privileges?
My L2 and L3 cache speeds are trash. I remember my system running games better with an older video card, so presumably this is the voltage problem and not the oxidation issue, but who knows. My choice of chip-breaking issues, lucky me.
I can't find much on the nature of this instability, but did find one reference to "speculation" that the voltage issue specifically affected the bridge between L2 and L3 cache. My chip seems to be stable in OCCT and Prime95 at stock speeds, but Core 1 and Core 6 can't overclock AT ALL, and 53x is the best I can get on three other cores. Ecores seem unaffected.
XxKripxDeMoNxX
12-18-2022, 08:43 PM #4I found the culprit with AIDA64 cache and memory benchmark.
My L2 and L3 cache speeds are trash. I remember my system running games better with an older video card, so presumably this is the voltage problem and not the oxidation issue, but who knows. My choice of chip-breaking issues, lucky me.
I can't find much on the nature of this instability, but did find one reference to "speculation" that the voltage issue specifically affected the bridge between L2 and L3 cache. My chip seems to be stable in OCCT and Prime95 at stock speeds, but Core 1 and Core 6 can't overclock AT ALL, and 53x is the best I can get on three other cores. Ecores seem unaffected.