Ecran Bleu W10 au démarrage

Signaler
-
Malekal_morte-
Messages postés
174185
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
21 janvier 2020
-
Bonjour,

Voila, j'ai des écrans bleu au démarrage de mon ordinateur (1jour sur 2), et uniquement a ce moment la.
Voici les 3 messages qui reviennent le plus souvent.
A titre d'information, ce problème n'est pas récent, cela fait au moins 2 ans que ça dure.

SYSTEM_SERVICE_EXCEPTION
KMODE_EXCEPTION_NOT_HANDLED
KERNEL_DATA_INPAGE_ERROR

Hier j'ai remis a jour tous les driver qui disposait d'une MAJ disponible via (tous les driver).
J'ai fait tourner CC cleaner pour réparer le registre.
J'ai fait un test pour voir l'intégrité de mon SSD avec crystaldisk et avec intel ssd toolbox, le résultat est parfait sur mon ssd ou le windows est installé (quelques erreurs sur le hdd secondaire de stockage)
J'ai fais tourner who crashed, vous pourrez trouver le rapport ci dessous.

Pour info, il y a 1 ans, j'ai remplacer mon Alimentation, et le problème était toujours la. ensuite j'ai remplacer ma carte graphique et le problème est toujours la, j'ai aussi déconnecter ma carte réseau, tous les ventilateurs débranchés excepté processeur et carte graphique, le lecteur dvd déconnecté, lecteur usb facade déconnecté.
Et le problème est toujours la.

Auriez vous une idée, ou une solution a me proposer?


Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: MS-7758, MSI, B75A-G43 (MS-7758)
CPU: GenuineIntel Intel(R) Core(TM) i5-3350P CPU @ 3.10GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 17109397504 bytes (15,9GB)


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 04-01-20 09:01:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010420-39453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000006, 0xFFFFF8077888E922, 0xFFFFFE08F0978CC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Thu 02-01-20 17:12:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010220-36265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000006, 0xFFFFF8007CC8E922, 0xFFFFBD0B2A2D74F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Wed 01-01-20 10:42:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\010120-35937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8054A2103FF, 0x0, 0xFFFFFFFFFFFFFFFF)
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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 22-12-19 08:21:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122219-46593-01.dmp
This was probably caused by the following module: serenum.sys (0xFFFFF807624E7250)
Bugcheck code: 0x7A (0xFFFF9703D5D52F68, 0xFFFFFFFFC000000E, 0x20040EB0A860, 0xFFFFF807624E7250)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\serenum.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Serial Port Enumerator
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a 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 Fri 06-12-19 07:50:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120619-34843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000006, 0xFFFFF8055108E592, 0xFFFFED81EC2BB4F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Mon 18-11-19 20:42:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\111819-39921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x3B (0xC0000006, 0xFFFFF8022F48E592, 0xFFFFFD0AE56D04F0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 29-10-19 18:36:34 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102919-30187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80461C103BF, 0x0, 0xFFFFFFFFFFFFFFFF)
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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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 15-10-19 18:06:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101519-35718-01.dmp
This was probably caused by the following module: serenum.sys (0xFFFFF8051E367250)
Bugcheck code: 0x7A (0xFFFF8A0F5FB76F88, 0xFFFFFFFFC000000E, 0x200274B63860, 0xFFFFF8051E367250)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\serenum.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Serial Port Enumerator
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a 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 Thu 26-09-19 07:52:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\092619-36265-01.dmp
This was probably caused by the following module: csc.sys (0xFFFFF8033C62A458)
Bugcheck code: 0x7A (0xFFFFAE0480B28CF0, 0xFFFFFFFFC000000E, 0x200302DB0860, 0xFFFFF8033C62A458)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\csc.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Client Side Caching Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a 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 Tue 24-09-19 18:14:51 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\092419-44406-01.dmp
This was probably caused by the following module: mrxsmb.sys (0xFFFFF8001C98F01D)
Bugcheck code: 0x7A (0xFFFF958E795C9B98, 0xFFFFFFFFC000000E, 0x20037CF5E860, 0xFFFFF8001C98F01D)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\drivers\mrxsmb.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Minirdr SMB Windows NT
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a 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.




Configuration: Windows / Chrome 79.0.3945.88

2 réponses

Messages postés
174185
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
21 janvier 2020
19070
Salut,

Ca ne sert à rien tous ces nettoyages CCLeaner.
D'ailleurs tu devrais le désinstaller.

Vu tous les plantages, il y a des chances que ce soit matériel.

Vérifie déjà le disque dur : Comment vérifier la santé du disque dur
Avec CrystalDiskInfo
- Télécharger CrystalDiskInfo
Il faut que le statut soit en bleu, sinon c'est pas bon signe.
Plus d'explications : CrystalDiskInfo: Vérifier l’état de santé du disque dur.


Vérifie l'état de santé de tes barrettes de mémoire :
- memtest : vérifier barette de mémoire (malekal.com)
- memtest : vérifier barette de mémoire (CCM)
Utilise bien memtest86+ et pas celui de Windows


et enfin :

Pour vérifier ton ordinateur, pour d'éventuels infections et avoir un état général du système :

Suis le tutoriel FRST en cliquant sur ce lien bleu. ( prends le temps de lire attentivement - tout y est bien expliqué ).

Télécharge et lance le scan FRST,
Attendre la fin du scan, un message indique que l'analyse est terminée.

Trois rapports FRST seront générés :
  • FRST.txt
  • Shortcut.
  • Additionnal.txt


Envoie ces 3 rapports sur le site https://pjjoint.malekal.com/ et en retour donne les 3 liens pjjoint qui mènent aux rapports ici dans une nouvelle réponse afin que l'on puisse les consulter.

(Les liens bleus mènent à des tutoriels explicatifs pas à pas, clic dessus pour avoir les instructions plus précises à suivre).



bonjour, j'ai effectuer le test demandé, voir post ci dessous et encore merci
Bonjour et merci pour votre aide.

J'ai effectué les tests demandés :

Cristaldisk :
Disque bootable (C) est bleu
Disque de stockage supplémentaire (D) a un petit bug mais est fonctionnel et ne me causerait pas d'écran bleu au démarrage...

Memtest86+ :
Tout est OK pas 1 seul erreur detectée.

Pour ce qui est des problèmes d'infections :
J'ai fait tourné les antivirus et antimalware et anti... suivant :
windows defender
Kaspersky
avast
Junkware Removal Tool
Malwarebyte
ccleaner
HiJackThis
adwcleaner
roguekiller
J'ai évidement éliminé tous les problèmes listés par les programmes.

Les ecran bleu sont toujours présents...
avez vous une autre idée?

Merci d'avance
Malekal_morte-
Messages postés
174185
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
21 janvier 2020
19070
Ca sert à rien de faire tourner tout ça.
Laisse Windows Defender.
Désinstalle Avast!.

Mais bon si déjà tua s des erreurs Memtest...
Faudrait tester quelques heures avec une barrette à la fois,
Voir si une fait planter en particulier.