Bonsoir à tous,
 
Alors voilà, depuis peu je viens de retourner sous Windows 7 version intégral.
Avant d'acheter une clef d'activation je suis rester quelques jours en version d'essais et dès la j'ai commencer à avoir quelque écran bleu. Suite à l'acquisition de la clef d'activation j'ai formater puis installer donc la version intégral de Windows 7.
Après quelques heures j'ai commencer à avoir quelques écran bleu avec à l'heure actuel des délais allumage-écran bleu de plus en plus rapprocher. J'ai également plusieurs erreurs, notamment avec Firefox, puis des ralentissements. Et souvent avant l'écran bleu j'ai ma barre des tâches qui disparaît. Je précise également que l'écran bleu est survenu en mode sans échec.
 
Voici le rapport de WhoCrashed:
 
    System Information (local)
------------------------------
--------------------------------------------------
 
computer name: ALLAN-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5 CPU 650 @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 5359390720 total
VM: 2147352576, free: 1966575616
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Sat 22/09/2012 20:54:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-15859-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x75123)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000C5123, 0xFFFFF880063DDA80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 22/09/2012 20:54:13 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngFntCacheLookUp+0x9353)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000C5123, 0xFFFFF880063DDA80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 22/09/2012 20:38:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-14625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007759060, 0xFFFFFA8007759340, 0xFFFFF80002BD7240)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 22/09/2012 03:24:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-15437-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1869D8)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF960002069D8, 0xFFFFF88002E84FF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 19/09/2012 17:10:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-10734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800770E060, 0xFFFFFA800770E340, 0xFFFFF80002B7F240)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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 Wed 19/09/2012 16:30:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-12484-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x2C920)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880010E3920, 0xFFFFF880031A14F8, 0xFFFFF880031A0D50)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 Wed 19/09/2012 16:29:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-11156-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x6519C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600006519C, 0xFFFFF88008B2EA60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Wed 19/09/2012 12:21:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091912-18109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x34 (0x50830, 0xFFFFF88003185708, 0xFFFFF88003184F60, 0xFFFFF800029B50BF)
Error: CACHE_MANAGER
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 problem occurred in the file system's cache manager.
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
--------------------------------------------------------------------------------
 
8 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
 
 
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.
 
 
 
 
 
Photo de l'écran bleu:
 

 
 
 
Photo fenêtre d'erreur (Ceci n'est pas réellement la bonne, c'est assez dur de prendre en photo l'erreur qui vient juste avant le redémarrage car il n'y a aucun délais):
 

 
 
 
Merci d'avance et bonne soirée

Bonjour,
 
 
j'ai effectuer le test et il s'avère qu'une barrette est bourrer d'erreur.  
Je l'ai donc enlever à l'instant même mais après quelques minutes j'ai eu à nouveau un écran bleu..

Et des erreurs aussi avec celle-ci seule lors du test ?

Non les 3 autres ne présenter aucunes erreurs

Donc tu utilises un nombre impair de barettes ?
Pas génant ? (notamment sur le fonctionnement du Dual channel)
Il faudrait que tu testes en laissant 2 barettes aussi (en fonctionnement Dual Channel) pour être sur.

Reférence des RAM ?

Ok je vais tester sa.
 
Oui actuellement vue que j'ai du enlever l'autre je suis avec 3 barrettes.
 
Ocz DDR3 en 1 go

Bonsoir à tous,
 
 
j'ai échanger mes barrettes avec celles de mon frères qui ne présente aucun problème.
Cependant le problème persiste.
 
J'ai donc voulue re-formater et là, pendant l'installation de Windows ( la 1er phase sous écran bleu ) j'ai eu un écran bleu me disant que l'installation avait du être arrêter pour éviter tout dommage bla bla...
 
Et donc la, apparemment le problème viendrait plutôt de mon disque dur, de plus il a parfois un fortement très anormal je trouve.
 
Comment faire pour formater ?

Bonjour  
J'ai finie par réussir à formater via les commandes dos cependant quand je lance l'installation j'ai cet écran bleu qui me dis que l installation doit être arrêter ...