Hi again
I'm not sure how accurate the Latency Monitor results are, since the program hasn't been updated since Windows 7. You can try creating a cpu trace with Windows 10's Performance Monitor ... hopefully that would work (though since it had trouble creating the health report, it's not certain).
Did we check your Virtual Memory settings yet? If it is currently set to have Windows 10 automatically adjust things, try setting the range manually, and see if there's any effect. Since you have 8 GB of system memory, a reasonable range would be 8192 MB for the lower setting and 16384 for the higher setting.
See if you can get the SysNative info collector to run - you can try it with administrative rights, and if that doesn't help, in Safe Mode (also with administrative rights).
Make sure that Latency Monitor isn't running when you are testing for the audio/visual effects: Latency Monitor itself can show rather high latency.
And ... one of the things you still have the option of trying: make a system image backup, and then go back to Windows 7. If everything runs well in Windows 7, it just might be that the Windows 7 drivers work better for your hardware/software mix. You could still upgrade your Windows 7 to Windows 10 again until July 29th of this year. You could make a system image of your Windows 7 then, too, if it is working well -- in case Windows 10 just doesn't behave itself either now or on a future upgrade try.
I've had to move some of my customers computers back to Windows 7 - but most of those were at least six or seven years old, and were borderline compatible for Windows 10. Windows 7 will still continue to get security updates until mid-January of 2020.
Let us know how things go. If you want to keep working on getting Windows 10 to a non-stuttering state, our next step is to get the info-collection app to run. There might be a clue in there.... and try a Performance Monitor cpu trace.
Hope for the best!
hi again.
first of all thank you again for keep replying me.
i'll try everything you just said.
in the meanwhile i uninstalled audio driver and i put the audio card on disabled. i left latecy mon ON and i let the computer in idle during dinner.
here the report :
Read More:
______________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. 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:51:26 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: VALERIO-PC
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASRock, H97 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
Logical processors: 4
Processor groups: 1
RAM: 8133 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3193 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): 137,597950
Average measured interrupt to process latency (µs): 1,984186
Highest measured interrupt to DPC latency (µs): 113,542365
Average measured interrupt to DPC latency (µs): 0,592230
_________________________________________________________________________________________________________
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): 101,476981
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,022908
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,029524
ISR count (execution time <250 µs): 385913
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): 1264,222675
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 364.72 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,018039
Driver with highest DPC total execution time: Wdf01000.sys - Runtime framework driver modalità kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,070284
DPC count (execution time <250 µs): 2324245
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 1
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: thunderbird.exe
Total number of hard pagefaults 49532
Hard pagefault count of hardest hit process: 30833
Highest hard pagefault resolution time (µs): 2562114,476668
Total time spent in hard pagefaults (%): 0,650749
Number of processes hit: 41
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 14,938050
CPU 0 ISR highest execution time (µs): 101,476981
CPU 0 ISR total execution time (s): 3,631556
CPU 0 ISR count: 383680
CPU 0 DPC highest execution time (µs): 1264,222675
CPU 0 DPC total execution time (s): 6,326299
CPU 0 DPC count: 1828717
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4,388314
CPU 1 ISR highest execution time (µs): 63,444723
CPU 1 ISR total execution time (s): 0,012791
CPU 1 ISR count: 2230
CPU 1 DPC highest execution time (µs): 161,021297
CPU 1 DPC total execution time (s): 0,144753
CPU 1 DPC count: 29448
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 5,136539
CPU 2 ISR highest execution time (µs): 34,273097
CPU 2 ISR total execution time (s): 0,000049
CPU 2 ISR count: 3
CPU 2 DPC highest execution time (µs): 160,119324
CPU 2 DPC total execution time (s): 0,207623
CPU 2 DPC count: 39459
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 7,703239
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): 182,604447
CPU 3 DPC total execution time (s): 1,997148
CPU 3 DPC count: 426623
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. 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:51:26 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: VALERIO-PC
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASRock, H97 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz
Logical processors: 4
Processor groups: 1
RAM: 8133 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3193 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): 137,597950
Average measured interrupt to process latency (µs): 1,984186
Highest measured interrupt to DPC latency (µs): 113,542365
Average measured interrupt to DPC latency (µs): 0,592230
_________________________________________________________________________________________________________
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): 101,476981
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,022908
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,029524
ISR count (execution time <250 µs): 385913
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): 1264,222675
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 364.72 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,018039
Driver with highest DPC total execution time: Wdf01000.sys - Runtime framework driver modalità kernel, Microsoft Corporation
Total time spent in DPCs (%) 0,070284
DPC count (execution time <250 µs): 2324245
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 1
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: thunderbird.exe
Total number of hard pagefaults 49532
Hard pagefault count of hardest hit process: 30833
Highest hard pagefault resolution time (µs): 2562114,476668
Total time spent in hard pagefaults (%): 0,650749
Number of processes hit: 41
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 14,938050
CPU 0 ISR highest execution time (µs): 101,476981
CPU 0 ISR total execution time (s): 3,631556
CPU 0 ISR count: 383680
CPU 0 DPC highest execution time (µs): 1264,222675
CPU 0 DPC total execution time (s): 6,326299
CPU 0 DPC count: 1828717
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4,388314
CPU 1 ISR highest execution time (µs): 63,444723
CPU 1 ISR total execution time (s): 0,012791
CPU 1 ISR count: 2230
CPU 1 DPC highest execution time (µs): 161,021297
CPU 1 DPC total execution time (s): 0,144753
CPU 1 DPC count: 29448
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 5,136539
CPU 2 ISR highest execution time (µs): 34,273097
CPU 2 ISR total execution time (s): 0,000049
CPU 2 ISR count: 3
CPU 2 DPC highest execution time (µs): 160,119324
CPU 2 DPC total execution time (s): 0,207623
CPU 2 DPC count: 39459
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 7,703239
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): 182,604447
CPU 3 DPC total execution time (s): 1,997148
CPU 3 DPC count: 426623
_________________________________________________________________________________________________________
and here the screenshots
i'm starting to think that is a nvidia driver issue. i'll tel you know new update after i will follow your advices.
thank you again.