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:
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:
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:
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:
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
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
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:
Vous devez être connecté pour voir les liens.
(nt+0x1AA0C0) Bugcheck code: 0x1A (0x3453, 0xFFFFDD81F294C080, 0x17BA00, 0x3)
Error:
Vous devez être connecté pour voir les liens.
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Vous devez être connecté pour voir les liens.
company:
Vous devez être connecté pour voir les liens.
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:
Vous devez être connecté pour voir les liens.
(nt!memset+0x3C49C) Bugcheck code: 0x1A (0x3453, 0xFFFFDD81F294C080, 0x17BA00, 0x3)
Error:
Vous devez être connecté pour voir les liens.
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:
Vous devez être connecté pour voir les liens.
(nt+0x1AA0C0) Bugcheck code: 0x1A (0x3453, 0xFFFFCA88E717D580, 0x12300, 0x3)
Error:
Vous devez être connecté pour voir les liens.
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Vous devez être connecté pour voir les liens.
company:
Vous devez être connecté pour voir les liens.
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:
Vous devez être connecté pour voir les liens.
(nt+0x1AA0C0) Bugcheck code: 0x1A (0x3453, 0xFFFF990383A13580, 0x53700, 0x3)
Error:
Vous devez être connecté pour voir les liens.
file path: C:\WINDOWS\system32\ntoskrnl.exe
product:
Vous devez être connecté pour voir les liens.
company:
Vous devez être connecté pour voir les liens.
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
Vous devez être connecté pour voir les liens.
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