New
#41
That's very interesting. I did notice that I got a "found new hardware" notification after I disabled my intel ethernet nic, and I thought the name of the controller changed at the same time. Can I roll the driver back?
That's very interesting. I did notice that I got a "found new hardware" notification after I disabled my intel ethernet nic, and I thought the name of the controller changed at the same time. Can I roll the driver back?
iaStor comes from IRST, the intel rapid storage raid program. I use it, but install it then go to services.msc and disable the IRST, but still have the iaStor driver that way without the raid program running.
I'm not sure what I need to install, because I already have IRST and iaStor on my system. I disabled IRST in services.msc, and no joy.
What will happen if I simply uninstall the Intel controller?
Edit: I searched for iaStor.sys in my Windows System32 folder and found both iaStor.sys and something called iaStorV.sys, the latter dated 2010 and the former 2011.
At this point, it probably time to make a backup, remove everything from the machine short of enough RAM to boot, the CPU, a video card, and the SSD, and start testing to see what happens after installing the OS (and take good notes). It could still be a hardware issue, but as to what, it'd be hard to say.
Well, I'm finally starting to make some headway.
One anomaly that continued to bother me was why Intel's IRST utility identified my WD storage drive as being the "system drive" while the SSD was clearly the system drive. On a hunch, I unplugged both SATA cables from my board, and then plugged the SSD into the SATA 6GB/s port formerly occupied by the WD. I hit the start button, and BAM, the SSD booted into Windows in nothing flat. I opened the IRST utility, and what do you know, the SSD was correctly identified as the system drive.
Adding the WD drive to the other 6GB/s port, unfortunately, slowed my boot back to a crawl. Unplugged it again, and the SSD was off to the races.
I'm wondering whether placing my temporary internet files and Google cache file on the storage drive (via a junction) is causing the OS to see the WD as a second system drive and screwing up my boot. Very weird.
Edit: Moved the page file and temporary internet file folder back to the SSD and uninstalled Google Earth. No change. Disconnected the WD and move the SSD back to port 0, blazingly fast boot. Plugged the WD into port 1, slow boot again, but at least the SSD is detected by IRST as the system drive again.
Why would the simple addition of a HDD storage drive cause boot slowdowns? I don't get it.
Last edited by Raillex; 24 Oct 2011 at 00:22.