Problème écran bleu

heliosyouyou

Nouveau membre
Bonjour, j'ai acheté un ordinateur pièce par pièce sur un site il y a de ça un mois or lors de l'installation de windows 10 j'ai installé par erreur le x86 donc je ne pouvais pas utilisé complètement mes 8 go de ram. J'ai décidé de formater mon disque dur puis ensuite mettre windows 10 x64 cependant après l'installation j'eux de nombreuse fois des écrans bleu d'erreur: "PAGE FAULT IN NONPAGED AREA" / "MEMORY MANAGEMENT" .
J'ai passé un mois à essayer de résoudre mon problème avec du forum mais en vain.
Donc j'essai sur ce forum pour obtenir de l'aide.

Carte mère : MSI H110M PRO-VD
Processeur : INTEL 3-6100
Carte graphique : MSI GTX 1050 Ti 4GT OC
Alimentation : TEXTORM ALIMENTATON TX350+ NON MODULAIRE 80+BRONZ
Barrette de ram : GSKILL DDR4 8GB F4-2400C15S-8GNT
Disque dur : WESTERN CAVIAR BLUE 1TB 64MB 3.5IN SATA 6 GB/S 7200RPM
Pilotes à jour grâce à touslesdrivers.com
Bios : version 7996v2E

J’espère que quelqu'un pourra m'aider ,
Merci d'avance =).
 

dandibot

Grand Maître
Bonjour, fais une analyse "whocrashed" et envois nous le rapport:
 

heliosyouyou

Nouveau membre
Merci d'avoir répondu =)
Voilà le rapport :

Welcome to WhoCrashed (HOME EDITION) v 5.54
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

Computer name: DESKTOP-VPNCKPG
Windows version: Windows 10 , 10.0, build: 15063
Windows dir: C:\WINDOWS
Hardware: MS-7996, MSI, H110M PRO-VD (MS-7996)
CPU: GenuineIntel Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8552353792 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 25/10/2017 11:58:40 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-55203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x50 (0xFFFFC10D64E40000, 0x0, 0xFFFFF802E12FDA65, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 25/10/2017 11:58:40 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltCheckAndGrowNameControl+0x463)
Bugcheck code: 0x50 (0xFFFFC10D64E40000, 0x0, 0xFFFFF802E12FDA65, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 Wed 25/10/2017 11:43:27 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-43468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1A (0x5200, 0xFFFFD5827610F000, 0xFD5762793CD70788, 0xFD5762793ED70788)
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 Tue 24/10/2017 22:45:23 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-37500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x19 (0x3, 0xFFFFCD8A68B02010, 0xFFFFCD8A68B02010, 0x0)
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.



On Tue 24/10/2017 13:30:06 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102417-46500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1A (0x41201, 0xFFFFD880000487E0, 0x80000000E7BA3867, 0xFFFFAF8F3FA8E8D0)
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
--------------------------------------------------------------------------------

6 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.




 

_Othy_

Helper
donc à priori un probleme matériel de RAM , de chauffe ou de drivers ...
- vérifie que ta RAM estcorrectement mise
- met tout tes pilotes à jour avec https://sdi-tool.org/ (clic "seulement ceux nécessaires")
- installe hwmonitor et vérifie tes températures
- peux tu te faire prêter de la RAM ?
 

heliosyouyou

Nouveau membre
J'ai vérifié la RAM elle est correctement mise, j'ai installé les drivers, j'ai des Screenshots du logiciel :

http://hpics.li/ba71045
Ensuite pour une autre RAM j'en ai une :


 

heliosyouyou

Nouveau membre
Nouveau message d'erreur de crash On Wed 25/10/2017 16:08:56 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-25546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x19 (0x3, 0xFFFF9A8227B84C30, 0xFFFF9A8237B84C30, 0xFFFF9A8227B84C30)
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.



On Wed 25/10/2017 16:08:56 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: wdfilter.sys (WdFilter+0x1F98E)
Bugcheck code: 0x19 (0x3, 0xFFFF9A8227B84C30, 0xFFFF9A8237B84C30, 0xFFFF9A8227B84C30)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\wdfilter.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft antimalware file system filter driver
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 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 Wed 25/10/2017 15:42:08 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-19390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x1A (0x411, 0xFFFFD4811A62F1E0, 0x1D0FFD8A0, 0xFFFFD48118EAA6B0)
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 Wed 25/10/2017 15:02:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-37203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x19 (0xD, 0xFFFFE60F6596F000, 0x0, 0x42A358625DFF94FE)
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.

Des micro freeze depuis l'installation des drivers
 

heliosyouyou

Nouveau membre
Je crois que les micro freeze viennent de l'installation du driver en rapport avec le stockage.
 

_Othy_

Helper
lance un coup de Malwarebytes complet (et mis à jour) suivi d'un ccleaner sur le registre
et à la rigueur un sfc /scannow
 

heliosyouyou

Nouveau membre
5 menaces mis en quarantaine ,j'aurai une autre question à propos de l'activité assez importante :


Est-ce quelque chose malveillant?

 

heliosyouyou

Nouveau membre
Deux nouveaux crash
:/

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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 25/10/2017 21:15:38 your computer crashed
crash dump file: C:\WINDOWS\Minidump\102517-29203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0)
Bugcheck code: 0x4E (0x2, 0x102D66, 0x26EFFF, 0x1)
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 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.
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 25/10/2017 21:15:38 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0x15566)
Bugcheck code: 0x4E (0x2, 0x102D66, 0x26EFFF, 0x1)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
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.
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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and 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.

 

jeanmay022

Modo hardware OC
Staff
Salut,

Tes crashs sont dû au module NVidia (pilote probablement) et l'autre au système de fichiers...
Que donne un test SMART de ton DD ? As tu fais le SFC/ scannow demandé par Othy ?

Il serait bon aussi de faire un Memtest86+ sur chacune des barrettes (au moins 5 passes) : http://www.memtest.org/#downiso.
C'est un fichier ISO donc faire un support bootable.
 

dandibot

Grand Maître
Hello, oui +1.
Voila pour tester le disque dur:
Et pour Nvidia, clean tout avec ddu:

(laisses le redémarrer en mode sans échec quand il le demande, une fois terminé reboot et réinstalles tes drivers via le site officiel de nvidia)
 

_Othy_

Helper
ca le fait aussi quand tu ne met que l'autre barette de RAM ? et avec la memoire correctement paramétrée dans le BIOS ?
 

heliosyouyou

Nouveau membre
Voici les screen pour le test du disque dur :

http://hpics.li/f1f72b5

Celui du sfc /scannow :


Et je vais essayer avec l'autre barette de RAM.
 

heliosyouyou

Nouveau membre
Donc j'ai mis seulement une seule barette de RAM de 4Go :

http://hpics.li/9e14301
 

_Othy_

Helper
et est ce que ca plante aussi avec juste 1 barette de 4g ?? ^^
bizarre, ton sfc /scannow n'est pas allé jusqu'à la fin ...
 

heliosyouyou

Nouveau membre
Pour l'instant non ,mon ordinateur n'a toujours pas planté ^^ et vais l'utiliser pendant la journée pour voir =)
 
Vous devez vous inscrire ou vous connecter pour répondre ici.
Derniers messages publiés
Statistiques globales
Discussions
730 098
Messages
6 717 102
Membres
1 586 287
Dernier membre
lucilleguffey
Partager cette page
Haut