Memory_Management/various BSOD issues

fried_pc_rice · Sep 29, 2020

System Manufacturer: N/A
Laptop or Desktop: Desktop
Exact model number: N/A
OS: Windows 10 64 bit
What was original installed OS on system?
Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Age of system: ~5 years
Age of OS installation: ~5 years
Have you re-installed the OS?
CPU: Intel Core i5-6500
RAM: 2x HyperX Fury 8GB, first 2 slots
Video Card: Nvidia GTX 960
MotherBoard: ASUS Z170-P
Is driver verifier enabled or disabled: disabled
What security software are you using? Windows Defender, Firewall, Malwarebytes
Are you using proxy, vpn, ipfilters or similar software: No
Are you using Disk Image tools?: No

Whenever I restart my PC, it tends to crash multiple times, oftentimes MEMORY_MANAGEMENT, Page fault in non-paged area, and IRQL not less than or equal.
Other things the probably don't matter: DISM can't find source files to repair disk but finds errors, CHKDSK returns nothing, MEMSCHED returns nothing.
Thanks in advance!

philc43 · Sep 29, 2020

Hello and welcome to Sysnative!

With so many crashes it is not too surprising that you have some system file corruption. The most important thing is to find the cause of the crashes. I am tending to think that there is a problem with the memory or the way it has been set up. Your processor is designed to work with DDR4 memory at a maximum speed of 2133MHz. Your memory is able to work at up to 2400MHz but I see you have clocked it at 2187MHz which is still a little bit overclocked and should be set to 2133MHz.

Please remove all overclocking and test the system to see if it is more stable. If you need advice on how to do this just ask.

If it continues to crash please go onto testing the memory for faults - follow the instructions in the tutorial below:
Test RAM with PassMark MemTest86

zbook · Sep 29, 2020

These were seen in the logs:
a) drive file system corruption including the Master File Table
b) registry hive corruption
c) RAM problems
d) insufficient drive free space
e) Malwarebytes problems

1) Open administrative command prompt (CP) and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

13) Free up drive space so that there is > 30 GB free space
Free Up Drive Space in Windows 10

14) Uninstall Malwarebytes using the applicable uninstall tool:
https://downloads.malwarebytes.com/file/mb_clean

15) Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /r /v
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
reboot

16) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

fried_pc_rice · Oct 7, 2020

Thank you both for the reply! I turned off overclocking on my RAM, and it became much more stable for a few days, but the problems came back recently. The PassMark test hasn't worked yet and I will keep trying to use it, but I have followed much of the instructions of zbook. Malwarebytes was removed, drive space was freed up, and I ran the suggested commands and got:

Microsoft Windows [Version 10.0.19041.1] (c) 2019 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.19041.1 Image Version: 10.0.19041.1 [==========================100.0%==========================] The component store is repairable. The operation completed successfully. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.19041.1 Image Version: 10.0.19041.1 [==========================100.0%==========================] Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32>chkdsk /scan The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 932608 file records processed. File verification completed. Phase duration (File record verification): 17.63 seconds. 15883 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. 0 bad file records processed. Phase duration (Bad file record checking): 0.73 milliseconds. Stage 2: Examining file name linkage ... 26370 reparse records processed. 1079944 index entries processed. Index verification completed. Phase duration (Index verification): 28.17 seconds. 0 unindexed files scanned. Phase duration (Orphan reconnection): 1.84 seconds. 0 unindexed files recovered to lost and found. Phase duration (Orphan recovery to lost and found): 0.40 milliseconds. 26370 reparse records processed. Phase duration (Reparse point and Object ID verification): 84.53 milliseconds. Stage 3: Examining security descriptors ... Security descriptor verification completed. Phase duration (Security descriptor verification): 61.14 milliseconds. 73669 data files processed. Phase duration (Data attribute verification): 1.66 milliseconds. CHKDSK is verifying Usn Journal... 7938624 USN bytes processed. Usn Journal verification completed. Phase duration (USN journal verification): 120.37 milliseconds. Windows has scanned the file system and found no problems. No further action is required. 119195265 KB total disk space. 94886024 KB in 453623 files. 305808 KB in 73670 indexes. 0 KB in bad sectors. 1021129 KB in use by the system. 65536 KB occupied by the log file. 22982304 KB available on disk. 4096 bytes in each allocation unit. 29798816 total allocation units on disk. 5745576 allocation units available on disk. Total duration: 47.94 seconds (47947 ms). C:\WINDOWS\system32>wmic recoveroswmic recoveros set autoreboot = false recoveroswmic - Alias not found. C:\WINDOWS\system32>wmic recoveros set autoreboot = false Updating property(s) of '\\JQK-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"' Property(s) update successful. C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7 Updating property(s) of '\\JQK-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"' Property(s) update successful. C:\WINDOWS\system32>wmic recoveros get autoreboot AutoReboot FALSE C:\WINDOWS\system32>wmic recoveros get DebugInfoType DebugInfoType 7 C:\WINDOWS\system32>bcdedit /enum {badmemory} RAM Defects ----------- identifier {badmemory} badmemorylist 0x17efc9 0x17efca 0x17efcb 0x17efcc 0x17efcd 0x17efce 0x17efcf C:\WINDOWS\system32>

