Hello again :)
I removed those SURT instructions as I noticed you were using Windows 8 (and SURT doesn't work on Windows 8). Instead, you must use DISM, which is a revamped and rebranded SURT on Windows 8 (but still effectively SURT) - more on that later.
There does appear to be hardware failure here. You have corrupt files, I can see that from your logfile. It's quite unlikely to have corrupt files within a week without hardware failures. Yes, there are non-hardware causes of corrupt files, which is what I mostly fix here, and yes, some people will run into these within a week, but it's statistically very unlikely. Now let's put that with your other symptoms, in particular the freezing....and that's another indication of hardware failure. Again, there are non-hardware causes, but it's often an indication of hardware failure. chkdsk hanging...very unlikely not to be hardware related to be honest. And BSODs...a good split between hardware and non-hardware causes. On their own, is no immediate indication of hardware failure, but often can be.
I mean, yes, there is no solid evidence here
at all, but, and I'm going to be completely honest here, I would be very surprised if this turns out not to be hardware failure.
Which piece of hardware? Very hard to say. Literally could be anything from hard disk to motherboard to RAM to CPU to PSU, or perhaps even something else, but those are the most likely. RAM we can test easily enough (be aware that all of these tests are statistical and not definitive - the longer you run it the stronger the evidence, but nothing can be absolutely proved), hard disk and CPU similarly, but not much else. A lot of evidence actually points to the hard-disk, and that is probably what we would logically pick on, but you know, I've got this niggling sense that it's actually the motherboard, perhaps CPU, but without any hard evidence I can show you, just a feeling.
First, run DISM. We can't start fixing until we sort out the hardware, but I want to see what sort of corruptions you have. I can refine my guess at which hardware might be failing over the length, look and count of each corruption.
First, please start an Elevated Command Prompt:
How to run an elevated command prompt
Copy and paste in
DISM.exe /Online /Cleanup-image /Restorehealth
and let it complete.
Once done
- Select Windows Explorer and then click Computer.
- Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
- Find and double click on the Logs folder.
- Right-click on the CBS folder, and select Copy.
- Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
- Into this folder paste the following additional logfile: C:\Windows\Logs\DISM\DISM.log
- Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
- A new file, also called CBS (CBS.zip), but this time with a different icon, will be created. Please upload it here.
Next, I suggest you contact Fry's and tell them that you have just bought a refurbished computer in the last week and that it's already becoming unusable over hardware failure. If necessary, tell them that you suspect it might be the motherboard or CPU based off the symptoms and/or point them to this thread. Ask them whether they can replace it (they'll probably offer only to repair & if it still isn't perfect after a first repair then you have more leverage for a replacement.)
Then test hard-disk:
https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html
SeaTools for DOS ideally, otherwise SeaTools for Windows (run SMART and then Short and then Long Self Test). Ensure important data is backed up first just in case it pushes it over the edge if it is dying (I've never actually seen it happen, but better to be safe rather than sorry)
Then come back before making any other tests (ideally post DISM logs even before HDD test). The reason is that the other tests are more complicated, and I want to make my recommendations off evidence. For example, a CPU test can fail but because of failing motherboard, for instance, and some other tests end up testing both RAM and CPU together. Unless tests are deployed strategically, a mis-diagnosis can easily be made.
Richard