Page 1 of 4 123 ... LastLast
  1.    3 Weeks Ago #1
    Join Date : Dec 2016
    Posts : 30
    Windows 10 64bit

    BSOD after computer waking up from sleep mode


    I've recently formatted my computer not long ago. So my computer would randomly wake up from sleep mode and I went into power settings to check if any wake up times are on but they weren't on. Now after the BSOD if I try to put it to sleep, the lights stays on and won't go to sleep.

    The bluescreenview says: The problem seems to be caused by the following file: ntoskrnl.exe MEMORY_MANAGEMENT.

    *** STOP: 0x0000001a (0x0000000000006001, 0xffffffffc000000e, 0x0000000004390000, 0xffffd282c2729480)*** ntoskrnl.exe - Address 0xfffff8009ab71960 base at 0xfffff8009aa0e000 DateStamp 0x59dc593b

    The DM Log Collector file is attached.
    Thanks for any help provided.
    BSOD after computer waking up from sleep mode Attached Files
      My ComputerSystem Spec
  2.    3 Weeks Ago #2
    Join Date : Apr 2017
    Posts : 8,607
    windows 10 professional version 1607 build 14393.969 64 bit

    Hi Shirotora ,

    Welcome to the BSOD forum.

    The log files displayed problems with the drive (possible corruption, and a large number of paging errors), bios (possible firmware), failed windows fast startup and hibernation. There was a failed dump and the available dumps displayed bugcheck 1a. This is an error related to memory management.

    Windows debugging is limited at this time and may be related to the Fall Creators update (FCU).

    Perform the following steps:

    1) Open administrative command prompt and type or copy and paste these commands:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) Powercfg -h off
    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) chkdsk /x /f /r
    This may take many hours so plan to run overnight.
    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>chkdsk /x /f /r
    The type of the file system is NTFS.
    Cannot lock current drive.
    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)
    Type: Y

    7) To find the chkdsk /x /f /r report open event.vwr and follow the instructions in this link:
    Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials

    8) Open the Asus website and enter the information about the computer to find the website URL for drivers.
    Post this link in to the thread.

    9) Make sure that there is no over clocking while troubleshooting.

    10) Sometimes there are problems in the bios that produce bsod.
    The BIOS: Version/Date American Megatrends Inc. 3003, 10/28/2015

    11) Please check to see if this is the most up to date version.

    12) To ensure that there are no improper bios settings please reset the bios.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    13) Run HDTune: http://www.hdtune.com/
    to check the health,
    scan for errors, no quick scan but full scan
    run a benchmark.

    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    the health,
    the error scan,
    the benchmark incl. following
    transfer rate,
    access time,
    burst rate,
    cpu usage.
    Take Screenshot in Windows 10 General Tips Tutorials

    14) Run memtest86+ version 5.01 for at least 8 passes.
    Memtest86+ - Advanced Memory Diagnostic Tool
    Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.

    Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool

    The testing is done not by time but by passes.
    The more passes the better.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a pass when there is malfunctioning RAM.
    There is 8 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    Again the more passes the better.

    If both RAM pass when tested 1 at a time after failing when tested together test the next DIMM with 1 RAM module for 8 or more passes. This will help to differentiate malfunctioning RAM from malfunctioning DIMM /Motherboard.

    Memtest86+ - Advanced Memory Diagnostic Tool
    Memtest86+ - Advanced Memory Diagnostic Tool

    Microsoft Community
    Memory problems. - Microsoft Community

    MemTest86+ - Test RAM Windows 10 BSOD Tutorials
    MemTest86+ - Test RAM BSOD Tutorials


    15) When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image of the results into the thread.



    16) For any new BSOD please post a new zip into the thread:
    BSOD - Posting Instructions - Windows 10 Forums



    Code:
    Event[402]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-10-19T12:15:15.808  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-Q78OM24  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume5.(A device which does not exist was specified.)
    Code:
    Event[881]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-10-21T10:32:52.803  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-Q78OM24  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume5.
    Code:
    Event[883]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-10-21T10:32:52.803  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-Q78OM24  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume5.
    Code:
    Event[397]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[398]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[399]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[400]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[401]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
    Code:
    Event[403]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[404]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[405]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[406]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[407]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[408]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[409]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[410]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[411]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.805  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[412]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.868  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[413]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.883  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[414]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.883  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[415]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.961  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[416]:  Log Name: System  Source: Disk  Date: 2017-10-19T12:15:15.961  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
    Code:
    Event[874]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[875]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[876]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[877]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[878]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[879]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[880]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
    Code:
    Event[882]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[883]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-10-21T10:32:52.803  Event ID: 140  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-Q78OM24  Description: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume5.(A device which does not exist was specified.)Event[884]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[885]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[886]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[887]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[888]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[889]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[890]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[891]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.798  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[892]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.829  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[893]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.829  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[894]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.829  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[895]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.829  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[896]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.829  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[897]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.829  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[898]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.829  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[899]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.876  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[900]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.876  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[901]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.938  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.Event[902]:  Log Name: System  Source: Disk  Date: 2017-10-21T10:32:52.938  Event ID: 51  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
    Code:
    Event[575]:  Log Name: System  Source: ACPI  Date: 2017-10-20T03:17:30.519  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.
    Code:
    Event[775]:  Log Name: System  Source: ACPI  Date: 2017-10-20T18:50:27.995  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.
    Code:
    Event[1023]:  Log Name: System  Source: ACPI  Date: 2017-10-21T12:15:15.766  Event ID: 15  Task: N/A  Level: Warning  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: : The embedded controller (EC) returned data when none was requested. The BIOS might be trying to access the EC without synchronizing with the operating system. This data will be ignored. No further action is necessary; however, you should check with your computer manufacturer for an upgraded BIOS.
    Code:
    Event[651]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2017-10-20T11:02:30.603  Event ID: 29  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-Q78OM24  Description: Windows failed fast startup with error status 0xC00000D4.
    Code:
    Event[731]:  Log Name: System  Source: Microsoft-Windows-Kernel-Boot  Date: 2017-10-20T18:50:22.599  Event ID: 16  Task: N/A  Level: Error  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-Q78OM24  Description: Windows failed to resume from hibernate with error status 0xC0000001.
    Code:
    Event[995]:  Log Name: System  Source: volmgr  Date: 2017-10-21T12:15:11.106  Event ID: 46  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: DESKTOP-Q78OM24  Description: Crash dump initialization failed!
    Code:
    10/20/2017 9:50 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 6001
    P3: ffffffffc000000e
    P4: 4390000
    P5: ffffd282c2729480
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\102017-3859-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-7953-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER30F3.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3122.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3152.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_5c2bef32858153f761322f5b8216981883ba9c5_00000000_cab_168c31be
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 2660df23-d7d5-48ad-b9f0-ea2bf362198e
    Report Status: 2049
    Hashed bucket:10/20/2017 9:50 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 6001
    P3: ffffffffc000000e
    P4: 4390000
    P5: ffffd282c2729480
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\102017-3859-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-7953-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER30F3.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3122.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3152.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_5c2bef32858153f761322f5b8216981883ba9c5_00000000_02f83160
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 2660df23-d7d5-48ad-b9f0-ea2bf362198e
    Report Status: 4
    Hashed bucket:
    10/21/2017 3:12 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 6001
    P3: ffffffffc000000e
    P4: 5ef0000
    P5: ffff8c8eb86cfaf0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\102117-3921-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-7937-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CCC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CEC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CED.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_f58f721124bbf32fca55a2ff8d4a42553c7f50_00000000_cab_16342d59
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a0e792db-11b0-40f8-8646-eb850b11acc4
    Report Status: 2049
    Hashed bucket:
    10/21/2017 3:11 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 1a
    P2: 6001
    P3: ffffffffc000000e
    P4: 5ef0000
    P5: ffff8c8eb86cfaf0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\102117-3921-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-7937-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CCC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CEC.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2CED.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_f58f721124bbf32fca55a2ff8d4a42553c7f50_00000000_02f82cfb
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: a0e792db-11b0-40f8-8646-eb850b11acc4
    Report Status: 4
    Hashed bucket:
    Last edited by zbook; 3 Weeks Ago at 02:29.
      My ComputerSystem Spec
  3.    3 Weeks Ago #3
    Join Date : Dec 2016
    Posts : 30
    Windows 10 64bit
    Thread Starter

    Up to step 5 now.

    Microsoft Windows [Version 10.0.16299.19](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.Beginning verification phase of system scan.Verification 100% complete.Windows Resource Protection did not find any integrity violations.C:\WINDOWS\system32>dism /online /cleanup-image /restorehealthDeployment Image Servicing and Management toolVersion: 10.0.16299.15Image Version: 10.0.16299.19[==========================100.0%==========================] The restore operation completed successfully.The operation completed successfully.C:\WINDOWS\system32>Powercfg -h offC:\WINDOWS\system32>

    Edit: I'll do chkdsk /x /f /r later on tonight.
      My ComputerSystem Spec
  4.    3 Weeks Ago #4
    Join Date : Dec 2016
    Posts : 30
    Windows 10 64bit
    Thread Starter

    I decided to do now and it was much faster than expected but couldn't edited this in the other post I made.

    chkdsk /x /f /r report: "Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk.
    Stage 1: Examining basic file system structure ... 370432 file records processed. File verification completed. 7614 large file records processed. 0 bad file records processed.
    Stage 2: Examining file name linkage ... 425 reparse records processed. 509410 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 425 reparse records processed.
    Stage 3: Examining security descriptors ... Cleaning up 1926 unused index entries from index $SII of file 0x9. Cleaning up 1926 unused index entries from index $SDH of file 0x9. Cleaning up 1926 unused security descriptors. Security descriptor verification completed. 69490 data files processed. CHKDSK is verifying Usn Journal... 38715272 USN bytes processed. Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ... 370416 files processed. File data verification completed.
    Stage 5: Looking for bad, free clusters ... 43234351 free clusters processed. Free space verification is complete. Windows has scanned the file system and found no problems. No further action is required. 243197623 KB total disk space. 69571904 KB in 284144 files. 202676 KB in 69491 indexes. 0 KB in bad sectors. 485635 KB in use by the system. 65536 KB occupied by the log file. 172937408 KB available on disk. 4096 bytes in each allocation unit. 60799405 total allocation units on disk. 43234352 allocation units available on disk. Internal Info: 00 a7 05 00 3e 65 05 00 8f 9f 0a 00 00 00 00 00 ....>e.......... 2f 01 00 00 7a 00 00 00 00 00 00 00 00 00 00 00 /...z........... Windows has finished checking your disk. Please wait while your computer restarts."

    Just let you know, I didn't do any over clocking.

    Asus website for Motherboard: MAXIMUS VII HERO Driver & Tools| Motherboards | ASUS Canada

    BIOS current version: BIOS Version: American Megatrends Inc. 3003, 10/28/2015

    I'll get to steps 12 and over soon.
      My ComputerSystem Spec
  5.    3 Weeks Ago #5
    Join Date : Apr 2017
    Posts : 8,607
    windows 10 professional version 1607 build 14393.969 64 bit

    Wasn't there an applicable BIOS update from 2015 > 2017 for the computers configuration?
    MAXIMUS VII HERO BIOS & FIRMWARE| Motherboards | ASUS Canada

    Version 32012017/03/03 update 5.55 MBytesMAXIMUS VII HERO BIOS 3201
    Improve system stability
      My ComputerSystem Spec
  6.    3 Weeks Ago #6
    Join Date : Dec 2016
    Posts : 30
    Windows 10 64bit
    Thread Starter

    Quote Originally Posted by zbook View Post
    Wasn't there an applicable BIOS update from 2015 > 2017 for the computers configuration?
    MAXIMUS VII HERO BIOS & FIRMWARE| Motherboards | ASUS Canada

    Version 32012017/03/03 update 5.55 MBytesMAXIMUS VII HERO BIOS 3201
    Improve system stability
    Yeah, I noticed. I just never did a bios update before and heard it was last resort to not cause other problems. I'm going to try it now.

    Edited: I keep finding old tutorials on how to do it. The website is different now and can't find Bios renamer, just the newest Bios firmware.

    Edited 2: Okay, so I never needed to use a Bios renamer and now it's updated to 3201. I'm going to see how it pans out for now but I'm going to do the HDtune with screenshots and memetest86+ later on. I actually did the memtest almost a year ago with no errors so I don't think anything would come up this time.
    Last edited by Shirotora; 3 Weeks Ago at 17:27.
      My ComputerSystem Spec
  7.    3 Weeks Ago #7
    Join Date : Apr 2017
    Posts : 8,607
    windows 10 professional version 1607 build 14393.969 64 bit

    Please run each chkdsk /x /f /r and HD Tune on all drives.

    There is 8 GB RAM on the computer. The Memtest86+ version 5.01 testing will be useful in ruling in/out problems with the RAM / DIMM / Motherboard.

    With 8 GB RAM it is likely that if you start testing in the evening it will complete 8 or more passes before the afternoon the following day.

    Just 1 error is a fail and you can abort testing.

    When the test has completed 8 or more passes please use a camera or smart phone camera to take a picture and post an image into the thread.
      My ComputerSystem Spec
  8.    3 Weeks Ago #8
    Join Date : Dec 2016
    Posts : 30
    Windows 10 64bit
    Thread Starter

    Quote Originally Posted by zbook View Post
    Please run each chkdsk /x /f /r and HD Tune on all drives.

    There is 8 GB RAM on the computer. The Memtest86+ version 5.01 testing will be useful in ruling in/out problems with the RAM / DIMM / Motherboard.

    With 8 GB RAM it is likely that if you start testing in the evening it will complete 8 or more passes before the afternoon the following day.

    Just 1 error is a fail and you can abort testing.

    When the test has completed 8 or more passes please use a camera or smart phone camera to take a picture and post an image into the thread.
    I'm going to try to run chkdsk /x /f /r but it keeps running on my SSD and not on my Hard Drive. I also tried Memtest86+ 5.01 but my computer won't or doesn't recognize it. If I select the flash drive with memtest86+, it just boots up my SSD into Windows. Though if it's just memtest86, I can boot up that.

    Here's the HD Tune files
    BSOD after computer waking up from sleep mode Attached Files
      My ComputerSystem Spec
  9.    3 Weeks Ago #9
    Join Date : Apr 2017
    Posts : 8,607
    windows 10 professional version 1607 build 14393.969 64 bit

    Open file explorer > this PC >view the letter for each drive.
    For chkdsk /x /f /r e: or chkdsk e: /x /f /r
    Use the above syntax changing the letter e to the letter of the applicable drive.

    For memtest86+ ersion 5.01 these are trial and error steps:

    Boot from USB Drive on Windows 10 PC Windows 10 Installation Upgrade Tutorials: Boot from USB Drive on Windows 10 PC Installation Upgrade Tutorials


    Note
    If you have fast boot or ultra fast boot enabled in your UEFI firmware settings, then you will need to temporarily disable fast boot or ultra fast boot to be able to boot from a USB.


    How to Enable Fast Boot or Ultra Fast Boot in UEFI Firmware Settings for Windows: Enable or Disable Fast Boot in UEFI Firmware Settings for Windows Performance Maintenance Tutorials


    1. Try another USB stick
    2. Try all USB ports (2.0 and 3.0)
    3. Maybe when using UEFI Bios u have temporarly switch to Legacy in BIOS settings
    4. Turn off temporarily fast boot, secure boot, CSM if enabled
      My ComputerSystem Spec
  10.    3 Weeks Ago #10
    Join Date : Dec 2016
    Posts : 30
    Windows 10 64bit
    Thread Starter

    Quote Originally Posted by zbook View Post
    Open file explorer > this PC >view the letter for each drive.
    For chkdsk /x /f /r e: or chkdsk e: /x /f /r
    Use the above syntax changing the letter e to the letter of the applicable drive.

    For memtest86+ ersion 5.01 these are trial and error steps:

    Boot from USB Drive on Windows 10 PC Windows 10 Installation Upgrade Tutorials: Boot from USB Drive on Windows 10 PC Installation Upgrade Tutorials


    Note
    If you have fast boot or ultra fast boot enabled in your UEFI firmware settings, then you will need to temporarily disable fast boot or ultra fast boot to be able to boot from a USB.


    How to Enable Fast Boot or Ultra Fast Boot in UEFI Firmware Settings for Windows: Enable or Disable Fast Boot in UEFI Firmware Settings for Windows Performance Maintenance Tutorials


    1. Try another USB stick
    2. Try all USB ports (2.0 and 3.0)
    3. Maybe when using UEFI Bios u have temporarly switch to Legacy in BIOS settings
    4. Turn off temporarily fast boot, secure boot, CSM if enabled

    Hard Drive: "Microsoft Windows [Version 10.0.16299.19](c) 2017 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>chkdsk e: /x /f /rThe type of the file system is NTFS.Volume dismounted. All opened handles to this volume are now invalid.Volume label is Hard Drive 1.
    Stage 1: Examining basic file system structure ... 29184 file records processed.File verification completed. 85 large file records processed. 0 bad file records processed.
    Stage 2: Examining file name linkage ... 144 reparse records processed. 31688 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 144 reparse records processed.
    Stage 3: Examining security descriptors ...Security descriptor verification completed. 1253 data files processed.CHKDSK is verifying Usn Journal... 40047616 USN bytes processed.Usn Journal verification completed.

    Stage 4: Looking for bad clusters in user file data ... 29168 files processed.File data verification completed.
    Stage 5: Looking for bad, free clusters ... 205486704 free clusters processed.Free space verification is complete.Windows has scanned the file system and found no problems.No further action is required. 976195583 KB total disk space. 154082428 KB in 8361 files. 1980 KB in 1254 indexes. 0 KB in bad sectors. 164359 KB in use by the system. 65536 KB occupied by the log file. 821946816 KB available on disk. 4096 bytes in each allocation unit. 244048895 total allocation units on disk. 205486704 allocation units available on disk.C:\WINDOWS\system32>C:\WINDOWS\system32>C:\WINDOWS\system32>C:\WINDOWS\system32>"

    That took all night for the Hard Drive, so I'll do the SSD tonight.
    I never got around to the memtest86+ yet. Though I never got another BSOD yet, but never tried sleep mode since then.
      My ComputerSystem Spec

 
Page 1 of 4 123 ... LastLast


Similar Threads
Thread Forum
BSOD when waking from sleep mode and randomly when starting PC
(PS when I tried to post this once it didn't show up so if it's like a moderator has to see this and this was submitted twice, really sorry!!) Hello all, my PC is crashing when it wakes up from sleep mode lately. I know it is a driver for sure,...
BSOD Crashes and Debugging
Solved BSOD when I've opened and closed OBS a lot/when waking from sleep mode
Hello, My laptop seems to keep blue screening off and on. This seems to happen if I open and close Open Broadcast Software a few times. The BSOD also seems to happen shortly after I wake my laptop from sleep mode. I did a little research and a...
BSOD Crashes and Debugging
Computer having trouble booting and waking up from Sleep Mode
Not sure what thread to post this under... My Computer's not working. I've been having trouble with it waking up from Sleep Mode or even just booting it up from being off since getting WINDOWS 10 it seems like. It would start and just get stuck on...
General Support
BSOD after waking computer from sleep mode
I had just finished about 4 hours of gaming and put my computer in sleep mode while I did some other personal things. Once I came back, I awoke my computer and when attempting to put in my log passcode, my computer froze. After about 1 minute,...
BSOD Crashes and Debugging
BSOD - Laptop restarts when waking from sleep mode
Hello. After upgrading from windows 8 to windows 10, the laptop wont wake up correctly and just restart. I have an Asus Q551LN * Upgraded the latest drivers of everything, including the intel hd graphics, the same with the nvidia integrated...
BSOD Crashes and Debugging
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 18:35.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums