There were no BSOD mini dump files.
Post #18 displayed a misbehaving hardware driver.
The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced. Typically the memory address is wrong or the memory address is pointing at freed memory.
The logs displayed multiple BSOD with bugcheck 50.
The logs displayed drive file corruption.
For all steps please post images into the thread.
If there are problems posting images please use one drive or drop box share links.
1) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings >
a) under performance click settings > on performance options click the advanced tab > under virtual memory click change > post an image of the virtual memory window into the thread
b) under startup and recovery click settings > post an image of the startup and recovery window into the thread
2) If the computer has Ccleaner > click on the Windows tab > scroll down to system and advanced > post an image into the thread
3) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
4) Run HD Tune:
http://www.hdtune.com/download.html
Post images of the test results for each of these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan
5) Open administrative command prompt and type or copy and paste:
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
reboot
6) Use the information in this link to find the chkdsk report in the event viewer: Copy and paste > notepad > save to the desktop > post a image into the thread.
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials
7) For any BSOD please run the beta version of the log collector by clicking extract.
If the beta collector does not collect files when using extract please use the DM log collector:
log collector v2-beta08.zip
BSOD - Posting Instructions - Windows 10 Forums
8) Open the website for the computer .or motherboard manufacturer > enter the product or serial number or model > select the operating system > view drivers and BIOS > post a URL or hyperlink into the thread
9) Run memtest86+ version 5.01 for at least 8 passes. Memtest86+ - Advanced Memory Diagnostic Tool
This may take hours so plan to run it overnight.
a) 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 test 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.
If there is more than 1 RAM module then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
b) When Memtest86+ has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
Memory problems. - Microsoft Community
MemTest86+ - Test RAM Windows 10 Tutorials
Code:
Event[477]: Log Name: System Source: Ntfs Date: 2018-02-18T23:36:30.197 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-M58OUOS 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 and fixed offline.
Code:
Event[587]: Log Name: System Source: Ntfs Date: 2018-02-18T23:50:39.273 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-M58OUOS Description: A corruption was discovered in the file system structure on volume C:.A corruption was found in a file system index structure. The file reference number is 0x4000000017f06. The name of the file is "\Users\UpdatusUser.DESKTOP-M58OUOS\AppData\Roaming\Microsoft\Windows". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".
Code:
18/02/2018 23:18 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffff8f254444c000
P3: 0
P4: fffff803d8101b31
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-31234-01.dmp
\\?\C:\Windows\TEMP\WER-57187-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER580E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A6F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A8F.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_d06db1b7617de75c743cc93683949b46e2e736ce_00000000_cab_18461831
Analysis symbol:
Rechecking for solution: 0
Report Id: 6ffb9ca2-0cd6-4bf0-a550-9e7c60722995
Report Status: 2049
Hashed bucket:18/02/2018 23:17 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffff8f254444c000
P3: 0
P4: fffff803d8101b31
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-31234-01.dmp
\\?\C:\Windows\TEMP\WER-57187-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER580E.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A6F.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5A8F.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_d06db1b7617de75c743cc93683949b46e2e736ce_00000000_02d95aec
Analysis symbol:
Rechecking for solution: 0
Report Id: 6ffb9ca2-0cd6-4bf0-a550-9e7c60722995
Report Status: 4
Hashed bucket:
18/02/2018 23:38 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffb0a904f08000
P3: 0
P4: fffff802ceba1b31
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-38046-01.dmp
\\?\C:\Windows\TEMP\WER-124390-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35EB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36E6.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_10d56ca2123953a7dac6c631fc9597f64d86e92_00000000_cab_1f5249f0
Analysis symbol:
Rechecking for solution: 0
Report Id: 49a2a64c-c646-4341-a83b-94b665c60b52
Report Status: 2049
Hashed bucket:
18/02/2018 23:38 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffb0a904f08000
P3: 0
P4: fffff802ceba1b31
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-38046-01.dmp
\\?\C:\Windows\TEMP\WER-124390-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35EB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36A6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER36E6.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_10d56ca2123953a7dac6c631fc9597f64d86e92_00000000_02d236f4
Analysis symbol:
Rechecking for solution: 0
Report Id: 49a2a64c-c646-4341-a83b-94b665c60b52
Report Status: 4
Hashed bucket:
18/02/2018 23:12 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffc1d2808fa000
P3: 0
P4: fffff80078501b31
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-32281-01.dmp
\\?\C:\Windows\TEMP\WER-228859-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC247.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC2C4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC2D5.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_c5703c35b312f1efdf512c203290b16092309bd5_00000000_cab_23b7c489
Analysis symbol:
Rechecking for solution: 0
Report Id: e1822965-3686-49ac-9836-6b4fc75ec884
Report Status: 2049
Hashed bucket:
18/02/2018 23:12 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: ffffc1d2808fa000
P3: 0
P4: fffff80078501b31
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-32281-01.dmp
\\?\C:\Windows\TEMP\WER-228859-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC247.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC2C4.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC2D5.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_c5703c35b312f1efdf512c203290b16092309bd5_00000000_02efc2e4
Analysis symbol:
Rechecking for solution: 0
Report Id: e1822965-3686-49ac-9836-6b4fc75ec884
Report Status: 4
Hashed bucket:
18/02/2018 23:50 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: fffffe1c4241f000
P3: 0
P4: fffff8012ab961db
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-33156-01.dmp
\\?\C:\Windows\TEMP\WER-56296-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3FB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA95A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA97A.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_aa51f10b0f3af7a53f449f189ca6886a2415bb_00000000_cab_031dc936
Analysis symbol:
Rechecking for solution: 0
Report Id: acfb40ec-fa29-495f-8ca3-184cf524642e
Report Status: 2049
Hashed bucket:
18/02/2018 23:50 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 50
P2: fffffe1c4241f000
P3: 0
P4: fffff8012ab961db
P5: 0
P6: 10_0_16299
P7: 0_0
P8: 768_1
P9:
P10:
Attached files:
\\?\C:\Windows\Minidump\021818-33156-01.dmp
\\?\C:\Windows\TEMP\WER-56296-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA3FB.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA95A.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA97A.tmp.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_aa51f10b0f3af7a53f449f189ca6886a2415bb_00000000_0311a989
Analysis symbol:
Rechecking for solution: 0
Report Id: acfb40ec-fa29-495f-8ca3-184cf524642e
Report Status: 4
Hashed bucket:
Code:
Name NVIDIA GeForce 7050 PV / NVIDIA nForce 630aPNP Device ID PCI\VEN_10DE&DEV_053B&SUBSYS_82B31043&REV_A2\3&267A616A&0&90
Adapter Type GeForce 7050 PV / nForce 630a, NVIDIA compatible
Adapter Description NVIDIA GeForce 7050 PV / NVIDIA nForce 630a
Adapter RAM 128.00 MB (134,217,728 bytes)
Installed Drivers nvd3dumx.dll
Driver Version 8.15.11.9038
INF File oem7.inf (Section001 section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 1920 x 1080 x 60 hertz
Bits/Pixel 32
Memory Address 0xDE000000-0xDEFFFFFF
Memory Address 0xC0000000-0xCFFFFFFF
Memory Address 0xDD000000-0xDDFFFFFF
IRQ Channel IRQ 22
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver c:\windows\system32\drivers\nvlddmkm.sys (8.15.11.9038, 10.80 MB (11,327,776 bytes), 14/07/2009 12:54)