Slow PC, high DPC Latency, and BSOD

K

KRzYamaneko

Hello,


I have some latency issue on my desktop, this computer should be very fast but it's not, each time I start an apps it freeze for 1sec or 2 then the apps start.

Also sometimes I have some BSOD.


My desktop configuration :

- Aorus X570 Elite firmware version F30a

- AMD Ryzen 3600X

- 16Gb of RAM (2x8Gb G.Skill F4-3200C16-8GVGB).

- 2 SSD SanDisk SSD PLUS 240GB

- RAID Controller M5015 fw 2.130.403 with 5 disks attached : 2x HitachiHDS72101 3x WDCWD1002FBYS1

- Video card Asus radeon rx 5700 xt

- 1 PCIe USB 3.1 controller card.


I done the following test with no result :

- Memory test (included in Windows and the Dell 32Bit diag test)

- CPU stress test with Dell 32bit diag and CPU-Z

- My disks (ssd and RAID) with Seagate Seatools and a CHKDSK /f on all my disk


All individual test of my hardware are ok.


My drivers are up to date (I use Driver Booster), I done a test with 2 versions of the NIC drivers, with no change the log attached are the one with the newest version.

I done a fresh install of windows 10 ver 2004.


I'm a bit lost I don't understand what is not working correctly, if someone can help it would be realy appreciate.


Here some logs I hope may help.


---------------------------------------------Latency Monitor result------------------------------------------------------------------------------

_________________________________________________________________________________________________________

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 DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:02:11 (h:mm:ss) on all processors.





_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: YAMANEKO-DESKTO

OS version: Windows 10, 10.0, version 2004, build: 19041 (x64)

Hardware: X570 AORUS ELITE, Gigabyte Technology Co., Ltd.

CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor

Logical processors: 12

Processor groups: 1

RAM: 16328 MB total





_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 3793 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): 1501,50

Average measured interrupt to process latency (µs): 16,724395



Highest measured interrupt to DPC latency (µs): 1498,80

Average measured interrupt to DPC latency (µs): 12,812439





_________________________________________________________________________________________________________

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): 68,075402

Driver with highest ISR routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation



Highest reported total ISR routine time (%): 0,025699

Driver with highest ISR total time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation



Total time spent in ISRs (%) 0,028749



ISR count (execution time <250 µs): 129788

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): 6582,435539

Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation



Highest reported total DPC routine time (%): 0,731182

Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation



Total time spent in DPCs (%) 1,174375



DPC count (execution time <250 µs): 191570

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-10000 µs): 34794

DPC count (execution time 1000-2000 µs): 10

DPC count (execution time 2000-4000 µs): 4

DPC count (execution time >=4000 µs): 2





_________________________________________________________________________________________________________

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: explorer.exe



Total number of hard pagefaults 2362

Hard pagefault count of hardest hit process: 565

Number of processes hit: 34





_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 17,119257

CPU 0 ISR highest execution time (µs): 68,075402

CPU 0 ISR total execution time (s): 0,184668

CPU 0 ISR count: 54536

CPU 0 DPC highest execution time (µs): 4139,815977

CPU 0 DPC total execution time (s): 12,873012

CPU 0 DPC count: 87436

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 7,033730

CPU 1 ISR highest execution time (µs): 48,709728

CPU 1 ISR total execution time (s): 0,150072

CPU 1 ISR count: 24990

CPU 1 DPC highest execution time (µs): 895,720011

CPU 1 DPC total execution time (s): 3,028513

CPU 1 DPC count: 43972

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 6,082618

CPU 2 ISR highest execution time (µs): 17,983127

CPU 2 ISR total execution time (s): 0,093765

CPU 2 ISR count: 15070

CPU 2 DPC highest execution time (µs): 6582,435539

CPU 2 DPC total execution time (s): 2,41620

CPU 2 DPC count: 36230

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 3,000537

CPU 3 ISR highest execution time (µs): 15,488532

CPU 3 ISR total execution time (s): 0,003699

CPU 3 ISR count: 381

CPU 3 DPC highest execution time (µs): 136,080675

CPU 3 DPC total execution time (s): 0,017022

CPU 3 DPC count: 4807

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 2,832168

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): 122,335355

CPU 4 DPC total execution time (s): 0,020563

CPU 4 DPC count: 7140

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 2,816757

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): 109,682046

CPU 5 DPC total execution time (s): 0,016071

CPU 5 DPC count: 6362

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 3,905760

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): 130,350119

CPU 6 DPC total execution time (s): 0,013015

CPU 6 DPC count: 5496

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 3,956892

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): 194,368046

CPU 7 DPC total execution time (s): 0,010814

CPU 7 DPC count: 4761

_________________________________________________________________________________________________________

CPU 8 Interrupt cycle time (s): 4,195161

CPU 8 ISR highest execution time (µs): 3,726865

CPU 8 ISR total execution time (s): 0,011612

CPU 8 ISR count: 19472

CPU 8 DPC highest execution time (µs): 910,817822

CPU 8 DPC total execution time (s): 0,040490

CPU 8 DPC count: 8436

_________________________________________________________________________________________________________

CPU 9 Interrupt cycle time (s): 4,124042

CPU 9 ISR highest execution time (µs): 2,654891

CPU 9 ISR total execution time (s): 0,001680

CPU 9 ISR count: 2363

CPU 9 DPC highest execution time (µs): 173,840232

CPU 9 DPC total execution time (s): 0,033328

CPU 9 DPC count: 7723

_________________________________________________________________________________________________________

CPU 10 Interrupt cycle time (s): 3,930624

CPU 10 ISR highest execution time (µs): 2,905352

CPU 10 ISR total execution time (s): 0,002605

CPU 10 ISR count: 3697

CPU 10 DPC highest execution time (µs): 166,867387

CPU 10 DPC total execution time (s): 0,035468

CPU 10 DPC count: 6965

_________________________________________________________________________________________________________

CPU 11 Interrupt cycle time (s): 4,009165

CPU 11 ISR highest execution time (µs): 2,995518

CPU 11 ISR total execution time (s): 0,005989

CPU 11 ISR count: 9279

CPU 11 DPC highest execution time (µs): 156,127603

CPU 11 DPC total execution time (s): 0,044763

CPU 11 DPC count: 7052

_________________________________________________________________________________________________________



----------------------------------WhoCrashed report ----------------------------------------------------------

System Information (local)



Computer name: YAMANEKO-DESKTO
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: X570 AORUS ELITE, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17122000896 bytes (15,9GB)





Crash Dump Analysis



Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 09/10/2020 22:21:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\101020-11031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x4E (0x99, 0x2B80FD, 0x2, 0x80001E0001EE994)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 09/10/2020 22:21:24 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!KeReenterRetpolinedCode+0x1007)
Bugcheck code: 0x4E (0x99, 0x2B80FD, 0x2, 0x80001E0001EE994)
Error: PFN_LIST_CORRUPT
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.






Conclusion



2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

Continue reading...
 

Similar threads

A
Replies
0
Views
313
AdityaPushkar
A
Y
Replies
0
Views
763
YamanashiMoondragon
Y
Y
Replies
0
Views
467
YamanashiMoondragon
Y
S
Replies
0
Views
255
Sphinxy66
S
Back
Top Bottom