• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Question chkdsk found corrupt files, windows doesn't scan on boot, 100% disk usage in games

blacking

Distinguished
Dec 18, 2012
69
1
18,545
Hi guys,

I'm on an adventure for weeks now which is fixing a problem in my computer which is getting 100% disk usage sometimes when playing games,

In a nutshell, I have two drives, an SSD and a HDD and most times with most games, when I enter them I get 100% disk usage, being only at the drive they're installed or in both, it's mostly random as it's not always the drive where the game is installed but it makes the computer to slow as hell and forces me to terminate the task in the task manager, sometimes it stops when I tab out of the game (most of the times) and sometimes it just persists

I've created a question a few weeks ago on the forums about the same subject where I was having such problems on COD:Warzone, PUBG, CS:GO (not always) and I thought I fixed it at the time by updating my BIOS which, in the short term, fixed it, I even reinstalled Windows and everything.

Now I'm getting the same problem, I uninstalled Avast and installed malwarebytes, did a full system scan which took 4 hours and detected 5 malware files which I removed, nothing changed, still.

I did a scan on the D: drive (the HDD) and everything came out fine and I did a scan on the SSD and this was the result:

Code:
C:\Windows\system32>chkdsk c: /r /scan /perf
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
    Found corrupt basic file structure for "\$Extend\$Deleted\00430000000182A35B6B3F43 <0x43,0x182a3>"
was not able to send command for self-healing due to lack of memory.

C:\Windows\system32>chkdsk c: /r /scan /perf
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
    Found corrupt basic file structure for "\$Extend\$Deleted\00430000000182A35B6B3F43 <0x43,0x182a3>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\$Extend\$Deleted\014200000002791B5FD18920 <0x142,0x2791b>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\ProgramData\Microsoft\Windows Defender\Scans\History\Results\Resource\{F4F80DDA-ECA0-44AE-BD33-0500554838F6} <0x30,0x2b627>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Microsoft\Edge\User Data\Default\Code Cache\js\feaa149e6d0b1373_0 <0x39,0x2be03>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\Downloads\Super Mario Bros 1985 Full Walkthrough NES Gameplay Nostalgia.mp4 <0x1b,0x4a6ef>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\ProgramData\NVIDIA\MessageBus_4688_0x1B6E3296EB0.log <0x14,0x67b9e>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\ProgramData\Microsoft\Windows Defender\Scans\History\Results\Resource\{54599C8C-68DB-4A1B-9411-C1C2DBA9559A} <0x2c,0x67ddb>"
        ... queued for offline repair.
    File "\ProgramData\USOShared\Logs\System\UpdateSessionOrchestration.3e9f3e97-bef9-4bc8-b8a5-347763c42b45.1.etl <0x1b,0x1701d>" and file "\$Extend\$Deleted\00430000000182A35B6B3F43 <0x43,0x182a3>" both own logical clusters [0x11e744, 0x11e746)
        ... queued for offline repair.
    File "\$Extend\$Deleted\0010000000018282268F57D9 <0x10,0x18282>" and file "\ProgramData\Microsoft\Windows Defender\Scans\History\Results\Resource\{F4F80DDA-ECA0-44AE-BD33-0500554838F6} <0x30,0x2b627>" both own logical cluster 0x11d41c
        ... queued for offline repair.
    File "\$Extend\$Deleted\0010000000018282268F57D9 <0x10,0x18282>" and file "\ProgramData\Microsoft\Windows Defender\Scans\History\Results\Resource\{54599C8C-68DB-4A1B-9411-C1C2DBA9559A} <0x2c,0x67ddb>" both own logical cluster 0x11c790
        ... queued for offline repair.
    File "\$Extend\$Deleted\00320000000183BF4C67C7BC <0x32,0x183bf>" and file "\Users\antab\AppData\Local\Microsoft\Edge\User Data\Default\Code Cache\js\feaa149e6d0b1373_0 <0x39,0x2be03>" both own logical cluster 0x11e1cd
        ... queued for offline repair.
    File "\$Extend\$Deleted\00320000000183BF4C67C7BC <0x32,0x183bf>" and file "\Users\antab\Downloads\Super Mario Bros 1985 Full Walkthrough NES Gameplay Nostalgia.mp4 <0x1b,0x4a6ef>" both own logical clusters [0x11eb80, 0x11eb83)
        ... queued for offline repair.
    File "\Users\antab\AppData\Local\Origin\Logs\IGOProxy_DX10_1032_Log.txt <0x40,0x28cde>" and file "\ProgramData\NVIDIA\MessageBus_4688_0x1B6E3296EB0.log <0x14,0x67b9e>" both own logical cluster 0x5d35a
        ... queued for offline repair.
    File "\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\wpndatabase.db-wal <0x2,0x16f24>" and file "\$Extend\$Deleted\014200000002791B5FD18920 <0x142,0x2791b>" both own logical clusters [0x11f4e5, 0x11f4e7)
        ... queued for offline repair.
  550656 file records processed.
