Ed,
I seem to have the same problem using Windows Vista Ultimate 64 on my HP
Pavilion dv9420us using a WD 250GB "passport" USB external hard drive.
I suspect the problem may not be with Western Digital but with NVIDIA
because your driver file nvstor.sys in the "blue screen of death" you are
getting is similar to the driver file I am using when I get the "blue screen
of death": nvstor64.sys.
The "nv" at the beginning of the driver file name "tips off" the culprit
behind the problem (nv meaning NVIDIA).
I'm going to look further into this and confirm a hypothesis of mine.
"Ed" wrote:
Quote:
> Hi, all. I posed this question to Western Digital's support people, but they
> were of absolutely no assistance, essentially blowing me off and blaming
> Microsoft.
>
> I have a WD MyBook 1TB external hard drive. It's a replacement for a LaCie
> drive that I broke accidentally. Because I broke my LaCie, which held all my
> backups, I need to do a full system backup so I have one on file. (I'm
> running Windows Vista Business SP1 on a Compaq Presario laptop. I've tried
> this both before and after SP1 and have got the same result.)
>
> The weekly file-only backups I have scheduled with Windows Backup work fine.
> It's only the full system backup that gives me problems. Everything goes as
> planned: I select the MyBook as the destination, and Windows starts the
> backup.
>
> Once it gets near the end (I'd say about 90% done according to the status
> bar), I get the blue crash screen. Here's what it says:
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
> Stop: 0X000000D1 (0X00000004, 0X00000002, 0X00000001, 0C807503FF)
> nvstor.sys - Address 807503FF base at 8074C000, DateStamp 458d543d
>
> It doesn't restart after that, it just sticks on the blue screen. I have to
> shut the computer off and then turn it back on to do anything.
>
> Can anyone clue me in on what might be going on?
>
> I thought maybe my driver was out of date, but Windows Update can't find a
> newer one, neither can it when I go into the device's properties. Unless I'm
> missing something there, or it's something other than a driver issue.
>
> Thanks