Windows 7: a request to this de device has been cancelled

Ok, today when I turn on my computer in the morning all of a sudden it took ages to boot, when it booted my D: drive was not showing in MY COMPUTER.

Computer wasvery unresponsive, so I checked the Administrative events and I saw like a hundred of this message:

A request to this device has been cancelled.
Device: \Device\RaidPort0
Model: WDC WD1002FAEX-007BA0
Firmware Version:05.0
Serial Number: WD-WMAUR0614125
Port: 1

I had 3 Sata drives in my system, this one (Wester Digital Caviar Black 1000gb) had my sample libraries and it had just like 19gb of free space.

When I disconnected the drive computer booted normaly.
I dismounted the drive and put it on a usb docking station and it was not recognized and computer was slow again..

I see the BIOS and the HDD shows there.. (strange)

I can't believe my HDD died on me cause I just have like 4 months with him..

What are your advices over this issue??



Thanks a lot people

Try burning this iso to a cd/dvd: WD Support / Downloads / SATA & SAS / WD VelociRaptor

Boot from the optical drive and see what WD's diagnostics program has to say about the drive. (WD's diagnostics program is the same for most of their products, so don't worry if the product on the d/l page doesn't match yours.)

If the drive seems to be only marginally healthy you may want to make sure you backup all data from it before running the tests.

By any chance do those errors list NVSTOR64 in the description?

yeah that;s correct

ok thanks man i will try that

yeah but how is a test going to alter my data, isn't a test just a test?

Also, could i do the test while the hdd is in the usb docking station, or should i put it back to its sata port??

Thanks a lot man

Modern HD's have firmware that manages the drive and monitors health and degradation. The WD software will access the info acquired by that firmware. More than likely you'll have to have it connected directly (via SATA or PATA, whichever is appropriate for the drive) rather than a USB adapter.

As far as data damage is concerned I'm really talking about drives that are somewhat close to being "on their last leg". If I'm unsure (which is always the case as it's typically someone else's HD I'm messing with) I always back up first because you never know how many more times you'll be able to reliably access the data if the HD is about to die. Stressing an HD in this condition (including just backing it up) may be one of the last times of being able to access it.

That said, running the tests or whatever checks on a healthy drive should not present a problem. I just seem to get a few laptops to repair from folks who've got kids who are kind of rough with the hardware.

I note that you've mentioned checking the drive status in the BIOS. Some BIOS's can read the HD's diagnostics data directly. Might want to try that.

Interested too in TVeblen's post mentioning NVSTOR64 in your error messages. Worth looking in to, especially if you've updated drivers recently.

Thanks a lot man. I'll try with the WD soft tomorrow, so in order to backup my data i need. to have acces to it. I will be able to do that via the software. right? Thanks talk tomorrow

You'll have to use something else if you can't use your boot OS to access it. You can run a version of XP to do it. You'll need to burn to another disk and boot from it: Download Hiren (scroll down towards the bottom of the page to find the link to d/l version 15.1).

That NVSTOR32 error means that the error originates from the nVidia chipset.

Do a google search using the term NVSTOR32 and your exact error message.
"A request to this device has been cancelled. Device: \Device\RaidPort0"

You will see that this is a common problem with some nVidia chipset drivers. Based on what you have, you can decide whether you think it would be best to reinstall or roll back the chipset driver.

Would research more, but I got to get to work!

I have no idea what happened.

First I did this when I read what TVeblen said about nvidia chipsets:

NVSTOR; Lag spikes; Freezing; Stuttering; Sound; Glitches - Windows | Zuki.org.uk

I did the whole procedure but nothing.

Then I followed F5ing advice but the image from WD site did not work with my sata DVD rom, so I downloaded Hirens boot and booted from there, ran Life Guard Diag for an extended test, I waited 2 hours and no errors.

Ok, then I involuntary booted to windows, (I wanted to go to bios), Chkdsk ran automatically and corrected lots of orphaned files and stuff I dont remember like for 10 minutes and booted with the driver visible in My computer!!..and no more messages in event viewer.

what was that??
who ran Chkdsk?
what are orphaned files?
do you think I may have corrupted files?

Then I went to event viewer and saw a couple of messages that said: The files system structure on the disk is corrupted and unusable, please run chkdsk utility volume D:
that message seemed from like 5 minutes before booting............????

Now I remember that this is the second time my D: drive suffer from this issue. The first time I just swapped my sata driver ports and everything went good again..
.....and I remember that chkdsk ran automatically too before booting..

This is strange and I don't want it to happen again!

anyways, I am back to bussines but I would you guys to give me some ideas to prevent this in the future

Thanks a lot