Vous êtes sur la page 1sur 12

PC crash au démarrage - écran bleu 0x000000F4

forums.cnetfrance.fr/topic/1405609-pc-crash-au-demarrage--ecran-bleu-0x000000f4/

1.
Membre

12/05/2018 18h51 #1

1/12
Bonjour, j'ai plusieurs problèmes avec mon PC, je ne sais pas s'ils sont liés, mais voilà
qu'aujourd'hui il crash dès le démarrage de manière systématique.
Depuis un moment, le PC buguait au démarrage de manière plus ou moins aléatoire, la
souris bougeait, mais rien de répondait, les programmes ne se lançaient pas et le menu
démarrer non plus. Parfois, j'avais le droit à un écran bleu.

Aujourd'hui, l'écran bleu devient systématique au démarrage. Le PC se lance, je peux


parfois accéder à quelques dossiers, j'ai réussi à aller regarder les services, mais
rapidement il plante, écran bleu, STOP: 0x000000F4

Je ne sais pas, et ne pense pas que le problème soit récent, à mon humble avis il s'inscrit
dans le temps long, donc je vous fais un petit récap des problèmes que j'ai pu
rencontrer:

- Les Mises à jour de Windows Update ne parviennent pas à s'installer, et l'installation


redémarre ad vitam eternam. Ne parvenant pas à régler le problème, j'ai désactivé
Windows Update (je sais, c'est pas bien, mais après des jours et des jours de recherche
de solution, j'ai opté pour une "solution" radicale)

- Lorsque Windows a proposé W10 gratuitement, je me suis dit que c'était l'opportunité
de remettre un peu d'ordre dans windows et potentiellement régler le problème. Mais
j'ai eu un problème à peu près similaire, à savoir que l'installation de W10 se déroulait
sans problème jusqu'à ce qu'à la fin, ça me dise qu'il y avait un problème, et
l'installation échouait. J'ai tenté de reboot windows 7, même problème. Là encore, j'ai
laissé tombé...

- Outre les problèmes randoms au démarrage, j'ai remarqué que depuis quelques mois
(j'ai fourgué mon PC à mes neveux je n'y ai plus accès très souvent) le PC crashait lors
de mises à jour, par exemple lorsqu'ils téléchargeaient une mise à jour de Fortnite. De
mon côté, plusieurs téléchargements ont également entraîné des crashs intempestifs, du
coup peut-être un lien avec l'inscription de données sur le DD, ou la ram ?

Je ne sais pas si c'est matériel ou logiciel, j'avais lancé des anti-malware à l'époque,
présentement je ne peux plus.
Le DD ne fait aucun bruit suspect

Le PC démarre très bien en mode sans échec.

Voilà, je crois que j'ai à peu près tout dit, si vous avez des idées, ça me sauverait !

Merci d'avance !

2. CNETFrance

Aujourd'hui

2/12
Ces sujets peuvent apporter des réponses ou des infos complémentaires :

3.
Habitué

12/05/2018 20h18 #2

3/12
Bonjour, bienvenue sur le forum,
Téléchargez : Whocrashed Free home Edition

Lancez Whocrashed et cliquez simplement sur: "Analyser"

Une fois le scan terminé, un message vous en informe, faites: "OK"

Puis allez dans


l'onglet rapport, et
faites un copier coller
du texte du rapport,

Cordialement config@33

4.
Membre

12/05/2018 21h09 #3
Merci pour votre réponse !
J'ai mené une analyse malwarebytes:

Malwarebyteswww.malwarebytes.com-Détails du journal-Date de l'analyse:


12/05/2018Heure de l'analyse: 21:32Fichier journal: 3b7e02ca-561b-11e8-a156-
00ffd28d84a6.jsonAdministrateur: Oui-Informations du logiciel-Version:
3.5.1.2522Version de composants: 1.0.365Version de pack de mise à jour:
1.0.5080Licence: Essai-Informations système-Système d'exploitation: Windows 7
4/12
Service Pack 1Processeur: x64Système de fichiers: NTFSUtilisateur: Paillou-
PC\Paillou-Résumé de l'analyse-Type d'analyse: Analyse des menacesAnalyse lancée
par: ManuelRésultat: TerminéObjets analysés: 305847Menaces détectées: 19Menaces
mises en quarantaine: 0(Aucun élément malveillant détecté)Temps écoulé: 14 min, 56
s-Options d'analyse-Mémoire: ActivéDémarrage: ActivéSystème de fichiers:
ActivéArchives: ActivéRootkits: DésactivéHeuristique: ActivéPUP: DétectionPUM:
Détection-Détails de l'analyse-Processus: 0(Aucun élément malveillant détecté)Module:
0(Aucun élément malveillant détecté)

Clé du registre: 4PUP.Optional.InstallCore, HKU\S-1-5-21-2260971112-752040479-


223628602-1000\SOFTWARE\csastats, Aucune action de l'utilisateur, [388],
[260986],1.0.5080PUP.Optional.Komodia, HKU\S-1-5-21-2260971112-752040479-
223628602-1000\SOFTWARE\INSTALLPATH\STATUS, Aucune action de
l'utilisateur, [457], [255363],1.0.5080PUP.Optional.InstallCore, HKU\S-1-5-21-
2260971112-752040479-223628602-1000\SOFTWARE\PRODUCTSETUP, Aucune
action de l'utilisateur, [388], [481004],1.0.5080PUP.Optional.SearchManager, HKU\S-
1-5-21-2260971112-752040479-223628602-
1000\SOFTWARE\GOOGLE\CHROME\EXTENSIONS\ijahobfejge
blmkpcmgpelfibgnnjpil, Aucune action de l'utilisateur, [243], [464615],1.0.5080Valeur
du registre: 3PUP.Optional.Komodia, HKU\S-1-5-21-2260971112-752040479-
223628602-1000\SOFTWARE\INSTALLPATH\STATUS|FLOWSURFCB, Aucune
action de l'utilisateur, [457], [255363],1.0.5080PUP.Optional.RestoreSearch.ChrPRST,
HKU\S-1-5-21-2260971112-752040479-223628602-
1000\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\RUN |C,
Aucune action de l'utilisateur, [6258], [258570],1.0.5080PUP.Optional.InstallCore,
HKU\S-1-5-21-2260971112-752040479-223628602-
1000\SOFTWARE\PRODUCTSETUP|TB, Aucune action de l'utilisateur, [388],
[481004],1.0.5080Données du registre: 1PUP.Optional.SnapDo,
HKLM\SOFTWARE\WOW6432NODE\MICROSOFT\INTERNET
EXPLORER\SEARCHURL|DEFAULT, Aucune action de l'utilisateur, [177],
[293198],1.0.5080Flux de données: 0(Aucun élément malveillant détecté)Dossier:
0(Aucun élément malveill

Quant à Whocrashed, voilà le rapport:

System Information (local)

Computer name: PAILLOU-PC


Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASRock, Z77 Extreme4

5/12
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8478789632 bytes total

Crash Dump Analysis

Crash dumps are enabled on your computer. This system is not configured for complete
or automatic crash dumps. For best results, configure your system to write out complete
or automatic crash dumps. Select Tools->Crash Dump Configuration from the main
menu to configure your system to write out complete memory dumps.

Crash dump directories:


C:\Windows
C:\Windows\Minidump

On Sat 12/05/2018 21:57:43 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\051218-51698-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800D0FAB10, 0xFFFFFA800D0FADF0,
0xFFFFF80003FDB6D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Sat 12/05/2018 21:57:43 your computer crashed or a problem was reported


crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe
(nt!PsSetCurrentThreadPrefetching+0x6E2)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800D0FAB10, 0xFFFFFA800D0FADF0,
0xFFFFF80003FDB6D0)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
6/12
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Sat 12/05/2018 21:14:50 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\051218-47455-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AE6C180, 0xFFFFFA800AE6C460,
0xFFFFF80003F946D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Sat 12/05/2018 20:55:20 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\051218-51776-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800A859870, 0xFFFFFA800A859B50,
0xFFFFF80003F9A6D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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.

7/12
On Sat 12/05/2018 20:44:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051218-51043-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800DB84060, 0xFFFFFA800DB84340,
0xFFFFF80003F886D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Sat 12/05/2018 19:36:25 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\051218-50731-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800DF39B10, 0xFFFFFA800DF39DF0,
0xFFFFF80003F946D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Sat 12/05/2018 19:14:34 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\051218-54413-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800DF58630, 0xFFFFFA800DF58910,
0xFFFFF80003F7E6D0)
Error: CRITICAL_OBJECT_TERMINATION
8/12
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Sat 12/05/2018 18:26:06 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\051218-39374-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800CC58A50, 0xFFFFFA800CC58D30,
0xFFFFF80003FD96D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Tue 19/09/2017 16:38:36 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\091917-29874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800D650060, 0xFFFFFA800D650340,
0xFFFFF80003FE16D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
9/12
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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 Mon 11/09/2017 16:25:05 your computer crashed or a problem was reported


