perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 9, 2020 #21 Should I remove all but one stick of ram and then test each one?
Z zbook Member Joined Oct 2, 2015 Posts 919 Oct 9, 2020 #22 Nice work. Now you can either spend time differentiating good from bad modules or replace the RAM (consider larger modules). The motherboard appears to be revision 2 and the manual RAM information was posted earlier. Windows 10 requires a minimum amount of RAM so test 2 modules or 4GB at a time in the same motherboard DIMMs to differentiate good from bad modules. Label the RAM modules and label the DIMM. Perform tests in the DDR3_1 and DDR3_3 sockets Just 1 error is a test fail. So take a picture and abort the test. Once you've found good modules a command can be ran and the modules retested. Find replacement RAM modules displayed on the QVL and use the Crucial scanner. When available post chkdsk results and upload a new Sysnative log collector result. See post #4, step #20 for chkdsk. When available upload Sea Tools long generic results and update progress creating a windows 10 iso (there is no rush). Last edited: Oct 9, 2020
Nice work. Now you can either spend time differentiating good from bad modules or replace the RAM (consider larger modules). The motherboard appears to be revision 2 and the manual RAM information was posted earlier. Windows 10 requires a minimum amount of RAM so test 2 modules or 4GB at a time in the same motherboard DIMMs to differentiate good from bad modules. Label the RAM modules and label the DIMM. Perform tests in the DDR3_1 and DDR3_3 sockets Just 1 error is a test fail. So take a picture and abort the test. Once you've found good modules a command can be ran and the modules retested. Find replacement RAM modules displayed on the QVL and use the Crucial scanner. When available post chkdsk results and upload a new Sysnative log collector result. See post #4, step #20 for chkdsk. When available upload Sea Tools long generic results and update progress creating a windows 10 iso (there is no rush).
perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 9, 2020 #23 Understood. I will test the ram. After I find the good ram and the good DIMMs (If some are bad). I will then update. Thank you so much for the help.
Understood. I will test the ram. After I find the good ram and the good DIMMs (If some are bad). I will then update. Thank you so much for the help.
Z zbook Member Joined Oct 2, 2015 Posts 919 Oct 9, 2020 #24 I'll post in the future instructions and a tutorial to troubleshoot the operating system corruption. First complete the drive testing and find normally functioning RAM. A lot of the testing can be performed overnight.
I'll post in the future instructions and a tutorial to troubleshoot the operating system corruption. First complete the drive testing and find normally functioning RAM. A lot of the testing can be performed overnight.
perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 10, 2020 #25 One ram stick was bad. I tested all of slots and the motherboard seems to be ok. I am still scanning the rest of the ram but it is taking a long time.
One ram stick was bad. I tested all of slots and the motherboard seems to be ok. I am still scanning the rest of the ram but it is taking a long time.
Z zbook Member Joined Oct 2, 2015 Posts 919 Oct 10, 2020 #26 Have you found any RAM yet that did not fail >8 passes?
perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 11, 2020 #27 9 scans and all the other sticks passed. Attachments memscan.jpg 118.6 KB · Views: 4
perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 11, 2020 #28 Here are the last chkdsk results. Attachments CHKDSKResults.txt 65.1 KB · Views: 4
perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 11, 2020 #29 Bew Sysnative log collector result Attachments SysnativeFileCollectionApp.zip 5.5 MB · Views: 5
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Oct 11, 2020 #30 And is the problem still present?
perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 11, 2020 #31 The system has not blue screened or locked up in the 3 hours it has been running. Windows is still missing some files If i can get the windows repair instructions I should be good.
The system has not blue screened or locked up in the 3 hours it has been running. Windows is still missing some files If i can get the windows repair instructions I should be good.
xilolee Moderator Staff member Joined Dec 31, 2013 Posts 3,670 Location World, Europe, Italy Oct 11, 2020 #32 What files? Are you referring to the SFC tool? In this case, open a new thread in the windows update subforum, if SFC doesn't correct files on its own.
What files? Are you referring to the SFC tool? In this case, open a new thread in the windows update subforum, if SFC doesn't correct files on its own.
Z zbook Member Joined Oct 2, 2015 Posts 919 Oct 11, 2020 #33 Chkdsk 10/9 Code: Cleaning up 14 unused index entries from index $SII of file 0x9. Cleaning up 14 unused index entries from index $SDH of file 0x9. Cleaning up 14 unused security descriptors. Windows has scanned the file system and found no problems. Chkdsk 10/6 Code: Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. Chkdsk 9/23 Code: Correcting errors in the Master File Table (MFT) mirror. Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. Chkdsk 9/12 Code: Windows has made corrections to the file system. There were 4 Chkdsk scans in the past 30 days. The scan on 10/9 was the only one without problems. 1) Plan to run chkdsk /r /v in the next 30 days. (run overnight) At the time the log collector was ran there were 5 RAM modules. What was done with the malfunctioning module? 2) Open administrative command prompt and copy and paste: (all at one time) bcdedit /deletevalue {badmemory} badmemorylist bcdedit /enum {badmemory} 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
Chkdsk 10/9 Code: Cleaning up 14 unused index entries from index $SII of file 0x9. Cleaning up 14 unused index entries from index $SDH of file 0x9. Cleaning up 14 unused security descriptors. Windows has scanned the file system and found no problems. Chkdsk 10/6 Code: Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. Chkdsk 9/23 Code: Correcting errors in the Master File Table (MFT) mirror. Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. Chkdsk 9/12 Code: Windows has made corrections to the file system. There were 4 Chkdsk scans in the past 30 days. The scan on 10/9 was the only one without problems. 1) Plan to run chkdsk /r /v in the next 30 days. (run overnight) At the time the log collector was ran there were 5 RAM modules. What was done with the malfunctioning module? 2) Open administrative command prompt and copy and paste: (all at one time) bcdedit /deletevalue {badmemory} badmemorylist bcdedit /enum {badmemory} 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
perry147 Active member Joined Oct 6, 2020 Posts 25 Oct 11, 2020 #35 Microsoft Windows [Version 10.0.19041.508] (c) 2020 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>bcdedit /deletevalue {badmemory} badmemorylist An error occurred while attempting to delete the specified data element. Element not found. C:\WINDOWS\system32>bcdedit /enum {badmemory} RAM Defects ----------- identifier {badmemory} C:\WINDOWS\system32>
Microsoft Windows [Version 10.0.19041.508] (c) 2020 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>bcdedit /deletevalue {badmemory} badmemorylist An error occurred while attempting to delete the specified data element. Element not found. C:\WINDOWS\system32>bcdedit /enum {badmemory} RAM Defects ----------- identifier {badmemory} C:\WINDOWS\system32>
Z zbook Member Joined Oct 2, 2015 Posts 919 Oct 11, 2020 #36 Look's good. This is a link to troubleshoot the operating system problems seen with scannow / restorehealth: Windows Update Forum Posting Instructions Include pictures / images of the error messages / codes if there are problems with sfcfix. Also run Farbar / frst64.exe > post the text file share links into the new thread Downloading Farbar Recovery Scan Tool Please post this link into the new thread and post a link for the new thread into this thread.
Look's good. This is a link to troubleshoot the operating system problems seen with scannow / restorehealth: Windows Update Forum Posting Instructions Include pictures / images of the error messages / codes if there are problems with sfcfix. Also run Farbar / frst64.exe > post the text file share links into the new thread Downloading Farbar Recovery Scan Tool Please post this link into the new thread and post a link for the new thread into this thread.
Z zbook Member Joined Oct 2, 2015 Posts 919 Oct 18, 2020 #37 perry147 said: The system has not blue screened or locked up in the 3 hours it has been running. Windows is still missing some files If i can get the windows repair instructions I should be good. Click to expand... How is the performance? How has it been during the week? A link to troubleshoot the Windows corruption wasn't seen. Windows repair can be performed as per the comments earlier in the thread (here or in the windows update forum).
perry147 said: The system has not blue screened or locked up in the 3 hours it has been running. Windows is still missing some files If i can get the windows repair instructions I should be good. Click to expand... How is the performance? How has it been during the week? A link to troubleshoot the Windows corruption wasn't seen. Windows repair can be performed as per the comments earlier in the thread (here or in the windows update forum).