sfc /scannow never finishes but it says that it detects corruption but cannot repair it.
Any other advice? Thanks!

zbook · Oct 8, 2020

Code:

Scannow results not displayed in the administrative command prompt commands / results

Code:

Restorehealth:  Error: 0x800f081f
The source files could not be found.

1) Open administrative command prompt and copy and paste:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Find the new text file on the desktop > post a share link into this thread

2) Search for

C:\Windows\Logs\CBS\CBS.log > post a share link into this thread

3) Run: SFCFix Official Download - Repair Windows Update > post a share link

4) Find a flash drive that you can format (> or = 8 GB).

5) Create a bootable Windows 10 iso 2004:
Download Windows 10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

6) The BIOS: Version/Date American Megatrends Inc. 0705, 2/23/2016

Missed BIOS versions:

Code:

Version 3805
2018/06/018.02 MBytes
Z170-P BIOS 3805
Intel New ME Update, Improve Stability.

Version 3610
2018/04/148.06 MBytes
Z170-P BIOS 3610
1. Improve memory compatibility.

Version 3606
2018/03/278.07 MBytes
Z170-P BIOS 3606
1. Update CPU Microcode
2. Improve system security and stability

Version -
2017/11/223.65 MBytes
MEUpdateTool
Intel has identified security issue that could potentially place impacted platform at risk.
Use ME Update tool to update your ME.
*We suggest you update ME Driver to the latest Version 11.7.0.1040 simultaneously.
Please download the file and check the MD5 code first.
MD5: 478dca5db24254d3a40824cc6b91ccf6

Version 3301
2017/03/028.04 MBytes
Z170-P BIOS 3301
Improve system stability

Version 3017 Beta Version
2016/12/308.02 MBytes
Z170-P BIOS 3017
Support new CPUs. Please refer to our website at:
http://www.asus.com/support/cpu_support.

Version 2003
2016/09/236.91 MBytes
Z170-P BIOS 2003
Support new CPUs. Please refer to our website at:
http://www.asus.com/support/cpu_support.

Version 1804
2016/06/206.73 MBytes
Z170-P BIOS 1804
Improve system stability

Version 1803
2016/05/206.73 MBytes
Z170-P BIOS 1803
Improve system compatibility

Upgrade the BIOS: 0705 > 3805

7) When available post images and text reports for Memtest86 (two tests each with four passes), chkdsk /r /v, drive free space

8) Open administrative Powershell (PS) and copy and paste: (all at one time)

Code:

[Cmdletbinding()]
Param(
    [string]$Computername = "localhost"
)
cls
$PysicalMemory = Get-WmiObject -class "win32_physicalmemory" -namespace "root\CIMV2" -ComputerName $Computername

Write-Host "Memore Modules:" -ForegroundColor Green
$PysicalMemory | Format-Table Tag,BankLabel,@{n="Capacity(GB)";e={$_.Capacity/1GB}},Manufacturer,PartNumber,Speed -AutoSize

Write-Host "Total Memory:" -ForegroundColor Green
Write-Host "$((($PysicalMemory).Capacity | Measure-Object -Sum).Sum/1GB)GB"

$TotalSlots = ((Get-WmiObject -Class "win32_PhysicalMemoryArray" -namespace "root\CIMV2" -ComputerName $Computername).MemoryDevices | Measure-Object -Sum).Sum
Write-Host "`nTotal Memory Slots:" -ForegroundColor Green
Write-Host $TotalSlots

$UsedSlots = (($PysicalMemory) | Measure-Object).Count
Write-Host "`nUsed Memory Slots:" -ForegroundColor Green
Write-Host $UsedSlots

If($UsedSlots -eq $TotalSlots)
{
    Write-Host "All memory slots are filled up, none is empty!" -ForegroundColor Yellow
}

9) When these have completed > right click on the top bar or title bar of the administrative powershell 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

10) Open administrative command prompt (CP) and type or copy and paste:

wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor

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

11) Find replacement RAM options on the Qualified Vendor List (QVL): (pending test results)
https://dlcdnets.asus.com/pub/ASUS/mb/LGA1151/Z170-K/Z170_DDR4_4DIMM_memory_QVL_report_201712.pdf

12) Run the Crucial scanner to view options for RAM replacement: (pending test results)
Crucial System Scanner

13) When replacing RAM: (pending test results)
a) replace in pairs with matching SKU
b) make sure the RAM modules are displayed on the QVL
(or RAM manufacturer guarantees compatibility)
c) consider manufacturers that have lifetime warranties

Search

Search

Memory_Management/various BSOD issues

fried_pc_rice

New member

Attachments

philc43

BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert

zbook

Member

fried_pc_rice

New member

zbook

Member