Forum Clubic

Bsod à répétition (carte mère suspectée)

Bonsoir,

J’ai des problèmes de BSOD sur on PC, ils sont apparu d’un coup, mais de manière aléatoire (je peux rien avoir pendant 1 semaine comme en avoir 5 en un jour, ça arrive a tout moment (sur le bureau, internet ou en jeux et même des fois j’ai l’impossibilté de retrouner sur le bureau, bsod en boucle…)).

J’ai surtout ces 2 codes :

  • 0x0000003B : SYSTEM_SERVICE_EXCEPTION
  • 0x0000000A : IRQL_NOT_LESS_OR_EQUAL

Ma config :

Asus P8Z68-V
i7 2600k
Noctua NH-UP12 SE2
MSI GTX 560 Ti 1GB
G.Skill 8Go 1600 MHz (2 x 4 Go)
Crucial M4 64 Go
WD Caviar blue 2 x 1 To
Corsair HX650W

Windows 7 x64 officiel

Les tests que j’ai effectué :

  • Memtest sur chacune de mes barretes de RAM (une a la fois) sur toute une nuit => aucune erreur sur les 2

  • Test d’intégrité des mes DD et de mon SSD avec HDTune => aucun secteur défectueux.

  • J’ai réinstallé le système, ça plante toujours (avec la config au complet).

  • J’ai réinstallé le système uniquement sur mon SSD, j’ai enlevé mes 2 DD (déconecté l’alim et le câble Sata) => ça palante…

  • J’ai réinstallé le système sur un des mes 2 DD, en enlevent le SSD (data + alim aussi) => ça plante.

  • J’ai refais ces 2 dernière opération en elevant aussi la CG (sortie du pc, alim débranchée), ça plante toujours.

(vive la clé usb boutable pour instaer windows, bien plus rapide, pour chaque réinstale c’étais avec tous les drivers a jours)

Constat :

Pour moi, ce n’est pas un problème des disque dur / SSD car ça plante que je sois sur l’un ou l’autre, et ni la CG car ça plante avec et sans.

Donc il me reste la Ram (sais pas si ce memtest est une fiabilité absolue), le proco (j’ai des doutes, car l’ordi ne démarerais même pas si il étais defectueux) et la cm, et la j’en ai pas d’autre pour tester, et pas envie de cramer 200 CHF pour en acheter une autre si le souci ne viens pas de la, mais je vois difficilement ce que ça pourrait etre d’autre…

Merci d’avence pour les réponses.

As tu essayé de tester les barrettes mémoires une à une sur chacun de des ports de ta carte mère ? Ou bien peut être de changer de nappe sata ou de branchement de tes disques durs sur ta carte mère ?

Pour la ram, je les ai testée une a une, mais que sur un seul port (le second que je pourrais utiliser est innacessible a cause du ventirad).

Pour la nappe Sata, j’ai essayé de faire des changement, sans succès.

:hello:
Tu as contôlé les températures avec openhardwaremonitor ?
Sinon tu as du matériel pour tester ? Ou un ami qui pourrait te prêter son alim, sa carte graphique, par exemple ?

Voici mes températures (qui me semblent normale)

http://www.freeshack.ch/images/J0zov.jpg

Je n’ai malheureusement pas de matériel de rechange pour faire des test.

Le rapport de WhoCrashed (j’ai vu qu’il a souvent été demandé dans d’autre sujet similaire, si ça peut servir)

System Information (local)

computer name: RÉGIS-FIXE-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core™ i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8482078720 total
VM: 2147352576, free: 1897467904


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 22.07.2012 12:55:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-7675-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CDC484, 0xFFFFF8800483DDE0, 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 which cannot be identified at this time.

On Sun 22.07.2012 12:55:22 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: 0x3B (0xC0000005, 0xFFFFF80002CDC484, 0xFFFFF8800483DDE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 which cannot be identified at this time.

On Sat 21.07.2012 08:27:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072212-6848-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF88009A45048, 0x2, 0x0, 0xFFFFF80002CE3484)
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 Fri 20.07.2012 21:26:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-8751-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF88003400048, 0x2, 0x0, 0xFFFFF80002CCC484)
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 Fri 20.07.2012 18:53:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-7675-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFF88003400048, 0x2, 0x0, 0xFFFFF80002C9A484)
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 Fri 20.07.2012 18:44:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-8611-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C9F484, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Fri 20.07.2012 00:11:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072012-7706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C90484, 0xFFFFF88009B21DE0, 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 which cannot be identified at this time.

The following dump files were found but could not be read. These files may be corrupt:
C:\Windows\Minidump\072012-8782-01.dmp


Conclusion

On your computer a total of 8 crash dumps have been found. Only 7 could be 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.