New
#11
Also perform these, it wont hurt:
Open up a Command Prompt (Admin)
Type sfc /scannow then Enter(Mind the space before "/")
And:
Type chkdsk /f /r then Enter(Mind the space before "/")
Also perform these, it wont hurt:
Open up a Command Prompt (Admin)
Type sfc /scannow then Enter(Mind the space before "/")
And:
Type chkdsk /f /r then Enter(Mind the space before "/")
Ah yes I saw that thread, I know that if that's the case then I'll have to live with a faulty sensor.
My concern is if that info is being interpreted by windows and causing the shutdowns.
Good morning!
I ran both commands the scannow came back fine, however the chkdsk took around four hours to run and did it's job but I cannot find a log for it. I went into the event view and navigated to where the report should be according to the various instructions I found online.
Okay, uhm. Here is an example guide for checking the log of chkdsk:
https://askleo.com/how_do_i_see_the_...t_ran_on_boot/
Any crashes?
I had to do a manual search of Winnit, for some reason the search function didn't pick it up... Here is the report;
Checking file system on C:
The type of the file system is NTFS.
A disk check has been scheduled.
Windows will now check the disk.
Stage 1: Examining basic file system structure ...
371968 file records processed. File verification completed.
6399 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
484554 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 1573 unused index entries from index $SII of file 0x9.
Cleaning up 1573 unused index entries from index $SDH of file 0x9.
Cleaning up 1573 unused security descriptors.
Security descriptor verification completed.
56294 data files processed. CHKDSK is verifying Usn Journal...
38850376 USN bytes processed. Usn Journal verification completed.
Stage 4: Looking for bad clusters in user file data ...
371952 files processed. File data verification completed.
Stage 5: Looking for bad, free clusters ...
167053735 free clusters processed. Free space verification is complete.
Windows has scanned the file system and found no problems.
No further action is required.
976195583 KB total disk space.
307279104 KB in 309187 files.
192896 KB in 56295 indexes.
0 KB in bad sectors.
508639 KB in use by the system.
65536 KB occupied by the log file.
668214944 KB available on disk.
4096 bytes in each allocation unit.
244048895 total allocation units on disk.
167053736 allocation units available on disk.
Internal Info:
00 ad 05 00 b4 93 05 00 f9 af 0a 00 00 00 00 00 ................
f6 01 00 00 b6 09 00 00 00 00 00 00 00 00 00 00 ................
Windows has finished checking your disk.
Please wait while your computer restarts.
Alrighty seems to be cleared!
I would recommend that you follow this tutorial for MemTest86+:
Diagnostic Test
RAM TEST
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums
Note
MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Make a photo of the result and post it.
And how about new hardware, anything that you might have put into the computer before the errors started to happen?
Cheers, Boris :)
Last edited by BorisTheAnimal; 16 Sep 2016 at 17:44.
Also even though chkdsk might have cleared your C drive, I would still recommend that you also run SeaTools:
SeaTools for Windows | Seagate
How to guide:
How to use SeaTools for Windows
Cheers, Boris :)