View Single Post
Old 09-15-2017, 06:14 PM   #28
Katsunami
Grand Sorcerer
Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.Katsunami ought to be getting tired of karma fortunes by now.
 
Katsunami's Avatar
 
Posts: 6,111
Karma: 34000001
Join Date: Mar 2008
Device: KPW1, KA1
Quote:
Originally Posted by Chris_Snow View Post
I have realised the issues all stem from a "write". That is, saving metadata, or updating an exising column or cell. I'm not sure what software I have that would effect that, or how I'm going to track it down.
At some point in the beginning of the year, Windows 10 suddenly started to be very slow on both my desktop and laptop, even freezing the laptop occasionally. After scouring the internet for hours, I found the cause to this problem: Microsoft seems to have changed something in one of their default hard drive controller drivers with regard to Intel-based boards. That made some Skylake Intel-based systems VERY slow while writing (my desktop), and could sometimes freeze a computer entirely (my laptop) by hanging the hard drive (busy 100% all the time without actually doing anything, clogging up the busses on the mainboard).

This appears to be a problem between the BIOS/UEFI and the hard drive controller drivers.

The solution was to install the Intel Rapid Storage Technology (RST) drivers for both my laptop and desktop. They are normally needed only if you want to set up some sort of special RAID-like hard drive solution. The driver in the RST package replaces the Microsoft driver, and that fixed the entire problem.

I don't know if Microsoft fixed this problem since then, but as the intallation of the RST package solved it, and did not create any new problems, I've left it as is.

What mainboard do you have? If it's Intel-based, it might be worth it to try this.

Note: back up your data before you start messing with drivers. Installing the wrong HDD-drivers (wrong RST drivers for your mainboard) could render your system unbootable.

Last edited by Katsunami; 09-15-2017 at 07:13 PM.
Katsunami is offline   Reply With Quote