Si c'est un problème matériel cela ne résoudra rien.
Essaie encore ceci :
http://www.chantal11.com/installer-demarrer-reparer-windows-seven-7-vista/
Cela prend moins de temps.
Windows 7 (Bluescreen - arrêt non planifié)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonyme
Bonjour,
J'ai un Sony Vaio sous windows 7 édition familiale premium 64bits.
Le problème est que mon ordinateur n'arrête pas de redémarrer.... Juste avant le redémarrage j'ai droit à un écran bleu. Après l'apparition de l'écran bleu mon ordinateur redémarre. Une fois redémarré, j'ai un message de la part de Windows me parlant d'un arrêt non planifié :
Signature du problème :
Nom d’événement de problème: BlueScreen
Version du système: 6.0.6001.2.1.0.768.3
Identificateur de paramètres régionaux: 1036
...
Le message que j'ai juste avant le redémarrage : [http://cjoint.com/?BCkxwKcGuuY]
Windows pour les particuliers | Versions antérieures de Windows | Niveau de performance et défaillances système
Question verrouillée. Cette question a été migrée à partir de la Communauté Support Microsoft. Vous pouvez voter pour indiquer si elle est utile, mais vous ne pouvez pas ajouter de commentaires ou de réponses ni suivre la question.
Réponse acceptée par l’auteur de la question
Anonyme
17 réponses supplémentaires
Trier par : Le plus utile
-
Anonyme
2012-03-04T17:47:56+00:00 Alors,
J'ai un Sony Vaio donc j'ai étais voir sur le site du constructeur, ma Bios et les autres pilotes sont bien à jour.
J'ai fais une analyse avec Malwarebyte = aucune infection détecté,
Idem avec scannow.
Et pour finir j'ai fais vérifier sur c:\propriétés\outils...
Merci pour ton aide J.-K
-
Anonyme
2012-03-04T14:34:28+00:00 Peut-être un problème de pilotes, de mises à jour.
Si c'est un ordinateur de marque faites un tour sur le site du constructeur, voir s'il y a une mise à jour du bios, sinon
Faites aussi une analyse :
http://www.malekal.com/2010/11/12/tutorial-malwarebyte-anti-malware/
Et encore touche Windows gauche et R cmd et ensuite sfc/scannow.
Un clic droit sur c:\propriétés\outils\vérifier, vous cochez les deux cases, il faut redémarrer, mais il faut faire cela lorsque l'on n'a pas besoin du pc car cela peut prendre des 10aines de minutes.
-
Anonyme
2012-03-04T13:48:33+00:00 Merci, voilà le rapport :
System Information (local)
computer name: ADMINISTRATEUR
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II P360 Dual-Core Processor AMD586, level: 16
2 logical processors, active mask: 3
RAM: 4021182464 total
VM: 2147352576, free: 1971134464
*** * Crash Dump Analysis*
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 04/03/2012 12:26:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-38235-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x86ADC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800034EDADC, 0xFFFFF880064BB7B8, 0xFFFFF880064BB010)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 04/03/2012 12:15:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-25053-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x18 (0x0, 0xFFFFFA800542B670, 0x1, 0x1)
Error: REFERENCE_BY_POINTER
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 reference count of an object is illegal for the current state of the object.
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 which cannot be identified at this time.
On Sun 04/03/2012 12:08:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-21964-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x86ADC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800034DCADC, 0xFFFFF880094C97B8, 0xFFFFF880094C9010)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 04/03/2012 12:01:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-25194-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x86ADC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003495ADC, 0xFFFFF88008BA27B8, 0xFFFFF88008BA2010)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 04/03/2012 11:54:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030412-24616-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x86ADC)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800034D6ADC, 0xFFFFF880089D77B8, 0xFFFFF880089D7010)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 01/03/2012 21:43:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030112-26098-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000372384E, 0x0, 0x4)
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.
*** * Conclusion*
6 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.
-
Anonyme
2012-03-04T13:44:47+00:00 Bonjour,
Faites une analyse complète :
http://www.forum-seven.com/whocrashed-outil-danalyse-des-ecrans-bleus-996
Vous copiez la totalité du rapport que vous collez dans votre réponse.