07-08-2023 11:22 PM
I am having two main issues laggy load on start up and that if my PC goes to sleep it will not reawaken and have to use the reset to restart. Also issue with audio when opening file explorer or having multiple windows open or more than one Chrome tab open. Crazy popping noises from speakers. All drivers installed correctly and currently up to date. The Current Bios 1415 system Windows 10 Pro. 64bit. MB Crosshair Extreme X670 E, GPU Strix RTX 4090 OC, PSU Thor 1200W Pat III, DDR5 Corsair 64GB Dominator x2 x 32GB. Samsung 990 PRO 2TB x 2 at M2_1 and M2_2 slots. It is a pain in the ass to not be able to wake the PC up from sleep mode. I am at a loss and if I have to disable hardware to make a 1000.00 Dollar mother board work then ASUS has seriously let us all down.
I paid 1000.00 USD for this MB and it is not living up to its expectation info on the box say that my board was manufacture 10/22 any help would be grateful.
07-09-2023 12:22 AM
Hello,
Failure to resume from low power states can indicate memory instability. It's important to revert to stock before troubleshooting further.
Clear the CMOS via the button on the motherboard's rear IO panel and then retest. Do not enable any form of overclocking, including DOCP profiles as this constitutes as such. Retest to see if the sleep state resume issue persists.
You can check DCP latency with LatencyMon to see if a particular process is causing issues with real-time audio.
https://www.techspot.com/downloads/6944-latencymon.html
07-09-2023 02:51 PM
I ran the app from the link I see that there is an issue. I have no over clocking enabled on the CPU nor the DDR5 modules and only went from the 4800MHz on the DDR5 to the 6000MHz that is listed on the QVL tab on the MB support page by enabling expo in Bios. ROG CPU Z is showing my DDR5 operating at DDR5-4800 (2400MHz) each for both modules in slot 2 and slot 4.
I am experiencing popping / clicking noise from the speakers my drivers are all up to date. bios is at 1415. I do not have the front audio cable connector plugged in as there is a black wire that is came out of the crimp on the connector and I am contacting ASUS about either a new cable.
It has been a good 10 years since I built a PC and I will say that I am way behind the curve on this newer technology. I pasted from the LatencyMon the data from the clipboard. I admit I do not know what I am searching for as to which driver is the issue. my power management in windows 10 is set to high performance and current bios settings are all stock no changes other than for the NVMe and the EXPO for ramm.
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more ISR routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:04:07 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: GR701
OS version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Hardware: System Product Name, ASUS
CPU: AuthenticAMD AMD Ryzen 9 7950X3D 16-Core Processor
Logical processors: 32
Processor groups: 1
RAM: 64651 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 420 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): 134.50
Average measured interrupt to process latency (µs): 7.842816
Highest measured interrupt to DPC latency (µs): 131.80
Average measured interrupt to DPC latency (µs): 1.469090
_________________________________________________________________________________________________________
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): 2258.320
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0.001276
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0.001355
ISR count (execution time <250 µs): 15487
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 3
ISR count (execution time 1000-2000 µs): 4
ISR count (execution time 2000-4000 µs): 2
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): 340.730
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 536.40 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0.001074
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation
Total time spent in DPCs (%) 0.003636
DPC count (execution time <250 µs): 50446
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 17
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: latmon.exe
Total number of hard pagefaults 2966
Hard pagefault count of hardest hit process: 2766
Number of processes hit: 21
___________________________________________________________
07-11-2023 03:46 AM
Hello,
It's not unusual for the DirectX kernel to induce latency on NVIDIA GPU systems. I've noted here that there's an open-case for increased latency. See the notes: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/521773/geforce-grd-53640-feedback-...