GixxerGSXR

...J'ai précisé en début de message sur mon 2e PC (pas celui ou j'avais des BSOD) et ZHPDIAG ne trouvera pas grand chose ou du moins le PC plantera et s'eteindra avant fin du diag.

Ben, je n'ai pas encore testé en fonctionnement à "plein régime" c à d avec softs gourmands en ressources (3D etc). Donc j'peux pas dire "résolu"

Bjr, tu peux essayer de le monter sur une autre mécanique HDD de même type mais bon... C'est chaud à tenter et faut le faire avec des gants, sans poussière, en apnée etc. Entends tu un bruit genre "gggrrrt..... grrrrrtttt", si tu l'as, la tete de lecture est morte... sinon tente une recup avec utilitaire genre "file scavenger" ou recuperation disque style TestDisk ou Recuva

Bonjour, mon 2e PC plante tout seul au bout d'une durée aléatoire, je démarre Win7 64bits sur SSD (M4 256 Mo) et j'ai un HDD de 1Go dessus. L'alim semble tourner, mais je n'ai pas de "bip" caractéristique au démarrage.... bizarre. Je précise aussi que l'écran passe en "pas de source" c à dire qu'il ne voit plus de source vidéo (carte graphique)... J'ai booté sur Vista 32 sur le HDD et, pareil plantages aléatoires des fois çà tient 5 min, des fois çà plante avant même démarrage Win7. Ptet la pile Lithium CR2032 sur carte mêre ??...

Bjr tous, bon... après mise à jour de tous les drivers plus de plantages BSOD...

Quelqu'un aurait une idée ?

Bsr, oui ou sinon essayez de lire les CDs sur un autre PC/lecteur et faire un backup sur Ddur, et oui... malgré les promesses dans les années 80 le CD n'est pas immortel, moi j'en ai qui ont jauni et qui sont illisibles.

hmmm... pas grand monde que çà interresse mon soucis, je précise que les BSOD sont totalement aléatoires, et interviennent sous navigateurs, logiciels 3D (3DSMax), ou 2D (After Effects) voire même des jeux. J'ai mis à jour les drivers de la Geforce GTX680, fais un windows update.

bsr, hummm... ca sent pas bon, éventuellement essaye de monter le disk sur un autre boitier des fois qu çà ne soit que l'alim. Sinon pour récupérer les datas il y avait file scavenger il y a longtemps qui était bien... Cherche sur Google. http://www.fr.quetek.com/prod02.htm

Bonjour à tous (tes), j'ai un soucis récurrent sur mon PC, plantages écrans bleu (BSOD), j'avais vu sur forum Zébulon qu'il était bon de mettra à jour son firmware de SSD (Crucial 256Go) ce que j'ai fait, çà a améliorer la chose, et pendant quelques temps plus de problêmes de crash écrans bleus. J'ai également fais des tests Ram avec memtest et... RAS. Je vous joint les rapports whocrashed qui indique que c'est NToskrnl.exe en cause. Je ne sais plus quoi faire à part vérifier/changer les barettes Ram ->Rue Montgallet Vous avez une partie de ma config en début de rapport Whocrashed : carte graphique NVidia Gefroce GTX 680 SSD crucial m4 256 Go 16 Go Ram Corsair System Information (local) computer name: STEFI7-3770K windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Core i7-3770K CPU @ 3.50GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 17132875776 total VM: 2147352576, free: 1923186688 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 09/09/2013 16:27:30 GMT your computer crashed crash dump file: C:\Windows\Minidump\090913-10342-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C072960, 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 09/09/2013 16:27:30 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: 0x1A (0x41790, 0xFFFFFA800C072960, 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. 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 02/09/2013 22:55:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\090313-9391-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C072900, 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 Sun 01/09/2013 08:27:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\090113-10140-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C072900, 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. Edit de Notpa : sujet déplacé dans forum Harware, plus approprié.

bonjour tous, mise à jour firmware m4 effectuée et... plus un seul plantage !!! mise a jour indispensable !!

Mémoire vérifiée avec Memtest et pas de problême, par contre l'update firmware a semble t'il bien fonctionné, pas de BSOD depuis...

çà pourrait venir du SSD 256 Go M4, il y a un update du firmware : Mon lien

les dates de whocrashed sont bidons...

Bonjour, depuis quelques temps et de plus en plus régulièrement, j'ai des crashs avec écrans bleus (BSOD). ma config : I7 3770K 3,5Ghz / 16 Go Ram Corsair / CG Geforce GTX680 2Go / Win7 64 bits pro. Je soupçonne un soucis avec une des barettes RAM, Je lance un check Ram avec memtest, mais dans le doute, je vous joint rapport whocrashed, apparemment il s'agit de ntoskrnl.exe Que faire ? Help ! ntoskrnl.exe System Information (local) -------------------------------------------------------------------------------- computer name: STEFI7-3770K windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Core i7-3770K CPU @ 3.50GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 17132875776 total VM: 2147352576, free: 1913053184 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 11/10/2012 17:24:16 GMT your computer crashed crash dump file: C:\Windows\Minidump\101112-10686-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C072930, 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 11/10/2012 17:24:16 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: 0x1A (0x41790, 0xFFFFFA800C072930, 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. 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 10/10/2012 19:45:01 GMT your computer crashed crash dump file: C:\Windows\Minidump\101012-9126-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x50 (0xFFFFD6000313A615, 0x8, 0xFFFFD6000313A615, 0x7) Error: PAGE_FAULT_IN_NONPAGED_AREA 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 invalid system memory has been referenced. 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 Wed 10/10/2012 15:22:53 GMT your computer crashed crash dump file: C:\Windows\Minidump\101012-9219-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x1A (0x41790, 0xFFFFFA800C072960, 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 17/09/2012 07:39:46 GMT your computer crashed crash dump file: C:\Windows\Minidump\091712-9048-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0) Bugcheck code: 0x19 (0x3, 0xFFFFF8A0049CD070, 0xFFFF58A0049CD070, 0xFFFFF8A0049CD070) Error: BAD_POOL_HEADER 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 pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 5 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.