Da un po' di tempo a questa parte, Windows 10 Pro 64bit mi si riavvia in momenti casuali.
Inizialmente credevo si trattasse della temperatura troppo alta della CPU (sale sopra gli 80° durante alcuni lavori che faccio abitualmente, tipo OCR e simili, e anche a 90° se lavoro su video), invece oggi è comparso lo BSOD mentre stavo soltanto passando alcuni file su chiavetta.
In ogni caso, prima dello BSOD di oggi, avevo fatto una pulizia con aria compressa.
WhoCrashed mi dice questo:
Questo il mio hardware:
CASE Cooler Master Elite 110
ALI Silverstone ST30SF
MOBO Gigabyte GA-F2A88XN-WIFI
CPU AMD A series A8-7600
RAM G.Skill F3-12800CL9S-4GBRL
HD crucial m500 120gb
FAN Noctua NH-L9a
Da qualche parte ho letto che può trattarsi di problema di driver grafico, per cui ho scaricato l'AMD minimal setup:
http://support.amd.com/en-us/download/apu?os=Windows 10 - 64
Ma mi dice che è già aggiornato.
Grazie per ogni informazione.
Inizialmente credevo si trattasse della temperatura troppo alta della CPU (sale sopra gli 80° durante alcuni lavori che faccio abitualmente, tipo OCR e simili, e anche a 90° se lavoro su video), invece oggi è comparso lo BSOD mentre stavo soltanto passando alcuni file su chiavetta.
In ogni caso, prima dello BSOD di oggi, avevo fatto una pulizia con aria compressa.
WhoCrashed mi dice questo:
Codice:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 08/03/2017 11:34:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030817-11953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803B866A439, 0xFFFFAC009E666B60, 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 Wed 08/03/2017 11:34:19 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kfull.sys (win32kfull!Win32AllocPoolWithQuotaImpl+0x31)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803B866A439, 0xFFFFAC009E666B60, 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 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 Thu 23/02/2017 13:08:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022317-11859-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFFB202BD731800, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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 Thu 16/02/2017 12:23:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021617-6046-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFFBB0C1396F800, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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 11/02/2017 12:11:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021117-6140-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFF9B0764979340, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.Questo il mio hardware:
CASE Cooler Master Elite 110
ALI Silverstone ST30SF
MOBO Gigabyte GA-F2A88XN-WIFI
CPU AMD A series A8-7600
RAM G.Skill F3-12800CL9S-4GBRL
HD crucial m500 120gb
FAN Noctua NH-L9a
Da qualche parte ho letto che può trattarsi di problema di driver grafico, per cui ho scaricato l'AMD minimal setup:
http://support.amd.com/en-us/download/apu?os=Windows 10 - 64
Ma mi dice che è già aggiornato.
Grazie per ogni informazione.