File verification completed.
 Phase duration (File record verification): 5.31 seconds.
  9529 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.72 milliseconds.

Stage 2: Examining file name linkage ...
  62598 reparse records processed.
    Found an unneeded link ($FILE_NAME: "7504eb8c89d348e7_0") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "7504EB~1") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "79D1E1~1") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "7B2941~1") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "96DDF8~1") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "B193CC~1") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "e3cb45fa4fcd7101_0") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "E3CB45~1") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
    Found an unneeded link ($FILE_NAME: "F72EC3~1") in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
        ... queued for offline repair.
  763846 index entries processed.
Index verification completed.
 Phase duration (Index verification): 14.59 seconds.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\1d7cbfa8-76eb-466d-811f-b6e3786e29b9\index-dir\THE-RE~1 <0x10,0xb2a3>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\index-dir\THE-RE~1 <0x71,0x16acc>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\0782B8~1 <0x26,0x2a3bb>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\79D1E1~1 <0x2e,0x665f6>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\3FF42B~1 <0x64,0x66628>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\B193CC~1 <0x16,0x666e7>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\7B2941~1 <0x29,0x666ec>"
        ... queued for offline repair.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\F72EC3~1 <0x2f,0x66961>"
        ... queued for offline repair.
  19 unindexed files scanned.
    Found corrupt basic file structure for "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\96DDF8~1 <0xe,0x66b1a>"
        ... queued for offline repair.
 Phase duration (Orphan reconnection): 0.00 milliseconds.
  2 unindexed files recovered to lost and found.
    Found 4 missing entries (\$Extend\$Deleted\0010000000018282268F57D9 <0x10,0x18282>, ...) in index "$I30" of directory "\$Extend\$Deleted <0x1,0x1d>"
was not able to send command for self-healing due to lack of memory.
    Found lost file "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\1d7cbfa8-76eb-466d-811f-b6e3786e29b9\index-dir\the-real-index <0x10,0xb2a3>"; requesting reconnection to index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\1d7cbfa8-76eb-466d-811f-b6e3786e29b9\index-dir <0x4,0x64997>"
was not able to send command for self-healing due to lack of memory.
    Found 11 missing entries (\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\7504eb8c89d348e7_0 <0xe,0xb2a0>, ...) in index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5 <0x4,0x649a6>"
was not able to send command for self-healing due to lack of memory.
    Found 2 lost files (...\d74a26020eab7fd172211de4c0c040d8ee102057.cachedmsg <0xf,0xb381>, ...); requesting reconnection to index "$I30" of directory "\??\C:\found.002"
was not able to send command for self-healing due to lack of memory.
    Found lost file "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\index-dir\the-real-index <0x71,0x16acc>"; requesting reconnection to index "$I30" of directory "\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\8577f624-ffe6-410a-9874-9c2462d248a5\index-dir <0xe,0x6498d>"
was not able to send command for self-healing due to lack of memory.
    Found 9 files (\Users\antab\AppData\Local\Origin\Origin\QtWebEngine\Default\Service Worker\CacheStorage\c588a44589f587eae21a269f7faf460318ef682f\1d7cbfa8-76eb-466d-811f-b6e3786e29b9\index-dir\the-real-index <0x10,0xb2a3>, ...) with bad links
        ... queued for offline repair.
 Phase duration (Orphan recovery to lost and found): 0.00 milliseconds.
  62598 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 135.45 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 35.95 milliseconds.
  106603 data files processed.
 Phase duration (Data attribute verification): 1.37 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  550640 files processed.
File data verification completed.
 Phase duration (User file recovery): 17.07 minutes.

Stage 5: Looking for bad, free clusters ...
  29944261 free clusters processed.
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.
Windows has found problems that must be fixed offline.
Please run "chkdsk /spotfix" to fix the issues.

 487756770 KB total disk space.
 367086200 KB in 429999 files.
    258268 KB in 106599 indexes.
         0 KB in bad sectors.
    635258 KB in use by the system.
     65536 KB occupied by the log file.
 119777044 KB available on disk.

      4096 bytes in each allocation unit.
 121939192 total allocation units on disk.
  29944261 allocation units available on disk.
Total duration: 17.43 minutes (1046382 ms).

Note that this was the 5th scan that I did, the previous one had a few problems that were able to be fixed "online" through the CMD (?) but the problem is that the system informs me that I need to reboot the computer for it to repair the drive, I restart my computer, the computer gives me the splash screen from my motherboard along with a bottom message asking me to press any button if I don't want there to be a disk scanning and repairing, I don't press anything and it prompts a message saying "Scanning and repairing drive" which only is printed for about 6 seconds because nothing is scanned (or is not displayed) and the computer takes me right away to the login screen. I login, re-do the scan and get the same results on chkdsk and message asking me to restart the computer to fix the drive..

