Ecran bleu
anny31
Messages postés
51
Statut
Membre
-
MyLaw Messages postés 88 Statut Membre -
MyLaw Messages postés 88 Statut Membre -
Bonjour,
j'ai un gros pb d'ecran bleu, j'ai reussi avec peine a installer whocrashed (ecran bleu....)
et cela nous donne cela.
mais materiel ou programme?
System Information (local)
________________________________________
computer name: ALAIN-PC
windows version: Windows 7 , 6.1, build: 7100
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2146754560 total
VM: 2147352576, free: 1979084800
________________________________________
Crash Dump Analysis
________________________________________
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 07/06/2011 20:53:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-24046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 20:53:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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.
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: hal.sys .
Google query: hal.sys MEMORY_MANAGEMENT
On Tue 07/06/2011 20:29:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-23375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 20:16:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-43687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 20:03:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-24078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x10C, 0x2, 0x0, 0xFFFFFFFF81D1DE65)
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 which cannot be identified at this time.
On Tue 07/06/2011 19:51:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-24250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x104, 0x2, 0x0, 0xFFFFFFFF81D16E65)
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 which cannot be identified at this time.
On Tue 07/06/2011 19:41:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-26140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 07:35:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-32765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF81CFE401)
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 which cannot be identified at this time.
On Tue 07/06/2011 07:31:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-32593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF81CD3401)
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 which cannot be identified at this time.
On Tue 07/06/2011 06:13:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-33156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Mon 06/06/2011 19:27:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060611-39703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x1CC2483, 0x2, 0x1, 0xFFFFFFFF81C4A2EC)
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 which cannot be identified at this time.
On Mon 06/06/2011 19:19:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060611-39062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x1D11, 0x0, 0x0)
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 which cannot be identified at this time.
________________________________________
Conclusion
________________________________________
12 crash dumps have been found and analyzed. 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:
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
merci
j'ai un gros pb d'ecran bleu, j'ai reussi avec peine a installer whocrashed (ecran bleu....)
et cela nous donne cela.
mais materiel ou programme?
System Information (local)
________________________________________
computer name: ALAIN-PC
windows version: Windows 7 , 6.1, build: 7100
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2146754560 total
VM: 2147352576, free: 1979084800
________________________________________
Crash Dump Analysis
________________________________________
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 07/06/2011 20:53:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-24046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 20:53:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KfLowerIrql+0x61)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
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.
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: hal.sys .
Google query: hal.sys MEMORY_MANAGEMENT
On Tue 07/06/2011 20:29:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-23375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 20:16:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-43687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 20:03:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-24078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x10C, 0x2, 0x0, 0xFFFFFFFF81D1DE65)
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 which cannot be identified at this time.
On Tue 07/06/2011 19:51:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-24250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x104, 0x2, 0x0, 0xFFFFFFFF81D16E65)
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 which cannot be identified at this time.
On Tue 07/06/2011 19:41:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-26140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Tue 07/06/2011 07:35:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-32765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF81CFE401)
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 which cannot be identified at this time.
On Tue 07/06/2011 07:31:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-32593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF81CD3401)
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 which cannot be identified at this time.
On Tue 07/06/2011 06:13:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060711-33156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.
On Mon 06/06/2011 19:27:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060611-39703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4471B)
Bugcheck code: 0xA (0x1CC2483, 0x2, 0x1, 0xFFFFFFFF81C4A2EC)
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 which cannot be identified at this time.
On Mon 06/06/2011 19:19:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060611-39062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73B55)
Bugcheck code: 0x1A (0x41287, 0x1D11, 0x0, 0x0)
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 which cannot be identified at this time.
________________________________________
Conclusion
________________________________________
12 crash dumps have been found and analyzed. 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:
hal.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
merci
A voir également:
- Ecran bleu
- Supprimer rond bleu whatsapp - Guide
- Double ecran - Guide
- Écran bleu - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
1 réponse
Salut,
En résumé, ce sont 2 fichiers qui posent problème :
ntoskrnl.exe qui est la cible de certain virus comme W32.Bolzano par exemple.
hal.sys qui est un fichier pilote.
Je pense donc que :
soit ton DD est abimé auquel cas il faut en changer.
soit tu es infecté.
Ce que je suggère. Débrancher les DD secondaires. Garder que le DD système.
Vérifier si le problème persiste.
Si le problème persiste :
Analyser avec un antivirus au démarrage. A l'aide d'un boot disk.
Si cela ne donne rien :
Changer le disque dur principal, garder l'ancien et le remettre en secondaire pour récupérer les données, et le "soigner".
Si le problème disparait, identifier le disque, récupérer si possible les données, le formater, et le tester a nouveau.
Mylaw
En résumé, ce sont 2 fichiers qui posent problème :
ntoskrnl.exe qui est la cible de certain virus comme W32.Bolzano par exemple.
hal.sys qui est un fichier pilote.
Je pense donc que :
soit ton DD est abimé auquel cas il faut en changer.
soit tu es infecté.
Ce que je suggère. Débrancher les DD secondaires. Garder que le DD système.
Vérifier si le problème persiste.
Si le problème persiste :
Analyser avec un antivirus au démarrage. A l'aide d'un boot disk.
Si cela ne donne rien :
Changer le disque dur principal, garder l'ancien et le remettre en secondaire pour récupérer les données, et le "soigner".
Si le problème disparait, identifier le disque, récupérer si possible les données, le formater, et le tester a nouveau.
Mylaw
Vérifier la mémoire vive aussi, avec MEMtest