Piccoli freeze durante uso del pc

[Blue_screen_of_death]

Sempre attorno a 900000 microsecondi? O più basse.
Disabilita da BIOS o scollegando i cavi i due hard disk meccanici.
Hanno prestazioni scadenti, probabilmente dovute all'usura.

[serpinu]

Originariamente inviato da Blue_screen_of_death

Sempre attorno a 900000 microsecondi? O più basse.
Disabilita da BIOS o scollegando i cavi i due hard disk meccanici.
Hanno prestazioni scadenti, probabilmente dovute all'usura.

si sempre su quelle cifre li anche più alte, come sempre via
Staccando i sata non mi si avvia il pc nonostante abbia l’ssd come boot primario.
“Reboot and select proper Boot Device”

[Blue_screen_of_death]

Non parte perché le informazioni di boot sono state installate su disco meccanico.

Scollega tutti i dischi meccanici e masterizzatori DVD (o disabilita da BIOS; come ti viene più comodo) lasciando collegato solo l'SSD.

Sei in UEFI/GPT? Se sì, segui questa procedura.

Avvia la console di ripristino di Windows e digita questi comandi

diskpart
list disk
select disk #disk (dove #disk è il numero del disco di sistema individuato dal comando precedente)
list partition
select partition #partition (dove #partition è il numero della partizione di sistema individuata dal comando precedente)
assign letter R:
exit
bcdboot R:\Windows /l it-IT /f UEFI

Riavvia e dovrebbe partire Windows.


Se invece sei in modalità BIOS/MBR la procedura è diversa, fammi sapere che la adatto.

[serpinu]

Originariamente inviato da Blue_screen_of_death

Non parte perché le informazioni di boot sono state installate su disco meccanico.

Scollega tutti i dischi meccanici e masterizzatori DVD (o disabilita da BIOS; come ti viene più comodo) lasciando collegato solo l'SSD.

Sei in UEFI/GPT? Se sì, segui questa procedura.

Avvia la console di ripristino di Windows e digita questi comandi

diskpart
list disk
select disk #disk (dove #disk è il numero del disco di sistema individuato dal comando precedente)
list partition
select partition #partition (dove #partition è il numero della partizione di sistema individuata dal comando precedente)
assign letter R:
exit
bcdboot R:\Windows /l it-IT /f UEFI

Riavvia e dovrebbe partire Windows.


Se invece sei in modalità BIOS/MBR la procedura è diversa, fammi sapere che la adatto.

Da dove lo posso vedere mi sembra di aver letto ieri una volta, per far partire la console devo far partire il disco di installazione giusto?
Edit: potrebbe essere questo il problema della latenza ?

[Blue_screen_of_death]

Originariamente inviato da serpinu

per far partire la console devo far partire il disco di installazione giusto?

Si.

Originariamente inviato da serpinu

Da dove lo posso vedere mi sembra di aver letto ieri una volta

Avvia la console di ripristino, apri il prompt dei comandi.

Esegui questi comandi

diskpart
list disk
exit


Individua l'SSD e guarda se sotto la colonna GPT c'è un simbolo di asterisco (*). Se sì, allora stai usando GPT, altrimenti MBR.

[serpinu]

Originariamente inviato da Blue_screen_of_death

Si.


Avvia la console di ripristino, apri il prompt dei comandi.

Esegui questi comandi

diskpart
list disk
exit


Individua l'SSD e guarda se sotto la colonna GPT c'è un simbolo di asterisco (*). Se sì, allora stai usando GPT, altrimenti MBR.

No il simbolo non c'è

[Blue_screen_of_death]

ok allora segui questa procedura, dopo aver scollegato tutti gli hard disk e masterizzatori DVD eccetto l'SSD.

diskpart
list disk
select disk #disk (mettendo al posto di #disk il numero del disco contenente Windows che ti viene restituito dal comando precedente)
list partition
select partition #partition (mettendo al posto di #partition il numero della partizione di Windows che ti viene restituito dal comando precedente)
assign letter R:
active
exit
bcdboot R:\Windows /l it-IT /s BIOS

Riavvia il PC e dovrebbe partire Windows.

Ripeti il test delle latenze senza ricollegare hard disk e masterizzatore.

[serpinu]

Originariamente inviato da Blue_screen_of_death

ok allora segui questa procedura, dopo aver scollegato tutti gli hard disk e masterizzatori DVD eccetto l'SSD.

