Bonjour  à vous tous
 
je viens exposer mon soucis.
 
j'ai voulu upgrader mon pc pour pouvoir jouer correctement a BF3 mais depuis que j'ai changer je n'ai que des soucis d'ecran bleu.
 
Voici la config de mon pc :
 
Ci dessous les éléments déjà en ma possession avant d évoluer mon pc
- SSD Crucial M4 128go
- 2 hdd en raid 0
 
et voici les nouveaux éléments :
 
- core i7 2600
- carte mère Asus P8Z68-V/gen 3
- Carte Graphique : Asus GTX 580 D CU II version du pilote : 285.62 (la derniere dispo à ce jour)
- Alim : Corsair TX 650
- 8 GB DDR 3 Corsair Vengeance (important en rapportant le pc au magasin pour ce soucis ils m 'ont change la memoire en me disant que ca venait surement de là. avant j'avais les G.Skill 8go
 
Malgré le changement des barrettes le problème persiste.
 
 
Mon Soucis :
 
j'ai des écran bleu suivi de redémarrage  de façon aléatoire,
néanmoins j'ai remarqué une chose :
 
j'en obtiens beaucoup plus fréquemment quand par exemple je fait du téléchargement (grabit)
 
j'ai regardé un peu sur le forum et j'ai vu qu on conseillait de telecharger Whocrashed et de poster le rapport.
 
donc je me permets de vous le partager ci dessous.
 
Le RAPPORT de WHOCRASHED
 
System Information (local)
--------------------------------------------------------------------------------
 
computer name: MIKE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8563703808 total
VM: 2147352576, free: 1934675968
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Thu 02/02/2012 18:58:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020212-6801-01.dmp
uptime: 00:08:47
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0001B668BA, 0x2, 0x0, 0xFFFFF800032BCF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 02/02/2012 18:58:57 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:08:47
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)  
Bugcheck code: 0xA (0xFFFFFC0001B668BA, 0x2, 0x0, 0xFFFFF800032BCF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 02/02/2012 18:49:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020212-7768-01.dmp
uptime: 00:10:58
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0000E3C770, 0x2, 0x1, 0xFFFFF800032CB97E)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 02/02/2012 18:36:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020212-9282-01.dmp
uptime: 00:32:30
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC000613CBAA, 0x2, 0x0, 0xFFFFF800032C2F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 02/02/2012 18:03:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020212-7722-01.dmp
uptime: 04:17:05
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC00050F0B3A, 0x2, 0x0, 0xFFFFF800032C1F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 01/02/2012 23:26:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020212-6146-01.dmp
uptime: 00:49:29
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC000101E9FA, 0x2, 0x0, 0xFFFFF800032B8F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 01/02/2012 22:36:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020112-5896-01.dmp
uptime: 01:58:58
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC000063E08A, 0x2, 0x0, 0xFFFFF800032CFF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 01/02/2012 20:17:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020112-6006-01.dmp
uptime: 00:55:56
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0005163AFA, 0x2, 0x0, 0xFFFFF800032D9AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 30/01/2012 22:05:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\013012-5912-01.dmp
uptime: 06:10:30
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0x109 (0xA3A039D89F47659C, 0xB3B7465EF1C434F2, 0xFFFFF80003301458, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 Wed 25/01/2012 13:28:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012512-5740-01.dmp
uptime: 01:29:54
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0005916D3A, 0x2, 0x0, 0xFFFFF80003294AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 22/01/2012 20:21:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-5943-01.dmp
uptime: 01:50:08
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC00040541BA, 0x2, 0x0, 0xFFFFF800030A3AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 22/01/2012 18:29:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-8829-01.dmp
uptime: 02:16:32
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x12BD67)  
Bugcheck code: 0xA (0xFFFFFC0002579020, 0x2, 0x1, 0xFFFFF800030B897E)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62  
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 285.62 , NVIDIA Corporation).  
Google query: nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL
 
 
 
 
On Sun 22/01/2012 16:11:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012212-5694-01.dmp
uptime: 04:09:10
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0004BDA38A, 0x2, 0x0, 0xFFFFF800030A9AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 21/01/2012 22:42:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-5631-01.dmp
uptime: 00:28:26
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0001905FAA, 0x2, 0x0, 0xFFFFF800030D6AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 17/01/2012 23:05:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011812-6630-01.dmp
uptime: 00:26:04
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0003BEBDF0, 0x2, 0x1, 0xFFFFF800030A4BDB)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
36 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 285.62 , 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.  
 
 
 
 
Dans ce rapport il parle donc d'un éventuel problème avec la carte graphique mais je ne comprends pas car je joue des fois plus d'une heure et je ne rencontre problème dans les jeux.
Il m'arrive même certaine fois d'allumer le pc et de le laisser ainsi, je reviens quelques temps apres et je m'aperois que le pc a été redemarré.
 
