- Joined
- Aug 10, 2007
- Messages
- 2,143 (0.35/day)
- Location
- Austin TX
Processor | i9 11900k |
---|---|
Motherboard | Maximus XII Apex |
Cooling | Custom Liquid W/ 360x60 Radiator |
Memory | 32Gb Team XTREEM ARGB 3600 b-die |
Video Card(s) | Waterblocked MSI RTX 4070 |
Storage | Intel 900p 480Gb + 4tb Intel 670p |
Display(s) | LG C2 evo 42" |
Case | Geometric Future Model 8 |
Audio Device(s) | HD58X + Sennheiser GSX 1000 |
Power Supply | Corsair RM 750x |
Mouse | Steelseries Aerox 5 wired |
Keyboard | Akko Mod 007b HE |
VR HMD | Samsung Odyssey+ |
Software | Windows 11 |
Maybe it's just taking up memory to run that scan?
no. becuase if you close it right after you start scan disk it will still eat up all of your memory untill there is none left. the only way to regain it is to kill the process and restart it. i've tried it on sevral diffrent hardware configs, all resulting in the same issue