New
#41
It was posts instead of steps.
It was posts instead of steps.
Ah, sorry. So for post 10, I'm not trying to be too stupid here, but which steps do want updated - there's alot of them. I must still be misunderstanding because I couldn't obviously update all of them.
8) Open administrative command prompt and type or copy and paste:
9) sfc /scannow
10) dism /online /cleanup-image /scanhealth
11) dism /online /cleanup-image /restorehealth
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
25) Open administrative command prompt and type or copy and paste:
chkdsk /x /f /r
This may take many hours so plan to run it overnight.
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
26) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste > notepad > save to desktop > post into the thread
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials
27) Run HD Tune:
http://www.hdtune.com/
Post images of the results for each of these tabs:
a) Health (SMART)
b) Benchmark
c) Full error scan
As for #33, I just ran CCleaner and do you want another zip of the beta log collector?
What is the progress with uninstalling all of the antivirus software products with the applicable uninstall tools?
Superantispyware
Avast
Malwarebytes
To fix the event viewer is a registry technique.
Are you more comfortable making changes in the registry or performing a reset with save files.
A reset with save files should fix all of the corruption. Applications will need to be reinstalled.
Antivirus products would not need to be uninstalled with the uninstall tools as they would be uninstalled with the reset with save files.
I'm Ok making changes to the registry, but I'm unsure what fixing the event viewer does. My last resort is a reset because who would want to reinstall everything........which leads me back to what fixing the event viewer actually would do.
As for uninstalling Avast, SAS, and MB, I haven't done those yet because I thought I was just going in order in steps. There's still other stuff I haven't done.......I haven't run any memory tests, I haven't done anything with that Dell drivers page, and I didn't d'load the "chipset" d'load that was listed as an important dell update that was located on the same page as the BIOS update was. I have no idea if any of the above stuff was needed to be done or not.
I guess I'm a little turned around at this point.
The registry step appears easy but a simple mistake can cause harm.
The opening post had comments about corruption.
So far there have been 2 areas of corruption identified:
1) The drive file system
2) The event viewer
The event viewer has all of the information about what happens on the computer:
critical events: BSOD, crashes, etc.
warnings
information
The log collector was able to collect the event viewer files but it reported corruption.
When there are problems on the computer and you want to know what happened most of the events were reported in the event viewer.
If you cannot open the event viewer then you are handicapped.
The HD Tune test results for the benchmark displayed a very low transfer rate for the drive.
Most drives should have a minimum transfer rate > 30 - 50.
The transfer rate on the drive was < 1.
What is the age of the drive?
What other corruption had you noticed on the computer?
The reset with save files requires re-installation of all drivers.
That fixes any BSOD that was caused by misbehaving software and hardware drivers.
It makes the drivers up to date.
So I'm presenting all of this to you so you can put it on a balance and make the decision.
If you fix the event viewer corruption and then find there is other corruption that was not detected at this time then you may want to at that time perform a reset with save files.
If you want better performance from the drive you would then replace the applications and drivers.
So you can think about the various pro and con and report at a later time in the thread what you want to do.
Performing the Memory testing does not impact any of the above. It has little if anything to do with the operating system.
The RAM is mismatched. RAM modules should be in pairs with the identical SKU. Memory testing can pass and mismatched RAM can produce BSOD. So the mismatched RAM does not produce errors or a fail on Memory testing.
The Memory testing will allow you to test all of the RAM. Whether you can keep using the mismatched RAM or not depends upon whether there are any BSOD. And if mismatched RAM is used it has the uncertainty of a BSOD.
The drive file system corruption results were not able to be viewed as they are in the event viewer. I will need to look in the files that were collected by the log collector to see if they are there. If they are I can post that information into the thread.
If you can run the Memtest86+ version 5.01 test it will take approximately 1 - 2 hours / GB RAM. The testing needs to be continuous. That is approximately 16 to 32 hours.
Think about all of the pro and con and post into the thread what your preferences are. Either method is okay, they have their pro and con.
Never mind, now I see what the event viewer is and why it needs to be fixed.
The RAM can also be tested 1 module at a time.
If the motherboard has multichannel capability this will not be tested when modules are tested 1 at a time.
The "settings not being saved and possibly more" we have not discussed.
Whatever this is would be fixed by the reset with save files.
We could do the event viewer fix and then see what happens.
Whatever is corrupt is not being detected by sfc /scannow nor dism /online /cleanup-image /restorehealth.
So the corruption is deeper than the OS and is in the registry.
There were no chkdsk reports in the logs after 3/5/2018.
So the current status after the chkdsk /x /f /r was not reported.
Now you can run the Memtest86+ version 5.01 testing:
Memtest86+ - Advanced Memory Diagnostic Tool
When the testing has completed 8 or more passes please use a camera or smart phone camera to take a picture and post an image into the thread.
The RAM testing can be done 1 RAM stick at a time but it will not test multichannel capability.
Post into the thread at a later time your preference for the drive, operating system, registry, event viewer, drivers, BSOD testing, etc.
The age of the drive is the same as the computer - which I believe is probably a little over a year, maybe a year and a half? Just out of curiosity - since I use HD Sentinel, the only thing I ever pay attention to is what the status of the health of the HD is. It says 100%. Is it not?
As for other corruption, the only things I've noticed have to do with the saving of certain settings. The ones I've mentioned already, but I've also noticed little things that I swore weren't like that before. It seemed like my cookies on a certain site got wiped out and possibly some settings in uBlock origin that also seemed to have reverted. Other than that, I've had issues with the front USB's since the beginning. I was never sure if it was just the thumb drive I was using or not, but like I mentioned, I did have the thumb drive in there transferring files when the computer rebooted last week. Not sure if there's any correlation.
I'd like to atleast take one shot at getting the event viewer up and running, it seems crazy not too. If the registry tweak is self explanatory than I should be able to do it. Some I've seen are easy, some have scared me a little.
I'll continue this tomorrow, I really need to go to sleep. Thanks.