windows 10 random bsod memory management gigabye z170x


  1. arkel99
    Posts : 7
    windows 10
       New #1

    windows 10 random bsod memory management gigabye z170x


    i get randomly bsod on memory management

    and ofcourse i installed win 10 creators again, changed bios etc etc
      My Computer
    Quote Quote

  3. zbook
    Posts : 41,475
    windows 10 professional version 1607 build 14393.969 64 bit
       New #2

    Hi

    There were 2 bsod mini dump files and there was no definitive misbehaving driver.
    Outlook was identified as a faulting application.
    Corruption on the drive file system was reported in the event log.
    Windows failed fast startup.

    Open administrative command prompt and type or copy and paste these commands:
    1) sfc /scannow
    2) dism /online /cleanup-image /restorehealth
    3) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    4) chkdsk /x /f /r (this may take many hours so plan to run it overnight
    5) when chkdsk has completed please post a link into the thread.
    6) Open control Panel > Programs and Features > right-click on your Office program and click Change > Repair
    7)     Run memtest86+ version 5.01 for at least 8 runs.
    This may take many hours so plan to run it overnight.Memtest86+ - Advanced Memory Diagnostic Tool
    When Memtest86+ has completed 8 or more runs use a camera or a smart phone camera to make an image of the results to post into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
    8) Turn Windows fast startup off:
    https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html


    Code:
    07/29/2017 8:04    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0x1648
Faulting application start time: 0x01d30841549363c1
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: 4c27461e-6a5c-4ad3-975b-f00a2f67db48
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail07/28/2017 12:41    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0x1ad0
Faulting application start time: 0x01d3079ec4e33448
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: d3b95f5c-76b8-42a0-8def-90f0ae245785
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail07/27/2017 21:33    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0x2320
Faulting application start time: 0x01d3071fe59296d6
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: bd469d5d-7e04-450c-8eb0-8fb88c4d280b
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail07/27/2017 21:34    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0x242c
Faulting application start time: 0x01d307202195e8e2
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: 7fcaaba2-6fd4-4691-ba52-4e4dad4ded86
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail07/27/2017 21:32    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0x2724
Faulting application start time: 0x01d3071fe262064c
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: 21130be0-ef0f-4ef2-97de-fd0efef6737c
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail07/29/2017 7:41    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0x66c
Faulting application start time: 0x01d3083e08296a55
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: c06be780-d3de-4ca8-a8b3-b33841713766
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail07/27/2017 21:33    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0xa88
Faulting application start time: 0x01d3071ffcd50a7d
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: 7f70d223-1208-4750-8d01-3db99d95150b
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail07/27/2017 21:32    Application Error    Faulting application name: HxOutlook.exe, version: 16.0.8241.4127, time stamp: 0x5967c24f
Faulting module name: wlibim.dll, version: 16.0.8201.1018, time stamp: 0x59415fdb
Exception code: 0xc0000005
Fault offset: 0x000000000002991a
Faulting process id: 0xc60
Faulting application start time: 0x01d3071fdbe50db7
Faulting application path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\HxOutlook.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe\wlibim.dll
Report Id: 374d0f9a-1521-4db9-8683-6e08a9e45964
Faulting package full name: microsoft.windowscommunicationsapps_17.8241.41275.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: microsoft.windowslive.mail
    Code:
    Event[1243]:  Log Name: System  Source: Ntfs  Date: 2017-07-29T10:03:13.279  Event ID: 55  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Arkelwin10  Description: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown.  The file system structures need to be scanned online.
    Code:
    Windows failed fast startup with error status 0xC00000D4.
    Code:
    Event[1242]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-07-29T10:03:13.279  Event ID: 98  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: Arkelwin10  Description: Volume C: (\Device\HarddiskVolume10) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.


    Code:
    BugCheck 3B, {c0000005, fffff8002e779d2f, ffff8e00603b0b10, 0}*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption
    Code:
    BugCheck 1A, {41792, fffffc800002ba10, 40000000000000, 0}Probably caused by : memory_corruptionFollowup: memory_corruption
      My Computer
    Quote Quote

  4. arkel99
    Posts : 7
    windows 10
    Thread Starter
       New #3

    Windows Resource Protection did not find any integrity violations.
    Image Version: 10.0.15063.0

    [== 4.5% ]
    Error: 14093

    The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.

    tonight i gonna do a chkdsk
      My Computer
    Quote Quote

  6. zbook
    Posts : 41,475
    windows 10 professional version 1607 build 14393.969 64 bit
       New #4

    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /checkhealth
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    6) Also use the Microsoft snipping tool to make an image of the results of the administrative command prompt commands and post into the thread.
      My Computer
    Quote Quote

  7. arkel99
    Posts : 7
    windows 10
    Thread Starter
       New #5

    zbook said:
    Open administrative command prompt and type or copy and paste:
    1) sfc /scannow
    2) dism /online /cleanup-image /checkhealth
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
    6) Also use the Microsoft snipping tool to make an image of the results of the administrative command prompt commands and post into the thread.
      My Computer
    Quote Quote

  8. arkel99
    Posts : 7
    windows 10
    Thread Starter
       New #6

      My Computer
    Quote Quote

  9. arkel99
    Posts : 7
    windows 10
    Thread Starter
       New #7

    C:\Windows\system32>dism /online /cleanup-image /checkhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0

    Image Version: 10.0.15063.0

    The component store is repairable.
    The operation completed successfully.
      My Computer
    Quote Quote

  10. arkel99
    Posts : 7
    windows 10
    Thread Starter
       New #8

    Image Version: 10.0.15063.0

    [== 5.0% ]
    Error: 14093

    The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    C:\Windows\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.15063.0

    Image Version: 10.0.15063.0

    [== 4.5% ]
    Error: 14093

    The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
      My Computer
    Quote Quote

  12. arkel99
    Posts : 7
    windows 10
    Thread Starter
       New #9

    i also checked the bios and i use xmp profile 1 . memory is on 1.2 volt
      My Computer
    Quote Quote

 

  Related Discussions
Purchased a 16" Macbook Pro back in April and have had nothing but problems since (using Windows and Mac OS). Most of my time spent using this machine is in Windows 10 Bootcamp (Version 1903) with graphics intensive applications like AutoCAD, Revit,...
Lenovo Ideapad 720s - crashes started about a month ago. Things I have tried: Memtest x86 - 3 successful passes All hardware tests available - all passed Clean install of windows - problems persisted Blue Screens include:...
My laptop has lately been suffering from random hard-freezes without any error messages or logs (I have to force-shutdown) But in between those freezes, it has given me 2 BSOD's before, both having the code MEMORY MANAGEMENT. I did find a...
Hi, I am facing random BSOD with different error messages as noted in the thread title.Attached is the zip file.
Random BSOD Memory Management issue...
in BSOD Crashes and Debugging

Hi I was wondering if someone can help me before I lose my sanity. I built a new system in September and things were going OK until the recent 1511 update to Windows 10. Since then I've been getting a lot of BSOD errors pointing to...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 05:04.
Find Us




Windows 10 Forums