[DMcCunney]

Originally Posted by Katsunami

Back in the time when you actually had control of your computer...

I still largely do, though blunt instruments are sometimes required.

The other side of that coin is that back then you had to know a lot more about the computer to be able to use it.

I compare computers with automobiles. You can own and drive a car without being a mechanic, or understanding the principles of operation of the four stroke internal combustion engine. We aren't there with computers, though things are better than they used to be. Depending upon what you are trying to do, it can still help to be a mechanic and have some notion of how the system works.

The huge Windows 10 update released at August 31 didn't resolve the disk hang problem I've been having since the anniversary update. Just now I remembered that something like "Intel Rapid Storage Technology" exists; a way to do things such as set up RAID0 or RAID1 on one disk, using multiple partitions instead of multiple drives. It uses a different driver.

By default, Windows 10 uses StorAHCI.sys, released by MS in 2006. (Device manager says so.) I've read that, for several users, the Intel Rapid Storage Technology driver resolves this issue. Even though I don't use the extra's that IRST offers, the driver might indeed solve this problem. I've now installed IRST, and the driver is now StorAHCI.sys, from 4-11-2015, from Intel.

I hope this fixes the problem.

Let us know if it does.

I *NEED* this system, Microsoft. It's a workstation class laptop, that should be rock solid. Rolling updates without (obvious) means to prevent or reverse installation is *NOT* a good idea.

When you have millions of installations, a few will always be problem children, and you drew a short straw.

I have Win10 on four laptops - my SO's older failed laptop she upgraded from Win7, an older travel laptop I upgraded, a Win8.1 laptop I ungraded for a friend, and my SO's new laptop that came with it. The laptops are all rock solid and run fine.

My desktop is odd man out. There were some initial issues that were resolved by turning off hybrid shutdown (which let the machine actually reboot without a power cycle), and turning off Windows write-cache buffer flushing, because I boot from an SSD and that give the machine severe heartburn. For a while, things were stable.

Now it's a case of "New and different Win10 BSODs. Collect the whole set!" and I have been. The biggest culprit is DCP_Protection_Error, which occurs when some process exceeds the hard-coded limit for how long something included under that should take. I've had other issues that are USB related. I dual boot Ubuntu Linux, so I can still get stuff done if Win10 is being recalcitrant. My annoyance is that I don't understand why the problems are occurring. After 30+ years of dealing with this stuff, I generally have an idea of what's wrong and how to fix it, but not this time...
______
Dennis