Dantel2210 Posted March 27 Author Share Posted March 27 every driver is updated Link to comment Share on other sites More sharing options...
Dantel2210 Posted March 27 Author Share Posted March 27 Maybe this will help, but i don´t know. It also seems, it´s allways core 1 that has the cycle problems. _________________________________________________________________________________________________________ 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:32:36 (h:mm:ss) on processors 0,1,2,3,4,5,6,7,8,9,10 and 11. _________________________________________________________________________________________________________ SYSTEM INFORMATION _________________________________________________________________________________________________________ OS version: Windows 11, 10.0, version 2009, build: 22631 (x64) Hardware: MS-7D32, Micro-Star International Co., Ltd. BIOS: 1.G0 CPU: GenuineIntel 13th Gen Intel(R) Core(TM) i7-13700K Logical processors: 24 Processor groups: 1 Processor group size: 24 RAM: 32549 MB total _________________________________________________________________________________________________________ CPU SPEED _________________________________________________________________________________________________________ Reported CPU speed (WMI): 340 MHz Reported CPU speed (registry): 3418 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): 545,0 Average measured interrupt to process latency (µs): 4,149053 Highest measured interrupt to DPC latency (µs): 152,60 Average measured interrupt to DPC latency (µs): 1,324887 _________________________________________________________________________________________________________ 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): 311,913107 Driver with highest ISR routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation Highest reported total ISR routine time (%): 0,000811 Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation Total time spent in ISRs (%) 0,000811 ISR count (execution time <250 µs): 966832 ISR count (execution time 250-500 µs): 0 ISR count (execution time 500-1000 µs): 1 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): 618,236103 Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation Highest reported total DPC routine time (%): 0,027096 Driver with highest DPC total execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation Total time spent in DPCs (%) 0,058101 DPC count (execution time <250 µs): 2600359 DPC count (execution time 250-500 µs): 0 DPC count (execution time 500-10000 µs): 29 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: msmpeng.exe Total number of hard pagefaults 100 Hard pagefault count of hardest hit process: 57 Number of processes hit: 8 _________________________________________________________________________________________________________ PER CPU DATA _________________________________________________________________________________________________________ CPU 0 Interrupt cycle time (s): 11,096691 CPU 0 ISR highest execution time (µs): 92,157109 CPU 0 ISR total execution time (s): 0,136672 CPU 0 ISR count: 355232 CPU 0 DPC highest execution time (µs): 146,469573 CPU 0 DPC total execution time (s): 0,496289 CPU 0 DPC count: 412353 _________________________________________________________________________________________________________ CPU 1 Interrupt cycle time (s): 73,477186 CPU 1 ISR highest execution time (µs): 311,913107 CPU 1 ISR total execution time (s): 0,244135 CPU 1 ISR count: 611601 CPU 1 DPC highest execution time (µs): 618,236103 CPU 1 DPC total execution time (s): 26,060887 CPU 1 DPC count: 2100011 _________________________________________________________________________________________________________ CPU 2 Interrupt cycle time (s): 7,303222 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): 593,025453 CPU 2 DPC total execution time (s): 0,010812 CPU 2 DPC count: 1130 _________________________________________________________________________________________________________ CPU 3 Interrupt cycle time (s): 6,633648 CPU 3 ISR highest execution time (µs): 0,0 CPU 3 ISR total execution time (s): 0,0 CPU 3 ISR count: 0 CPU 3 DPC highest execution time (µs): 87,228204 CPU 3 DPC total execution time (s): 0,001011 CPU 3 DPC count: 175 _________________________________________________________________________________________________________ CPU 4 Interrupt cycle time (s): 5,432496 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): 131,091867 CPU 4 DPC total execution time (s): 0,005751 CPU 4 DPC count: 683 _________________________________________________________________________________________________________ CPU 5 Interrupt cycle time (s): 5,238608 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): 123,726448 CPU 5 DPC total execution time (s): 0,002698 CPU 5 DPC count: 434 _________________________________________________________________________________________________________ CPU 6 Interrupt cycle time (s): 6,774862 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): 543,099181 CPU 6 DPC total execution time (s): 0,008242 CPU 6 DPC count: 840 _________________________________________________________________________________________________________ CPU 7 Interrupt cycle time (s): 6,762727 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): 106,660035 CPU 7 DPC total execution time (s): 0,001583 CPU 7 DPC count: 209 _________________________________________________________________________________________________________ CPU 8 Interrupt cycle time (s): 10,706941 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): 591,486834 CPU 8 DPC total execution time (s): 0,311781 CPU 8 DPC count: 35644 _________________________________________________________________________________________________________ CPU 9 Interrupt cycle time (s): 11,311407 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): 227,527209 CPU 9 DPC total execution time (s): 0,054056 CPU 9 DPC count: 8592 _________________________________________________________________________________________________________ CPU 10 Interrupt cycle time (s): 11,311054 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): 614,690170 CPU 10 DPC total execution time (s): 0,310128 CPU 10 DPC count: 36692 _________________________________________________________________________________________________________ CPU 11 Interrupt cycle time (s): 11,514689 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): 614,977180 CPU 11 DPC total execution time (s): 0,019249 CPU 11 DPC count: 3625 _________________________________________________________________________________________________________ Link to comment Share on other sites More sharing options...
HeyYou Posted March 28 Share Posted March 28 The latency times seem kinda odd to me. The 'highest" value is lower than the average? How does that work???? Link to comment Share on other sites More sharing options...
RomanR Posted March 29 Share Posted March 29 (edited) If the driver or codec used used isn't a problem I would try to switch off the efficient cores and also SMT in UEFI Bios, if it's possible. Efficient cores are still something new and scheduler in Windows isn't much good. Also running Task Manager while playing something could show if some core is overloaded to 100%. Windows 10/11 loads CPU much more than older systems, so switching some unecessary programs/services/schedule tasks off can improve things, but in this case you must know what you're doing. Edit: It's also good to check yor sound card capabilities and settings according to sound specs. If system or codec must resample a sound, it adds time to sound playing/processing. Regarding SoundBlaster - I disposed of my SoundBlaster X-Fi and returned to integrated RealTek Codec, because of various problems with drivers. At least on paper any external sound card isn't much better than capabilities of integrated one and if all effect are now computed by CPU so what? We have plenty of cores now. Edited March 29 by RomanR some additions Link to comment Share on other sites More sharing options...
Dantel2210 Posted March 29 Author Share Posted March 29 (edited) Ye i was thinking about disabling the E-Cores too. My bios has a option for older games, i can activate it and disable E-Cores on the fly. I give it a try. I don´t know what SMT means, but maybe google will tell me. So if i wanna stick to a soundcard, i should switch to a internal one? If so, suggestions? But man .... i would miss the feature on my "X4", since i can connect speakers + headphones and switch by pressing a button and both have different settings. It´s so nice to have. One of the reasons, why i kept it. I forgot to mention, i switched my High definition Audio Controllers to "MSI" Mode, don´t even know if that is good. Someone said, MSI on all Devices that can use it, is better. Edited March 29 by Dantel2210 Link to comment Share on other sites More sharing options...
RomanR Posted March 29 Share Posted March 29 SMT stands for Simultenous Multi Threading. It allows modern CPU handle more than one HW thread (mostly two) and can boost overall speed when SW is written for it (high parallel tasks like rendering etc.) Speed gain can be about 20%. System sees such CPU with more cores than it really has. MSI mode is another interupt handling style. I practically know nothing about it. From googling it speeds up interrupt handling by writing directly into mapped memory. However such interrupt is unshared, so don't use this mode for devices with shared IRQs. But as I listen to music in video you linked, I don't hear anything wrong (except short sound drop on about 12:00, but it could be caused by anything as it's online) and load of my CPU was mostly at 2%. If you have problems while playing music and sound saved locally too, something seems slowing processing so much that sound buffer is drained too early before is filled with next sound data. Link to comment Share on other sites More sharing options...
HeyYou Posted March 29 Share Posted March 29 Anti-virus software? Other startup programs?? Link to comment Share on other sites More sharing options...
Dantel2210 Posted March 30 Author Share Posted March 30 (edited) It´s crazy that people don´t hear the pops in the video. Since i can hear it on the TV, Smartphone and my PC. I only use Defender and i almost completly disabled it. So i can test stuff and if it maybe is the problem maker. In other forums people say, it could be the xmp profil for the ram and i need to manually adjust it. I will give it a try. Edited March 30 by Dantel2210 Link to comment Share on other sites More sharing options...
RomanR Posted March 30 Share Posted March 30 I would suspect something with network, since problem persist through different devices. If you can play your own recordings (music, sounds, video with sounds) on all these devices just fine, I would assume that PC, TV and smartphone is OK. Also many people are listening to music with too high volume, intesifing any imperfection of record and damaging their own hearing in the process. In this case just one linked video is propably not enough example. Perhaps your internet connection is the culprit and not your PC in the end? Link to comment Share on other sites More sharing options...
RichWithLife Posted November 5 Share Posted November 5 Hey man, I have been solving this issue for more than a year and I believe that we are dealing with broken drivers from CREATIVE side. I also have X4 sound card and running hi-spec PC, disabled integrated soundcard drivers and my issue is that I am loosing DDL or DTS decoding and I believe that those cracking sounds are only when we are setting our cards to work through SPDIF/OPTICAL inputs. My case is that I have installed latest drivers and when You go into Creative app and set your speakers to 5.1 Dolby Digital Live and when You press test it does not recognize 5.1 CH, basically it runs test inside to each channel and sound is like you have 2.1 Other weird thing is that when You go into Win Control panel -> Sound Settings and into SPDIF props - There we have DD & DTS when You press test - IT clearly activates every single channel as it supposed to be but not in Creative app TEST on 5.1 DDL. It gets even weirder as I have uninstalled Realtek audio driver and Creative as well and my X4 lights are off now but still when You go through Win control panel Sound properties You can test DD & DTS and every single channel works as it should. I have no explanations for this matter as I have teared apart most of the forums and YT videos. As I am using Logitech Z906 5.1 speakers many ppl complained that these speakers are giving out cracking/popping sounds but that is not the case in this matter & issue is with Digital decoding in my opinion. For now latest what I have found is this thread on Redit: I will try to work around this and see if my DD and DTS will be back without any cracks. There is always a way. More deeper You go, More knowledge You know. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now