Différents crash... PC neuf

Fermé
Tchoupi&Nexus Messages postés 5 Date d'inscription mercredi 23 janvier 2013 Statut Membre Dernière intervention 11 janvier 2017 - 18 avril 2016 à 18:03
Tchoupi&Nexus Messages postés 5 Date d'inscription mercredi 23 janvier 2013 Statut Membre Dernière intervention 11 janvier 2017 - 11 janv. 2017 à 14:28
Bonjour,

Je viens vers vous après avoir chercher sur net et sur ce forum, j'ai eu pas mal de retour et compris à peu près les différents types d'erreurs, mais je voulais quand même venir ici car mon PC est tout neuf et j'ai eu plusieurs crash mais plusieurs code d'erreur. Je vous colle les rapports de crash ci-dessous :

On Mon 18/04/2016 15:37:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041816-5015-01.dmp
This was probably caused by the following module: gm300fltr.sys (GM300Fltr+0x68C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF80142677304, 0x0, 0xFFFFF80144495ED8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\gm300fltr.sys
product: Gaming Mouse 33052
company: LXD Development, Inc.
description: Gaming Mouse 33052 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gm300fltr.sys (Gaming Mouse 33052 Driver, LXD Development, Inc.).
Google query: LXD Development, Inc. KMODE_EXCEPTION_NOT_HANDLED

---------------

On Mon 18/04/2016 15:37:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: gm300fltr.sys (GM300Fltr+0x68C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000047, 0xFFFFF80142677304, 0x0, 0xFFFFF80144495ED8)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\gm300fltr.sys
product: Gaming Mouse 33052
company: LXD Development, Inc.
description: Gaming Mouse 33052 Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: gm300fltr.sys (Gaming Mouse 33052 Driver, LXD Development, Inc.).
Google query: LXD Development, Inc. KMODE_EXCEPTION_NOT_HANDLED

---------------

On Tue 12/04/2016 10:23:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041216-5046-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!TreeUnlinkMulti+0x140)
Bugcheck code: 0x1A (0x4477, 0x800000000, 0x0, 0x0)
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. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
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 Sun 10/04/2016 10:13:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041016-5390-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsTeardownStructures+0x124)
Bugcheck code: 0x50 (0xFFFFC00891B72424, 0x0, 0xFFFFF8004B81CD64, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 08/04/2016 13:57:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040816-5453-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6803F187138, 0x800000000, 0x0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

------------------------------------------------------------

Je sais pas si tout ces crash on un rapprochement entre eux, si vous pouvez m'éclaircir avant que je porte l'ordinateur chez mon vendeur.

Je vous remercie d'avance.

Cordialement,
A voir également:

2 réponses

Tchoupi&Nexus Messages postés 5 Date d'inscription mercredi 23 janvier 2013 Statut Membre Dernière intervention 11 janvier 2017
25 avril 2016 à 17:59
Personne ?
0
Tchoupi&Nexus Messages postés 5 Date d'inscription mercredi 23 janvier 2013 Statut Membre Dernière intervention 11 janvier 2017
11 janv. 2017 à 14:28
Bonjour,

Je me permet de relancer le sujet, car c'est toujours d'actualité !

J'ai testé ma ram avec l'application fournie par windows et rien de trouvé.
J'ai testé aussi sfc /scannow en mode sans échec et pareil, rien de trouvé.

Si on pouvait me guider sur certaines pistes.

Je rappel que j'ai ces écrans bleus depuis que j'ai acheté l'ordinateur.

Cordialement,
0