Bonjour à tous,
Je rencontre un soucis sur mon PC depuis quelques semaines maintenant.
En effet, j'ai des bluescreen de plus en plus fréquents.
J'ai changé le disque dur ce jour et j'ai installé windows seven home premium comme à l'origine.
J'ai toujours des bluescreen.
Voilà le résultat avec WhoCrashed
Merci pour votre aide
System Information (local)
--------------------------------------------------------------------------------
computer name: V-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel® Pentium® Dual CPU E2160 @ 1.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3219378176 total
VM: 2147352576, free: 2001870848
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 05/05/2011 18:48:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050511-27378-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x224239)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000006, 0xFFFFFFFF82A76239, 0xFFFFFFFFA1607B84, 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 Thu 05/05/2011 18:48:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x8E (0xFFFFFFFFC0000006, 0xFFFFFFFF82A76239, 0xFFFFFFFFA1607B84, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 KERNEL_MODE_EXCEPTION_NOT_HANDLED
On Thu 05/05/2011 17:02:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\050511-41636-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x13EC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFFFFF8FAF33EC, 0xFFFFFFFF8CC81700, 0xFFFFFFFF8CC812E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 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
--------------------------------------------------------------------------------
3 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:
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.