For all of the testing please make sure that images are posted into the thread.
In case there are problems posting images please use one drive or drop box share links to post into the thread.
Open administrative command prompt and type or copy and paste:
1) sfc /scannow
2) dism /online /cleanup-image /restorehealth
3)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
4) chkdsk /x /f /r
5) Use the information in this link to find the chkdsk report in the event viewer and post the report into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Performance Maintenance Tutorials
6) Make sure that there is no over clocking while troubleshooting.
7) Sometimes there are problems in the bios that produce bsod.
The BIOS: Version/Date Dell Inc. A08, 25/04/2008
8) Please check to see if this is the most up to date version.
9) 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
10) 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
11) 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.
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 20 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.
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 BSOD Tutorials
12) Please open the website for the computer's drivers and post a URL into the thread.
Code:
Event[3833]: Log Name: System Source: Ntfs Date: 2017-11-03T09:10:08.893 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: mercury Description: A corruption was discovered in the file system structure on volume ??.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000000000. The name of the file is "<unable to determine file name>".
Code:
Event[3991]: Log Name: System Source: Ntfs Date: 2017-11-06T13:49:35.316 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: mercury Description: A corruption was discovered in the file system structure on volume ??.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000000000. The name of the file is "<unable to determine file name>".
Code:
Event[3998]: Log Name: System Source: Ntfs Date: 2017-11-06T15:12:33.601 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: mercury Description: A corruption was discovered in the file system structure on volume ??.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000000000. The name of the file is "<unable to determine file name>".
Code:
Event[4008]: Log Name: System Source: Ntfs Date: 2017-11-06T17:14:19.787 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: mercury Description: A corruption was discovered in the file system structure on volume ??.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000000000. The name of the file is "<unable to determine file name>".
Code:
Event[4059]: Log Name: System Source: Ntfs Date: 2017-11-08T15:09:41.812 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: mercury Description: A corruption was discovered in the file system structure on volume ??.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000000000. The name of the file is "<unable to determine file name>".
Code:
Event[4085]: Log Name: System Source: Ntfs Date: 2017-11-09T12:59:35.938 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: mercury Description: A corruption was discovered in the file system structure on volume ??.The Master File Table (MFT) contains a corrupted file record. The file reference number is 0x1000000000000. The name of the file is "<unable to determine file name>".
Code:
Event[59]: Log Name: System Source: Microsoft-Windows-Kernel-PnP Date: 2017-06-29T17:41:37.042 Event ID: 219 Task: N/A Level: Warning Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: mercury Description: The driver \Driver\ni488k failed to load for the device PCI\VEN_1093&DEV_C801&SUBSYS_00000000&REV_02\5&375146b3&0&300310.
Code:
Event[3038]: Log Name: System
Source: NTFS
Date: 2017-11-01T12:20:19.169
Event ID: 134
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: mercury
Description:
The transaction resource manager on volume \\?\Volume{6f664bff-0000-0000-0000-100000000000} encountered an error during recovery. The resource manager will continue recovery.
Event[3039]:
Log Name: System
Source: NTFS
Date: 2017-11-01T12:20:19.169
Event ID: 134
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: mercury
Description:
The transaction resource manager on volume \\?\Volume{6f664bff-0000-0000-0000-100000000000} encountered an error during recovery. The resource manager will continue recovery.
Code:
Event[3836]: Log Name: System
Source: NTFS
Date: 2017-11-03T09:23:35.447
Event ID: 50
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: mercury
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.