[WIN10] BSOD continui!

[Userro]

Ciao a tutti, sto avendo grossissimi problemi con il mio fisso, problemi che si intensificano ogni giorno di più: BSOD continui che mi fanno crashare il sistema.

Ne ho appena avuti 4 sequenziali, ognuno con un codice di errore differente.

Facciamo il punto: come OS ho win10 build 11082 (insider preview), ho appena upgradato la RAM e la VGA, installando per quest'ultima i driver più aggiornati.
Ho fatto due volte un memtest senza che venissero riscontrati problemi alla RAM.

Tra i vari errori, ultimamente ho segnato questi:

• Cache Manager
• Page fault in non paged area
• Kmode exception not handled
• Kernel security check failure
• System service exception

Il sistema crashava anche prima di upgradare ma installati i nuovi componenti il problema si è ripresentato sempre più frequente.

Monto:
Gigabyte GA-770TA-UD3 aggiornata ad ultimo BIOS stabile
AMD Athlon II X4 630
Kingston HyperX Fury 2X4gb PC1600
XFX Radeon R9 380


Sinceramente non so cosa fare, voi che dite?

[tallines]

Originariamente inviato da Userro

Facciamo il punto: come OS ho win10 build 11082 (insider preview), ho appena upgradato la RAM e la VGA, installando per quest'ultima i driver più aggiornati.
Ho fatto due volte un memtest senza che venissero riscontrati problemi alla RAM.
Sinceramente non so cosa fare, voi che dite?

Ciao, queste bsod da quanto ti sono iniziare a uscire ?

Hai fatto qualcosa tipo scaricato qualcosa, fatto l' upgrade a qualcosa o.........ti sono comparse cosi all' all' improvviso ?

Prova a usare un punto di ripristino, a prima del problema .

[Userro]

Come ho scritto, ho rinnovato RAM e VGA, prima e ho quindi installato il driver della VGA (che ora è il ATI 15.301.1801.1001-160203a-299101E)
(non sono sicuro al 100%) avevo già avuto dei crash ma decisamente più rari.
Non sono in possesso di punti di ripristino, purtroppo.

Ho fatto alcune analisi con Whocrashed:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 18/02/2016 08:19:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021816-20921-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800127B71C7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Thu 18/02/2016 08:19:45 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800127B71C7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Wed 17/02/2016 22:05:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021716-8421-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpNumaDynamicMemoryRanges PERF (hal+0x50a80)+0x0) 
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80245268A80, 0xFFFFD001BA8060C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 Wed 17/02/2016 22:05:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021716-12453-01.dmp
This was probably caused by the following module: Unknown () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error. 
Google query: CUSTOM_ERROR



On Wed 17/02/2016 22:01:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021716-12296-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x50 (0xFFFFF8030E0E3801, 0x0, 0xFFFFF8031629C671, 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. 
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 17/02/2016 21:57:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021716-11875-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8020A2957EB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
On Thu 18/02/2016 08:53:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021816-8937-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpNumaDynamicMemoryRanges PERF (hal+0x50a80)+0x0) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8020B26AA80, 0xFFFFD00151D6F6F8, 0xFFFFD00151D6EF10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that a system thread 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 Thu 18/02/2016 08:53:33 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalpNumaDynamicMemoryRanges PERF (hal+0x50a80)+0x0) 
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF8020B26AA80, 0xFFFFD00151D6F6F8, 0xFFFFD00151D6EF10)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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.

[stefano25]

Controllerei l'hardware. Prova a far andare il pc con un solo modulo di ram, se non va provi l'altro.

[Userro]

Ho fatto memtest da bios dici che potrebbe comunque essere fallato?

[tallines]

Prova a disinstallare i driver della VGA, riavvii il pc e lasci installare a W10 i driver, nel senso non istallare tu i driver proprietari .

Vedi come si comporta il pc .

La tam testala con MemTest freeware, tre passaggi per banco .

Prima di testare la ram, a pc spento scollegala dagli alloggiamenti, pulisci la parte dorata con una gomma morbida, pulisci gli slot di alloggiamento o con un pennellino tipo quelli da disegno o con un aspirapolvere piccolo, come quelli per auto .

Poi inserisci un banco di ram alla volta, cambiandogli slot di alloggiamento .

Avvia il pc, vedi come si comporta il pc stesso e fai anche il MemTest dell' unico banco di ram con cui hai avviato il pc .

Cosi anche con gli altri banchi di ram che ha il pc .