diskpart
list disk
select disk #disk (mettendo al posto di #disk il numero del disco contenente Windows che ti viene restituito dal comando precedente)
list partition
select partition #partition (mettendo al posto di #partition il numero della partizione di Windows che ti viene restituito dal comando precedente)
assign letter R:
active
exit
bcdboot R:\Windows /l it-IT /s BIOS

Riavvia il PC e dovrebbe partire Windows.

Ripeti il test delle latenze senza ricollegare hard disk e masterizzatore.

Mi da errore BFSVC Error: Failed to set element application devices. Status = [c000000bb]
B.....ecc failed to populate BCD store c000000bb

[Blue_screen_of_death]

Esegui il comando dir R:\Windows
Dovresti vedere i file contenuti nella cartella Windows. Li vedi?

Se sì, allora esegui il comando bcdboot R:\Windows /l it-IT. Dà ancora errore?

Se no, allora la lettera di unità non è stata assegnata correttamente.

[serpinu]

Originariamente inviato da Blue_screen_of_death

Esegui il comando dir R:\Windows
Dovresti vedere i file contenuti nella cartella Windows. Li vedi?

Se sì, allora esegui il comando bcdboot R:\Windows /l it-IT. Dà ancora errore?

Se no, allora la lettera di unità non è stata assegnata correttamente.

Creazione dei file di avvio completato
Partito
ecco il report:
https://ibb.co/mXnLczD
_________________________________________________________________________________________________________
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:03:15 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-9P086B6
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16300 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3693 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.

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): 108,80
Average measured interrupt to process latency (µs): 4,045279

Highest measured interrupt to DPC latency (µs): 106,60
Average measured interrupt to DPC latency (µs): 1,675250


_________________________________________________________________________________________________________
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): 24,766856
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,000464
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0,000469

ISR count (execution time <250 µs): 2293
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): 793463,206336
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

Highest reported total DPC routine time (%): 1,001107
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Total time spent in DPCs (%) 1,418962

DPC count (execution time <250 µs): 17391894
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
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: msmpeng.exe

Total number of hard pagefaults 5466
Hard pagefault count of hardest hit process: 1285
Number of processes hit: 50


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 19,235075
CPU 0 ISR highest execution time (µs): 24,766856
CPU 0 ISR total execution time (s): 0,010296
CPU 0 ISR count: 1658
CPU 0 DPC highest execution time (µs): 137,981045
CPU 0 DPC total execution time (s): 13,895377
CPU 0 DPC count: 3906653
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 14,815018
CPU 1 ISR highest execution time (µs): 12,363390
CPU 1 ISR total execution time (s): 0,004344
CPU 1 ISR count: 630
CPU 1 DPC highest execution time (µs): 58,119957
CPU 1 DPC total execution time (s): 8,559294
CPU 1 DPC count: 5414370
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6,029782
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): 601750,251828
CPU 2 DPC total execution time (s): 4,332340
CPU 2 DPC count: 1347388
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 5,885337
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): 55,414839
CPU 3 DPC total execution time (s): 3,151130
CPU 3 DPC count: 1328125
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 5,971171
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): 793463,206336
CPU 4 DPC total execution time (s): 4,114082
CPU 4 DPC count: 1350197
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 5,993154
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): 38,883563
CPU 5 DPC total execution time (s): 3,298644
CPU 5 DPC count: 1347787
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 6,255519
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): 285,069320
CPU 6 DPC total execution time (s): 3,299613
CPU 6 DPC count: 1353376
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 5,890673
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): 387090,167885
CPU 7 DPC total execution time (s): 3,587820
CPU 7 DPC count: 1334017
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,944871
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): 42,470349
CPU 8 DPC total execution time (s): 0,007742
CPU 8 DPC count: 2295
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,957530
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): 41,378283
CPU 9 DPC total execution time (s): 0,004210
CPU 9 DPC count: 965
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,266696
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): 134,494449
CPU 10 DPC total execution time (s): 0,015711
CPU 10 DPC count: 2713
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1,013326
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): 27,311671
CPU 11 DPC total execution time (s): 0,000911
CPU 11 DPC count: 196
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 1,185312
CPU 12 ISR highest execution time (µs): 1,021933
CPU 12 ISR total execution time (s): 0,000003
CPU 12 ISR count: 4
CPU 12 DPC highest execution time (µs): 38,873545
CPU 12 DPC total execution time (s): 0,009306
CPU 12 DPC count: 1872
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 1,080466
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 37,320607
CPU 13 DPC total execution time (s): 0,001235
CPU 13 DPC count: 185
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 1,255887
CPU 14 ISR highest execution time (µs): 1,262388
CPU 14 ISR total execution time (s): 0,000001
CPU 14 ISR count: 1
CPU 14 DPC highest execution time (µs): 40,236122
CPU 14 DPC total execution time (s): 0,009124
CPU 14 DPC count: 1415
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 1,246763
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 38,653128
CPU 15 DPC total execution time (s): 0,002773
CPU 15 DPC count: 345
_________________________________________________________________________________________________________

