-

[Risolto] Improvvisi BSOD [Win 10 64bit]

#1
Buongiorno (e buone feste),

Da ieri il mio computer ha iniziato a lanciare BSOD a intervalli molto variabili (parlo dai 5 min dall'accensione a delle ore intere) in assenza di alcuna modifica sia software che hardware fatta al sistema.

Ho controllato gli aggiornamenti automatici di windows ma non risulta nessun update dal 03/12

Problemi simili li ho avuti quando mi è morto il mio povero vecchio HDD ma è successo meno di un mese fa e da allora ho reinstallato windows su un nuovo HDD.

Ho scaricato WhoCrashes e questo è quanto:

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 09/12/2017 11:14:24 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120917-31140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8016E485370, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 09/12/2017 11:14:24 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal+0x34C6)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8016E485370, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard 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 Sat 09/12/2017 10:28:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120917-30156-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x689F)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802CFB9689F, 0x0, 0x10)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 standard 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 Sat 09/12/2017 10:24:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120917-30062-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x3F7A4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFF81C8805DF7A4, 0xFFFF8A029F05F1C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver kernel Win32k di base
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 standard 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 Sat 09/12/2017 00:35:59 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120917-29125-01.dmp
This was probably caused by the following module: fvevol.sys (fvevol+0x344B0)
Bugcheck code: 0x1A (0x61941, 0xFFFFF808286344B0, 0x9, 0xFFFFA8812DE7F2F0)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\fvevol.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: BitLocker Drive Encryption Driver
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard 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.







Da quel poco che ne capisco sembra possibile ci sia un driver che sta creando i problemi, sarebbe possibile risalire a quale? (Sfortunatamente non ho installato periferiche nuove di recente quindi non posso andare ad ovvia esclusione, inoltre non ho nemmeno eseguito update di recente di nessun driver)

Nello specifico il sistema è questo:

Windows 10 64bit Pro
MoBo: Asrock B150A-X1
Processore: Intel i5-6400 6th Gen
RAM: 2x 4GB DDR4
Scheda Video: AMD Radeon RX 480 8GB
HDD: WD Blue 1TB
 

lionx08

Utente Attivo
2,155
532
Hardware Utente
CPU
7600K
Dissipatore
CRYORIG H5
Scheda Madre
GIGABYTE Z170 HD3P
Hard Disk
SAMSUNG 960 EVO 500GB, HDD 3TB GREEN
RAM
CORSAIR VENGEANCE LPX KIT 16GB
Scheda Video
RX470 ( con frequenze della 570)
Scheda Audio
ASUS XONAR XT
Monitor
SAMSUNG CF24F390 FREESYNC
Alimentatore
XFX TS 550W
Case
ANTEC P100
Periferiche
RAZER BLACKWIDOW ULTIMATE, RAZER IMPERATOR 2012, RAZER KRAKEN PRO V2, SUPERLUX HD681 EVO BK
Sistema Operativo
windows 10 FCU
#2
@Winthorp Darkrites Inizia a controllare l'integrità del file system:
-prompt(admin) :
sfc /scannow
-Integrità immagine di windows :
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /RestoreHealth
- integrità hard-drive:
lettere del drive: chkdsk /r /f
- integrità memorie ram:
https://www.memtest86.com/
- Controlla i driver se ci sono tutti con:
http://www.nirsoft.net/utils/driverview.html
e
https://www.iobit.com/it/driver-booster.php
Nel caso aggiorna tutto e controlla anche da gestione dispositivi.
Altrimenti reinstallazione in place mantenendo i file.
 
Ultima modifica:
Mi Piace: Winthorp Darkrites

Federico83

UTENTE LEGGENDARIO
35,157
6,152
Hardware Utente
CPU
Intel 3570k @4.200
Scheda Madre
AsRock Z77 Extreme4
Hard Disk
4.5TB + 7 di NAS lol
RAM
16 GB G.Skill 2133
Scheda Video
AMD R9 290 TRI-X
Monitor
IIyama 28" 4K
Alimentatore
Cooler Master GX 650
Case
Corsair 600T
Sistema Operativo
Windows10x64pro
#3
secondo me sono problemi alla scheda video...
 
#4
Spero di no, è relativamente nuova, presa a fine 2016, però si sa che a volte succede...

Cmq non saprei ho fatto quanto suggerito liox e non ho trovato errori in Windows
Di driver da aggiornare ce n'erano parecchi e veramente datati, ma già quando ho iniziato ad usare Driver Booster il pc aveva smesso i crash, da svariati giorni non ho visto un BSoD, andati via come sono venuti.

Grazie cmq del supporto ^^'
 
Mi Piace: lionx08

Discussioni Simili


Entra