[Résolu] Mise en veille intempestive

[oneill76]

http://forum.zebulon.fr/eradication-de-trovi-et-autres-t212229.html

 

Cette eradication a résolu le sujet

 

 

 

 

Bonjour depuis quelques jours mon ordi se met en veille tout seul.

 

En gros je suis sur l'ordi à travailler et d'un seul coup il passe en veille sans que je lui ai demandé quoi que ce soit, je rappuie sur la touche allumer et il revient à la demande de mot de passe.

 

Pourriez-vous m'en dire plus... un virus ? un fichier de paramètres ?

 

Cordialement

alexis

Modifié le 24 mai 2015 par oneill76

[oneill76]

a oui et le dernier truc en date ;

 

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: 109
BCP1: A3A039D89EE2F5DC
BCP2: B3B7465EF16134DA
BCP3: FFFFF8800317D640
BCP4: 0000000000000003
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Fichiers aidant à décrire le problème :
C:\Windows\Minidump\051915-55099-01.dmp
C:\Users\bonheur\AppData\Local\Temp\WER-288804-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt

 

 

 

JE RAJOUTE UNE RAPPORT WHOCRASHED

 

 

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 19/05/2015 14:42:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051915-55099-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x109 (0xA3A039D89EE2F5DC, 0xB3B7465EF16134DA, 0xFFFFF8800317D640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 Tue 19/05/2015 14:42:19 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: 0x109 (0xA3A039D89EE2F5DC, 0xB3B7465EF16134DA, 0xFFFFF8800317D640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 Tue 19/05/2015 13:54:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051915-50154-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x109 (0xA3A039D89E939760, 0xB3B7465EF111D64E, 0xFFFFF8800317D640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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 Mon 18/05/2015 23:09:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\051915-35677-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x109 (0xA3A039D89EBB283D, 0xB3B7465EF139696B, 0xFFFFF880032B0640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 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.

Modifié le 19 mai 2015 par oneill76

[ab-web]

bonjour

 

ce genre de crash est difficilement identifiable

il n'y a pas de modules ou pilotes clairement mis en cause , sur le rapport .

 

bien que la RAM ne soi pas mise en cause d'une façon nette .

il faut envisager un controle .

 

dans un premier temps

il faut faire une vérification des fichiers

sous XP dans exécuter [/b],tape ou colle : sfc /scannow
le disque d'installation est généralement nécessaire
a l'insertion du disque fermer la fenêtre bleu des choix qui va s'ouvrir .

pour les autre systèmes ouvrir une invite de commande

- sous vista 7
menu démarrer > tous les programmes > accessoires > clic droit sur invite de commande > exécuter en tant qu'administrteur

- windows8-8.1 touche windows+x invite de commandes (admin)

tape ou colle cette commande : sfc /scannow
valide par entrée

Pour déterminer si des fichiers ne peuvent pas être réparés par l'outil Vérificateur des fichiers système :
créer un fichier de commande
copier ce qui suis dans le bloc note , lignes vertes

@echo off
findstr /c:"[sR]" %windir%\Logs\CBS\CBS.log > %userprofile%\Desktop\sfcdetails.txt

enregistrer sous cbslog.bat ( sur le bureau )
lancer par double clic sous XP
pour les autres systèmes >clic droit > exécuter en tant qu'administrateur .


ou
Télécharger cbslog.bat >http://fspsa.free.fr/cbslog.bat
Enregistre le sur le Bureau
Sous XP lance par double clic
sous vista 7 ou8 :Clic droit sur cbslog.bat > exécuter entant qu'administrateur

Le rapport sfcdetailsrepair.txt s'afficheil ya deux rapports souvent l'un sur l'autre ( faire glisser le premier pour avoir accès au second)
mettre le rapport sfcdetailsrepair.txt sur la réponse

Modifié le 19 mai 2015 par ab-web

[oneill76]

2015-05-20 00:35:58, Info CSI 00000009 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:35:58, Info CSI 0000000a [sR] Beginning Verify and Repair transaction
2015-05-20 00:36:03, Info CSI 0000000c [sR] Verify complete
2015-05-20 00:36:10, Info CSI 0000000d [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:36:10, Info CSI 0000000e [sR] Beginning Verify and Repair transaction
2015-05-20 00:36:18, Info CSI 00000010 [sR] Verify complete
2015-05-20 00:36:24, Info CSI 00000011 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:36:24, Info CSI 00000012 [sR] Beginning Verify and Repair transaction
2015-05-20 00:36:29, Info CSI 00000014 [sR] Verify complete
2015-05-20 00:36:34, Info CSI 00000015 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:36:34, Info CSI 00000016 [sR] Beginning Verify and Repair transaction
2015-05-20 00:36:39, Info CSI 00000018 [sR] Verify complete
2015-05-20 00:36:43, Info CSI 00000019 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:36:43, Info CSI 0000001a [sR] Beginning Verify and Repair transaction
2015-05-20 00:36:50, Info CSI 0000001c [sR] Verify complete
2015-05-20 00:36:58, Info CSI 0000001d [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:36:58, Info CSI 0000001e [sR] Beginning Verify and Repair transaction
2015-05-20 00:37:05, Info CSI 00000020 [sR] Verify complete
2015-05-20 00:37:18, Info CSI 00000021 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:37:18, Info CSI 00000022 [sR] Beginning Verify and Repair transaction
2015-05-20 00:37:31, Info CSI 00000024 [sR] Verify complete
2015-05-20 00:37:40, Info CSI 00000025 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:37:40, Info CSI 00000026 [sR] Beginning Verify and Repair transaction
2015-05-20 00:37:48, Info CSI 00000028 [sR] Verify complete
2015-05-20 00:37:59, Info CSI 00000029 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:37:59, Info CSI 0000002a [sR] Beginning Verify and Repair transaction
2015-05-20 00:38:05, Info CSI 0000002c [sR] Verify complete
2015-05-20 00:38:08, Info CSI 0000002d [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:38:08, Info CSI 0000002e [sR] Beginning Verify and Repair transaction
2015-05-20 00:38:12, Info CSI 00000030 [sR] Verify complete
2015-05-20 00:38:15, Info CSI 00000031 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:38:15, Info CSI 00000032 [sR] Beginning Verify and Repair transaction
2015-05-20 00:38:19, Info CSI 00000034 [sR] Verify complete
2015-05-20 00:38:21, Info CSI 00000035 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:38:21, Info CSI 00000036 [sR] Beginning Verify and Repair transaction
2015-05-20 00:38:25, Info CSI 00000038 [sR] Verify complete
2015-05-20 00:38:28, Info CSI 00000039 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:38:28, Info CSI 0000003a [sR] Beginning Verify and Repair transaction
2015-05-20 00:38:33, Info CSI 0000003c [sR] Verify complete
2015-05-20 00:38:39, Info CSI 0000003d [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:38:39, Info CSI 0000003e [sR] Beginning Verify and Repair transaction
2015-05-20 00:38:43, Info CSI 00000040 [sR] Verify complete
2015-05-20 00:38:46, Info CSI 00000041 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:38:46, Info CSI 00000042 [sR] Beginning Verify and Repair transaction
2015-05-20 00:38:51, Info CSI 00000044 [sR] Verify complete
2015-05-20 00:38:54, Info CSI 00000045 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:38:54, Info CSI 00000046 [sR] Beginning Verify and Repair transaction
2015-05-20 00:39:28, Info CSI 00000048 [sR] Verify complete
2015-05-20 00:39:31, Info CSI 00000049 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:39:31, Info CSI 0000004a [sR] Beginning Verify and Repair transaction
2015-05-20 00:39:36, Info CSI 0000004c [sR] Verify complete
2015-05-20 00:39:38, Info CSI 0000004d [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:39:38, Info CSI 0000004e [sR] Beginning Verify and Repair transaction
2015-05-20 00:39:51, Info CSI 00000050 [sR] Verify complete
2015-05-20 00:39:54, Info CSI 00000051 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:39:54, Info CSI 00000052 [sR] Beginning Verify and Repair transaction
2015-05-20 00:40:03, Info CSI 00000054 [sR] Verify complete
2015-05-20 00:40:06, Info CSI 00000055 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:40:06, Info CSI 00000056 [sR] Beginning Verify and Repair transaction
2015-05-20 00:40:14, Info CSI 00000058 [sR] Verify complete
2015-05-20 00:40:17, Info CSI 00000059 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:40:17, Info CSI 0000005a [sR] Beginning Verify and Repair transaction
2015-05-20 00:40:29, Info CSI 0000005c [sR] Verify complete
2015-05-20 00:40:32, Info CSI 0000005d [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:40:32, Info CSI 0000005e [sR] Beginning Verify and Repair transaction
2015-05-20 00:40:37, Info CSI 00000060 [sR] Verify complete
2015-05-20 00:40:40, Info CSI 00000061 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:40:40, Info CSI 00000062 [sR] Beginning Verify and Repair transaction
2015-05-20 00:40:48, Info CSI 00000064 [sR] Verify complete
2015-05-20 00:40:50, Info CSI 00000065 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:40:50, Info CSI 00000066 [sR] Beginning Verify and Repair transaction
2015-05-20 00:41:04, Info CSI 00000068 [sR] Verify complete
2015-05-20 00:41:05, Info CSI 00000069 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:41:05, Info CSI 0000006a [sR] Beginning Verify and Repair transaction
2015-05-20 00:41:36, Info CSI 0000006c [sR] Verify complete
2015-05-20 00:41:36, Info CSI 0000006d [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:41:36, Info CSI 0000006e [sR] Beginning Verify and Repair transaction
2015-05-20 00:41:53, Info CSI 00000070 [sR] Verify complete
2015-05-20 00:41:54, Info CSI 00000071 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:41:54, Info CSI 00000072 [sR] Beginning Verify and Repair transaction
2015-05-20 00:42:09, Info CSI 00000074 [sR] Verify complete
2015-05-20 00:42:11, Info CSI 00000075 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:42:11, Info CSI 00000076 [sR] Beginning Verify and Repair transaction
2015-05-20 00:42:48, Info CSI 00000079 [sR] Verify complete
2015-05-20 00:42:50, Info CSI 0000007a [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:42:50, Info CSI 0000007b [sR] Beginning Verify and Repair transaction
2015-05-20 00:43:27, Info CSI 0000007f [sR] Verify complete
2015-05-20 00:43:27, Info CSI 00000080 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:43:27, Info CSI 00000081 [sR] Beginning Verify and Repair transaction
2015-05-20 00:43:53, Info CSI 00000084 [sR] Verify complete
2015-05-20 00:43:56, Info CSI 00000085 [sR] Verifying 100 (0x0000000000000064) components
2015-05-20 00:43:56, Info CSI 00000086 [sR] Beginning Verify and Repair transaction

 

 

 

 

Modifié le 19 mai 2015 par oneill76

[oneill76]

Lignes avec Repairing, Repaired, ou "cannot" :
============================================

LIGNES AVEC REPAIRING :
=====================
2015-05-20 01:04:18, Info CSI 0000034e [sR] Repairing 1 components
============================================

LIGNES AVEC REPAIRED :
====================
============================================

LIGNES AVEC CANNOT :
==================
2015-05-20 00:52:10, Info CSI 000001bd [sR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-20 00:52:10, Info CSI 000001bf [sR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-20 00:52:13, Info CSI 000001c1 [sR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-20 00:52:13, Info CSI 000001c4 [sR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-20 01:04:18, Info CSI 00000351 [sR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-20 01:04:18, Info CSI 00000353 [sR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-20 01:04:18, Info CSI 00000355 [sR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-05-20 01:04:18, Info CSI 00000358 [sR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

[ab-web]

bonjour

 

les lignes Telemetry

avec Cannot ( ne peu pas réparer )

semble correspondre a une mise a jour de windows qui pose problème .

 

je ne t'assure pas que cela va résoudre le souci de crash

mais il faut vérifier !

 

ouvre windows update > clic mise a jours installées > laisse le temps a windows de créer complètement la liste.

en haut a droite dans la Zone recherche tape (KB3022345)

 

si cette mise a jour est présente > clic droit dessus désinstaller

l'ordinateur devras être redémarré .

 

ne pas laisser cette mise a jour se réinstaller il faut la masquer.

 

après tu feras une vérification simple

en invite de commande en tant qu'administrateur > sfc /verifyonly

 

a la fin de l'analyse il est indiqué si des fichiers ( avec violation d'intégrité) ont été trouvés ou non

donne moi la teneur du message

Modifié le 20 mai 2015 par ab-web

[oneill76]

salut l ami

pas de violation d integriter suite a l analyse

plus d ecran bleu mais toujours des mise en veille inexpliquer.

des idées ?

alex

[ab-web]

bonjour

 

vérifie les conditions de mise en veille .

 

panneau de configuration > Options d'alimentation

modifier les conditions de mise en veille !

Modifié le 21 mai 2015 par ab-web

[oneill76]

BOnsoir AB-Web

 

 

 

PAS de mise en veille. autorisée que se soit sur chargeur ou sur batterie.

 

 

Cela pourrait t'il venir d'un mauvais refroidissement ou d'un materiel defaillant ?

[ab-web]

hello

 

d'un mauvais refroidissement : c'est bien possible .

il faut vérifier l'état intérieur .

(accumulation de poussiere a tous les niveaux )