Blender 2.83 runs VERY SLOW: constantly accesses HDD even though it's installed on SSD I have Blender 2.83 installed on my main C: drive, which is a SSD (Samsung 970 EVO Plus). I just installed 2.83 last week. I started with Blender last Sep with version 2.80. I installed 2.80 on my D: drive, which is an old-school 1 TB HDD.
I've iterated through 2.81 and 2.82, both of which were installed to my C: drive (SSD). I have 32 GB of RAM and a Nvidia RTX 2080 GPU.
My problem is that, even though 2.83 is installed to my (supposedly super-fast) SSD, Blender run RIDICULOUSLY SLOW. A single key press often causes the HDD D: drive to whir into action for five to ten minutes. During that time, Blender is unresponsive - completely locked up.
At first, I uninstalled the previous versions of Blender by just deleting the Blender folders out (like the online guides and forums say to do). Then, I used Revo Uninstaller to hopefully clean up any registry entries from the previous versions that refer the current version back to the D: drive. But that didn't help.
What am I missing? Why is Blender constantly accessing my D: drive even though 2.83 is installed to a very fast (and not close to full) SSD? It makes Blender very painful to use. I have to pull up a book on my Kindle and read during the very frequent and very long periods when Blender is accessing the D: drive. The proportion of time I actually spend getting anything done on Blender compared to the time it's locked up spinning the HDD is very, very low.
What gives?
This is how I fixed the problem, though Blender does still run fairly slow on this particular file since it is very large. However, I had corrupted Windows files. I didn't know that until my Task Manager started acting oddly.
This is what I did to fix:
Using the CMD application in Windows 10, as an administrator, I ran the following command: &quot;sfc /scannow&quot;. That scan indicated I had some corrupted files.
Them, from CMD as an administrator, I ran &quot;DISM.exe /Online /Cleanup-image /Scanhealth&quot;. This let me know the faults were repairable.
3). Then, from CMD as an administrator, I ran &quot;DISM.exe /Online /Cleanup-image /Restorehealth&quot;. This fixed the faults.
After the above steps, my D: drive has not been being accessed at all by Windows. It's right at 0% all the time now. Earlier, the norm was 90% or higher.