Crash windows 7 - écran bleu

Bonjour,

J'ai fréquemment des crashs windows 7 PRO 64 bit lorsque je démarre mon ordinateur.
L'écran devient tout bleu! Par la suite, il redémarre et ainsi de suite...

J'ai déjà reformater mon pc plusieurs fois mais rien n'y change. (C'est une nouvel ordinateur qui à 1 mois maximum).


D'après ce que j'ai pu lire comme informations sur le net, il peut y avoir de multiples causes à ces crashs.

J'ai créer un rapport concernant ces crashs grâce au programme Whocrashed et au fichier C: -> windows -> minidump.

J'espère que quelqu'un pourra m'aider à trouver une solution...


ps: je me suis renseigner sur l'application ntoskrnl.exe

NTOSKRNL
Le processus ntoskrnl.exe (ntoskrnl signifiant Windows Boot-Up Kernel) est un processus critique de Windows XP servant au démarrage (boot-up) de Microsoft Windows.

Il s'agit d'un processus ne pouvant pas être arrêté et n'apparaissant normalement pas dans le gestionnaire des tâches.

Sa présence dans le gestionnaire des tâches peut révéler une infection par le ver réseau W32.Bolzano.

J'espère que quelqu'un pourra m'aider à trouver une solution...



Voici le rapport qui est fort long:


[quote]


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

windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4275265536 total
VM: 2147352576, free: 1990934528



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 20/12/2011 18:44:30 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: 0x1A (0x41790, 0xFFFFFA800121DEE0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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.

----------------------------------------------------------------------------
On Tue 20/12/2011 18:06:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-16083-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x18 (0x0, 0xFFFFFA8001500743, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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 Tue 20/12/2011 18:01:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-18423-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800121A040, 0xFFFF, 0x0)
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
--------------------------------------------------------------------------------

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

/quote