Da qualche giorno ecco che iniziano anche per me le schermate blu di Vista, con la differenza che le mie sono quasi tutte a schermo completamente blu senza scritte, e quindi senza nemmeno un’ indicazione sulla causa. Tuttavia ultimamente mi sono comparse due schermate blu, questa volta però con delle scritte e che magari possono dare qualche indicazione; sospettando che si potesse trattare di un problema di driver (dato che spesso mi usciva un mex di errore del driver video che smetteva di funzionare e veniva automaticamente ripristinato) ho aggiornato i driver video e audio.
Riporto qui sotto l’analisi degli ultimi crash grazie al programma “WhoCrashed” (anche se l’orario dei crash non è esatto):

codice:
System Information (local) 
________________________________________

computer name: SCALEO-J
windows version: Windows Vista , 6.0, build: 6000
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 3.00GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 938278912 total
VM: 2147352576, free: 2014105600

________________________________________
Crash Dump Analysis 
________________________________________

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 21/10/2012 15.10.51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x50 (0xFFFFFFFFEC148001, 0x0, 0xFFFFFFFF9621201E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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. 
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: Unknown . 
Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA




On Sun 21/10/2012 14.17.21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102112-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8FC44) 
Bugcheck code: 0xD1 (0xFFFFFFFF96C528B2, 0x2, 0x0, 0xFFFFFFFF8A699221)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time. 


On Sat 20/10/2012 16.56.11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini102012-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0xC735D) 
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0x233D2BA5, 0xFFFFFFFF94C4A894, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.0 wrapper driver
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 which cannot be identified at this time. 


On Fri 19/10/2012 21.10.47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101912-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5EF21) 
Bugcheck code: 0xD1 (0xFFFFFFFFC946C2A8, 0x2, 0x1, 0xFFFFFFFF8B465F21)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time. 


On Thu 18/10/2012 16.15.06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101812-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x84C66) 
Bugcheck code: 0x50 (0xFFFFFFFF85A5F96F, 0x0, 0xFFFFFFFF84943C66, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Mon 15/10/2012 19.57.27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101512-02.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8FC44) 
Bugcheck code: 0xA (0x1EED69DC, 0x2, 0x0, 0xFFFFFFFF81827B9D)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 which cannot be identified at this time. 


On Sun 14/10/2012 22.40.43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101512-01.dmp
This was probably caused by the following module: volmgrx.sys (volmgrx+0x1479C) 
Bugcheck code: 0x50 (0xFFFFFFFF8B8048D4, 0x0, 0xFFFFFFFF8496175E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\volmgrx.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Volume Manager Extension 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 standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 


On Fri 12/10/2012 13.32.14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini101212-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x159AF) 
Bugcheck code: 0x48 (0xFFFFFFFF8B33B968, 0xFFFFFFFFFBAAF596, 0x0, 0x0)
Error: CANCEL_STATE_IN_COMPLETED_IRP
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an I/O request packet (IRP) was completed, and then was subsequently canceled.
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 which cannot be identified at this time. 


On Mon 01/10/2012 16.11.49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini100212-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x7986C) 
Bugcheck code: 0x117 (0xFFFFFFFF90F13258, 0xFFFFFFFF8B101814, 0x0, 0x0)
Error: VIDEO_TDR_TIMEOUT_DETECTED
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 the display driver failed to respond in a timely fashion. 
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 which cannot be identified at this time.
Dal momento che ho diversi programmi installati mi seccherebbe molto ricorrere alla formattazione, inoltre ho effettuato anche scansione con antvirus e programmi antimalware aggiornati, quindi spero che qualcuno possa darmi una mano..