Bonjour à tous,
Depuis quelques temps mon pc plante en faisant une page bleue, j'avais un souci de désinstallation d'avast qui ne se mettait plus à jour, j'ai enfin réussi à l'enlever, j'ai fait un scan avec plusieurs logiciels qui me disent qu'il n'y a pas de souci particulier sur mon pc. Il plante toujours. On m'a conseillé d'utiliser whocrashed mais j'ai du mal à comprendre ce qu'il en ressort du test effectué.
Si quelqu'un pourrait me conseiller pour en finir avec ces pages bleues, voici le rapport :
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 11/10/2011 17:36:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-33977-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3639B2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000316D9B2, 0xFFFFF880037D9A48, 0xFFFFF880037D92B0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 11/10/2011 17:36:55 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: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8000316D9B2, 0xFFFFF880037D9A48, 0xFFFFF880037D92B0)
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.
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 11/10/2011 17:30:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-40887-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA80199F1010, 0x2, 0x1, 0xFFFFF80002F30AB7)
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 11/10/2011 11:29:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-26863-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EC7A84, 0xFFFFF880084E9250, 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 which cannot be identified at this time.
On Tue 11/10/2011 05:55:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-28002-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x50 (0xFFFFF89A7D004100, 0x0, 0xFFFFF8000332BB71, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 which cannot be identified at this time.
On Tue 11/10/2011 05:37:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-33789-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x213D8)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800ADBF5C8, 0xFFFFF8800ADBEE30, 0xFFFFF80002E48404)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
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 which cannot be identified at this time.
On Mon 10/10/2011 11:25:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101011-25927-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B58A80, 0xFFFF, 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 Sun 09/10/2011 16:01:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-33805-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA8014C42010, 0x2, 0x1, 0xFFFFF80002F96AB7)
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 Sun 09/10/2011 11:24:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-31512-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA80167EA010, 0x2, 0x1, 0xFFFFF80002F90AB7)
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 Sun 09/10/2011 08:22:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100911-31527-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA8018ECB010, 0x2, 0x1, 0xFFFFF80002F95AB7)
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 Fri 07/10/2011 23:07:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100811-36301-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A50F3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800030010F3, 0xFFFFF880037F58B8, 0xFFFFF880037F5120)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 07/10/2011 21:36:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100711-33711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA801B739010, 0x2, 0x1, 0xFFFFF80002D30AB7)
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 Fri 07/10/2011 21:16:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100711-35630-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000B58A80, 0xFFFF, 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 Fri 07/10/2011 06:23:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100711-48797-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xA (0xFFFFFA800A631010, 0x2, 0x1, 0xFFFFF80002D84AB7)
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 Thu 06/10/2011 19:31:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100611-36535-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F61A0F, 0xFFFFF88009FAB930, 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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
19 crash dumps have been found and analyzed. Only 15 are included in this report.
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 d'avance à celui ou celle qui pourra me conseiller sur ce que je dois ou peux faire pour régler ce souci.
Amicalement.
Page bleue et whocrashed
Re: Page bleue et whocrashed
Personne pour m'aider ??
-
txuku
- Messages : 1411
- Enregistré le : lun. 1 févr. 2010 13:41
- Etes vous un robot ? : Non
- Localisation : Bayonne 64
- Contact :
Re: Page bleue et whocrashed
Bonjour wolf02000
ntoskrnl.exe jamais facile....
Utilises google comma traducteur pour les dmp ( le resume ).
Testes les memoires - Memtest et teste d une seule barette a la fois )
Mise a jour des drivers ( et parfois retour en arriere pour certains ).
Restauration a une date anterieure.
commande sfc /scannow dans une console en mode administrateur.
Les erreurs stop : http://www.hotline-pc.org/stop.htm
ntoskrnl.exe jamais facile....
Utilises google comma traducteur pour les dmp ( le resume ).
Testes les memoires - Memtest et teste d une seule barette a la fois )
Mise a jour des drivers ( et parfois retour en arriere pour certains ).
Restauration a une date anterieure.
commande sfc /scannow dans une console en mode administrateur.
Les erreurs stop : http://www.hotline-pc.org/stop.htm