Bonjour à tous,
 
Je me permets de vous écrire car j'ai un pb avec mon nouveau pc, il me fait des écrans bleus à répétition. J'ai déjà parcouru le forum et je ne trouve pas de solutions...
 
Voici ma config :
processeur Quad Core Intel Core i5-3450
Carte mère MSI Z77A-G43 (Intel Z77 Express)
Carte graphique NVIDIA GeForce GTX 650
4 Go de mémoire vive "Dual Channel" de type DDR3 1333 MHz
Disque SSD 90 Go serial ATA 6 Gb/s
Alimentation 450W - 80PLUS Bronze
 
 
J'ai les rapports whocrashed si sa peut vous servir ...
 
Merci d'avance pour votre aide et bonne soirée

Tu as eu ces écrans bleus suite à quoi ?
Tu viens de monter ton pc et il fonctionne pas ?
Tu as déjà installer windows et tu l'as utilisé ?
Tu as installer des logiciels particuliers ?

On a besoin de plus de précisions :-)

C'est quoi la marque de ton SSD?
Est-il en AHCI (je pense que oui mais bon)

Je ne sais pas suite à quoi j'ai eu ces écrans bleus, enfait le pc est neuf, je les ai eu peut être une semaine après avoir eu l'ordi, le plus souvent en jeu, mais dès que j'en ai un, plus possible de redémarrer le pc après.
 
Oui j'ai déjà installé windows 7, & pour les logiciels, rien de particulier, avast google chrome mozilla steam.
 
Mon SSD c'est un intel et oui il est en AHCI

Utilise Bluescreenview pour voir les codes d'erreur de tes BSOD, ça pourra donner une piste sur leur origine.

Oki, pour l'instant je ne peux pas le rallumer, est-ce qu'un rapport whocrashed irait en attendant ou j'attends de pouvoir redémarrer ??

bon alors du coup, voilà le lien de la capture pour BSV : http://imageshack.us/f/266/capture1ea.png/
 
& voila le rapport whocrashed :s
 
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
 
On Fri 18/01/2013 19:39:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A5AC80, 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.  
A third party driver was identified as the probable root cause of this system error.  
Google query: MEMORY_MANAGEMENT
 
On Thu 17/01/2013 16:58:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-6708-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x7902C)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000F902C, 0xFFFFF88007D0CA00, 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 that cannot be identified at this time.
 
On Thu 17/01/2013 16:56:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-5959-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x1A (0x41287, 0x6548FF8, 0x0, 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 that cannot be identified at this time.
 
On Thu 17/01/2013 15:13:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-3525-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009705C0, 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 that cannot be identified at this time.
 
On Thu 17/01/2013 14:08:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-3619-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x7A (0x1, 0xFFFFFFFFC0000005, 0xFFFFFA8007393B30, 0xFFFFF680003B2000)
Error: KERNEL_DATA_INPAGE_ERROR
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 requested page of kernel data from the paging file could not be read into memory.  
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
On Thu 17/01/2013 14:05:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011713-3619-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)  
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006FE5078, 0xFFFFF88006FE48D0, 0xFFFFF80002CCF0B4)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.  
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 that cannot be identified at this time.
 
On Wed 16/01/2013 02:57:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-4196-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800093B940, 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 that cannot be identified at this time.
 
On Wed 16/01/2013 02:43:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-4243-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xD953D)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88004937E79, 0xFFFFF880065E73C8, 0xFFFFF880065E6C20)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 306.97  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 306.97  
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.  
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 306.97 , NVIDIA Corporation).  
Google query: NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
On Wed 16/01/2013 02:29:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-4321-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000A612E0, 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 that cannot be identified at this time.
 
On Wed 16/01/2013 02:27:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-3697-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C91C60, 0xFFFFF880093D7B80, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
On Mon 14/01/2013 00:47:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-4321-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000921330, 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 that cannot be identified at this time.
On Mon 14/01/2013 00:43:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-3572-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x28412)  
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800499C412, 0xFFFFF88009B1D5C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 that cannot be identified at this time.
 
On Mon 14/01/2013 00:26:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-5382-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009B9FA0, 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 that cannot be identified at this time.
 
On Mon 14/01/2013 00:25:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-3541-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)  
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80009C3930, 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 that cannot be identified at this time.
 
On Mon 14/01/2013 00:23:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011413-3681-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48D8)  
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800906E0A8, 0xFFFFF8800906D900, 0xFFFFF80002C2BB2B)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.  
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 that cannot be identified at this time.
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
19 crash dumps have been found and analyzed. Only 15 are included in this report. 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 306.97 , 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.

En mode sans echec tu as aussi des BSOD ?  
 
Les dump disent comme tu vois d'essayer un autre pilote de carte graphique, revient a un plus récent ou plus vieux dans gestionnaire périph clic droit et revenir a une ancienne version
 
Teste ta RAM barrette par barrette ( memtest )
 
Teste ton disque dur avec crystaldiskinfo

Oui en mode sans échec sa me fait aussi des bsod.
 
Les pilotes de cartes graphiques je les ai déjà changé, disque dur dejà testé avec crystaldiskinfo RAS, et barrettes de RAM idem avec memtest.
Mais là jai changé les barettes de RAM et pour l'instant plus de BSOD

J'dirais les ram aussi.

tu nous fera un autre retour dans quelques temps si ca foncitonne merci

pour les ram tu memtest 86+ pour voir les erreurs, pour la carte graphique tu retir le pilote tu laisse juste le pilote windows pendent 48h.
Les BOSD peuvent malheureusement venir de n'importe quoi, le tout est de bien ciblé le problème si il est hardware ou software.

souvent la RAM ou les pilote graphique