I'm not even sure if this is related to me getting these 100% disk usage problems when in some games, I feel lost as hell and I'm feeling desperate to fixing this, I've updated all drivers, reinstalled Windows, updated the BIOS about a month ago, uninstalled Avast, what can I do more?

Thanks in advance!
 
Sounds like your SSD may be slowly dying...I would replace it asap. The 100% disk usage is likely Windows trying to access data on it, failing and retrying constantly. Also if the SSD is over full it might give you these same data access problems.
 
Sounds like your SSD may be slowly dying...I would replace it asap. The 100% disk usage is likely Windows trying to access data on it, failing and retrying constantly.
The think is that if the game is installed in the C: drive it's the HDD who is pushing the usage to 100% while the SSD is fine, I downloaded Samsung Magician (I have the Samsung 860 Evo) and did all tests and nothing came out negative,

But regardless of that, how do I force windows to fix the problems it found if it doesn't do that when booting?
 
have you tried running chkdsk in windows recovery?

if this is win 10
go to settings/update & security/recovery
under advanced startup, click restart now button
this restarts PC in a blue menu
choose troubleshoot
choose advanced
choose command prompt
run chkdsk c: /f and press enter

not sure if it will ask for restart.

what brand is ssd?
 
have you tried running chkdsk in windows recovery?

if this is win 10
go to settings/update & security/recovery
under advanced startup, click restart now button
this restarts PC in a blue menu
choose troubleshoot
choose advanced
choose command prompt
run chkdsk c: /f and press enter

not sure if it will ask for restart.

what brand is ssd?
It is Windows 10 and it's the Samsung 860 Evo 500GB,

Will try that in recovery mode to see it fixes the corrupt files it found and will come back to you in a bit!
 
the problem is that the system informs me that I need to reboot the computer for it to repair the drive, I restart my computer, the computer gives me the splash screen from my motherboard along with a bottom message asking me to press any button if I don't want there to be a disk scanning and repairing, I don't press anything and it prompts a message saying "Scanning and repairing drive" which only is printed for about 6 seconds because nothing is scanned (or is not displayed) and the computer takes me right away to the login screen.
Why are you running chkdsk with those switches? Do you understand, what they do?
chkdsk c: /r /scan /perf

Use instead
chkdsk c: /f
BTW - what are model names of drives used?
 
The think is that if the game is installed in the C: drive it's the HDD who is pushing the usage to 100% while the SSD is fine, I downloaded Samsung Magician (I have the Samsung 860 Evo) and did all tests and nothing came out negative,

But regardless of that, how do I force windows to fix the problems it found if it doesn't do that when booting?

You stated above that you did a clean Windows install. Windows keeps throwing a disk issue at you...that would indicate a hardware issue unless you suspect a specific app or game that you re-installed is causing the issue.

Have you tried running Windows without reinstalling your apps and games for a few hours to see if the problem happens ?

What is Task Manager showing as the culprit for the high disk usage ?
 
You stated above that you did a clean Windows install. Windows keeps throwing a disk issue at you...that would indicate a hardware issue unless you suspect a specific app or game that you re-installed is causing the issue.

Have you tried running Windows without reinstalling your apps and games for a few hours to see if the problem happens ?

What is Task Manager showing as the culprit for the high disk usage ?
Mostly "System" but transfer speeds are at 0%, almost, here's a screenshot:

aaaa.png


It shows 50% disk usage because in this case only the SSD is at 100%
 
Why are you running chkdsk with those switches? Do you understand, what they do?
chkdsk c: /r /scan /perf

Use instead
chkdsk c: /f
BTW - what are model names of drives used?
What do you mean by switches?

Also tried the second option but it didn't fix anything offline on boot time,

The models of the two drives I use are Samsung 860 Evo (SSD) and Seagate Barracude 2TB 7200RPM (ST2000DM008).
 
SMR drive.
Inconsistent performance and high HDD activity is common thing with these.
Would it affect my SSD tho? That doesn't make much sense, and if it did make sense, that would imply that if I would unplug my HDD and try to do any of the tasks I mentioned (playing some games) I wouldn't have a single problem, right?

I've just resetted Windows, keeping my personal files, and I'm downloading the games again, I'll try tomorrow again to see if it's still happening (which it probably will stil happen)
 
You could start Solitaire for the first time and a hard drive would show 100% disk usage, for at least a moment.

I am also puzzled as to why you know the hard drive is pushing hard when the SSD is being accessed? The performance tab?

One more question- was Windows ever installed on the hard drive?
 
