PROBLEMA BSOD continui!

Pubblicità
U

Userro

Nuovo Utente
Messaggi
12
Reazioni
0
Punteggio
25
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?
 
Ultima modifica:
Userro ha detto:
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?
Clicca per espandere...

scarica whocrahed e posta la lettura del dmp grazie
 
Ecco qua:

Codice: 
[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dump directory: C:\WINDOWS\Minidump[/COLOR][/SIZE][/FONT]

[FONT=Segoe UI][SIZE=2][COLOR=#000000]Crash dumps are enabled on your computer.
[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Thu 18/02/2016 08:19:45 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\021816-20921-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800127B71C7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Thu 18/02/2016 08:19:45 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800127B71C7, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 17/02/2016 22:05:19 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\021716-8421-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=hal.dll"]hal.dll[/URL][/COLOR][/SIZE][/FONT] (hal!HalpNumaDynamicMemoryRanges PERF (hal+0x50a80)+0x0) 
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80245268A80, 0xFFFFD001BA8060C0, 0x0)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_SERVICE_EXCEPTION"]SYSTEM_SERVICE_EXCEPTION[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\hal.dll
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 17/02/2016 22:05:17 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\021716-12453-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Unknown"]Unknown[/URL][/COLOR][/SIZE][/FONT] () 
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]
A third party driver was identified as the probable root cause of this system error. 
Google query: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=CUSTOM_ERROR"]CUSTOM_ERROR[/URL][/COLOR][/SIZE][/FONT]


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 17/02/2016 22:01:58 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\021716-12296-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x50 (0xFFFFF8030E0E3801, 0x0, 0xFFFFF8031629C671, 0x2)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+PAGE_FAULT_IN_NONPAGED_AREA"]PAGE_FAULT_IN_NONPAGED_AREA[/URL][/COLOR][/SIZE][/FONT]
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Wed 17/02/2016 21:57:49 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\021716-11875-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=ntkrnlmp.exe"]ntkrnlmp.exe[/URL][/COLOR][/SIZE][/FONT] (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8020A2957EB, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+KMODE_EXCEPTION_NOT_HANDLED"]KMODE_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

- - - Updated - - -

Ulteriore crash:

Codice: 
 [FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Thu 18/02/2016 08:53:33 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\Minidump\021816-8937-01.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=hal.dll"]hal.dll[/URL][/COLOR][/SIZE][/FONT] (hal!HalpNumaDynamicMemoryRanges PERF (hal+0x50a80)+0x0) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8020B26AA80, 0xFFFFD00151D6F6F8, 0xFFFFD00151D6EF10)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\hal.dll
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 


[/COLOR][/SIZE][/FONT]
[FONT=Segoe UI][SIZE=2][COLOR=#000000][B]On Thu 18/02/2016 08:53:33 GMT your computer crashed[/B]
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=hal.dll"]hal.dll[/URL][/COLOR][/SIZE][/FONT] (hal!HalpNumaDynamicMemoryRanges PERF (hal+0x50a80)+0x0) 
Bugcheck code: 0x7E (0xFFFFFFFFC000001D, 0xFFFFF8020B26AA80, 0xFFFFD00151D6F6F8, 0xFFFFD00151D6EF10)
Error: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=MSDN+bugcheck+SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED[/URL][/COLOR][/SIZE][/FONT]
file path: C:\WINDOWS\system32\hal.dll
product: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System"]Microsoft® Windows® Operating System[/URL][/COLOR][/SIZE][/FONT]
company: [FONT=Segoe UI][SIZE=2][COLOR=#000000][URL="http://www.google.com/search?q=Microsoft%20Corporation"]Microsoft Corporation[/URL][/COLOR][/SIZE][/FONT]
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. 
[/COLOR][/SIZE][/FONT]

- - - Updated - - -

Nessuno sa darmi una mano? Potrebbero essere i driver della VGA? Dico così perché ogni tanto vedo degli artefatti grafici, sia in game che in windows (p.e. stanotte è crashato e quando sono andato a vedere ero nella schermata di login con *****te strane al posto del cursore.
Ho installato i driver ufficiali ATI 15.301.1801.1001-160203a-299101E.
 
Ultima modifica:
Tramite impostazioni prova ad affidare la grafica solo alla gpu, isolando la gpu interna della cpu. Guarda se funziona.
 
Pubblicità
Pubblicità
Indietro
Top