D
DavisOdom1
I have been randomly getting BSODs either MEMORY_MANAGEMENT or page fault, but have not been able to fix the problem after several different troubleshooting methods. memtest passes (both memtest86 and mdsched), /sfc scannow passes, chkdsk passes, windows is up to date, gpu drivers up to date. Recently I discovered the tool WhoCrashed which is helping me track down the cause of these crashes. However, I do not know what ntoskrnl.exe is or what I can do about it.
On Fri 10/2/2020 10:58:15 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100220-4640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x50 (0xFFFFC90E2D4B6080, 0x0, 0xFFFFF80753D1601B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10/2/2020 10:58:15 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x130920)
Bugcheck code: 0x50 (0xFFFFC90E2D4B6080, 0x0, 0xFFFFF80753D1601B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
I feel as though I have run out of options. A fresh installation of windows is not a new strategy either because this system is only a couple weeks old. I just bought a new SSD and installed windows fresh so it is relatively clean.
UPDATE: SFC /scannow is now failing again. Seems as though something is corrupting my system even after I repair it. This time the files could not be repaired automatically. Some interesting bits from the CBS.log:
Info CSI 000001b4 Warning: Overlap: Directory \??\C:\Program Files (x86)\ is owned twice or has its security set twice
Info CSI 000001f7 [SR] Cannot repair member file [l:25]'Windows Message Nudge.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
Looks like something with my windows installation may be configured wrong. There are multiple folders owned twice and multiple windows shell sounds that are corrupted
Just got two new crash reports:
On Fri 10/2/2020 11:49:53 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100220-3750-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFBBFFC3B0168, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Fri 10/2/2020 11:49:53 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFBBFFC3B0168, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Fri 10/2/2020 11:48:41 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100220-5015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xA (0x80000000020, 0xFF, 0x0, 0xFFFFF80327515FE0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Also, I tried running startup repair after these crashes. It told me that it couldn't repair my pc and to look for the logs somewhere under "F:\WINDOWS\"
Windows has never been installed on drive F:\ of my machine and the drive doesn't even contain anything at the moment.
I have three hard drives: an NVMe SSD, a SATA SSD, and an HDD. The NVMe is new, system used to reside on the SATA SSD, perhaps there is something left from that setup screwing me up?
Found an srttrail from startup repair:
Last successful boot time: 10/2/2020 2:58:51 PM (GMT)
Number of repair attempts: 1
Session details
---------------------------
System Disk = \Device\Harddisk2
Windows directory = F:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
What's interesting here is that my system is on C:\, this logfile is on C:\, but its contents are referring to F:\
Continue reading...
On Fri 10/2/2020 10:58:15 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100220-4640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x50 (0xFFFFC90E2D4B6080, 0x0, 0xFFFFF80753D1601B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 10/2/2020 10:58:15 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntfs.sys (Ntfs+0x130920)
Bugcheck code: 0x50 (0xFFFFC90E2D4B6080, 0x0, 0xFFFFF80753D1601B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.
I feel as though I have run out of options. A fresh installation of windows is not a new strategy either because this system is only a couple weeks old. I just bought a new SSD and installed windows fresh so it is relatively clean.
UPDATE: SFC /scannow is now failing again. Seems as though something is corrupting my system even after I repair it. This time the files could not be repaired automatically. Some interesting bits from the CBS.log:
Info CSI 000001b4 Warning: Overlap: Directory \??\C:\Program Files (x86)\ is owned twice or has its security set twice
Info CSI 000001f7 [SR] Cannot repair member file [l:25]'Windows Message Nudge.wav' of Microsoft-Windows-Shell-Sounds, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
Looks like something with my windows installation may be configured wrong. There are multiple folders owned twice and multiple windows shell sounds that are corrupted
Just got two new crash reports:
On Fri 10/2/2020 11:49:53 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100220-3750-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFBBFFC3B0168, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Fri 10/2/2020 11:49:53 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFFBBFFC3B0168, 0x80000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Fri 10/2/2020 11:48:41 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\100220-5015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0xA (0x80000000020, 0xFF, 0x0, 0xFFFFF80327515FE0)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Also, I tried running startup repair after these crashes. It told me that it couldn't repair my pc and to look for the logs somewhere under "F:\WINDOWS\"
Windows has never been installed on drive F:\ of my machine and the drive doesn't even contain anything at the moment.
I have three hard drives: an NVMe SSD, a SATA SSD, and an HDD. The NVMe is new, system used to reside on the SATA SSD, perhaps there is something left from that setup screwing me up?
Found an srttrail from startup repair:
Last successful boot time: 10/2/2020 2:58:51 PM (GMT)
Number of repair attempts: 1
Session details
---------------------------
System Disk = \Device\Harddisk2
Windows directory = F:\WINDOWS
AutoChk Run = 0
Number of root causes = 1
What's interesting here is that my system is on C:\, this logfile is on C:\, but its contents are referring to F:\
Continue reading...