PROBLEMA BSOD continui

Pubblicità
Famoso bug del bios in combo con HWmonitor. Ignora quella temp. Non e' quello il problema.

Piuttosto e' la tensione del 12V a essere tutta sbagliata, ma e' un noto bug di quel programma anche quello.
 
Non saprei che dirti.

Se hai gia' fatto un memtest86,

e formattato > reinstallato windows,

bisognera' andare a esclusione per trovare qual'e' il componente hardware che da' problemi.
 
È un errore generico;
Prova a farti prestare un pc non più usato, ma con socket compatibile, da qualcuno e prova ad esclusione ogni combinazione hardware...
 
maxtheduke ha detto:
Overclock di qualcosa? Il bsod avviene totalmente random o in qualche momento particolare?


Inviato da Tapatalk
Clicca per espandere...
Non ho nulla in oc, ma c'è abilitata di default da BIOS l'opzione turbo 50 che credo lo faccia in automatico in caso di necessità

I bsod Sono del tutto casuali. Potrei dire che avvengono frequentemente quando gioco, ma non vorrei che fosse solo perché spesso quando il PC è acceso è perché gioco.
(Anche se non ricordo di bsod durante film o serie tv)

Inviato da Nexus 5 tramite App ufficiale di Tom\\\'s Hardware Italia Forum
 
prova a disabilitare turbo 50, poi fai dei stress test con kombustor e prime95 o simile, dando un'occhiata a hwmonitor (visualizzazione grafico) oppure i grafici di msi afterburner
 
263e5e2ee4300a9545de5db663622f33.jpg


Stavo guardando un video sul tubo :[

Inviato da Nexus 5 tramite App ufficiale di Tom\\\'s Hardware Italia Forum
 
Capisci che in casi del genere e' difficile capire persino per te da dove derivi l'errore;

figurati per noi che non abbiamo il pc sottomano.

Il memtest lo hai fatto?

Vai a vedere con whocrashed cos'e' successo stavolta
 
Falco75 ha detto:
Capisci che in casi del genere e' difficile capire persino per te da dove derivi l'errore;

figurati per noi che non abbiamo il pc sottomano.

Il memtest lo hai fatto?

Vai a vedere con whocrashed cos'e' successo stavolta
Clicca per espandere...
dovrei aver disattivato il turbo 50; il memtest l'ho fatto per 9 ore, whocrashed mostra solo:
Codice: 
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Thu 20/04/2017 21:43:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042017-27625-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 Thu 20/04/2017 21:42:01 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: wow64cpu.sys (wow64cpu!TurboDispatchJumpAddressEnd+0x544)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803D0E12AE4, 0xFFFFE380FEBC7180, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: wow64cpu.sys .
Google query: wow64cpu.sys SYSTEM_SERVICE_EXCEPTION



On Thu 20/04/2017 00:12:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042017-28250-01.dmp
This was probably caused by the following module: hal.dll (hal+0x1AE4)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801F1E9EAE4, 0xFFFF94019835E380, 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 19/04/2017 22:11:38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\042017-29734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8038F2C40F0, 0xFFFF808018060100, 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 19/04/2017 01:19:22 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\041917-25781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BF70)
Bugcheck code: 0xA (0x20625A98, 0x2, 0x0, 0xFFFFF803D0E31E4B)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

18 crash dumps have been found and analyzed. Only 5 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

wow64cpu.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
non avendo la versione pro non posso vedere gli altri. dove trovo i dump, che magari posto direttamente quelli?
 
hal.dll e ntoskrnl.

Sono due tra i componenti piu' profondi di windows. Quindi il crash anche stavolta puo' dipendere da qualsiasi cosa.
 
Pubblicità
Pubblicità
Indietro
Top