Blue screen(hal.dll,ntoskrnl.exe),erreur dans les pilotes

Fermé
El psy - Modifié par El psy le 15/08/2013 à 13:47
 El psy - 16 août 2013 à 11:38
Bonjour,

Je vous met un lien de ma config :



http://www.ma-config.com/fr/configurationtemporaire/7812-1_resume.html

je vous poste tout d'abord un rapport de WhoCrashed








Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 15/08/2013 01:56:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-52931-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1A654C)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 that cannot be identified at this time.



On Wed 14/08/2013 17:29:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-68047-01.dmp
This was probably caused by the following module: bhdrvx64.sys (BHDrvx64+0xC8928)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF88002D63928, 0x1, 0xAD97200)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NAV_20.3.1.22\Definitions\BASHDefs\20130715.001\BHDrvx64.sys
product: BASH
company: Symantec Corporation
description: BASH 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.
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: bhdrvx64.sys (BASH Driver, Symantec Corporation).
Google query: Symantec Corporation KMODE_EXCEPTION_NOT_HANDLED



On Mon 12/08/2013 21:06:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-37487-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B687748, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 29/07/2013 19:58:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-80309-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B5A1748, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 28/07/2013 21:56:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072813-61698-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE0C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B5C08F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 28/07/2013 11:28:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFFFFC0000005)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF88005AB0460, 0xFFFFF88002188048, 0xFFFFF880021878A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Thu 11/07/2013 08:31:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071113-38906-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800ABAE028, 0xB43B2000, 0x7D000135)
Error: WHEA_UNCORRECTABLE_ERROR
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 fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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 Sun 30/06/2013 11:40:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063013-41153-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B509028, 0xB67D2000, 0x135)
Error: WHEA_UNCORRECTABLE_ERROR
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 fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
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.

--------------------------------------------------------------------


J'ai commencé à mettre à jour tous mes pilotes hier depuis je n'ai plus de problème avec le hal.dll ou ce ntoskrnl.exe, du moins j'espère... ses deux problèmes là me donner des blue screen et quand je relançais normalement la tour ne voulait plus détecter l'écran ce qui m'a forcé à faire de nombreux redémarrages pour que le système inclut l'affichage du moniteur.
Parfois je pouvais jouer pendant 2 heures no problem. Et d'autres fois moins de 15 minutes, assez varier je dirais, ça dépendait de son humeur!
J'ai fait pas mal de manip choper sur les forums sans réellement savoir si sa cibler mon problème entre le Chkdsk /r, sfcscannow, test de la mémoire, et d'autre.. mais ça n'a rien fait


M'enfin ce problème m'a l'air d'être réglé en installant mes pilotes lesquels? aucune idée mais maintenant quand j'allume le Pc j'ai soit l'écran qui freeze (sa freeze qu'à partir du moment ou on rentre le mot de passe admin, pas avant) soit un redémarrage direct après quelques minutes sur le net, j'ai d'ailleurs corrigé un message d'erreur "kdbsync.exe a cessé de fonctionner" (pour le réparer, config>amd>modifier>et décocher AMD APP SDK Runtime)
M'enfin perso je ne crois pas que ce soit le problème.


J'ai mis à jour mes drivers via "Driver Booster" lorsque j'ai mis à jour ma carte graphique c'est à partir de là que j'ai eu les messages d'erreurs du 14/08 et du 15/08 sur whocrashed, j'ai restauré la version précédente et j'ai fait une mise à jour logicielle sur Amd
En ce moment même 1heure que je suis connecté depuis que j'ai mis à jour via Amd et j'attends que sa plante (y'a toujours un problème qui se déclenche derrière un autre..)
Est ce que le fait d'avoir mis à jour mes pilotes de Cg ont réparer les erreurs que m'afficher dernièrement whocrashed ?

Je vous remercie d'avance pour votre aide.

Cordialement,

Kamel
A voir également:

1 réponse

Bonjour ,

Sa plante toujours, nouveau whocrashed en espérant que quelqu'un passe par la..

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 16/08/2013 09:32:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-40607-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4ADE7C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800B5D34F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 16/08/2013 09:26:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-23914-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B50)
Bugcheck code: 0xC (0x0, 0x0, 0x0, 0x0)
Error: MAXIMUM_WAIT_OBJECTS_EXCEEDED
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 the current thread exceeded the permitted number of wait objects.
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 Fri 16/08/2013 09:25:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-45786-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x1A (0x5003, 0xFFFFF781C0000000, 0xF41F, 0xF4210001E83F)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 16/08/2013 09:21:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081613-46675-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x19 (0x3, 0xFFFFF80003415FA0, 0xFFFFF80003415FB0, 0xFFFFF80003415FA0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 15/08/2013 21:11:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-58110-01.dmp
This was probably caused by the following module: bhdrvx64.sys (BHDrvx64+0xAB51C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880044FE51C, 0xFFFFF88003B937A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\NAV_20.3.1.22\Definitions\BASHDefs\20130715.001\BHDrvx64.sys
product: BASH
company: Symantec Corporation
description: BASH 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.
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: bhdrvx64.sys (BASH Driver, Symantec Corporation).
Google query: Symantec Corporation SYSTEM_SERVICE_EXCEPTION



On Thu 15/08/2013 01:56:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081513-52931-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x1A654C)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote TCP/IP
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 that cannot be identified at this time.
0