Redemarage incéssant de Windows (7)
jinkyle
Messages postés
7
Statut
Membre
-
jinkyle Messages postés 7 Statut Membre -
jinkyle Messages postés 7 Statut Membre -
Bonjour,
Il y a une ou deux semaine de cela mon pc a commencé à s'éteindre tout seul suite à un écran bleu dont je n'ai pas trop compris le sens, de temps à autre, ça rester très rare, je ne me suis pas vraiment inquiéter.
Jusqu'à avant hier où là, plus moyen d'utiliser mon ordinateur, celui-ci se mettait a redémarrer tout seul encore et encore. C'est devenu incompréhensible, je pouvais rester parfois une heure dessus sans que rien ne se passe puis ça recommencé.
En plus de cela, il s'est mis à avoir divers bug inexplicables, comme par exemple: des logiciels qui ne répondent plus, qui vont parfois jusqu'à ne plus marcher du tout, l'explorateur Windows est devenu très très long, tout a tendance à "planter".
Pensant que j'avais choppé un méchant virus, j'ai décidé de formater mon disque dur et de réinstaller Windows 7.
Malheureusement, les redémarrages de l'ordinateur continuent, et de plus il ne m'a pas fallu plus d'une journée pour que des bugs étranges commencent à réapparaitre.
J'ai alors décidé d'installer "Whocrashed" pour essayer de comprendre le problème, sauf que je ne comprends pas vraiment de quoi il s'agit.
Je vous copie/colle les resultats obtenus en espérant que quelqu'un réussira à cibler le problème, si c'est un problème matériel? si oui lequel?
Merci d'avance, je vous laisse avec ce charabia:
System Information (local)
--------------------------------------------------------------------------------
computer name: FLORENT-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488735232 total
VM: 2147352576, free: 1988575232
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 20/08/2011 14:33:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-24616-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467CB)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFFFFF82A7B740)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Sat 20/08/2011 14:33:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29D3)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFFFFF82A7B740)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Sat 20/08/2011 05:38:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-50762-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839)
Bugcheck code: 0xA (0x4000000, 0x2, 0x1, 0xFFFFFFFF82E2F839)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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 IRQL_NOT_LESS_OR_EQUAL
On Sat 20/08/2011 01:52:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-39437-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x9E26)
Bugcheck code: 0x50 (0xFFFFFFFF898CC4D3, 0x8, 0xFFFFFFFF898CC4D3, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
On Fri 19/08/2011 19:32:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-30139-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467CB)
Bugcheck code: 0xA (0x6ACE178, 0x2, 0x0, 0xFFFFFFFF82ABD0BF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 19/08/2011 18:14:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-36317-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xFCC0)
Bugcheck code: 0x19 (0x22, 0xFFFFFFFF863DE000, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 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 Fri 19/08/2011 18:12:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-38547-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1C55)
Bugcheck code: 0x50 (0xFFFFFFFF823FF5CE, 0x0, 0xFFFFFFFF8289E0E9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 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 Fri 19/08/2011 18:09:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-35162-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A23)
Bugcheck code: 0x50 (0xFFFFFFFF80000000, 0x0, 0xFFFFFFFF8287CD2E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Fri 19/08/2011 18:06:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-32947-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x52E31)
Bugcheck code: 0x50 (0xFFFFFFFF8E95D484, 0x1, 0xFFFFFFFF8289E608, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l'infrastructure de pilotes en mode noyau
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 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 Fri 19/08/2011 17:41:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-35973-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2E8C)
Bugcheck code: 0x50 (0xFFFFFFFF95203770, 0x0, 0xFFFFFFFF8292A6D6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 Fri 19/08/2011 15:12:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-22167-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0x50 (0xFFFFFFFF827B0186, 0x0, 0xFFFFFFFF82AC2E41, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Fri 19/08/2011 15:02:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-12932-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x223A8B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A73A8B, 0xFFFFFFFF8CAE2B14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Fri 19/08/2011 14:58:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-23883-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x34 (0x50830, 0xFFFFFFFF8CD06A6C, 0xFFFFFFFF8CD06650, 0xFFFFFFFF8284E2CE)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
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 19/08/2011 14:46:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-18860-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x4868)
Bugcheck code: 0xD1 (0xB7A27D9, 0x2, 0x8, 0xB7A27D9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. 3 third party drivers have 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:
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
hal.sys
ntkrpamp.exe
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.
Il y a une ou deux semaine de cela mon pc a commencé à s'éteindre tout seul suite à un écran bleu dont je n'ai pas trop compris le sens, de temps à autre, ça rester très rare, je ne me suis pas vraiment inquiéter.
Jusqu'à avant hier où là, plus moyen d'utiliser mon ordinateur, celui-ci se mettait a redémarrer tout seul encore et encore. C'est devenu incompréhensible, je pouvais rester parfois une heure dessus sans que rien ne se passe puis ça recommencé.
En plus de cela, il s'est mis à avoir divers bug inexplicables, comme par exemple: des logiciels qui ne répondent plus, qui vont parfois jusqu'à ne plus marcher du tout, l'explorateur Windows est devenu très très long, tout a tendance à "planter".
Pensant que j'avais choppé un méchant virus, j'ai décidé de formater mon disque dur et de réinstaller Windows 7.
Malheureusement, les redémarrages de l'ordinateur continuent, et de plus il ne m'a pas fallu plus d'une journée pour que des bugs étranges commencent à réapparaitre.
J'ai alors décidé d'installer "Whocrashed" pour essayer de comprendre le problème, sauf que je ne comprends pas vraiment de quoi il s'agit.
Je vous copie/colle les resultats obtenus en espérant que quelqu'un réussira à cibler le problème, si c'est un problème matériel? si oui lequel?
Merci d'avance, je vous laisse avec ce charabia:
System Information (local)
--------------------------------------------------------------------------------
computer name: FLORENT-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3488735232 total
VM: 2147352576, free: 1988575232
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 20/08/2011 14:33:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-24616-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467CB)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFFFFF82A7B740)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Sat 20/08/2011 14:33:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29D3)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFF, 0x2, 0x1, 0xFFFFFFFF82A7B740)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL
On Sat 20/08/2011 05:38:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-50762-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839)
Bugcheck code: 0xA (0x4000000, 0x2, 0x1, 0xFFFFFFFF82E2F839)
Error: IRQL_NOT_LESS_OR_EQUAL
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.
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 IRQL_NOT_LESS_OR_EQUAL
On Sat 20/08/2011 01:52:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082011-39437-01.dmp
This was probably caused by the following module: aswsnx.sys (aswSnx+0x9E26)
Bugcheck code: 0x50 (0xFFFFFFFF898CC4D3, 0x8, 0xFFFFFFFF898CC4D3, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\aswsnx.sys
product: avast! Antivirus System
company: AVAST Software
description: avast! Virtualization Driver
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.
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: aswsnx.sys (avast! Virtualization Driver, AVAST Software).
Google query: aswsnx.sys AVAST Software PAGE_FAULT_IN_NONPAGED_AREA
On Fri 19/08/2011 19:32:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-30139-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467CB)
Bugcheck code: 0xA (0x6ACE178, 0x2, 0x0, 0xFFFFFFFF82ABD0BF)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 19/08/2011 18:14:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-36317-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xFCC0)
Bugcheck code: 0x19 (0x22, 0xFFFFFFFF863DE000, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 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 Fri 19/08/2011 18:12:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-38547-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0x1C55)
Bugcheck code: 0x50 (0xFFFFFFFF823FF5CE, 0x0, 0xFFFFFFFF8289E0E9, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost Driver
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 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 Fri 19/08/2011 18:09:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-35162-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85A23)
Bugcheck code: 0x50 (0xFFFFFFFF80000000, 0x0, 0xFFFFFFFF8287CD2E, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Fri 19/08/2011 18:06:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-32947-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x52E31)
Bugcheck code: 0x50 (0xFFFFFFFF8E95D484, 0x1, 0xFFFFFFFF8289E608, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Runtime de l'infrastructure de pilotes en mode noyau
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 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 Fri 19/08/2011 17:41:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-35973-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2E8C)
Bugcheck code: 0x50 (0xFFFFFFFF95203770, 0x0, 0xFFFFFFFF8292A6D6, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 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 Fri 19/08/2011 15:12:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-22167-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0x50 (0xFFFFFFFF827B0186, 0x0, 0xFFFFFFFF82AC2E41, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 Fri 19/08/2011 15:02:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-12932-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x223A8B)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82A73A8B, 0xFFFFFFFF8CAE2B14, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 which cannot be identified at this time.
On Fri 19/08/2011 14:58:47 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-23883-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x34 (0x50830, 0xFFFFFFFF8CD06A6C, 0xFFFFFFFF8CD06650, 0xFFFFFFFF8284E2CE)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
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 19/08/2011 14:46:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081911-18860-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x4868)
Bugcheck code: 0xD1 (0xB7A27D9, 0x2, 0x8, 0xB7A27D9)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote de port USB 1.1 & 2.0
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
14 crash dumps have been found and analyzed. 3 third party drivers have 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:
aswsnx.sys (avast! Virtualization Driver, AVAST Software)
hal.sys
ntkrpamp.exe
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.
A voir également:
- Redemarage incéssant de Windows (7)
- Clé windows 7 - Guide
- Photofiltre 7 - Télécharger - Retouche d'image
- Passer de windows 7 à windows 10 - Accueil - Mise à jour
- Windows defender windows 7 - Télécharger - Antivirus & Antimalwares
- Movie maker windows 7 - Télécharger - Montage & Édition
2 réponses
Bonsoir,
On dirait que ton disque dur est endommagé. Les écran bleus se produisant à chaque fois lors de l'accès au disque.
Ton PC a quel âge?
On dirait que ton disque dur est endommagé. Les écran bleus se produisant à chaque fois lors de l'accès au disque.
Ton PC a quel âge?
Je ne saurais pas dire l'âge exact de chaque pièce de mon pc étant donné que j'ai récupéré des pièces par ci par là, mais je pense qu'il doit avoir au moins 2 ans.
Tu ne connaitrais pas une astuce qui pourrait me permettre de confirmer le problème?
Tu ne connaitrais pas une astuce qui pourrait me permettre de confirmer le problème?
Ben j'ai un ptit soucis, lorsque je fais ça j'ai droit à :
Le type du système de fichiers est NTFS.
Impossible de verrouiller le lecteur en cours.
CHKDSK ne peut pas s'exécuter parce que le volume est utilisé par un autre processus. Voulez-vous que ce volume soit vérifié au prochain redémarrage du système ? (o/n)
Donc je met "o" puis je redemarre, du coup j'y est bien le droit au démarrage (même si une fois sur deux j'ai un écran bleu pendant la vérif).
Sauf que du coup, comme c'est au démarrage, je ne sais pas comment vous donner le résultat, une idée de comment faire? ou alors dans ce cas, dites moi qu'est ce que je dois regarder comme info pendant la vérif?
(En tout cas, merci de votre aide)
Le type du système de fichiers est NTFS.
Impossible de verrouiller le lecteur en cours.
CHKDSK ne peut pas s'exécuter parce que le volume est utilisé par un autre processus. Voulez-vous que ce volume soit vérifié au prochain redémarrage du système ? (o/n)
Donc je met "o" puis je redemarre, du coup j'y est bien le droit au démarrage (même si une fois sur deux j'ai un écran bleu pendant la vérif).
Sauf que du coup, comme c'est au démarrage, je ne sais pas comment vous donner le résultat, une idée de comment faire? ou alors dans ce cas, dites moi qu'est ce que je dois regarder comme info pendant la vérif?
(En tout cas, merci de votre aide)
