Storage

Ask something
Question Locked

I/O Device Error

0 helpful
3 replies

by anvar_darkwolf

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi guys,

Been having a recurring problem with my system regarding I/O device errors.
Ive got Vista Home Premium and when running the computer on moderate capacity, say FM2007 (RAM intensive game) and downloading a file i usually get these errors which foul up my system and actually prevent the system from rebooting from the start menu (it hangs on the "shutting down" screen).

Im fairly sure its not a failed HDD as i have replaced it twice, my drivers and such are up do date i believe, at least the important ones like BIOS and nForce. Most people seem to have this issue with CD/DVD drives and Floppy's and i cant seem to find much help out there for a SATA2 related issue.

Its my understanding that and I/O is a lack of power supply to the device, correct?
if this is so then is my 430W PSU sufficient for the system i have?

Core 2 Duo 6400
2x1GB Corsair CM2x1024-5400c4 RAM
8800 GTS
80GB IDE & 320GB WD3200KS SATA2
p5n32 SLI_Premium mobo.
Thermaltake XP 550 NP 430W PSU
Vista Home Premium.

Thanks for any help that may be forthcoming.

3 replies

by mckool

I have a very similar issue with my secondary drive! It's been driving me crazy!!! I haven't found anyone else with this issue until I just googled it opne more time and saw our thread on both Techguy and here. I have the same exact model drive WD 3200KS, a dual boot to XP and Vista, AMD dual core, 2 Gb RAM, MSI Mobo, 2 8800 GTX in SLI, and an 850W PSU so power is NOT the issue.

Here are the facts for my situation:

The problem does NOT occur in XP EVER!!
It only happens on that one drive (WD 3200KS)
I'm seeing other threads about WD drives (external too) that have this issue in Vista.

I do not beleve this issue is power related as my PSU is huge and XP never shows the issue. I'm thinking it's a WD issue.

by mckool

The latest NForce drivers for the SLI 570 chipset from Nvidia were the fix for me!! I guess this was an issue they fixed in this last release dated within the last few weeks. I hope that helps!

This discussion is closed to new replies.