Ecran freeze
kyuuuu7
Messages postés
4
Statut
Membre
-
kyuuuu7 Messages postés 4 Statut Membre -
kyuuuu7 Messages postés 4 Statut Membre -
Bonjour,
J'ai problème mon écran freeze aléatoirement et je ne peux pu rien faire j'ai beau cliqué sur toutes les icônes ou les pages internet. Mais par contre je continu d'entendre la musique ou alors je peux continuer à parler sur skype. Quand ça plante un écran bleu apparaît parfois ou sinon sa reste figé indéfiniment, je suis alors obligé de reboot en appuyant sur le bouton sur la tour.
Ça peut planter à n'importe quel moment, quand je ne suis pas sur l'ordinateur avec aucune application de lancer ou alors en plein jeu.
A priori aucun virus j'ai passer scan de Ccleaner, spybot, malwarebytes, bitdefender ils ont rien trouver.
Mis à jour les drivers de ma carte graphique, mais le problème persiste.
Si quelqu'un à déjà eu ce problème ou sait comment le régler. Merci d'avance.
J'ai problème mon écran freeze aléatoirement et je ne peux pu rien faire j'ai beau cliqué sur toutes les icônes ou les pages internet. Mais par contre je continu d'entendre la musique ou alors je peux continuer à parler sur skype. Quand ça plante un écran bleu apparaît parfois ou sinon sa reste figé indéfiniment, je suis alors obligé de reboot en appuyant sur le bouton sur la tour.
Ça peut planter à n'importe quel moment, quand je ne suis pas sur l'ordinateur avec aucune application de lancer ou alors en plein jeu.
A priori aucun virus j'ai passer scan de Ccleaner, spybot, malwarebytes, bitdefender ils ont rien trouver.
Mis à jour les drivers de ma carte graphique, mais le problème persiste.
Si quelqu'un à déjà eu ce problème ou sait comment le régler. Merci d'avance.
A voir également:
- Ecran freeze
- Pc freeze - Guide
- Deep freeze - Télécharger - Sécurité
- Double ecran - Guide
- Capture d'écran whatsapp - Accueil - Messagerie instantanée
- Retourner ecran pc - Guide
2 réponses
soit un probleme de pilotes ou barrette mémoire qui flanche ou alim trop faible ou en train de lacher
@Miuar564 J'ai fais des test memtest86 apparament les barrettes mémoires sont OK. Peut être l'alim comme tu dis mais j'ai pas d'autre alim pour test.
A chaque fois qu'il y a un blue screen après le redémarrage il y a écrit ceci:
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8007CC7060
BCP3: FFFFFA8007CC7340
BCP4: FFFFF800033D8460
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\123112-13462-01.dmp
C:\Users\KYU\AppData\Local\Temp\WER-15178-0.sysdata.xml
J'ai également fais une analyse avec Whocrashed voici le report :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 31/12/2012 05:16:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-13462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007CC7060, 0xFFFFFA8007CC7340, 0xFFFFF800033D8460)
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 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 Mon 31/12/2012 05:16:49 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: 0xF4 (0x3, 0xFFFFFA8007CC7060, 0xFFFFFA8007CC7340, 0xFFFFF800033D8460)
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 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 Sun 30/12/2012 23:16:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-12792-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007C21B30, 0xFFFFFA8007C21E10, 0xFFFFF80003382460)
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 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 Sun 30/12/2012 06:12:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123012-12058-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007B71060, 0xFFFFFA8007B71340, 0xFFFFF800033E4460)
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 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.
Quelqu'un pour m'aider?
A chaque fois qu'il y a un blue screen après le redémarrage il y a écrit ceci:
Signature du problème :
Nom d'événement de problème: BlueScreen
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036
Informations supplémentaires sur le problème :
BCCode: f4
BCP1: 0000000000000003
BCP2: FFFFFA8007CC7060
BCP3: FFFFFA8007CC7340
BCP4: FFFFF800033D8460
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Fichiers aidant à décrire le problème :
C:\Windows\Minidump\123112-13462-01.dmp
C:\Users\KYU\AppData\Local\Temp\WER-15178-0.sysdata.xml
J'ai également fais une analyse avec Whocrashed voici le report :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 31/12/2012 05:16:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-13462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007CC7060, 0xFFFFFA8007CC7340, 0xFFFFF800033D8460)
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 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 Mon 31/12/2012 05:16:49 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: 0xF4 (0x3, 0xFFFFFA8007CC7060, 0xFFFFFA8007CC7340, 0xFFFFF800033D8460)
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 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 Sun 30/12/2012 23:16:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-12792-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007C21B30, 0xFFFFFA8007C21E10, 0xFFFFF80003382460)
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 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 Sun 30/12/2012 06:12:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123012-12058-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8007B71060, 0xFFFFFA8007B71340, 0xFFFFF800033E4460)
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 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.
Quelqu'un pour m'aider?
