Re: Rapport Whocrashed Help
le 20 Oct 2011 16:46
Bonjour,
J'ai remis la barrette de mémoire que j'avais retiré en enlevant l'autre, aucun soucis . Quand je remets les deux ça ne fonctionne pas ..
En gros si je lance avec une seul barrette ça marche peut importe laquelle, mais quand je mets les deux ensemble ça bug .
Ensuite j'ai refait un rapport :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 20/10/2011 15:25:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-17300-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x58F865)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002C16490, 0xFFFFF80000C16490, 0xFFFFF80002C16490)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 280.26
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 280.26
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 280.26 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_HEADER
On Thu 20/10/2011 15:25:52 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1FE063)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002C16490, 0xFFFFF80000C16490, 0xFFFFF80002C16490)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 280.26
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 280.26
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 280.26 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation BAD_POOL_HEADER
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
2 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 280.26 , NVIDIA Corporation)
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.