Écrans bleus, impossible de démarrer Windows 7 Fermé

Question

Bonjour à tous, me voici nouveau sur le forum.

Je possède un Asus P5K avec dessus une ZOTAC GeForce GTX285.
Je n'y connais pas grand chose en informatique, je fais donc appel aux connaisseurs!
Il y a une semaine je regardais un replay d'une émission, quand mon ordinateur a fait un écran bleu. Je l'ai redémarré et mon boot ami était différent, je suis donc rentré dans le BIOS pour remettre mon profil de paramètres qui était sauvegardé, j'ai pu redémarrer mais ça me l'a refait après le démarrage de Windows.
J'ai donc éteint et coupé l'alimentation un instant en appuyant sur l'interrupteur (on m'a dit que parfois cela suffisait), le démarrage normal de Windows s'est effectué mais après quelques secondes l'écran est resté figé et j'ai du forcé l'arrêt. (Ce qui ne m'arrive jamais ayant un SSD)
J'ai donc redémarré en mode sans échec avec prise en charge réseau et voilà que j'ai le même écran bleu une fois les fichiers système chargés. Photo à disposition.


J'attends donc vos avis pour la suite ! Merci beaucoup d'avance pour vos aides chaleureuses.

Chris9a · Answer

Up

istaff · Answer

Bonjour
Ca pourrait bien être un problème d'usb à en croire microsoft essaies ce qui est proposé sur cette page et dis moi ce que ça donne.
https://support.microsoft.com/en-us/help/979538/stop-error-message-in-windows-7-or-windows-server-2008-r2-stop-error-c

Utilisateur anonyme · Answer

Salut,

Que donne le fait de tapoter F8 au démarrage ? Si une liste est proposée, quelles sont les entrées qui "répondent" ?

Chris9a · Answer

J'ai entendu parler que Kaspersky pouvait créer ce problème d'erreur "0x0000007E", j'ai tenté un démarrage normal aujourd'hui et mon ordinateur a très bien démarré, je suis allé dans l'observateur d'évènements et je vois un événement critique " Kernel-Power", de quoi s'agit-il ?

Chris9a · Answer

Up...
Un peu de neuf... Mon ordinateur a démarré normalement, tout fonctionnait très bien, jusqu'à ce que je clique sur Chrome pour l'ouvrir, là mon ordi s'est mis à ramer et je ne pouvais faire grand chose à part bouger ma souris, jusqu'à avoir un écran bleu que voici.

Chris9a · Answer

Je désespère vraiment... J'ai en effet réalisé un sfc/ scannow et c'est aux alentours des 62% que mon ordinateur a planté et a fait cet écran bleu.

Chris9a · Answer

Bonjour, j'ai retenté un sfc /scannow et cette fois-ci il est allé jusqu'à 100% et m'a indiqué que le système se portait bien. En revanche, quelques secondes après, nouvel écran bleu que voici:


Moi qui n'y connait pas grand chose et qui pourtant prend très soin de ces affaires, je commence un peu à saturer... Merci de toute aide apportée

Chris9a · Answer

J'ai installé Whocrashed et voici l'analyse:

Merci de bien vouloir me guider pour la suite !




Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are disabled for your computer. 

On Sat 04/07/2015 21:29:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070415-7971-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74E90) 
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32
toskrnl.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 that cannot be identified at this time. 



On Sat 04/07/2015 21:28:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070415-8970-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x40F975) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000302C975, 0xFFFFF880041C48C8, 0xFFFFF880041C4120)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32
toskrnl.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 that cannot be identified at this time. 



On Wed 01/07/2015 09:28:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070115-8096-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C75D05, 0xFFFFF88009F1B8B0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.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 that cannot be identified at this time. 



On Tue 30/06/2015 17:51:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-8970-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0) 
Bugcheck code: 0x109 (0xA3A039D8956CC5F4, 0xB3B7465EE7E9955A, 0xFFFFF80002C21CD0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32
toskrnl.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 that cannot be identified at this time. 



On Thu 11/06/2015 19:47:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061115-8096-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0) 
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8003149A90, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32
toskrnl.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 Wed 10/06/2015 13:41:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061115-8080-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3FF38E) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000224B38E, 0xFFFFF880009A9788, 0xFFFFF880009A8FE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32
toskrnl.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 that cannot be identified at this time. 



On Sat 06/06/2015 10:46:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061015-7956-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800B02BFE8, 0xFFFFF8800B02B840, 0xFFFFF80002CD1243)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers
tfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Sat 30/05/2015 09:35:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\053015-10374-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0) 
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006C3DB30, 0xFFFFFA8006C3DE10, 0xFFFFF80002F8D130)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
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 21/05/2015 20:19:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052115-7737-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800A4CDF38, 0xFFFFF8800A4CD790, 0xFFFFF80002CC8497)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers
tfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Sun 10/05/2015 10:26:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051015-7519-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F77576, 0xFFFFF88003B4EE70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32
toskrnl.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 that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

21 crash dumps have been found and analyzed. Only 10 are included in this report. 2 third party drivers have 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: 

klif.sys (Klif Mini-Filter [fre_wlh_x64], Kaspersky Lab ZAO)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 340.52 , 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 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.

Malekal_morte- · Answer

Salut,

Possible problème de disque.
Tu devrais vérifier si HDD tune rapporte des erreurs depuis l'onglet Health :
=> https://forum.malekal.com/viewtopic.php?t=44006&start=

Chris9a · Answer

Voici le rapport fait par HDTune

Chris9a · Answer

Bonjour,

Mon ordinateur ne bootant jamais du premier coup, j'ai remis les paramètres du BIOS par défaut, et là mon ordinateur boot à chaque fois mais une fois sur le démarrage de windows, BSOD erreur 0x00000006.
J'ai donc décidé de tester mes barrettes mémoire une à une avec memtest86+ et l'une était défectueuse.
Je l'ai donc retiré et depuis tout fonctionne normalement.
Mais la première fois que j'avais eu un écran bleu (BSOD) c'était lors d'une vidéo que je regardais sur Chrome et depuis quand je tente d'ouvrir Chrome, mon ordinateur rame et freeze limite sans parvenir à ouvrir Google Chrome.
Comment puis-je réinstaller Chrome en conservant mes mots de passe enregistrés et mes données?

Cordialement.