PROBLEMA PC Gaming/Audio crash improvviso (codice errore: 1 lungo, 2 brevi)

[Mr.Rubbei]

Ciao, ecco la mia build:

Asus Prime X470-Pro
AMD Ryzen 5 2600X
Arctic Freezer 33 eSports One
Corsair Vengeance LPX 4 x 8 GB 3200 MHz
WD Black NVMe 250 GB + Crucial MX500 500 GB + Seagate Barracuda 2 TB
Sapphire Nitro RX480 4 GB
Sharkoon SilentStorm Icewind Black 550W
Sharkoon TG5

Uso il PC principalmente per audio, ma gioco anche spesso, ultimamente sto giocando solo ad Apex Legends.
Da qualche settimana, quando metto a schermo intero un video su YouTube, per qualche secondo ho una schermata glitchata verde, dopo un po' se ne va. Vi ho messo uno screen come allegato.
Ieri e oggi mentre giocavo ad Apex mi è successo che mi crasha all'improvviso mentre sto in game, blue screen e si riavvia, il BIOS suona una volta lungo e due brevi -> _ . . codice che ho letto essere "1 Lungo, 2 Brevi - Indica un problema con la scheda video o con le memorie montate su di essa".

Non riesco a riavviare il PC quando succede questo, neanche dal pulsantino piccolo sul case. Devo spegnere e riaccendere, ieri l'ho spento e basta perché dovevo uscire. Oggi idem. Quindi 2 volte su 2, mentre giocavo ad Apex. E tra l'altro mi sembra scaldi leggermente più del solito, sempre zona CPU/GPU.

La scheda video l'ho presa usata da un utente su questo forum, inverno 2018, l'ho usata senza problemi (o quasi, a volte quando riavvio il PC le ventole accellerano al massimo per un secondo e poi si fermano - ma oltre questo nient'altro) fino ad ora, ovvero qualche settimana fa prima che comparissero questi problemi.

Vi dico per dovizia di particolari, che 2 banchi di RAM dei 4 che ho, li ho installati di recente, ma non mi hanno mai dato problemi fin'ora.

Come posso fare per monitorare e capire dove sia il problema? Grazie mille in anticipo!

 

[Mr.Rubbei]

no, nessuna forma strana. solo crash.

ok, ho installato tutti e 3. quale comando devo selezionare per verificare lo stato di salute della GPU (se è visibile in qualche modo)? Grazie. Screen di GPU-Z, se può esservi utile.

 

[Mr.Rubbei]

Eccone altri 2, questa volta mentre NON giocavo, ma facevo altre cose di lavoro.

On Tue 22/12/2020 19:19:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122220-9468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5780)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8067EC4EE84, 0xFFFFFD87B1867070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 22/12/2020 19:19:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: win32kfull.sys (win32kfull+0xE2EB4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8067EC4EE84, 0xFFFFFD87B1867070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 22/12/2020 15:18:17 your computer crashed or a problem was reported
crash dump file: C:\Windows\LiveKernelReports\PoW32kWatchdog-20201222-1518.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!IoUnregisterShutdownNotification+0xF84)
Bugcheck code: 0x1A1 (0xFFFFBC078E0C0040, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Mr.Rubbei]

ero su Premiere e ho avuto un momento di schermata nera, come quando riavii Explorer dal Task Manager. ho aperto il TM e ho ricollegato questo lag momentaneo ad un picco sulla 3D della GPU. niente di riparabile immagino.

 

[Mr.Rubbei]

WhoCrashed stavolta mi ha dato come colpevole del BSOD il driver di Intel Gigabit Adapter, ecco il log:

On Fri 25/12/2020 23:42:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122520-401843-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x2ec7)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF807778FA320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.



On Fri 25/12/2020 23:42:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: e1r68x64.sys (e1r68x64+0x1944f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF807778FA320)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\e1r68x64.sys
product: Intel(R) Gigabit Adapter
company: Intel Corporation
description: Intel(R) Gigabit Adapter NDIS 6.x driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: e1r68x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
Google query: e1r68x64.sys Intel Corporation DPC_WATCHDOG_VIOLATION

 

