PROBLEMA Blocchi e Crash in gioco

[ettorefiltek2000]

Come riassunto in titolo,il computer presenta spesso la seguente problematica,principalmente in gioco:mi è infatti accaduto più di una volta che,dopo circa un'ora di gioco,il computer si bloccasse sull'ultimo frame rappresentato del videogioco,cominciando a riprodurre un suono continuo e distorto;una volta caduto in questa situazione,il computer non risponde ad alcun comando,e l'unica soluzione disponibile sembra essere un riavvio.

Il fenomeno si è presentato,a quanto ricordo,solamente in gioco,ma non so se altri programmi particolarmente pesanti possano causare il medesimo problema.

Vedendo come si è presentato ho subito pensato ad una problematica legata alle RAM,ma ho preferito chiedere qui per sentire le opinioni di persone più esperte.

Nel caso servisse,questa è la mia configurazione:
Processore:AMD FX 8320;
Scheda Madre:Gigabyte Ga-990XA-UD3;
RAM:Kingston HyperX Fury,DDR3,1866 MHz,2x4Gb;
Scheda Video:Nvidia GeForce GTX 970;
Dischi:Samsung 860 EVO,256 GB;
Western Digital Caviar Blue,1TB;
Alimentatore:Antec HCG620,620 Watt.

Grazie in anticipo e ciao.

 

[Pandaemonio]

installa msi afterburner e attiva l'overlay, in pratica accedi ai grafici e spunta "mostra in tempo reale" le temperatura della GPU e della CPU. Metti anche la percentuale di utilizzo della CPU e della RAM. Vai in gioco e guarda cosa succede, potrebbe crashare per temperature troppo alte o semplicemente il processore non ce la fa. Se è tutto nella norma potrebbe essere la ram. Il gioco lo hai su ssd o hdd? Prova a spostarlo e vedi se anche sull'altro succede la stessa cosa. Hai per caso attivo l'overclock? Se così fosse disattivalo e prova senza.

 

[ettorefiltek2000]

Grazie mille per la risposta ed i consigli.Mi dispiace di aver accumulato così tanti ritardo nel rispondere,ma purtroppo non ho avuto modo di toccare il computer negli ultimi giorni.

In qualsiasi caso,oggi ho provato ad utilizzare Afterburner,ed il problema non si è presentato in più di un'ora di gioco.Le temperature di CPU e GPU mi sono poi sembrate abbastanza nella norma,quasi sempre fra i 60 ed i 70 gradi.L'unica cosa che mi ha lasciato perplesso è stata la percentuale d'utilizzo del processore,che è stata quasi sempre inferiore al 50%;non saprei che cosa dedurre,forse si tratta solamente dell'ottimizzazione del gioco.

Tutto ciò mi fa comunque pensare sempre più che il problema sia legato alle RAM,credo che proverò ad effettuare un test con Memtest86.

 

[Pandaemonio]

È normale che il processore abbia percentuali basse, pochi giochi lo sfruttano, ad alte risoluzioni poi grava tutto sulla GPU.

 

[Syndrome87]

Grazie mille per la risposta ed i consigli.Mi dispiace di aver accumulato così tanti ritardo nel rispondere,ma purtroppo non ho avuto modo di toccare il computer negli ultimi giorni.

In qualsiasi caso,oggi ho provato ad utilizzare Afterburner,ed il problema non si è presentato in più di un'ora di gioco.Le temperature di CPU e GPU mi sono poi sembrate abbastanza nella norma,quasi sempre fra i 60 ed i 70 gradi.L'unica cosa che mi ha lasciato perplesso è stata la percentuale d'utilizzo del processore,che è stata quasi sempre inferiore al 50%;non saprei che cosa dedurre,forse si tratta solamente dell'ottimizzazione del gioco.

Tutto ciò mi fa comunque pensare sempre più che il problema sia legato alle RAM,credo che proverò ad effettuare un test con Memtest86.

Il fatto che spesso ti accada dopo un ora di gioco non mi fa pensare ad un problema hardware. Prova a fare qualche benchmark pesante e lascialo lavorare per un oretta e mezza e guarda come si comporta. Potrebbe anche essere un rallentamento nel sistema operativo causato da qualcosa. Scarica Latencymonitor e testa la tua latenza e posta i risultati

Inviato da SM-J415FN tramite App ufficiale di Tom\'s Hardware Italia Forum

 

[ettorefiltek2000]

Con "Latencymonitor" intendi "Latencymon" di Resplendence Software?

Comunque ho provato a scaricarlo,ed il test sta procedendo senza problemi.Sottolineo che lo sto effettuando senza alcun gioco o processo particolarmente pesante attivo,nel caso possa influire.

Un'ultima cosa,il test dovrebbe essere lasciato procedere per qualche mezz'ora?

 

