Page 1 sur 1

Ecran Bleu / Crash Dump

Posté : sam. 21 avr. 2012 13:06
par Aurel912009
Voilà sa va faire un mois que j'ai de temps en temps des écrans bleus. Pour une des erreurs trouver avec Whocrashed, j'ai résolu le problème enfin je crois j'ai mis ma carte graphique à jour et cette erreur n'es pas revenu, par contre pour l'autre sa reviens plus souvent. Je vous met le rapport whocrashed vous pourrez peut-être m'aider, je précise j'ai vérifier les barrettes de mémoires et elles fonctionnent bien. Je l'ai formater donc pas grand chose dedans, antivirus fait également.

System Information (local)
--------------------------------------------------------------------------------

computer name: LILI-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU E5400 @ 2.70GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294066176 total
VM: 2147352576, free: 1988780032



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sat 21/04/2012 09:09:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\042112-20888-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xD1 (0x4265, 0x2, 0x0, 0xFFFFF880043A6B1D)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 21/04/2012 09:09:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xDCA7C)
Bugcheck code: 0xD1 (0x4265, 0x2, 0x0, 0xFFFFF880043A6B1D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 296.10
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 296.10
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.
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 296.10 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Fri 13/04/2012 07:49:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041312-22932-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x50 (0xFFFFF80000000104, 0x1, 0xFFFFF800033CDB4D, 0x0)
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 Thu 05/04/2012 09:26:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040512-37175-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x406F8, 0xFFFFF800030C3B7D)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 04/04/2012 08:08:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040412-23618-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xD1 (0xA, 0x2, 0x0, 0xFFFFF880038798D9)
Error: DRIVER_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 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 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. 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 296.10 , 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.

Merci d'avance pour votre aide