[Blue_screen_of_death]

Perfetto, come sono le latenze staccando tutte le periferiche SATA compreso il masterizzatore?

[serpinu]

Originariamente inviato da Blue_screen_of_death

Perfetto, come sono le latenze staccando tutte le periferiche SATA compreso il masterizzatore?

mi sembrano sempre alte
https://ibb.co/mXnLczD

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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-9P086B6
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: ASUSTeK COMPUTER INC., PRIME X470-PRO
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16300 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3693 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.

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): 108,80
Average measured interrupt to process latency (µs): 4,045279

Highest measured interrupt to DPC latency (µs): 106,60
Average measured interrupt to DPC latency (µs): 1,675250


_________________________________________________________________________________________________________
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): 24,766856
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,000464
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0,000469

ISR count (execution time <250 µs): 2293
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): 793463,206336
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

Highest reported total DPC routine time (%): 1,001107
Driver with highest DPC total execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Total time spent in DPCs (%) 1,418962

DPC count (execution time <250 µs): 17391894
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
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: msmpeng.exe

Total number of hard pagefaults 5466
Hard pagefault count of hardest hit process: 1285
Number of processes hit: 50


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 19,235075
CPU 0 ISR highest execution time (µs): 24,766856
CPU 0 ISR total execution time (s): 0,010296
CPU 0 ISR count: 1658
CPU 0 DPC highest execution time (µs): 137,981045
CPU 0 DPC total execution time (s): 13,895377
CPU 0 DPC count: 3906653
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 14,815018
CPU 1 ISR highest execution time (µs): 12,363390
CPU 1 ISR total execution time (s): 0,004344
CPU 1 ISR count: 630
CPU 1 DPC highest execution time (µs): 58,119957
CPU 1 DPC total execution time (s): 8,559294
CPU 1 DPC count: 5414370
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6,029782
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): 601750,251828
CPU 2 DPC total execution time (s): 4,332340
CPU 2 DPC count: 1347388
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 5,885337
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): 55,414839
CPU 3 DPC total execution time (s): 3,151130
CPU 3 DPC count: 1328125
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 5,971171
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): 793463,206336
CPU 4 DPC total execution time (s): 4,114082
CPU 4 DPC count: 1350197
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 5,993154
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): 38,883563
CPU 5 DPC total execution time (s): 3,298644
CPU 5 DPC count: 1347787
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 6,255519
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): 285,069320
CPU 6 DPC total execution time (s): 3,299613
CPU 6 DPC count: 1353376
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 5,890673
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): 387090,167885
CPU 7 DPC total execution time (s): 3,587820
CPU 7 DPC count: 1334017
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 0,944871
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): 42,470349
CPU 8 DPC total execution time (s): 0,007742
CPU 8 DPC count: 2295
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 0,957530
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): 41,378283
CPU 9 DPC total execution time (s): 0,004210
CPU 9 DPC count: 965
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 1,266696
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): 134,494449
CPU 10 DPC total execution time (s): 0,015711
CPU 10 DPC count: 2713
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 1,013326
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): 27,311671
CPU 11 DPC total execution time (s): 0,000911
CPU 11 DPC count: 196
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 1,185312
CPU 12 ISR highest execution time (µs): 1,021933
CPU 12 ISR total execution time (s): 0,000003
CPU 12 ISR count: 4
CPU 12 DPC highest execution time (µs): 38,873545
CPU 12 DPC total execution time (s): 0,009306
CPU 12 DPC count: 1872
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 1,080466
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 37,320607
CPU 13 DPC total execution time (s): 0,001235
CPU 13 DPC count: 185
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 1,255887
CPU 14 ISR highest execution time (µs): 1,262388
CPU 14 ISR total execution time (s): 0,000001
CPU 14 ISR count: 1
CPU 14 DPC highest execution time (µs): 40,236122
CPU 14 DPC total execution time (s): 0,009124
CPU 14 DPC count: 1415
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 1,246763
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 38,653128
CPU 15 DPC total execution time (s): 0,002773
CPU 15 DPC count: 345

[Blue_screen_of_death]

Si, ancora alte.

Credo che abbiamo provato di tutto.
L'hardware è ottimizzato come si vede dal benchmark, driver aggiornati, cambiato il timer di sistema, disattivato il risparmio energetico.