[ettorefiltek2000]

Mi scuso,come al solito,per i ritardi nelle risposte,ma il tempo a disposizione non è mai parecchio.

Ho provato ad effettuare un test con "Latencymon",lasciandolo procedere per circa un'ora e mezza,ed effettivamente i risultati non sono stati fra i più rassicuranti.Qui sotto copio ciò che è risultato dal processo:

"
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 1:20:57 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: COMPUTO
OS version: Windows 10 , 10.0, build: 17763 (x64)
Hardware: Gigabyte Technology Co., Ltd., 990XA-UD3
CPU: AuthenticAMD AMD FX(tm)-8320 Eight-Core Processor
Logical processors: 8
Processor groups: 1
RAM: 8152 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3516 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): 917,90
Average measured interrupt to process latency (µs): 12,462592

Highest measured interrupt to DPC latency (µs): 862,0
Average measured interrupt to DPC latency (µs): 4,089516


_________________________________________________________________________________________________________
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): 229,513652
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,053512
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,059401

ISR count (execution time <250 µs): 1208446
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): 1196,041809
Driver with highest DPC routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Highest reported total DPC routine time (%): 0,060213
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%) 0,177186

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

Total number of hard pagefaults 34917
Hard pagefault count of hardest hit process: 4854
Number of processes hit: 144


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 294,127042
CPU 0 ISR highest execution time (µs): 229,513652
CPU 0 ISR total execution time (s): 22,745762
CPU 0 ISR count: 1120043
CPU 0 DPC highest execution time (µs): 1196,041809
CPU 0 DPC total execution time (s): 66,241282
CPU 0 DPC count: 9773890
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 133,732629
CPU 1 ISR highest execution time (µs): 184,721274
CPU 1 ISR total execution time (s): 0,221853
CPU 1 ISR count: 21307
CPU 1 DPC highest execution time (µs): 766,074516
CPU 1 DPC total execution time (s): 0,638859
CPU 1 DPC count: 34278
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 135,337838
CPU 2 ISR highest execution time (µs): 98,029579
CPU 2 ISR total execution time (s): 0,018739
CPU 2 ISR count: 8549
CPU 2 DPC highest execution time (µs): 477,023606
CPU 2 DPC total execution time (s): 0,33630
CPU 2 DPC count: 23098
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 142,328012
CPU 3 ISR highest execution time (µs): 56,152446
CPU 3 ISR total execution time (s): 0,009782
CPU 3 ISR count: 6182
CPU 3 DPC highest execution time (µs): 341,853811
CPU 3 DPC total execution time (s): 0,086637
CPU 3 DPC count: 7738
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 139,220743
CPU 4 ISR highest execution time (µs): 56,236348
CPU 4 ISR total execution time (s): 0,029230
CPU 4 ISR count: 16667
CPU 4 DPC highest execution time (µs): 350,288680
CPU 4 DPC total execution time (s): 0,927374
CPU 4 DPC count: 60830
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 148,328992
CPU 5 ISR highest execution time (µs): 24,528441
CPU 5 ISR total execution time (s): 0,006780
CPU 5 ISR count: 4712
CPU 5 DPC highest execution time (µs): 224,953925
CPU 5 DPC total execution time (s): 0,086529
CPU 5 DPC count: 6285
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 117,779974
CPU 6 ISR highest execution time (µs): 65,447383
CPU 6 ISR total execution time (s): 0,020879
CPU 6 ISR count: 11221
CPU 6 DPC highest execution time (µs): 314,779579
CPU 6 DPC total execution time (s): 0,458649
CPU 6 DPC count: 30430
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 126,215590
CPU 7 ISR highest execution time (µs): 67,023606
CPU 7 ISR total execution time (s): 0,029666
CPU 7 ISR count: 19765
CPU 7 DPC highest execution time (µs): 211,939135
CPU 7 DPC total execution time (s): 0,077348
CPU 7 DPC count: 7236
_________________________________________________________________________________________________________"

Spero che possa esservi utile a comprendere meglio la natura del problema.

Grazie in anticipo e ciao.

 

[ettorefiltek2000]

Sono poi finalmente riuscito ad effettuare un test alle RAM con Memtest86,il quale risultato non ha fatto altro che disorientarmi maggiormente.

Ecco,infatti,quello che è uscito dai quattro benchmarks effettuati dal programma:


Nell'ultimo dei benchmark è stato riscontrato un errore,il che farebbe quindi pensare ad una problematica alle RAM.Anche i risultati del test di latenza non sono però stati rosei.Non so veramente più che cosa pensare,spero voi riusciate a dedurre qualcosa da questi dati.

Grazie in anticipo e ciao.

 

[ettorefiltek2000]