[Mr.Rubbei]

su un altro forum mi hanno fatto notare che, avendo sempre driver diversi nel BSOD, potrebbe essere un problema di PSU che non eroga bene potenza nei momenti più "carichi" (ho BSOD quando gioco, sempre, e a volte su Premiere, e ho schermate glitchate verdi quando metto a schermo intero qualsiasi video) verso la GPU.

dovrò fare un tentativo con un'altra GPU facendomela prestare da un amico così da cercare di isolare il problema e capire se con un'altra GPU ho ancora questi problemi.

in ogni caso, per un possibile/probabile upgrade di PSU, sapete darmi un consiglio? ecco la mia build, che trovate anche in firma:

Asus Prime X470-Pro
AMD Ryzen 5 2600X
Arctic Freezer 33 eSports One
Corsair Vengeance LPX 4 x 8 GB 3200 MHz
WD Black NVMe 250 GB + Crucial MX500 500 GB + Seagate Barracuda 500 GB
Sapphire Nitro RX480 4 GB
Sharkoon SilentStorm Icewind Black 550W
Sharkoon TG5

Vorrei prenderne uno veramente buono, modulare se possibile. Non ho un budget preciso, o meglio sono abbastanza elastico, quindi preferisco spendere un po' di più se conviene. vorrei tenere conto anche di un possibile (ma non certo) upgrade della GPU nVidia RTX 30xx in futuro, quindi più potenza da erogare in previsione. grazie!

 

[Mr.Rubbei]

ho effettuato un calcolo del power consumption con questo tool, ecco i risultati

 

[Mr.Rubbei]

ok, ho provato ad utilizzare OCCT per fare dei test.

ho scollegato tutto lo scollegabile dal pc, sono rimasto solo con CPU GPU RAM e tastiera e mouse (non quelli gaming soliti, un set wireless tranquillo)

non riesco neanche a tenere aperto OCCT senza fare il test, che già mi sono capitati 2 bsod.
la terza volta riesco ad avviarlo, ma solo per 10 secondi e mi trovava già più di 350 errori. che non ho fatto in tempo a vedere, per un altro bsod.

come faccio a analizzare gli errori trovati? grazie.

ecco i bsod:

On Sun 27/12/2020 21:34:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122720-8093-01.dmp
This was probably caused by the following module: ucx01000.sys (0xFFFFF80555592DE1)
Bugcheck code: 0xD1 (0x1DF9769EF3BA, 0x2, 0x0, 0xFFFFF80555592DE1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ucx01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Controller Extension
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 27/12/2020 21:34:37 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: usbxhci.sys (USBXHCI+0xB91C)
Bugcheck code: 0xD1 (0x1DF9769EF3BA, 0x2, 0x0, 0xFFFFF80555592DE1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbxhci.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver USB XHCI
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 27/12/2020 21:24:12 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122720-9328-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8076E6E823C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8076E6E823C, 0xFFFFB38741A041C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver file system NT
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Sun 27/12/2020 21:15:47 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\122720-10234-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8066DA3914F, 0xFFFF858BB91D8E40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_SERVICE_EXCEPTION

ed ecco uno screen di OCCT dopo 7 secondi e 10 errori

 

[Mr.Rubbei]

buon anno a tutti ragazzi :)

ho resettato le impostazioni di fabbrica nel BIOS e i frequenti BSOD sono scomparsi. ne ho avuto soltanto uno poco fa, stavolta con un errore di driver mai comparso prima. eccolo:

On Fri 01/01/2021 02:43:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010121-442250-01.dmp
This was probably caused by the following module: npfs.sys (0xFFFFF8022B98D118)
Bugcheck code: 0x50 (0xFFFF800F9BFFE808, 0x2, 0xFFFFF8022B98D118, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 01/01/2021 02:43:34 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x6B6)
Bugcheck code: 0x50 (0xFFFF800F9BFFE808, 0x2, 0xFFFFF8022B98D118, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Gestione filtri file system Microsoft
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

sapete dirmi qualcosa? grazie :)

 

[Mr.Rubbei]

up :)