Win 10 continuously corrupted

Kbird said:

Hi sounds similar to my issue about 2 months back , look in device manager for me and tell me the driver Version running on the AHCI/RAID Controller . Do you have a ICH9 or ICH10/10R Chipset onboard?

KB

Unless I'm missing something, I don't have a AHCI/RAID Controller. However, I do have a Standard SATA AHCI Controller. That driver version for storshci.sys is 10.0.10586.0 (th2_release 151029-1700).

I don't know if I have a ICH9 or ICH10/10R Chipset onboard.

Hi DS , you do , it is the same thing , the reason you don't see it is because you are using the M$ AHCI Driver , not the Intel Driver for your Motherboard. I can not tell from the Asus Site what the Motherboard is for your Tower (CM6870) but it it does use the Intel Drivers , same as my MB does, they are listed under SATA in the Downloads.

Are you on Bios 708?

CM6870 | Tower PCs | ASUS USA


In Device Manager if you goto Properties>Details >Hardware IDs ( see mine below) that Code should help identify the SATA Chip. I am using Raid so it is shown under Storage Controllers, so it may look slightly different, but same chip, just a different driver (Raid vs AHCI) .

The DEV_2822 no# is the identifier which maybe different on your system as it is using AHCI, not Raid. You can copy and paste the HW ID into Google and it should Identify the Chip, see below. Post the info here , and I'll check it too for you.





Intel(R) ICH8R/ICH9R/ICH10R/DO/PCH SATA RAID Controller Driver Download for 2K,XP,2K3,VISTA,WIN7/32bits - Gigabyte Technology Co., Ltd. EG45M-UD2H


If it is indeed an Intel ICH9/10 Chip , usually Win10 tries to load an Intel 13 Series Driver which is not 100% compatible with the ICH9/10 Chips . ( I am guessing your computer was using the M$ Driver before the Win10 Update so it is using it in Win10 as well , or trying to) It took me a while to figure out why Win10 kept corrupting itself but eventually I tracked it down to the Controller , and did a bit more research and found the issues with the ICH9/10 on other Sites . In particular on WinRaid, where there is a Tutorial on how to Use Nlite to remove the 13 series driver from Windows 10 ISO and inject the stable fast 11.2.1006 Driver into a Win10 1SO. since doing that , and doing a Reinstall, I have had no issues with Win10 ........after turning Driver Updates off in windows Update too.

WinRaid Tut.

[Guide] Integration of drivers into a Win7/8/10 image


***Note : In your case since Win10 didnt install a ver. 13 Driver I wonder if you can just install the Intel 11.2.1006
without the Boot issues normally associated with trying to downgrade Win10 directly with a driver install.
Might be best to ask at WinRaid on the Integration thread above about that.

Kbird said:

In Device Manager if you goto Properties>Details >Hardware IDs ( see mine below) that Code should help identify the SATA Chip. I am using Raid so it is shown under Storage Controllers, so it may look slightly different, but same chip, just a different driver (Raid vs AHCI) .

The DEV_2822 no# is the identifier which maybe different on your system as it is using AHCI, not Raid. You can copy and paste the HW ID into Google and it should Identify the Chip, see below. Post the info here , and I'll check it too for you.

My hardware driver is pci ven_8086&dev_1e02&subsys_84ca1043&rev_04

Google tells me that I have an Intel 7 Series C216 Chipset.

Yes. I have BIOS version 0708.

I should also add...
This computer is about 2 years old. It ran Win 8 for a year without problems. After the update to Win 10, it also ran for a year without problems. It only started to act up a couple of months ago. Other than the normal Win updates, there were no significant hardware or software changes prior to my problems.

dsscottage said:

My secondary drive is a standard HDD that originally came with the computer. I could use that as a boot drive but, as I recall, I went through technical hell installing the SDD and demoting the HDD to a secondary drive (about 2 years ago). I don't want to go through that again.

As they say, "If it looks like a duck, and quacks like a duck......".

All indications are that I have an SSD problem but I wanted to prove it before I bought a new one and I haven't been able to do that. I've been through the "failure/reinstall Windows" loop so many times that I think that I'll just bite the bullet and buy a new SSD and see what happens.

I'll post my results.

As I said, "If it looks like a duck and quacks like a duck...."

I bought a new SSD and replaced the old one.

This seems to have resolved the problem. I'll keep my fingers crossed because it sometimes took a little over a week for my old problem to appear.

I found it disappointing that the OCZ monitoring utility always told me that the SSD was healthy yet replacing it seems to have resolved the issue.