Capisco di non essere stato molto costante nel rispondere,e mi scuso per questo,ma qualcuno riesce ad interpretare i risultati dei vari test?

 

[Syndrome87]

Mi scuso,come al solito,per i ritardi nelle risposte,ma il tempo a disposizione non è mai parecchio.

Ho provato ad effettuare un test con "Latencymon",lasciandolo procedere per circa un'ora e mezza,ed effettivamente i risultati non sono stati fra i più rassicuranti.Qui sotto copio ciò che è risultato dal processo:

"
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 1:20:57 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: COMPUTO
OS version: Windows 10 , 10.0, build: 17763 (x64)
Hardware: Gigabyte Technology Co., Ltd., 990XA-UD3
CPU: AuthenticAMD AMD FX(tm)-8320 Eight-Core Processor
Logical processors: 8
Processor groups: 1
RAM: 8152 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3516 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): 917,90
Average measured interrupt to process latency (µs): 12,462592

Highest measured interrupt to DPC latency (µs): 862,0
Average measured interrupt to DPC latency (µs): 4,089516


_________________________________________________________________________________________________________
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): 229,513652
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,053512
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,059401

ISR count (execution time 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): 1196,041809
Driver with highest DPC routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Highest reported total DPC routine time (%): 0,060213
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%) 0,177186

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

Total number of hard pagefaults 34917
Hard pagefault count of hardest hit process: 4854
Number of processes hit: 144


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 294,127042
CPU 0 ISR highest execution time (µs): 229,513652
CPU 0 ISR total execution time (s): 22,745762
CPU 0 ISR count: 1120043
CPU 0 DPC highest execution time (µs): 1196,041809
CPU 0 DPC total execution time (s): 66,241282
CPU 0 DPC count: 9773890
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 133,732629
CPU 1 ISR highest execution time (µs): 184,721274
CPU 1 ISR total execution time (s): 0,221853
CPU 1 ISR count: 21307
CPU 1 DPC highest execution time (µs): 766,074516
CPU 1 DPC total execution time (s): 0,638859
CPU 1 DPC count: 34278
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 135,337838
CPU 2 ISR highest execution time (µs): 98,029579
CPU 2 ISR total execution time (s): 0,018739
CPU 2 ISR count: 8549
CPU 2 DPC highest execution time (µs): 477,023606
CPU 2 DPC total execution time (s): 0,33630
CPU 2 DPC count: 23098
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 142,328012
CPU 3 ISR highest execution time (µs): 56,152446
CPU 3 ISR total execution time (s): 0,009782
CPU 3 ISR count: 6182
CPU 3 DPC highest execution time (µs): 341,853811
CPU 3 DPC total execution time (s): 0,086637
CPU 3 DPC count: 7738
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 139,220743
CPU 4 ISR highest execution time (µs): 56,236348
CPU 4 ISR total execution time (s): 0,029230
CPU 4 ISR count: 16667
CPU 4 DPC highest execution time (µs): 350,288680
CPU 4 DPC total execution time (s): 0,927374
CPU 4 DPC count: 60830
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 148,328992
CPU 5 ISR highest execution time (µs): 24,528441
CPU 5 ISR total execution time (s): 0,006780
CPU 5 ISR count: 4712
CPU 5 DPC highest execution time (µs): 224,953925
CPU 5 DPC total execution time (s): 0,086529
CPU 5 DPC count: 6285
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 117,779974
CPU 6 ISR highest execution time (µs): 65,447383
CPU 6 ISR total execution time (s): 0,020879
CPU 6 ISR count: 11221
CPU 6 DPC highest execution time (µs): 314,779579
CPU 6 DPC total execution time (s): 0,458649
CPU 6 DPC count: 30430
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 126,215590
CPU 7 ISR highest execution time (µs): 67,023606
CPU 7 ISR total execution time (s): 0,029666
CPU 7 ISR count: 19765
CPU 7 DPC highest execution time (µs): 211,939135
CPU 7 DPC total execution time (s): 0,077348
CPU 7 DPC count: 7236
_________________________________________________________________________________________________________"

Spero che possa esservi utile a comprendere meglio la natura del problema.

Grazie in anticipo e ciao.

Rieffettua il test sulle ram e controlla se ci risono errori. In oltre dal tuo test con latencymon sembra che i tuoi driver video abbiano qualche problema. Scaricati il software DDU che disinstalla correttamente ogni driver sul pc e appunto elimini il tuo driver video (Nvidia, amd o intel) facendo la procedura pulisci e riavvia. Successivamente al riavvio vai sul sito Nvidia o amd (dipende dalla tua scheda video) e scarichi il driver più recente e lo installi

Inviato da SM-J415FN tramite App ufficiale di Tom\'s Hardware Italia Forum