BSOD à répétition (ntoskrnl.exe) - Win 7 - Windows & Software
Marsh Posté le 22-05-2012 à 09:46:26
Ton OC est-il vraiment stable?
Et si il l'est ===> l'est-il sur la durée?
Quand tu dis: Réinstaller le système sur mon SSD et sur un partition de mon disque dur
Tu as fait un raid des deux disque?
Fait un test OCCT et pas de 10 minutes mais minimum 1H.
Fait un test mémoire au démarrage.
Vérifie si ton alim fournie se qu'il faut "stabilité de l'alimentation a apporter l'énergie a ton PC"
Es-tu en double canal sur ta carte mère ou as-tu 4x2Go?
Test tes barrettes de RAM une par une t'enlève les autres et tu en laisse qu'une.
Test ton DD.
Ta pâte thermique est-elle encore bonne.
Ton CPU chauffe t'il trop ou pas?
Tes drivers sont ils a jour?
As-tu bien configuré ton SSD?
Marsh Posté le 23-05-2012 à 13:21:05
Je vois que tu as un crucial M4, à tout hasard, quelle est ta version du Firmware?
Je suppose que tu as entendu parler du "bug" des M4 qui provoque des BSOD toutes les heures, problème qui se résout en mettant à jour le Firmware. Sinon, c'est peut être ça? ^^
Marsh Posté le 23-05-2012 à 15:48:26
Sa dois pas vraiment le déranger vue le temps qu'il met a répondre.
Marsh Posté le 20-05-2012 à 23:49:07
Bonsoir,
J'ai depuis peut des BSOD à répétition, que je sois sur le bureau, sur internet ou sur un jeu, c'est aléatoire.
J'ai fais les choses suivantes :
- Un memtest, aucune erreur
- Réinstaller le système sur mon ssd et sur un partition de mon disque dur, toujours ces BSOD
- Enlever la carte graphique et utiliser celle intégrée, même soucis
Ma config
Windows 7 x64
Asus P8Z68-V
i7 2600k @4.8 GHz
Noctua NH-UP12 SE2
MSI GTX 560 Ti 1GB
G.Skill 8Go 1600 MHz
Crucial M4 64 Go
WD Caviar blue 2 x 1 To
Corsair HX650W
Détail des BSOD
On Sun 20.05.2012 21:17:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-16707-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ED21E6, 0xFFFFF88005A262E0, 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 20.05.2012 21:15:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-21247-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002ED01E6, 0xFFFFF880067D75B0, 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 20.05.2012 21:06:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052012-21699-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8E1E6, 0xFFFFF88004057FA0, 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and 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.
Merci de vos réponses
Message édité par _Reg24_ le 21-05-2012 à 08:58:50