Bonjour à tous et merci d'avance pour votre aide.
J'ai la machine de mon papi qui bug, j'ai donc fait un nettoyage de tous les logiciels inutiles voir installés par mégarde. Ensuite j'ai utilisé malwerbytes et d'autre logiciel anti malwers. rien n'y fait j'ai toujours cette alerte au démarrage de windows avec pleins de bluscreen.
J'ai donc suivi l'excellent tuto FRST et voici les liens des 3 fichiers txt :
FRST : https://pjjoint.malekal.com/files.php?i ... f7p5j13b14
Addition : https://pjjoint.malekal.com/files.php?i ... 15z5h11t12
Shorcut : https://pjjoint.malekal.com/files.php?i ... y1414t9x14
Merci d'avance pour votre aide
cnmssc~1.dll win32 n'est pas une application valide
Modérateurs : Mods Windows, Helper
- Messages : 24
- Inscription : 05 oct. 2018 11:51
- Messages : 32262
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne
Re: cnmssc~1.dll win32 n'est pas une application valide
Bonjour/Bonsoir
ça vient de ton imprimante Canon
Apres ci dessous, Tu as des trucs d'avast non présents dans ton gestionnaire de désinstallation, télécharge donc et exécute https://www.malekal.com/desinstaller-supprimer-avast/
Windows defender reprendra la main
Télécharge à coté de FRST.EXE , PAS AILLEURS !!!!! le fichier fixlist.txt en pièce jointe en bas du message.
➯ Relance FRST(clic droit exécuter en tant qu'administrateur) et clic sur le bouton corriger/fix
Un redémarrage peut être nécessaire (pas obligatoire).
Un fichier texte apparaît, copie/colle le contenu ici dans un nouveau message avec ton commentaire.
/!\ Ce script a été établi pour cet utilisateur, il ne doit, en aucun cas, être appliqué sur un autre système, au risque de provoquer de graves dysfonctionnements et endommager Windows /!\
Tu as ton C:\WINDOWS\Minidump\ qui a l'air de rapporter des BSOD apparamment demuis qu' a été installé ta canon ou une mise à jour Windows ?
ça vient de ton imprimante Canon
Apres ci dessous, Tu as des trucs d'avast non présents dans ton gestionnaire de désinstallation, télécharge donc et exécute https://www.malekal.com/desinstaller-supprimer-avast/
Windows defender reprendra la main
Télécharge à coté de FRST.EXE , PAS AILLEURS !!!!! le fichier fixlist.txt en pièce jointe en bas du message.➯ Relance FRST(clic droit exécuter en tant qu'administrateur) et clic sur le bouton corriger/fix
Un redémarrage peut être nécessaire (pas obligatoire).
Un fichier texte apparaît, copie/colle le contenu ici dans un nouveau message avec ton commentaire.
/!\ Ce script a été établi pour cet utilisateur, il ne doit, en aucun cas, être appliqué sur un autre système, au risque de provoquer de graves dysfonctionnements et endommager Windows /!\
Tu as ton C:\WINDOWS\Minidump\ qui a l'air de rapporter des BSOD apparamment demuis qu' a été installé ta canon ou une mise à jour Windows ?
Vous ne pouvez pas consulter les pièces jointes insérées à ce message.
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique
Merci.
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique
Merci.- Messages : 24
- Inscription : 05 oct. 2018 11:51
Re: cnmssc~1.dll win32 n'est pas une application valide
Plus de message d'erreur concernant le fichier dll mais des écran bleue lorsque la machine sort de veille ou pendant une période d'inactivité avec un message d'erreur mémoire missing….
Voici le fichier TEXTE LOG
Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 14-12-2019
Exécuté par Edouard (19-12-2019 20:24:57) Run:1
Exécuté depuis C:\Users\Edouard\Desktop
Profils chargés: Edouard (Profils disponibles: Edouard)
Mode d'amorçage: Normal
==============================================
fixlist contenu:
*****************
CreateRestorePoint:
HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\McMPFSvc => ""="Service"
Startup: C:\Users\Edouard\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk [2017-05-03]
ShortcutAndArgument: Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk -> C:\WINDOWS\system32\rundll32.exe => C:\Users\Edouard\CNMSSC~1.DLL,SMStarterEntryPoint WSD-0c5abca0-2479-4d63-8c10-0c8e47f1c839.0036;Canon MG3500 series Printer WS;cnmss Canon MG3500 series Printer WS (Local).dll;Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk
FF HKLM\SOFTWARE\Policies\Mozilla\Firefox: Restriction <==== ATTENTION
HKLM\SOFTWARE\Policies\Microsoft\Windows Defender: Restriction <==== ATTENTION
Task: {FABBC582-F6B0-4CCB-87F6-77149CE0C34C} - \Microsoft\Windows\UNP\RunCampaignManager -> Pas de fichier <==== ATTENTION
S4 mccspsvc; "C:\Program Files\Common Files\McAfee\CSP\1.9.829.0\\McCSPServiceHost.exe" [X]
Hosts:
Emptytemp:
*****************
Erreur: (0) Impossible de créer un point de restauration.
HKLM\System\CurrentControlSet\Control\SafeBoot\Network\McMPFSvc => supprimé(es) avec succès
C:\Users\Edouard\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk => déplacé(es) avec succès
ShortcutAndArgument: Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk -> C:\WINDOWS\system32\rundll32.exe => C:\Users\Edouard\CNMSSC~1.DLL,SMStarterEntryPoint WSD-0c5abca0-2479-4d63-8c10-0c8e47f1c839.0036;Canon MG3500 series Printer WS;cnmss Canon MG3500 series Printer WS (Local).dll;Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk => Erreur: Pas de correction automatique trouvée pour cet élément.
HKLM\SOFTWARE\Policies\Mozilla => supprimé(es) avec succès
HKLM\SOFTWARE\Policies\Microsoft\Windows Defender => supprimé(es) avec succès
"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain\{FABBC582-F6B0-4CCB-87F6-77149CE0C34C}" => supprimé(es) avec succès
"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{FABBC582-F6B0-4CCB-87F6-77149CE0C34C}" => supprimé(es) avec succès
"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\UNP\RunCampaignManager" => non trouvé(e)
HKLM\System\CurrentControlSet\Services\mccspsvc => supprimé(es) avec succès
mccspsvc => service supprimé(es) avec succès
C:\Windows\System32\Drivers\etc\hosts => déplacé(es) avec succès
Hosts restauré(es) avec succès.
=========== EmptyTemp: ==========
BITS transfer queue => 9461760 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 29313952 B
Java, Flash, Steam htmlcache => 6149 B
Windows/system/drivers => 594338173 B
Edge => 180821138 B
Chrome => 23399414 B
Firefox => 0 B
Opera => 0 B
Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 11536 B
systemprofile32 => 11536 B
LocalService => 173156 B
NetworkService => 173156 B
Edouard => 104541482 B
RecycleBin => 263702170 B
EmptyTemp: => 1.1 GB données temporaires supprimées.
================================
Le système a dû redémarrer.
==== Fin de Fixlog 20:26:40 ====
Voici le fichier TEXTE LOG
Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 14-12-2019
Exécuté par Edouard (19-12-2019 20:24:57) Run:1
Exécuté depuis C:\Users\Edouard\Desktop
Profils chargés: Edouard (Profils disponibles: Edouard)
Mode d'amorçage: Normal
==============================================
fixlist contenu:
*****************
CreateRestorePoint:
HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\McMPFSvc => ""="Service"
Startup: C:\Users\Edouard\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk [2017-05-03]
ShortcutAndArgument: Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk -> C:\WINDOWS\system32\rundll32.exe => C:\Users\Edouard\CNMSSC~1.DLL,SMStarterEntryPoint WSD-0c5abca0-2479-4d63-8c10-0c8e47f1c839.0036;Canon MG3500 series Printer WS;cnmss Canon MG3500 series Printer WS (Local).dll;Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk
FF HKLM\SOFTWARE\Policies\Mozilla\Firefox: Restriction <==== ATTENTION
HKLM\SOFTWARE\Policies\Microsoft\Windows Defender: Restriction <==== ATTENTION
Task: {FABBC582-F6B0-4CCB-87F6-77149CE0C34C} - \Microsoft\Windows\UNP\RunCampaignManager -> Pas de fichier <==== ATTENTION
S4 mccspsvc; "C:\Program Files\Common Files\McAfee\CSP\1.9.829.0\\McCSPServiceHost.exe" [X]
Hosts:
Emptytemp:
*****************
Erreur: (0) Impossible de créer un point de restauration.
HKLM\System\CurrentControlSet\Control\SafeBoot\Network\McMPFSvc => supprimé(es) avec succès
C:\Users\Edouard\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk => déplacé(es) avec succès
ShortcutAndArgument: Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk -> C:\WINDOWS\system32\rundll32.exe => C:\Users\Edouard\CNMSSC~1.DLL,SMStarterEntryPoint WSD-0c5abca0-2479-4d63-8c10-0c8e47f1c839.0036;Canon MG3500 series Printer WS;cnmss Canon MG3500 series Printer WS (Local).dll;Canon IJ Status Monitor Canon MG3500 series Printer WS.lnk => Erreur: Pas de correction automatique trouvée pour cet élément.
HKLM\SOFTWARE\Policies\Mozilla => supprimé(es) avec succès
HKLM\SOFTWARE\Policies\Microsoft\Windows Defender => supprimé(es) avec succès
"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain\{FABBC582-F6B0-4CCB-87F6-77149CE0C34C}" => supprimé(es) avec succès
"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks\{FABBC582-F6B0-4CCB-87F6-77149CE0C34C}" => supprimé(es) avec succès
"HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft\Windows\UNP\RunCampaignManager" => non trouvé(e)
HKLM\System\CurrentControlSet\Services\mccspsvc => supprimé(es) avec succès
mccspsvc => service supprimé(es) avec succès
C:\Windows\System32\Drivers\etc\hosts => déplacé(es) avec succès
Hosts restauré(es) avec succès.
=========== EmptyTemp: ==========
BITS transfer queue => 9461760 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 29313952 B
Java, Flash, Steam htmlcache => 6149 B
Windows/system/drivers => 594338173 B
Edge => 180821138 B
Chrome => 23399414 B
Firefox => 0 B
Opera => 0 B
Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 11536 B
systemprofile32 => 11536 B
LocalService => 173156 B
NetworkService => 173156 B
Edouard => 104541482 B
RecycleBin => 263702170 B
EmptyTemp: => 1.1 GB données temporaires supprimées.
================================
Le système a dû redémarrer.
==== Fin de Fixlog 20:26:40 ====
Dire merci avant d’être dépanné c’est comme si vous l’étiez déjà 
- Messages : 24
- Inscription : 05 oct. 2018 11:51
Re: cnmssc~1.dll win32 n'est pas une application valide
désolé j'ai cliqué trop vite
Dire merci avant d’être dépanné c’est comme si vous l’étiez déjà
- Messages : 24
- Inscription : 05 oct. 2018 11:51
Re: cnmssc~1.dll win32 n'est pas une application valide
Maintenant j’ai le droit à un PFN_LIST_CORRUPT
Je lance des onc chkdsk c: /f puis je ferai ensuite /r puis memtest
Est ce que je fait bien ?
Je lance des onc chkdsk c: /f puis je ferai ensuite /r puis memtest
Est ce que je fait bien ?
Dire merci avant d’être dépanné c’est comme si vous l’étiez déjà
- Messages : 24
- Inscription : 05 oct. 2018 11:51
Re: cnmssc~1.dll win32 n'est pas une application valide
Et le bal du screen bleu avec memory management ... ça ne sent pas bon
S’il s’agit de la ddr je ne peux pas changer il s’agit d’un pc 2 en 1
S’il s’agit de la ddr je ne peux pas changer il s’agit d’un pc 2 en 1
Dire merci avant d’être dépanné c’est comme si vous l’étiez déjà
- Messages : 32262
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne
Re: cnmssc~1.dll win32 n'est pas une application valide
Essaie d'identifier ton problème de BSOD avec https://www.malekal.com/tutoriel-whocrashed/
Sinon oui teste ta ram et fait un checkdisk (chkdsk c: /f /r)
Sinon oui teste ta ram et fait un checkdisk (chkdsk c: /f /r)
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique Merci.
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique
Merci.- Messages : 24
- Inscription : 05 oct. 2018 11:51
Re: cnmssc~1.dll win32 n'est pas une application valide
Merci pas de problème mémoire chkdsk r et f effectué pas de soucis... l’erreur vient du noyaux apparement : ntoskrnl.exe
Est ce que je vous transmet les log de whocrashed ?
Est ce que je vous transmet les log de whocrashed ?
Dire merci avant d’être dépanné c’est comme si vous l’étiez déjà
- Messages : 32262
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne
Re: cnmssc~1.dll win32 n'est pas une application valide
oui
Noyau = système chargé en RAM
Noyau = système chargé en RAM
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique Merci.
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique
Merci.- Messages : 24
- Inscription : 05 oct. 2018 11:51
Re: cnmssc~1.dll win32 n'est pas une application valide
voici le résumé :
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-S3D3F5V
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: T100HAN, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Atom(TM) x5-Z8500 CPU @ 1.44GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 2035888128 bytes (1,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 20/12/2019 12:03:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122019-30781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x3F, 0x2C37D, 0x8090B83F, 0x66286DC9)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 23:22:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-24968-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x3F16)
Bugcheck code: 0x1A (0x3F, 0x2B3A4, 0x1D43BB50, 0x4B683BBF)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 19/12/2019 23:10:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-22546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFBA0B2B892C4A, 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 Thu 19/12/2019 22:56:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-19984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x6000, 0xFFFFAE846E9E1200, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 22:54:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-22562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x1236, 0xFFFFD38843C16120, 0xFFFFD38843C16238, 0x9204C)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 22:40:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-22453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x109 (0xA39FF565BE58D6F3, 0xB3B701EC10D72014, 0xFFFFF80473DC4F60, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. 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 Thu 19/12/2019 22:29:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-21859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x6000, 0xFFFFE48F46B58030, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 22:17:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-21640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x4E (0x99, 0x2E44C, 0x2, 0x60000100001A8CD)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 19/12/2019 21:54:15 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-56750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x139 (0x3, 0xFFFFF8046BE6B810, 0xFFFFF8046BE6B768, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 19/12/2019 21:17:41 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-60437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x6000, 0xFFFF9687CC927B50, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 43 crash dumps have been found. Only 10 have been analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 fur
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-S3D3F5V
Windows version: Windows 10 , 10.0, build: 18363
Windows dir: C:\WINDOWS
Hardware: T100HAN, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Atom(TM) x5-Z8500 CPU @ 1.44GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 2035888128 bytes (1,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 20/12/2019 12:03:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\122019-30781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x3F, 0x2C37D, 0x8090B83F, 0x66286DC9)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 23:22:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-24968-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR+0x3F16)
Bugcheck code: 0x1A (0x3F, 0x2B3A4, 0x1D43BB50, 0x4B683BBF)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
Bug check description: This indicates that a severe memory management error occurred.
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
On Thu 19/12/2019 23:10:04 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-22546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFBA0B2B892C4A, 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 Thu 19/12/2019 22:56:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-19984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x6000, 0xFFFFAE846E9E1200, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 22:54:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-22562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x1236, 0xFFFFD38843C16120, 0xFFFFD38843C16238, 0x9204C)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 22:40:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-22453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x109 (0xA39FF565BE58D6F3, 0xB3B701EC10D72014, 0xFFFFF80473DC4F60, 0x0)
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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. 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 Thu 19/12/2019 22:29:14 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-21859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x6000, 0xFFFFE48F46B58030, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 Thu 19/12/2019 22:17:50 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-21640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x4E (0x99, 0x2E44C, 0x2, 0x60000100001A8CD)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
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 19/12/2019 21:54:15 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-56750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x139 (0x3, 0xFFFFF8046BE6B810, 0xFFFFF8046BE6B768, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 19/12/2019 21:17:41 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121919-60437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C14E0)
Bugcheck code: 0x1A (0x6000, 0xFFFF9687CC927B50, 0xFFFFFFFFC0000225, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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. 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 43 crash dumps have been found. Only 10 have been analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
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 fur
Dire merci avant d’être dépanné c’est comme si vous l’étiez déjà
- Messages : 32262
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne
Re: cnmssc~1.dll win32 n'est pas une application valide
Tu as vérifié comme tu as dit ta RAM https://www.malekal.com/memtest-verifie ... moire-ram/
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique Merci.
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique
Merci.- Messages : 24
- Inscription : 05 oct. 2018 11:51
Re: cnmssc~1.dll win32 n'est pas une application valide
Oui bien effectué le test et aucun soucis sur la ram
Dire merci avant d’être dépanné c’est comme si vous l’étiez déjà
- Messages : 32262
- Inscription : 28 févr. 2008 13:58
- Localisation : Breizhilienne
Re: cnmssc~1.dll win32 n'est pas une application valide
Voit si y'a pas des mises à jour de drivers avec driversCloud ou Snappy Driver
Tu as vérifié tes T° CPU avec hwinfo par exemple ➯ https://www.malekal.com/tutoriel-temper ... rdinateur/
Tu as vérifié tes T° CPU avec hwinfo par exemple ➯ https://www.malekal.com/tutoriel-temper ... rdinateur/
Avec Gnu_Linux t'as un Noyau ... avec Ѡindows t'as que les pépins
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique Merci.
https://helicium.altervista.org/
Supprimer les "virus" gratuitement http://www.supprimer-trojan.com/
Un p'tit Don à Angélique
Merci.-
- Sujets similaires
- Réponses
- Vues
- Dernier message
-
- 10 Réponses
- 289 Vues
-
Dernier message par Malekal_morte
-
- 1 Réponses
- 95 Vues
-
Dernier message par Malekal_morte
-
- 8 Réponses
- 297 Vues
-
Dernier message par Parisien_entraide
-
-
L'application Microsoft Store nest plus active [Résolu]
par seichesman » » dans Windows : Résoudre les problèmes - 4 Réponses
- 134 Vues
-
Dernier message par seichesman
-
-
-
Application COURRIER les mails restent dans Boite d'Envoi
par seichesman » » dans Windows : Résoudre les problèmes - 13 Réponses
- 422 Vues
-
Dernier message par seichesman
-