crash dump file: C:\Windows\Minidump\091117-144644-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x73C40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800DA57060, 0xFFFFFA800DA57340,
0xFFFFF80003F7F6D0)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system
operation has unexpectedly exited or been terminated. This bug check is typically
caused by a thermal issue. It's suggested that you do temperature checking on your
CPUs and hardware.
This is likely to be caused by a hardware problem. This problem might also be caused
because of overheating (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.

Conclusion

On your computer a total of 25 crash dumps have been found. Only 10 have been
analyzed. No offending third party drivers have been found.
Donc un bête cas de surchauffe ? Le PC ne plante pas en mode sans échec, ça chauffe
moins j'imagine cela dit... J'ai fait tourner Speedfan, mon proc est à 45-50° en mode
sans échec donc...

J'avais changé de ventilateur pour le proc et remis de la pâte thermique, y a de ça un an


environ, je l'ai peut être mal fait...

Dernière modification de Squalli, 12/05/2018 à 21h26

5.
Habitué

10/12
13/05/2018 15h10 #4
Bonjour, fournissez nous un rapport speccy
Cordialement config@33

6.
Membre

15/05/2018 15h31 #5
Je viens de tenter une analyse speccy ça a fait crash le PC. A la réflexion, mes neveux
pouvaient jouer sans aucun problème pendant des heures, les crashs n'intervenaient
qu'en cas de téléchargement, du coup à priori la surchauffe est hors de propos.
Je tente de relancer une analyse. Nouveau crash

Dernière modification de Squalli, 15/05/2018 à 15h34

7.
Habitué

15/05/2018 22h18 #6
Bonjour,
suivez: http://forums.cnetfrance.fr/topic/12...ystaldiskinfo/

Cordialement config@33

8.
Membre

Hier 16h06 #7

11/12
Alors, le logiciel reconnaît mon DD mais l'icône est grise avec un statut "inconnu"
J'ai vu que le gris était plutôt mauvais signe, par ailleurs, le logiciel du constructeur m'a
également dit que le DD était out, cela dit, sur CrystalDiskInfo, quand je vais dans
"Gestion des Disques", le statut est sur "sain".

Du coup, j'me dis qu'avec un peu de chance les câbles de connexion sont en cause ? Et
je crains aussi que ça puisse concerner la carte mère ? Aucune idée...

9.
Habitué

Hier 22h30 #8
Bonjour, si c'est inconnue ça sens mauvais, faites un test depuis un autre PC, si besoin
avec un adaptateur SATA vers USB
Cordialement config@33

10.

Tutoriels

Photoshop : comment réduire taille et poids d'une image ou photo et la


sauvegarder
Windows 10 : comment vérifier la version d'un pilote de matériel
Photoshop : comment zoomer avec la molette de la souris ou centrer au
zoom
Office Word ou Excel : lecture à voix haute d'un document depuis la barre
d'accès rapide
Windows 7/8/10 "Fix it" : toutes les solutions rapides de dépannage pour les
problèmes courants

12/12