- 28
- 0
- CPU
- Intel Core i7-2600k
- Scheda Madre
- Asus P8H67
- HDD
- Barracuda sata 3 500gb
- RAM
- Corsair Vengeance 4x4gb
- GPU
- ASUS GEFORCE GTX 660 (2Gb)
- Monitor
- Tv LG HDMI
- PSU
- Enermax revolution 87+ 850 watt
- Case
- CM Storm Scout II
- OS
- Windows 7 64bit
Ho iniziato a lamentarmi delle mie cuffie (strix7.1) circa un paio di mesi fa, quando ho notato che l'audio iniziava a scoppiettare. Pensando fosse un problema delle cuffie ho iniziato a contattare il supporto ma mentre per puro caso ho lasciato accese le casse del monitor mentre guardavo un video ho sentito lo stesso disturbo.. Clickando il suono scoppietta, fa suono d'interferenza
Ho provato a leggere in giro ma non ho trovato nulla che potesse essermi d'aiuto (disabilitare il miglioramento del suono o forzare da console un file check di sistema)
Questa è la mia build attuale http://pcpartpicker.com/list/XbdH4C
Sto letteralmente impazzendo
Ho fatto girare latencymon e ho visto che il driver che prende piu' cpu è wdf01000.sys, subito dopo l' nvidia win kernel mode. Questo è il report ma non so che farmene di queste informazioni
_________________________________________________________________________________________________________
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. 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:18 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: WOLFLIE
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASUSTeK COMPUTER INC., MAXIMUS VIII RANGER
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Logical processors: 8
Processor groups: 1
RAM: 16309 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 4008 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): 95527,528356
Average measured interrupt to process latency (µs): 39,400582
Highest measured interrupt to DPC latency (µs): 95484,861608
Average measured interrupt to DPC latency (µs): 27,217303
_________________________________________________________________________________________________________
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): 129,926397
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,151573
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,159480
ISR count (execution time <250 µs): 75640
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): 96022,412675
Driver with highest DPC routine execution time: Wdf01000.sys - Runtime framework driver modalità kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0,527872
Driver with highest DPC total execution time: Wdf01000.sys - Runtime framework driver modalità kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,720234
DPC count (execution time <250 µs): 345343
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 6
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: vsserv.exe
Total number of hard pagefaults 116
Hard pagefault count of hardest hit process: 79
Highest hard pagefault resolution time (µs): 23803,606038
Total time spent in hard pagefaults (%): 0,013150
Number of processes hit: 6
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 11,347176
CPU 0 ISR highest execution time (µs): 129,926397
CPU 0 ISR total execution time (s): 1,545216
CPU 0 ISR count: 55516
CPU 0 DPC highest execution time (µs): 96022,412675
CPU 0 DPC total execution time (s): 7,279795
CPU 0 DPC count: 287261
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2,924929
CPU 1 ISR highest execution time (µs): 117,587325
CPU 1 ISR total execution time (s): 0,201787
CPU 1 ISR count: 11647
CPU 1 DPC highest execution time (µs): 49736,094311
CPU 1 DPC total execution time (s): 0,391416
CPU 1 DPC count: 17649
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,297972
CPU 2 ISR highest execution time (µs): 51,826347
CPU 2 ISR total execution time (s): 0,001130
CPU 2 ISR count: 552
CPU 2 DPC highest execution time (µs): 298,034681
CPU 2 DPC total execution time (s): 0,087556
CPU 2 DPC count: 9701
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,006372
CPU 3 ISR highest execution time (µs): 46,046657
CPU 3 ISR total execution time (s): 0,005605
CPU 3 ISR count: 3667
CPU 3 DPC highest execution time (µs): 97,572355
CPU 3 DPC total execution time (s): 0,020169
CPU 3 DPC count: 3703
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1,587460
CPU 4 ISR highest execution time (µs): 45,177395
CPU 4 ISR total execution time (s): 0,000610
CPU 4 ISR count: 288
CPU 4 DPC highest execution time (µs): 174,566367
CPU 4 DPC total execution time (s): 0,032067
CPU 4 DPC count: 5172
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,520487
CPU 5 ISR highest execution time (µs): 48,218313
CPU 5 ISR total execution time (s): 0,002386
CPU 5 ISR count: 1514
CPU 5 DPC highest execution time (µs): 78,562375
CPU 5 DPC total execution time (s): 0,021868
CPU 5 DPC count: 3499
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,877994
CPU 6 ISR highest execution time (µs): 18,543663
CPU 6 ISR total execution time (s): 0,001035
CPU 6 ISR count: 419
CPU 6 DPC highest execution time (µs): 75,387974
CPU 6 DPC total execution time (s): 0,044269
CPU 6 DPC count: 6736
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2,787957
CPU 7 ISR highest execution time (µs): 49,112275
CPU 7 ISR total execution time (s): 0,003487
CPU 7 ISR count: 2037
CPU 7 DPC highest execution time (µs): 260,565619
CPU 7 DPC total execution time (s): 0,076947
CPU 7 DPC count: 11780
_________________________________________________________________________________________________________
Chiedo scusa se la sezione è quella errata ma non saprei dove scriverlo ^^
Ho provato a leggere in giro ma non ho trovato nulla che potesse essermi d'aiuto (disabilitare il miglioramento del suono o forzare da console un file check di sistema)
Questa è la mia build attuale http://pcpartpicker.com/list/XbdH4C
Sto letteralmente impazzendo
Ho fatto girare latencymon e ho visto che il driver che prende piu' cpu è wdf01000.sys, subito dopo l' nvidia win kernel mode. Questo è il report ma non so che farmene di queste informazioni
_________________________________________________________________________________________________________
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. 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:18 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: WOLFLIE
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASUSTeK COMPUTER INC., MAXIMUS VIII RANGER
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Logical processors: 8
Processor groups: 1
RAM: 16309 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 4008 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): 95527,528356
Average measured interrupt to process latency (µs): 39,400582
Highest measured interrupt to DPC latency (µs): 95484,861608
Average measured interrupt to DPC latency (µs): 27,217303
_________________________________________________________________________________________________________
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): 129,926397
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,151573
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,159480
ISR count (execution time <250 µs): 75640
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): 96022,412675
Driver with highest DPC routine execution time: Wdf01000.sys - Runtime framework driver modalità kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0,527872
Driver with highest DPC total execution time: Wdf01000.sys - Runtime framework driver modalità kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,720234
DPC count (execution time <250 µs): 345343
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 6
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: vsserv.exe
Total number of hard pagefaults 116
Hard pagefault count of hardest hit process: 79
Highest hard pagefault resolution time (µs): 23803,606038
Total time spent in hard pagefaults (%): 0,013150
Number of processes hit: 6
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 11,347176
CPU 0 ISR highest execution time (µs): 129,926397
CPU 0 ISR total execution time (s): 1,545216
CPU 0 ISR count: 55516
CPU 0 DPC highest execution time (µs): 96022,412675
CPU 0 DPC total execution time (s): 7,279795
CPU 0 DPC count: 287261
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2,924929
CPU 1 ISR highest execution time (µs): 117,587325
CPU 1 ISR total execution time (s): 0,201787
CPU 1 ISR count: 11647
CPU 1 DPC highest execution time (µs): 49736,094311
CPU 1 DPC total execution time (s): 0,391416
CPU 1 DPC count: 17649
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,297972
CPU 2 ISR highest execution time (µs): 51,826347
CPU 2 ISR total execution time (s): 0,001130
CPU 2 ISR count: 552
CPU 2 DPC highest execution time (µs): 298,034681
CPU 2 DPC total execution time (s): 0,087556
CPU 2 DPC count: 9701
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,006372
CPU 3 ISR highest execution time (µs): 46,046657
CPU 3 ISR total execution time (s): 0,005605
CPU 3 ISR count: 3667
CPU 3 DPC highest execution time (µs): 97,572355
CPU 3 DPC total execution time (s): 0,020169
CPU 3 DPC count: 3703
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 1,587460
CPU 4 ISR highest execution time (µs): 45,177395
CPU 4 ISR total execution time (s): 0,000610
CPU 4 ISR count: 288
CPU 4 DPC highest execution time (µs): 174,566367
CPU 4 DPC total execution time (s): 0,032067
CPU 4 DPC count: 5172
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,520487
CPU 5 ISR highest execution time (µs): 48,218313
CPU 5 ISR total execution time (s): 0,002386
CPU 5 ISR count: 1514
CPU 5 DPC highest execution time (µs): 78,562375
CPU 5 DPC total execution time (s): 0,021868
CPU 5 DPC count: 3499
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 1,877994
CPU 6 ISR highest execution time (µs): 18,543663
CPU 6 ISR total execution time (s): 0,001035
CPU 6 ISR count: 419
CPU 6 DPC highest execution time (µs): 75,387974
CPU 6 DPC total execution time (s): 0,044269
CPU 6 DPC count: 6736
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2,787957
CPU 7 ISR highest execution time (µs): 49,112275
CPU 7 ISR total execution time (s): 0,003487
CPU 7 ISR count: 2037
CPU 7 DPC highest execution time (µs): 260,565619
CPU 7 DPC total execution time (s): 0,076947
CPU 7 DPC count: 11780
_________________________________________________________________________________________________________
Chiedo scusa se la sezione è quella errata ma non saprei dove scriverlo ^^
