[10v1703b15063 x64] DPC Spiking issues

KitsuneFoxy

Member
Joined
Jun 12, 2014
Posts
18
Hi, I'm currently having rather bad DPC latency's with a few things. Although, I don't actually have any audio pops or anything, though, my SSD usage spikes when a stutter happens. I particularly watch streams like on twitch and stream.me and they stop anywhere from two seconds to a full twenty and the disk like is spiking then it stop and then continues normally till the next one again. I have a decent connection 350Mbps down/15Mbps up. I use Chrome, But the same issue happens in firefox too. I get stutters under heavy disk load and heavy network loads, No amounts of settings seem to work, bios is set up. I have two network cards because i thought the killer one was doing it.


My trace/msinfo/dxdiag is here: [FONT=source_sans_proregular]https://mega.nz/#!8KB3DDrb!5MUjZ0KbK4x4Sxa8ZlKj_KMkuARNl-huPTjgrtVQyc4

[/FONT]
My primary system details are here. I will also include details from AIDA 64.




A: Self Built.
B: Desktop
D: Windows 10 Enterprise
E: 64Bit
F: Windows 10 1703.
G: Same as above
H: Retail/Obtained through MSDN.
I: Various.. Oldest being the GPU/Rotational HD
J: 1 Day
K: Yes on 22/02/18
Q: No
P: 600W Bequiet.Pure power i think
R Windows 10 Default antivirus
S: no
T: no
U: no




CPU Type OctalCore AMD FX-8320, 3700 MHz (18.5 x 200)
Motherboard Name MSI 970 Gaming (MS-7693) (2 PCI, 2 PCI-E x1, 2 PCI-E x16, 4 DDR3 DIMM, Audio, Gigabit LAN)
Motherboard Chipset AMD 970, AMD K15
System Memory 16341 MB (DDR3 SDRAM)
DIMM1: G Skill Ares F3-2133C11-4GAO 4 GB DDR3-1600 DDR3 SDRAM (11-11-11-28 @ 800 MHz) (10-10-10-27 @ 761 MHz) (9-9-9-24 @ 685 MHz) (8-8-8-22 @ 609 MHz) (7-7-7-19 @ 533 MHz) (6-6-6-16 @ 457 MHz) (5-5-5-14 @ 380 MHz)
DIMM2: G Skill Ares F3-2133C11-4GAO 4 GB DDR3-1600 DDR3 SDRAM (11-11-11-28 @ 800 MHz) (10-10-10-27 @ 761 MHz) (9-9-9-24 @ 685 MHz) (8-8-8-22 @ 609 MHz) (7-7-7-19 @ 533 MHz) (6-6-6-16 @ 457 MHz) (5-5-5-14 @ 380 MHz)
DIMM3: G Skill RipjawsX F3-12800CL9-4GBXL 4 GB DDR3-1600 DDR3 SDRAM (11-11-11-28 @ 800 MHz) (10-10-10-27 @ 761 MHz) (9-9-9-24 @ 685 MHz) (8-8-8-22 @ 609 MHz) (7-7-7-19 @ 533 MHz) (6-6-6-16 @ 457 MHz)
DIMM4: G Skill RipjawsX F3-12800CL9-4GBXL 4 GB DDR3-1600 DDR3 SDRAM (11-11-11-28 @ 800 MHz) (10-10-10-27 @ 761 MHz) (9-9-9-24 @ 685 MHz) (8-8-8-22 @ 609 MHz) (7-7-7-19 @ 533 MHz) (6-6-6-16 @ 457 MHz)




Display:
Video Adapter AMD Radeon HD 7950 Series (3 GB)



Multimedia:
Audio Adapter Asus Xonar DG Sound Card

Storage:
IDE Controller AMD SATA Controller
Storage Controller Microsoft Storage Spaces Controller
Disk Drive Samsung SSD 850 EVO 250GB (250 GB, SATA-III)
Disk Drive TOSHIBA HDWD110 (1 TB, 7200 RPM, SATA-III)
Disk Drive SAMSUNG HD103SI (1 TB, 5400 RPM, SATA-II)
SMART Hard Disks Status OK

Network Adapter D-Link DGE-528T Gigabit Ethernet Adapter (192.168.1.21)
Network Adapter Killer E2200 Gigabit Ethernet Controller

USB1 Controller ATI SB900 - OHCI USB Controller
USB1 Controller ATI SB900 - OHCI USB Controller
USB1 Controller ATI SB900 - OHCI USB Controller
USB1 Controller ATI SB900 - OHCI USB Controller
USB2 Controller ATI SB900 - EHCI USB 2.0 Controller
USB2 Controller ATI SB900 - EHCI USB 2.0 Controller
USB2 Controller ATI SB900 - EHCI USB 2.0 Controller
USB3 Controller Fresco Logic USB 3.0 xHCI Controller
USB Device AVerMedia Live Gamer EXTREME
USB Device Logitech USB Input Device



_________________________________________________________________________________________________________
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:31:12 (h:mm:ss) on all processors.




_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: KITSYPC
OS version: Windows 10 , 10.0, build: 15063 (x64)
Hardware: MS-7693, MSI, 970 GAMING (MS-7693)
CPU: AuthenticAMD AMD FX(tm)-8320 Eight-Core Processor
Logical processors: 8
Processor groups: 1
RAM: 16341 MB total




_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 350 MHz
Measured CPU speed: 1 MHz (approx.)


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.


WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.






_________________________________________________________________________________________________________
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): 5483.553581
Average measured interrupt to process latency (µs): 12.426166


Highest measured interrupt to DPC latency (µs): 2507.285610
Average measured interrupt to DPC latency (µs): 6.767985




_________________________________________________________________________________________________________
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): 143.8820
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation


