Ecran bleu avec smiley triste

[Fermé]
Signaler
Messages postés
3
Date d'inscription
dimanche 26 février 2017
Statut
Membre
Dernière intervention
26 février 2017
-
Messages postés
3
Date d'inscription
dimanche 26 février 2017
Statut
Membre
Dernière intervention
26 février 2017
-
Bonjour,

J'ai depuis 2 mois un nouveau pc que j'ai fais monter chez LDLC et depuis 2 semaines l'ordi plante avec des écrans bleus et un smiley triste avec différents codes tel que " memory management, irql less or not equal, system service exception". J'ai réinstallé windows 10 et il a crash malgrés ça. J'ai fais un test ram qui n'a rien donné ainsi qu'une réparation du disque qui m'a réparé des erreurs. Depuis, je ne peux plus ouvrir les applications de bases windows tel que les paramètre, windows store, photos etc..

Si une personne bienveillante pourrait m'aider car je ne sais plus quoi faire.

Merci beaucoup !

Je vous met ce que Whocrashed m'a détecté :

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-22MGTFL
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., H170I-PLUS D3
CPU: GenuineIntel Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8529252352 bytes total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 26/02/2017 00:31:11 your computer crashed
crash dump file: C:\Windows\Minidump\022617-7796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x1A (0x41793, 0xFFFFA500F36968E8, 0x11E, 0x11D)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 Sun 26/02/2017 00:31:11 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: 0x1A (0x41793, 0xFFFFA500F36968E8, 0x11E, 0x11D)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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. 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 25/02/2017 21:45:57 your computer crashed
crash dump file: C:\Windows\Minidump\022517-7859-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x1A (0x41792, 0xFFFFC481061A8010, 0x4000, 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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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 25/02/2017 21:29:15 your computer crashed
crash dump file: C:\Windows\Minidump\022517-6968-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x201D91)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8021BA41D91, 0xFFFFE4806E1F3950, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
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 a standard 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 Sat 25/02/2017 20:53:57 your computer crashed
crash dump file: C:\Windows\Minidump\022517-5031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x1A (0x41201, 0xFFFF9181D6D45A00, 0xFFFFFFFF, 0xFFFFB88ED00D8E50)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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
--------------------------------------------------------------------------------

8 crash dumps have been found and analyzed. Only 5 are included in this report. 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 further.

3 réponses

Messages postés
92
Date d'inscription
dimanche 25 octobre 2015
Statut
Membre
Dernière intervention
24 août 2019
33
c'est problablement un virus ou le processeur qui est mort, tu faisais quoi dessus?
Messages postés
3
Date d'inscription
dimanche 26 février 2017
Statut
Membre
Dernière intervention
26 février 2017

Je joue en général et ça crash aléatoirement ou alors quand j'installe un truc
Messages postés
3
Date d'inscription
dimanche 26 février 2017
Statut
Membre
Dernière intervention
26 février 2017

Il vient de m'en faire un nouveau

On Sun 26/02/2017 11:20:03 your computer crashed
crash dump file: C:\Windows\Minidump\022617-4984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x19 (0x24, 0x40, 0x1, 0xFFFFB8ABC277E260)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 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.