Merci beaucoup par avance de votre aide, et si il y a des choses, éléments à vous transmettre en plus n'hésitez pas à me demander.
 
 

le ssd est a jour  ?
tu as fait un test sur la mémoire ?

bonjour gougoul07
alors je viens de faire un test sur la memoire avec memtest 86+ v.4.20
 
il a decouvert une erreur qui est la suivante :
 
TST  Pass Failing adress                  Good       Bad           Err Bits
6       2    0017f7293a4 - 6135.1MB  00020000  00020400  00000400
 
Counts  Chan
   1          0
 
 
Une chose je ne sais pas si cela peux vous aider mais:
 
a chaque fois que j'utilise QuickPar pour par exemple faire une vérification de fichier savoir si il est complet ou pas, quelques minutes après avant même que cela soit fini cela me Fait un BSOD  
voici donc aujourd'hui ce que Whocrashed m'as dis :
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Mon 06/02/2012 20:41:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5772-01.dmp
uptime: 00:14:13
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC00039F63AA, 0x2, 0x0, 0xFFFFF800032FCF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 20:26:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5787-01.dmp
uptime: 00:19:47
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0000C70D2A, 0x2, 0x0, 0xFFFFF800032CBF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 20:05:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5756-03.dmp
uptime: 01:46:21
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0000F20BCA, 0x2, 0x0, 0xFFFFF800032C8F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 18:17:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5756-02.dmp
uptime: 00:07:37
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0005C000EA, 0x2, 0x0, 0xFFFFF8000330AF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 18:09:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5865-01.dmp
uptime: 00:21:26
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC000137854A, 0x2, 0x0, 0xFFFFF80003310F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 17:47:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5756-01.dmp
uptime: 00:05:06
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC000409648A, 0x2, 0x0, 0xFFFFF800032A8AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 17:41:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5834-02.dmp
uptime: 00:24:01
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC000378202A, 0x2, 0x0, 0xFFFFF800032CAF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 17:16:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-5834-01.dmp
uptime: 00:15:31
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0000F51B2A, 0x2, 0x0, 0xFFFFF80003312F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 06/02/2012 17:00:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020612-6801-01.dmp
uptime: 00:27:00
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFC0000F5401A, 0x2, 0x0, 0xFFFFF80003304F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.  
 
 
concernant le SSD je viens de voir qu il y avait un firmware 0309 a installer je vais essayer de l'installer sans faire trop de betises suffit juste de trovuer un bon tuto
 
je vous tiens au courant par la suite merci d'avance, car la ça devient vraiment gênant

Je viens de mettre à jour le ssd avec le nouveau firmware
et la donc je fait mon analyse Quickpar ca passe.
 
j'ouvre donc le fichier avec Winrar et au moment de la decompression CRASH DUMP à nouveau.
 
Donc peux on dire que mon soucis ne viens pas du SSD ?  
 
Il resterait le soucis des barrettes de ram d'apres memtest.
et concernant whocrashed quand il me dis qu'il y a un éventuel soucis au niveau de la carte graphique dans le rapport comment pourrais je faire ? car le pilote est à jour  
 
Merci par avance encore  
 

 et il t'on deja changé les barettes ,donc  je ne vois qu'une maniere de proceder il faut resteter avec d'autre barette en même quantité  ,et si sa plante toujours un de tes slots mémoires est defectueux. il arrive parfois que ce ne soit pas la barette elle même la coupable!!

salut garlok je vais rapporter le pc vu qu il est sous garantie encore la ou je  l ai acheter et leur dis ca de changer a nouveau les barrettes.
la 1ere fois avec les 1eres barrettes mon pc me faisait des écrans bleu même en pleine partie de battlefield mais depuis qu ils ont change les barrettes ca n arrive plus en jeux mais toujours dans des applications de décompressions etc ( winrar, grabit, quickpar)
 
Par contre si cela est un slot qui est défectueux comment peux tu le savoir y a t il un moyen de le vérifier ?
 merci

malheuresement non   a par mettre les barrettes une a une et faire des mem test avec differentes barettes sur chaque slot a conditions que la cm le permette,il  ni a pas vraiment de technique miracle

