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.
FORUM HardWare.fr
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!!