Problème blue screen : Memory management

  • Auteur de la discussion Au2606
  • Date de début

Au2606

Nouveau membre
Bonjour !
Depuis quelques temps je suis confrontée au blue screen : memory management quasi tous les jours.
J'ai mis à jour tous mes drivers, j'ai fait un memtest + outil de diagnostic de windows et RAS
Merci à ceux qui pourraient m'aider !

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

Computer name: AURORE
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: ASUSTeK COMPUTER INC., B150M-A D3
CPU: GenuineIntel Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Intel8664, level: 6
4 logical processors, active mask: 15
RAM: 17102594048 bytes (15,9GB)

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


Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Mon 04/03/2019 19:37:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030419-49187-01.dmp
This was probably caused by the following module: (nt+0x1AA0C0)
Bugcheck code: 0x1A (0x3453, 0xFFFFDD81F294C080, 0x17BA00, 0x3)
Error:
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
company:
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 Mon 04/03/2019 19:37:46 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: (nt!memset+0x3C49C)
Bugcheck code: 0x1A (0x3453, 0xFFFFDD81F294C080, 0x17BA00, 0x3)
Error:
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 Mon 04/03/2019 19:30:03 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030419-60093-01.dmp
This was probably caused by the following module: (nt+0x1AA0C0)
Bugcheck code: 0x1A (0x3453, 0xFFFFCA88E717D580, 0x12300, 0x3)
Error:
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
company:
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 Sun 03/03/2019 16:45:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\030319-25515-01.dmp
This was probably caused by the following module: (nt+0x1AA0C0)
Bugcheck code: 0x1A (0x3453, 0xFFFF990383A13580, 0x53700, 0x3)
Error:
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
company:
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



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


Read the topic 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.


------- On m'a aussi conseillé de faire un WinDBG (mais ça ne m'aide pas plus à comprendre)----

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: a69de68faba6ff7adcd59590ca38e4e2485454e4

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: eb50f97921d926f4e8c1adf134bca19b635b3348

THREAD_SHA1_HASH_MOD: 9f457f347057f10e1df248e166a3e95e6570ecfe

FOLLOWUP_IP:
nt!MiDeleteFinalPageTables+fd358
fffff801`0fa9d29c cc int 3

FAULT_INSTR_CODE: 6483cccc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiDeleteFinalPageTables+fd358

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5c5a45ab

IMAGE_VERSION: 10.0.17134.590

IMAGE_NAME: memory_corruption

BUCKET_ID_FUNC_OFFSET: fd358

FAILURE_BUCKET_ID: 0x1a_3453_nt!MiDeleteFinalPageTables

BUCKET_ID: 0x1a_3453_nt!MiDeleteFinalPageTables

PRIMARY_PROBLEM_CLASS: 0x1a_3453_nt!MiDeleteFinalPageTables

TARGET_TIME: 2019-03-03T15:45:31.000Z

OSBUILD: 17134

OSSERVICEPACK: 590

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2019-02-06 03:25:47

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.17134.590

ANALYSIS_SESSION_ELAPSED_TIME: 13c8

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1a_3453_nt!mideletefinalpagetables

FAILURE_ID_HASH: {5341b5a0-5b02-2da1-51b3-df124a48f6f9}


Merci d'avance
 

Basturbe

Modérateur configopathe
Staff
Bonjour,
recupère ta clef d'activation windows (si besoin tu peux utiliser ProduKey) et fait une installation propre de l'os. Pour se faire tu vas chercher le dernier iso ou le media creation tool et tu prépare une clef bootable.
Est-ce que le problème persiste après l'installation propre ?

Cdt
 

chonos

Helper
Un module de ram (barette)ou le slot lui même, peut être hs avec panne aléatoire.

Tu peut faire une tentative de test avec une autre barette de RAM mais le 1er test que tu doit faire a mon sens c'est de savoir si c'est matériel ou soft (OS)

un live linux permetra de le faire (si tu a le même pb avec os différent c'est matériel !

si OS ;-)

Mais dans tous les cas tu peut refait on systeme ! cela permet de faire du propre
et fait une image de système cela ne coute que du temps et moyen de sauvegarde ;-)
a+
 
Dernière édition:
U

User_1505931

Invité
Pense à mettre le BIOS à jour.
Les rames sont elle identiques?
Le PC chauffe t'il?
Et nous mettre le détail de ta configuration serait un+.
Merci.
 

Au2606

Nouveau membre
Bonjour à tous et merci pour les réponses ! J'ai donc formaté mon PC mais j'ai malheureusement encore eu un blue screen avec la même erreur :(
 

_Othy_

Helper
Salut,
BIOS à jour comme demandé ?
pour commencer, verifie que TOUS tes pilotes sont à jour avec (clic "seulement ceux necessaires")
en supposant que tu ai 2 barettes, fait tourner ton PC avec 1 seul barette pendant quelques jours.
si ca tient, met l'autre barrette à la place et verifie si ca tient aussi.
si ca crash dans les 2 cas ... on verra
et quelle carte mere as tu ?
RAM dans quels slots ?
 

chonos

Helper
Bonjour à tous et merci pour les réponses ! J'ai donc formaté mon PC mais j'ai malheureusement encore eu un blue screen avec la même erreur :(

Tu as fait une action pour faire une correction et ce n'est pas cette action !
-> si je fait un paralele avec le médical :
---> tu as donner un medicament sans aller consulté !
---> du paracétamole pour un doigt amputer cela ne résoud pas ton pb

et bien pareil en info le diagnostique en 1er !
la seul chose ou tu a avance c'est qu'a présent tu sais que c'est soit un pb matériel ou pb de mise a jour et pense bien au BIOS comme te le dit nos amis philou21850 & Othy
 
Vous devez vous inscrire ou vous connecter pour répondre ici.
Derniers messages publiés
Statistiques globales
Discussions
730 098
Messages
6 717 065
Membres
1 586 286
Dernier membre
petitangebleu1977
Partager cette page
Haut