Mon ordi plante , Ecran bleu

Bonjour à tous,

J'aurai besoin de votre aide.
Mon ordi est un Asus K50in pour les caractéristique technique
http://fr.asus.com/Notebooks/Versatile_Performance/K50IN/#specifications
PS: le processeur est un P7450

Depuis quelque temps mon ordi plante, en général lorsque je regarde une vidéo,l'ordi plante puis un écran bleu apparait qui me prévient que l'ordi s'arrête pour éviter un crash du disque .Par contre aujourd'hui il me l'a fait plusieurs fois alors que je ne faisait que surfer sur internet.j'ai mis la carte graphique a jour ,sans résultat.

J'ai le rapport Who Crashed;

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU P7450 @ 2.13GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3757330432 total
VM: 2147352576, free: 1895903232

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 28/05/2012 17:50:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052812-30014-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120C6B)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88648718, 0xFFFFFFFF88648740, 0x8050001)
Error: BAD_POOL_HEADER
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 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 Mon 28/05/2012 17:50:34 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!ExFreePoolWithTag+0x1B1)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF88648718, 0xFFFFFFFF88648740, 0x8050001)
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.
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 BAD_POOL_HEADER

On Mon 28/05/2012 17:15:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052812-36176-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1B501)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF950BB501, 0xFFFFFFFF915D5BA0, 0xFFFFFFFF915D5780)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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.

On Sun 27/05/2012 19:34:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052712-26956-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120C6B)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x0, 0xFFFFFFFF86D76E70)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
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 Sun 27/05/2012 15:32:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052712-27518-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1D6BC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9556F6BC, 0xFFFFFFFFB6395B00, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 Thu 24/05/2012 18:58:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052412-48500-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1D6BC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF9554E6BC, 0xFFFFFFFF94785B90, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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
--------------------------------------------------------------------------------

6 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.

Merci d'avance pour votre aide.