I recently built a new PC, BOTH HDDs that newegg sent me did not work. One wouldn't power up at all, the other wouldn't allow me to partition it or put the OS on it - So instead, I just used the HDD out of my old PC, which already had a few issues.
In the old PC, when the PC started, it would be at 100% disk in task manager for 5 - 10 minutes, then go to normal (3 - 10%). I also had a lot of BSODs on the old PC, I couldn't leave it idle for longer than 30 mins or it'd BSOD (even with no programs running).
When I put it in this PC, I did a few self-tests... I let it sit idle for about 24 hours, no blue screen. I'm on day 4 of having this PC now, and have noticed a lot of issues.
MOST of the time, the disk sits at 100% in task manager. However, sometimes it'll drop to 3%, then quickly make it's way back up to 100%. Sometimes, but rarely, it'll even drop to 0% for a couple seconds before shooting back up to 100%. But most commonly, if it's not sitting at 100%, it's going back and forth between 100% and 80%.
But there's something that's making it hard for me to figure out if it's having an issue with something in my build or not. At once I was building a new PC and planned to have 100% new items in it, I quit monitoring the disk % in task manager. So I'm not sure if the old PC was also staying at 100% before I switched the drives.
I've tried a number of things. I found elsewhere on these forums to disable windows search and something else (not the only place i saw to try disabling them with cmd, so you guys probably know what I'm talking about lol). Disabling the search made it immediately change to 4% Disk - But it also immediately started working it's way back up to 100%. Same result for disabling the other item.
I also saw to run malwarebytes, which did find a few things and fixed them, but still no change - 100% Disk.
I decided to do a chkdsk with tuneup utilities 2014 while I was sleeping last night. It got to 12% long before I went to sleep, and was still 12% when I checked it today (over 8 hours) - So I took the risk and shut the PC down.
PC started up normally. I used CMD to cancel the chkdsk so it wouldn't continue attempting to do it on start up.
I ran a program that came on my mobo's disc (just a free trial) called Advanced SystemCare 9 Pro. It's very similar to tuneup utilities, but so far seems to do a better job at things. It also has a disk doctor, I ran that, and it found errors. It wanted to restart my PC to fix the errors. I restarted, it ran a chkdsk. When PC came back on, I ran the disk doctor again... It found NEW errors. So I did chkdsk again. I've done it about 5 times now, every time disk doctor finds new errors.
However, on the 4th time, it caused a blue screen at "scanning and repairing disk c: 100%". The BSOD said "Critical_Service_Failed" and I had to run start up repair. Start up repair said it couldn't automatically fix the problem, and restarted... However, after restarting, it was back at scanning/repairing 100%. Restarted itself, coming up with scanning/repairing 100% yet again, and then after a minute or 2, started windows normally.
i currently have disk doctor open with the errors again. I've noticed some similarities in the details of the scans. Stage 1 ALWAYS finds "0 bad file records processed" and Stage 2 ALWAYS finds errors. They're always different errors, but they are ALWAYS "in index $I30"
The time it caused the blue screen, I'm pretty sure it had chkdsk in the list of errors. It was something like
Index entry CHKDSK-(long line of numbers).bin in index $I30 of file (not sure on the number) is incorrect.
Here is the current list:
C:\ Volume Label: OS, File System: NTFS
Volume label is OS.
Stage 1: Examining basic file system structure ...
1337344 file records processed.
File verification completed.
17870 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
Index entry PK811A~1.BIN in index $I30 of file 2076 is incorrect.
Index entry pkg160219000000007f.bin in index $I30 of file 2076 is incorrect.
Index entry data.dat in index $I30 of file 1163412 is incorrect.
1516264 index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
However, I would like to point out, now that I've done those disk doctor checks, it stays lower A LOT longer and drops to low % Disk A LOT more often. Just a moment ago it was going from 0% to 3% Disk for roughly 5 minutes or so, but is now back to 100%.
Should I continue restarting and fixing the errors that disk doctor is finding? Or are those types of errors just something that'll continue to pop up everytime, no matter how many times I do dskchk?
I also plan to do a scan with avast, was going to do it first thing today, but after tuneup's disk doctor chkdsk froze at 12%, I've been doing scans with SystemCare 9's disk doctor all day.
In the old PC, when the PC started, it would be at 100% disk in task manager for 5 - 10 minutes, then go to normal (3 - 10%). I also had a lot of BSODs on the old PC, I couldn't leave it idle for longer than 30 mins or it'd BSOD (even with no programs running).
When I put it in this PC, I did a few self-tests... I let it sit idle for about 24 hours, no blue screen. I'm on day 4 of having this PC now, and have noticed a lot of issues.
MOST of the time, the disk sits at 100% in task manager. However, sometimes it'll drop to 3%, then quickly make it's way back up to 100%. Sometimes, but rarely, it'll even drop to 0% for a couple seconds before shooting back up to 100%. But most commonly, if it's not sitting at 100%, it's going back and forth between 100% and 80%.
But there's something that's making it hard for me to figure out if it's having an issue with something in my build or not. At once I was building a new PC and planned to have 100% new items in it, I quit monitoring the disk % in task manager. So I'm not sure if the old PC was also staying at 100% before I switched the drives.
I've tried a number of things. I found elsewhere on these forums to disable windows search and something else (not the only place i saw to try disabling them with cmd, so you guys probably know what I'm talking about lol). Disabling the search made it immediately change to 4% Disk - But it also immediately started working it's way back up to 100%. Same result for disabling the other item.
I also saw to run malwarebytes, which did find a few things and fixed them, but still no change - 100% Disk.
I decided to do a chkdsk with tuneup utilities 2014 while I was sleeping last night. It got to 12% long before I went to sleep, and was still 12% when I checked it today (over 8 hours) - So I took the risk and shut the PC down.
PC started up normally. I used CMD to cancel the chkdsk so it wouldn't continue attempting to do it on start up.
I ran a program that came on my mobo's disc (just a free trial) called Advanced SystemCare 9 Pro. It's very similar to tuneup utilities, but so far seems to do a better job at things. It also has a disk doctor, I ran that, and it found errors. It wanted to restart my PC to fix the errors. I restarted, it ran a chkdsk. When PC came back on, I ran the disk doctor again... It found NEW errors. So I did chkdsk again. I've done it about 5 times now, every time disk doctor finds new errors.
However, on the 4th time, it caused a blue screen at "scanning and repairing disk c: 100%". The BSOD said "Critical_Service_Failed" and I had to run start up repair. Start up repair said it couldn't automatically fix the problem, and restarted... However, after restarting, it was back at scanning/repairing 100%. Restarted itself, coming up with scanning/repairing 100% yet again, and then after a minute or 2, started windows normally.
i currently have disk doctor open with the errors again. I've noticed some similarities in the details of the scans. Stage 1 ALWAYS finds "0 bad file records processed" and Stage 2 ALWAYS finds errors. They're always different errors, but they are ALWAYS "in index $I30"
The time it caused the blue screen, I'm pretty sure it had chkdsk in the list of errors. It was something like
Index entry CHKDSK-(long line of numbers).bin in index $I30 of file (not sure on the number) is incorrect.
Here is the current list:
C:\ Volume Label: OS, File System: NTFS
Volume label is OS.
Stage 1: Examining basic file system structure ...
1337344 file records processed.
File verification completed.
17870 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
Index entry PK811A~1.BIN in index $I30 of file 2076 is incorrect.
Index entry pkg160219000000007f.bin in index $I30 of file 2076 is incorrect.
Index entry data.dat in index $I30 of file 1163412 is incorrect.
1516264 index entries processed.
Index verification completed.
Errors found. CHKDSK cannot continue in read-only mode.
However, I would like to point out, now that I've done those disk doctor checks, it stays lower A LOT longer and drops to low % Disk A LOT more often. Just a moment ago it was going from 0% to 3% Disk for roughly 5 minutes or so, but is now back to 100%.
Should I continue restarting and fixing the errors that disk doctor is finding? Or are those types of errors just something that'll continue to pop up everytime, no matter how many times I do dskchk?
I also plan to do a scan with avast, was going to do it first thing today, but after tuneup's disk doctor chkdsk froze at 12%, I've been doing scans with SystemCare 9's disk doctor all day.