Écrans bleus

[moorpheeus]

Bonjour, j'ai de temps en temps des ecrans bleus sans que la cause soit déterminé par exemple je vous donne mon dernier rapport WHocrashed :

 

On Sat 18/08/2012 07:02:13 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081812-17955-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x19 (0x20, 0xFFFFFA8001D4CF10, 0xFFFFFA8001D4D020, 0xC11C080)

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 which cannot be identified at this time.

 

 

On Sat 18/08/2012 07:02:13 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: 0x19 (0x20, 0xFFFFFA8001D4CF10, 0xFFFFFA8001D4D020, 0xC11C080)

Error: BAD_POOL_HEADER

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 which cannot be identified at this time.

 

 

On Sat 18/08/2012 06:58:17 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081812-19780-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x50 (0xFFFFF88204D9C0C7, 0x1, 0xFFFFF88004D9C08F, 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 14/08/2012 21:22:39 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081412-17752-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x34 (0x50853, 0xFFFFF8800318C508, 0xFFFFF8800318BD60, 0xFFFFF80002EBC14D)

Error: CACHE_MANAGER

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 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 Mon 13/08/2012 13:59:09 GMT your computer crashed

crash dump file: C:\Windows\Minidump\081312-18954-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)

Bugcheck code: 0x1A (0x41284, 0x2175001, 0x0, 0xFFFFF70001080000)

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

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

 

5 crash dumps have been found and analyzed.

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.

 

J'ai testé ma ram avec utilitaire present sous win7 pas d'erreurs détectées, j'ai egalement verifier les fichiers systeme avec la commande sfc /verifyonly tout est ok. que puis je faire d'autre merci ?

[thorgal]

Bonsoir,

 

 

 

Il faudrait peut être commencer par une vérification minutieuse du disque dur via Windows.