The device is not ready for access yet
on 09.23.04, 02:06pm in windows • digg this • comments (3)
Last night, I noticed an interesting problem on my freshly repaved Windows XP box: After Windows booted and the desktop came up, I was unable to do anything with the box for several minutes. Every time I double-clicked on an icon, the cursor would change to an hourglass for a second, then nothing. No window. No anything.
Great. First thing that came to mind is that I’ve picked up a spybot or virus, even though I run eTrust Antivirus and check the machine with Spybot Search and Destroy regularly. I scanned the machine and found no problems. What was interesting though was that I could get into a command window, so I was able to find out what processes were running, but nothing seemed wierd or suspicious.
After a short bout of tourette’s where I screamed at the computer and told it what I thought of it (like it cares), I collected myself and checked the event viewer to see if there was any sort of network failure. I was startled to find several of these entries:
Event ID: 15
Source: Disk
Description: The device, \Device\Harddisk0\D, is not ready for access yet.
Obviously (well, obvious to me) this was the source of my problems.
To make a long story short, it turned out that during my reinstall I had installed the drivers for the motherboards RAID controller, even though I don’t have any RAID drives attached. Once I disabled it in Device Manager, my timeouts went away and everything was fine.
My point: I still don’t understand how the average user gets around these types of problems.




Jason Silver (September 23, 2004 @ 6:29 pm)
I have the same question regularly. At my job, I’m often helping people with computer problems and they ask me, How would I know to do that. I just shrug and groan and agree. Computers, for all their accessability attempts, are not for the faint-of-heart. If someone gets a couple of bad spy programs that involve booting in safe mode and renaming a file, etc. then it’s quickly beyond the reach of most people. And most people don’t realise how much faster a machine can be if you clean your registry once in a while. Why isn’t this part of the OS’s auto sweep functions?
~Jason
John Newbould (September 26, 2004 @ 7:02 pm)
Boy Thats true indeed and its been that way since DOS 3.1…
Why oh why doesn’t Microsoft really get it?
Keep those Incident Reports going!
doug varn (January 5, 2006 @ 12:02 pm)
i just found this error on my own computer. indeed, i have a RAID controller installed, but device manager doesn’t even give the option to disable it. i chose to uninstall it and it doesn’t work, what happens is on re-boot it auto installs a generic windows RAID driver. i cannot disable RAID anywhere in my BIOS either. i have 2 SATA drives btw…if it matters. if anyone could help, please email me dougvarn@yahoo.com