Bonjour,
 
je viens de recevoir donc ma carte mere de retour de chez ASUS depuis un peu plus d une semaine maintenant RESULTAT :
 
ENCORE PIRE QU AVANT :
 
j 'ai des BSOD encore plus souvent et tres frequemment et le soucis c est que ca m arrive vraiment aléatoirement plus seulement quand je decompresse à l aide svp !!!!!
 
voici le rapport de Whocrashed
 
 
 
--------------------------------------------------------------------------------
Welcome to WhoCrashed Professional Edition v 3.01
--------------------------------------------------------------------------------
 
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.  
 
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.  
 
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. If will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.  
 
 
To obtain technical support visit www.resplendence.com/support
 
To check if an update of this program is available, click here.
 
Click the Analyze Local button to analyze this computer or the Analyze Remote button for a computer on the network...
 
 
 
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
 
computer name: MIKE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8563654656 total
VM: 2147352576, free: 1937154048
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Wed 07/03/2012 17:15:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-6115-01.dmp
uptime: 00:08:15
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB00218851A, 0x2, 0x0, 0xFFFFF800030BFF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 17:15:24 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:08:15
This was probably caused by the following module: ntfs.sys (Ntfs+0x16BF6)  
Bugcheck code: 0xA (0xFFFFFAB00218851A, 0x2, 0x0, 0xFFFFF800030BFF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 17:05:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-8502-01.dmp
uptime: 03:32:02
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB003DD52DA, 0x2, 0x0, 0xFFFFF80003104F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 13:32:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-7378-01.dmp
uptime: 00:07:37
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB00271594A, 0x2, 0x0, 0xFFFFF800030F2AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 12:11:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-8299-01.dmp
uptime: 04:10:26
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB0062431FA, 0x2, 0x0, 0xFFFFF800030BAF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 07:59:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-5226-01.dmp
uptime: 00:20:23
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB00345D4BA, 0x2, 0x0, 0xFFFFF800030B4F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 07:37:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-7800-01.dmp
uptime: 06:39:31
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB00568C5DA, 0x2, 0x0, 0xFFFFF800030B8F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 00:56:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-6177-01.dmp
uptime: 00:17:21
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB000E51E3A, 0x2, 0x0, 0xFFFFF800030FEF1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 07/03/2012 00:38:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-5491-01.dmp
uptime: 00:47:48
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB0050889D0, 0x2, 0x1, 0xFFFFF80003097E7D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 06/03/2012 23:49:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-6864-01.dmp
uptime: 00:21:47
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB004552F3A, 0x2, 0x0, 0xFFFFF800030C3F1F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 06/03/2012 23:27:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030712-6942-01.dmp
uptime: 00:43:11
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB001375750, 0x2, 0x1, 0xFFFFF800030AAE7D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 06/03/2012 22:42:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030612-5569-01.dmp
uptime: 00:28:04
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB001501CC0, 0x2, 0x1, 0xFFFFF8000306AE7D)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 06/03/2012 22:13:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030612-5616-01.dmp
uptime: 00:40:38
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB00048940A, 0x2, 0x0, 0xFFFFF80003093AD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Tue 06/03/2012 21:31:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030612-7316-01.dmp
uptime: 00:14:49
This was probably caused by the following module: asmtxhci.sys (asmtxhci+0x1B716)  
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88003B64716, 0xFFFFF8800A2F5708, 0xFFFFF8800A2F4F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\asmtxhci.sys
product: ASMedia USB 3.0 Host Drivers
company: ASMedia Technology Inc
description: ASMEDIA XHCI Host Controller Driver
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: asmtxhci.sys (ASMEDIA XHCI Host Controller Driver, ASMedia Technology Inc).  
Google query: asmtxhci.sys ASMedia Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
 
 
 
 
On Tue 06/03/2012 21:15:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030612-6271-01.dmp
uptime: 01:58:43
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)  
Bugcheck code: 0xA (0xFFFFFAB0033605EA, 0x2, 0x0, 0xFFFFF800030DAAD7)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.  
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
30 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have 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:  
 
asmtxhci.sys (ASMEDIA XHCI Host Controller Driver, ASMedia Technology Inc)
 
unknown  
 
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.  
 
 
Je vous remercie deja par avance de votre aide car j'aimerai enfin avoir un pc stable

il t'on changé la cm?

Le fichier asmtxhci.sys semble lié à une puce USB 3 : est-ce à jour ?