Secondo me conviene installare una build vecchia di Windows, almeno per capire se il problema è stato introdotto con qualche aggiornamento.

Durante l'installazione ricordati di disconnetterti da Internet, per evitare che Windows cerca e installa automaticamente gli aggiornamenti.

Se riesci a trovare una vecchia build che non ha problemi di latenze, puoi tenere quella (almeno temporaneamente) e segnalare a Microsoft il tuo problema. E quindi potrai attendere che il problema venga risolto prima di aggiornare nuovamente.


Hai aperto questo thread in data 3 ottobre. Da quanto tempo avevi questo problema? Così scegliamo una build rilasciata prima.

[serpinu]

Originariamente inviato da Blue_screen_of_death

Si, ancora alte.

Credo che abbiamo provato di tutto.
L'hardware è ottimizzato come si vede dal benchmark, driver aggiornati, cambiato il timer di sistema, disattivato il risparmio energetico.

Secondo me conviene installare una build vecchia di Windows, almeno per capire se il problema è stato introdotto con qualche aggiornamento.

Durante l'installazione ricordati di disconnetterti da Internet, per evitare che Windows cerca e installa automaticamente gli aggiornamenti.

Se riesci a trovare una vecchia build che non ha problemi di latenze, puoi tenere quella (almeno temporaneamente) e segnalare a Microsoft il tuo problema. E quindi potrai attendere che il problema venga risolto prima di aggiornare nuovamente.


Hai aperto questo thread in data 3 ottobre. Da quanto tempo avevi questo problema? Così scegliamo una build rilasciata prima.

io penso quella vecchia 1700 e qualcosa perchè la 1803 da lo stesso problema

[Blue_screen_of_death]

Quindi le release rilasciate nel 2017?

https://tb.rg-adguard.net/public.php

Comunque si, puoi provare ad installare una release del 2017 e installare gli aggiornamenti un po' per volta finché non individui l'aggiornamento che crea problemi.

E sperare che almeno le vecchie release non danno problemi.

Forse l'unica cosa che è rimasta non testata è la scheda video. Non ti ho chiesto di provarne un'altra perché immagino che tu non ne abbia altre. Ma se ce l'hai allora prova a sostituirla.

[serpinu]

Originariamente inviato da Blue_screen_of_death

Quindi le release rilasciate nel 2017?

https://tb.rg-adguard.net/public.php

Comunque si, puoi provare ad installare una release del 2017 e installare gli aggiornamenti un po' per volta finché non individui l'aggiornamento che crea problemi.

E sperare che almeno le vecchie release non danno problemi.

Forse l'unica cosa che è rimasta non testata è la scheda video. Non ti ho chiesto di provarne un'altra perché immagino che tu non ne abbia altre. Ma se ce l'hai allora prova a sostituirla.

provo con una build vecchia se mi da lo stesso problema allora penso anche alla scheda video, si ne ho una vecchia da un 1gb ahaha

[Blue_screen_of_death]

Originariamente inviato da serpinu

provo con una build vecchia se mi da lo stesso problema allora penso anche alla scheda video, si ne ho una vecchia da un 1gb ahaha

ok, se non si risolve né con una vecchia build né con il cambio di scheda video allora resta sempre valido il suggerimento di Nicodemo Timoteo Taddeo a pagina 11

Originariamente inviato da Nicodemo Timoteo Taddeo

Comunque è il problema più strano che io abbia mai visto.

[serpinu]

Originariamente inviato da Blue_screen_of_death

ok, se non si risolve né con una vecchia build né con il cambio di scheda video allora resta sempre valido il suggerimento di Nicodemo Timoteo Taddeo a pagina 11



Comunque è il problema più strano che io abbia mai visto.

ma più che altro non diminuisce nemmeno..

[Blue_screen_of_death]

Ricordati di staccare internet mentre installi Windows per evitare che vengono installati gli aggiornamenti.

E testa le latenze subito dopo l'installazione, prima di installare ogni cosa o di eseguire gli aggiornamenti.

[serpinu]

Originariamente inviato da Blue_screen_of_death

Ricordati di staccare internet mentre installi Windows per evitare che vengono installati gli aggiornamenti.

E testa le latenze subito dopo l'installazione, prima di installare ogni cosa o di eseguire gli aggiornamenti.

Provato ora con la build 1703 e niente latenze alte ugualmente quindi non ne ho idea ho anche disinstallato il driver della scheda video infatti nella gestione dispositivi mi fa vedere scheda generica Microsoft