You could start Solitaire for the first time and a hard drive would show 100% disk usage, for at least a moment.

I am also puzzled as to why you know the hard drive is pushing hard when the SSD is being accessed? The performance tab?

One more question- was Windows ever installed on the hard drive?
Yeah but a peak of a fifth of a second is different than being STUCK at 100% ahah leaving the computer unusable,

No, I've built this PC a year ago and it was always installed on the SSD, also why I don't want to think the SSD drive is defective, because it's only a one year old drive and because I honestly think this is due to Windows itself and an update they made a few months ago, tbh
 
When you installed Windows, was the HDD still hooked up? Or did you unplug the data cable and just install windows to the SSD?

Windows 10 is greedy, it wants everything to be under its control at all times. If you install Win10 with any other storage hooked up, it'll tie those into its search/library engine, meaning anything run will include both drives in the process. Windows will treat it as a single drive with 2 partitions, not seperate drives.

That gets ugly in a hurry, makes an already slow HDD slower, and runs it at higher than necessary usage.
 
When you installed Windows, was the HDD still hooked up? Or did you unplug the data cable and just install windows to the SSD?

Windows 10 is greedy, it wants everything to be under its control at all times. If you install Win10 with any other storage hooked up, it'll tie those into its search/library engine, meaning anything run will include both drives in the process. Windows will treat it as a single drive with 2 partitions, not seperate drives.

That gets ugly in a hurry, makes an already slow HDD slower, and runs it at higher than necessary usage.
I didn't unplug the HDD as I didn't know that could affect anything in any way, I've resetted the computer last night, with the option of keeping personal files and haven't installed programs that could, in theory, interfere like Corsair ICUE and drivers for components RGBs and such, if that doesn't fix it, I'll reinstall Windows entirely and unplug the HDD aswell
 
Well, if Windows and the game are on the SSD, best way to tell would be to disconnect the hard drive and see if performance returns to normal.

I am also not sure if the SSD actually has issues, but at least it's still under warranty.
Will come back to you later as I'm on my lunch break (Europe timezone) but will do that at the end of the day and report back!
 
Two recovery partitions, wonder which one win 10 is using.

This is what you need to do. Open a Command Prompt (Admin), and I think Powershell (Admin) will work too. Run this command:

reagentc /info

The result will tell you which recovery partition is active. Make sure to note the results! Then run:
diskpart
select disk 0
list part

That should tell you which real partition numbers are assigned to the recovery partitions.
https://www.tenforums.com/drivers-hardware/96389-why-two-recovery-partitions.html
recovery partition is used for system restore. if the one on disk 0 is active, it probably explains any hdd activity while ssd is actioned.

note, since you have 2 drives you will need to do this stage for both disk 0 & 1
diskpart
select disk 0
list part
just change 0 to 1
 
Two recovery partitions, wonder which one win 10 is using.


https://www.tenforums.com/drivers-hardware/96389-why-two-recovery-partitions.html
recovery partition is used for system restore. if the one on disk 0 is active, it probably explains any hdd activity while ssd is actioned.

note, since you have 2 drives you will need to do this stage for both disk 0 & 1
diskpart
select disk 0
list part
just change 0 to 1
What? I didn't quite get what you meant by "two recovery partitions" but it looks like I do have two, indeed, resetted my Windows since the last post and have been going fine on games but today Star Wars Battlefront II started giving me a 100% disk usage problem again, darn..

But here are the results of what you specified:

Code:
DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list part

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           529 MB  1024 KB
  Partition 2    Reserved            16 MB   629 MB
  Partition 3    Primary           1862 GB   645 MB

DISKPART> select disk 1

Disk 1 is now the selected disk.

DISKPART> list part

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Reserved            15 MB    17 KB
  Partition 2    System             100 MB    16 MB
  Partition 3    Primary            465 GB   116 MB
  Partition 4    Recovery           498 MB   465 GB

(disk 0 is my HDD and disk 1 is my SSD, where my Windows is installed)

Code:
PS C:\WINDOWS\system32> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk1\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: ef69aee4-344e-11eb-9112-e3b8b0daffd7
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

I'm considering buying a an 970 Plus M.2 to see if the problem is related to the SSD being faulty, which I don't think it is, though or else some benchmarks whould accuse something or both drives wouldn't act up sometimes like this..
 
Last edited:
Guys can someone please help me?

I've started having this problem again,

It's been happening playing Ghost Recon: Breakpoint, for example, and the game was installed on the SSD and the disk started acting up a few days after installing the game, getting spikes of 100% disk usage, I decided to move the game to the D: drive (the HDD) and test it out and these are the results of the same problem but on the HDD, I'm totally clueless about this

(meanwhile the SSD is having those weird spikes while playing the game on the HDD)

ghostrecon3.png

ghostrecon4.png