Highest reported total ISR routine time (%): 0.007089
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation


Total time spent in ISRs (%) 0.016803


ISR count (execution time <250 µs): 1917922
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 2339.610571
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation


Highest reported total DPC routine time (%): 0.196964
Driver with highest DPC total execution time: cmudaxp.sys - C-Media Audio WDM Driver, C-Media Inc


Total time spent in DPCs (%) 0.523045


DPC count (execution time <250 µs): 10011783
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 626
DPC count (execution time 1000-1999 µs): 36
DPC count (execution time 2000-3999 µs): 1
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.




Process with highest pagefault count: none


Total number of hard pagefaults 0
Hard pagefault count of hardest hit process: 0
Highest hard pagefault resolution time (µs): 0.0
Total time spent in hard pagefaults (%): 0.0
Number of processes hit: 0




_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 151.389353
CPU 0 ISR highest execution time (µs): 143.8820
CPU 0 ISR total execution time (s): 1.994865
CPU 0 ISR count: 1188067
CPU 0 DPC highest execution time (µs): 2339.610571
CPU 0 DPC total execution time (s): 74.196162
CPU 0 DPC count: 9527832
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 34.978779
CPU 1 ISR highest execution time (µs): 61.075143
CPU 1 ISR total execution time (s): 0.128376
CPU 1 ISR count: 67641
CPU 1 DPC highest execution time (µs): 769.8120
CPU 1 DPC total execution time (s): 1.159608
CPU 1 DPC count: 102985
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 34.440182
CPU 2 ISR highest execution time (µs): 57.266571
CPU 2 ISR total execution time (s): 0.047324
CPU 2 ISR count: 57625
CPU 2 DPC highest execution time (µs): 282.576286
CPU 2 DPC total execution time (s): 0.624220
CPU 2 DPC count: 83677
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 35.635522
CPU 3 ISR highest execution time (µs): 44.564571
CPU 3 ISR total execution time (s): 0.040086
CPU 3 ISR count: 55737
CPU 3 DPC highest execution time (µs): 314.435714
CPU 3 DPC total execution time (s): 0.520981
CPU 3 DPC count: 69712
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 31.052368
CPU 4 ISR highest execution time (µs): 59.798571
CPU 4 ISR total execution time (s): 0.035052
CPU 4 ISR count: 53894
CPU 4 DPC highest execution time (µs): 225.1040
CPU 4 DPC total execution time (s): 0.552874
CPU 4 DPC count: 68593
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 31.542879
CPU 5 ISR highest execution time (µs): 35.681714
CPU 5 ISR total execution time (s): 0.044516
CPU 5 ISR count: 78066
CPU 5 DPC highest execution time (µs): 269.674857
CPU 5 DPC total execution time (s): 0.433954
CPU 5 DPC count: 57663
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 28.636484
CPU 6 ISR highest execution time (µs): 16.348571
CPU 6 ISR total execution time (s): 0.066318
CPU 6 ISR count: 118098
CPU 6 DPC highest execution time (µs): 135.006857
CPU 6 DPC total execution time (s): 0.446373
CPU 6 DPC count: 54568
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 28.635278
CPU 7 ISR highest execution time (µs): 36.720571
CPU 7 ISR total execution time (s): 0.159861
CPU 7 ISR count: 298794
CPU 7 DPC highest execution time (µs): 134.970857
CPU 7 DPC total execution time (s): 0.397786
CPU 7 DPC count: 47416
_________________________________________________________________________________________________________






 

Attachments

  • latencymon picture.png
    latencymon picture.png
    62.5 KB · Views: 4
Re: Windows 10 DPC Spiking issues

Thanks for the amazing post.

I don't work for a company.
Enterprise was downloaded by my brothers link with his university when he attended there.
I have a proper key. It is not a VLK or KMS.

It is activated normally through windows activation
 
Re: Windows 10 DPC Spiking issues

Thanks for the amazing post.

I don't work for a company.
Enterprise was downloaded by my brothers link with his university when he attended there.
I have a proper key. It is not a VLK or KMS.

It is activated normally through windows activation

Sorry for sounding like an *** last night
 
Re: Windows 10 DPC Spiking issues

Not sure if anyone's able to find out anything, or if they just don't know

Would be grateful for any help.
 
Latest official and stable bios is M4 2015-12-23; your logs say V22.5B5, 07/06/2016 (July 6th).
Alternate your sticks (dimm0 ares, dimm1 ripjaws, dimm2 ares, dimm3 ripjaws).
Increase your ram speed to 1866.
"cmudaxp.sys is not digitally signed" found in dxdiag log. Try to use the tested and stable driver for it.
 
Latest official and stable bios is M4 2015-12-23; your logs say V22.5B5, 07/06/2016 (July 6th).
Alternate your sticks (dimm0 ares, dimm1 ripjaws, dimm2 ares, dimm3 ripjaws).
Increase your ram speed to 1866.
"cmudaxp.sys is not digitally signed" found in dxdiag log. Try to use the tested and stable driver for it.

It is the latest bios that was made for this board, however msi havent updated the boards page in a long time. It is Given when requested, from the staff over on MSI forums.
But i'll try switching back.
And i will try doing that, Though i think i did.

The ripjaw ram is rated for 1600mhz, while the other 2133, If i increase the ram speed, wont that be overclocking the ripjaws?

And yea. It's not signed, since it's a custom updated driver by the guy at maxedtech who does the Asus/cmedia drivers. UNi Xonar Drivers official page - MaxedTech
However i will give the last driver from 2015 from asus a try.

Thank you very much for your input.
 
~I ahve purchased the same sticks as the Ares, so they should come soon, so i wont be using mixed ram atleast.

Will try it again once those come along. I will also do a no power battery cmos clear.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top