Author Topic: Windows Update optional driver causing BSOD.  (Read 401 times)

Offline Ghastly

  • Silver Member
  • ****
  • Posts: 1756
Windows Update optional driver causing BSOD.
« on: August 19, 2010, 11:19:29 AM »
Be very very careful installing the optional PROMISE AHCI Raid Driver that Windows Update started pushing out to Windows 7 64 bit yesterday or the day before on an ASUS P5K-E based system, and perhaps other systems that might use a similar controller (JMicron controller in this instance).  Doing so on one of our work system causes the system to BSOD on the next boot.

Fortunately, we don't boot from that controller, so we were able to use Windows 7 recovery options for "easy" (if a bit "scary") recovery.  I have to say that Windows 7 is MUCH better than XP in that regard, although what would have happened had that controller been connected to the boot drive, I can't say.

Anyway, thought I'd mention it here, as I know that the P5K-E is fairly popular.

<S>

P.S. In case it matters, that controller is set to IDE mode in BIOS on this machine, and is attached to a DVD drive only - no disk drives.

« Last Edit: August 19, 2010, 11:21:50 AM by Ghastly »
"Curse your sudden (but inevitable!) betrayal!"
Grue

Offline TilDeath

  • Silver Member
  • ****
  • Posts: 1199
      • TD Computer Systems
Re: Windows Update optional driver causing BSOD.
« Reply #1 on: August 19, 2010, 12:45:09 PM »
You should never use the MS Drivers for your hardware.  You should not allow auto-update, update manually and never choose drivers.  If you want to update a driver, go to the makers website and DL it from there.

My .02

TD

Offline Ghastly

  • Silver Member
  • ****
  • Posts: 1756
Re: Windows Update optional driver causing BSOD.
« Reply #2 on: August 19, 2010, 01:18:46 PM »
Which is what I do on my own system - but at work I use a tool that forces every non-hidden update to be installed automatically nightly as part of nightly processing, otherwise I either end up spending hours of time each month manually updating Windows systems, or accept the fact that fully half of them will be hit or miss as to patch state, which is worse.

Easier to deal with the one or two exceptions than give each system the same TLC I can my own.

But just in case others out there get bit the same way, I thought I'd post.

<S>
"Curse your sudden (but inevitable!) betrayal!"
Grue