BSOD - ntkrnlmp.exe/ntoskrnl.exe.

zbook · 26 Dec 2018

Open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > zip > post a share link into the thread using one drive, drop box, or google drive

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 12/26/2018 15:00:44
Size on disk: 1014 MB

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) Powercfg -h off
6) bcdedit /enum {badmemory}
7) 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

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

9) Run Memtest86 version 8.0 for 8 or more passes
MemTest86 - Official Site of the x86 Memory Testing Tool
Testing is not done by time but by passes.
The more the passes the better the testing conditions.
The computer has 16 GB DDR4 RAM.
There are 2 RAM modules with each 8 GB.
Testing time is approximately 1 -2 hours / GB RAM.
Testing must be continuous.
A substantial portion of the testing can be performed overnight.
Just one error is a test fail and testing can be aborted.
Then test one RAM module at a time in the same DIMM for 8 or more passes to differentiate good from malfunctioning RAM.
For each test please use a camera or smartphone camera to post an image into the thread.

Code:

Event[1229]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2018-12-16T10:02:52.847
  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-OSLQL77
  Description: 
Windows failed to resume from hibernate with error status 0xC0000001.

Code:

Event[1580]:
  Log Name: System
  Source: Microsoft-Windows-Memory-Diagnostic-Task-Handler
  Date: 2018-12-19T10:38:58.676
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-1824743079-4167592317-1585261083-1003
  User Name: DESKTOP-OSLQL77\mikes
  Computer: DESKTOP-OSLQL77
  Description: 
Windows removed bad memory regions from this PC.

Schirmy · 26 Dec 2018

Attachment 218655

Should be it. Will run the other troubleshooting now. Thanks, zbook. :)

zbook · 26 Dec 2018

Download and install Everything: voidtools

Use everything to search for: C:\windows\memory.dmp
The file size is approximately 1 GB

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 12/26/2018 15:00:44
Size on disk: 1014 MB

Schirmy · 26 Dec 2018

zbook said:

Download and install Everything: voidtools

Use everything to search for: C:\windows\memory.dmp
The file size is approximately 1 GB

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 12/26/2018 15:00:44
Size on disk: 1014 MB

https://drive.google.com/open?id=1PC...yNoKb-etYvdpqr

zbook · 26 Dec 2018

There were no misbehaving drivers identified with the routine windbg commands.

Plan sufficient time to run Memtest86 for 8 or more passes and post images of the test results into the thread.
There is also a txt report that can be posted but definitely post the image of the results.
If there is just one error you can abort testing.
Then test one RAM module at a time to differentiate good from malfunctioning RAM.

When available please post the results of steps 1 - 7 in the earlier post.

Schirmy · 26 Dec 2018

Here are results 2 and 4:
Microsoft Windows [Version 10.0.17134.472](c) 2018 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>chkdsk /scanThe type of the file system is NTFS.Stage 1: Examining basic file system structure ... 432640 file records processed.File verification completed. 26899 large file records processed. 0 bad file records processed.Stage 2: Examining file name linkage ... 33752 reparse records processed. 528962 index entries processed.Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 33752 reparse records processed.Stage 3: Examining security descriptors ...Security descriptor verification completed. 48162 data files processed.CHKDSK is verifying Usn Journal... 39630840 USN bytes processed.Usn Journal verification completed.Windows has scanned the file system and found no problems.No further action is required. 116640767 KB total disk space. 85383812 KB in 221585 files. 160240 KB in 48163 indexes. 0 KB in bad sectors. 559023 KB in use by the system. 65536 KB occupied by the log file. 30537692 KB available on disk. 4096 bytes in each allocation unit. 29160191 total allocation units on disk. 7634423 allocation units available on disk.C:\WINDOWS\system32>

Schirmy · 26 Dec 2018

Also, how would Powercfg -h off work if I put my computer into sleep every night?
Attachment 218662
Attachment 218663

zbook · 26 Dec 2018

The hibernation had failed.
It is being turned off during the troubleshooting.
If can be turned back on and reevaluated after the troubleshooting.
Hibernate, sleep, or shut down: what's best for your PC? | Windows Central

Open administrative command prompt and type or copy and paste:
bcdedit /enum all
bcdedit /enum {badmemory}
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

Schirmy · 26 Dec 2018

Microsoft Windows [Version 10.0.17134.472]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>bcdedit /enum all

Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{acaf4ecb-01e8-11e8-b307-806e6f6e6963}
timeout 1

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume4
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {1c43fbb9-edbb-11e7-8b4a-ce7d503dde20}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Firmware Application (101fffff)
-------------------------------
identifier {acaf4ecb-01e8-11e8-b307-806e6f6e6963}
description Hard Drive

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {f91ddd84-5a25-11e8-b8e3-a320c9b29774}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {1c43fbb9-edbb-11e7-8b4a-ce7d503dde20}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {f91ddd84-5a25-11e8-b8e3-a320c9b29774}
device ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{f91ddd85-5a25-11e8-b8e3-a320c9b29774}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{f91ddd85-5a25-11e8-b8e3-a320c9b29774}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Resume from Hibernate
---------------------
identifier {1c43fbb9-edbb-11e7-8b4a-ce7d503dde20}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {f91ddd84-5a25-11e8-b8e3-a320c9b29774}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume4
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Local

RAM Defects
-----------
identifier {badmemory}
badmemorylist 0x646e3
0x20f58b

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {f91ddd85-5a25-11e8-b8e3-a320c9b29774}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume3
ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}
badmemorylist 0x646e3
0x20f58b

C:\WINDOWS\system32>

Ztruker · 26 Dec 2018

Dump doesn't have any useful data in it. There is a full memory.dmp available:

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 12/26/2018 15:00:44
Size on disk: 1014 MB

Zip that up and upload to OneDrive or another file sharing site and post a link to it here. Maybe there is more information in it than in the small memory dump.

Also, Nvidia has a new driver available: Version: 417.35 Release Date: 2018.12.12
Give that a try even though the dump did not indicate a Nvidia problem?