Results 1 to 5 of 5

Thread: I/O error 0x8007045D reading/writing to HDD

  1. #1
    Senior Member
    Join Date
    Jul 2003
    Location
    Reading, Berkshire
    Posts
    1,106
    Thanks
    48
    Thanked
    39 times in 26 posts
    • tfboy's system
      • Motherboard:
      • Gigabyte GA-Z77-D3H
      • CPU:
      • i5 3570K
      • Memory:
      • 16GB (4x4GB Crucial)
      • Storage:
      • 512GB OCZ Vector SSD for OS + 600GB WD Black Data
      • Graphics card(s):
      • 560 Ti
      • PSU:
      • Corsair RM 650W
      • Case:
      • CM Silencio 550
      • Operating System:
      • W7 Ultimate 64bit
      • Monitor(s):
      • HP LP2475w + Dell 2001FP
      • Internet:
      • VM 60Mb

    Unhappy I/O error 0x8007045D reading/writing to HDD

    PC Specs for this problem:
    A64 X2 AM2 CPU on nforce 590 mobo
    1x 80GB Samsung SATA HDD - C: partition formatted as NTFS
    1x 320GB WD SATA HDD - D: partition also formatted NTFS

    I'm running out of ideas here. After changing over some faulty memory on my dad's PC, I was hoping to have a stable system, however when copying some files over the network to his D drive (320GB WD SATA harddrive), I came across an error which was something like failed I/O device 0x8007045D. I forgot to write down the exact phrasing, sorry. This error popped up with a random file 10-20 seconds after copying started. I tried different source files from the network, same problem. I then tried coping stuff from C: to D:, same problem. I then tried copying the original network files onto C:, no problem at all.

    So I was thinking that the problem was the WD HDD: either a corrupt partition / file system or something more sinister like a hardware failure. So I then booted with UBCD and ran some diagnostics on the drive. Did a quick test, no problem found. I've now done a full test (all sectors checked), and it's still fine. So the hard drive must be physically OK. I then reformatted in Vista and tried copying some stuff over again. Back to the initial I/O error

    I've now taken out the WD drive and stuck it in my own PC. I've done another full sector scan which appears fine and have done a full erase (write 0 values on all sectors). I am now in the process of doing a full format in Windows (the long winded way) and I'm 25% in and no problem.

    I can't see it being a hardware problem, whether harddrive, motherboard, SATA controller or cable because all low level tools run without any glitch at all, yet start reading / writing the drive in Vista and within 20 seconds, it pretty much brings the whole system down with that error.

    I can only think it's an OS issue. I've ruled out other hardware issues (full memtest), etc. Doing a quick google talks about a similar error and same code when trying to backup data. Solutions suggest disabling restore points (In System properties -> System Protection tab). I've tried this but with no change to the problem.

    edit: If I go to the device manager and select the WD hard drive and go to the Volumes tab and click populate, it seems to crash the PC. If I do this with the 80GB Samsung drive, details are populated straight away with no problems at all.

    Any ideas? I'm stumped
    Last edited by tfboy; 04-07-2007 at 11:10 PM.

  2. #2
    Senior Member
    Join Date
    Jul 2003
    Location
    Reading, Berkshire
    Posts
    1,106
    Thanks
    48
    Thanked
    39 times in 26 posts
    • tfboy's system
      • Motherboard:
      • Gigabyte GA-Z77-D3H
      • CPU:
      • i5 3570K
      • Memory:
      • 16GB (4x4GB Crucial)
      • Storage:
      • 512GB OCZ Vector SSD for OS + 600GB WD Black Data
      • Graphics card(s):
      • 560 Ti
      • PSU:
      • Corsair RM 650W
      • Case:
      • CM Silencio 550
      • Operating System:
      • W7 Ultimate 64bit
      • Monitor(s):
      • HP LP2475w + Dell 2001FP
      • Internet:
      • VM 60Mb
    OK, I've now finished doing a full reformat in my PC and tested the drive. It's working fine. Copied loads of big iso images over at around 55MB/sec and doing the device manager / populate is fine.

    I can only think it's a cable or SATA port on the motherboard that's tempremental. Maybe if I had another SATA drive to compare with that would help.

  3. #3
    Senior Member Pob255's Avatar
    Join Date
    Apr 2007
    Location
    London
    Posts
    9,326
    Thanks
    481
    Thanked
    1,096 times in 1,013 posts
    • Pob255's system
      • Motherboard:
      • Asus M5A99X EVO
      • CPU:
      • PhenomII x4 955 & CM Hyper 212+
      • Memory:
      • 2x 4gb Corsair Vengence 1600mhz cas9
      • Storage:
      • 250gb SATA Westerndigital + 500gb samsung +1tb Samsung
      • Graphics card(s):
      • Asus GTX560ti CuII
      • PSU:
      • Be Quiet E9 680w
      • Case:
      • HAF 912+
      • Operating System:
      • W7 Pro
      • Monitor(s):
      • Acer P223w 22" TFT DVI
    Could be mother board drivers or BIOS issue or port or cable.

    Stick it back in the other pc and see it the error returns.
    Try another cable and/or socket most motherboards come with 4 to 6 sata ports and cables
    Check motherboard manufactors website for updates to motherboard drivers and BIOS

  4. #4
    Pedandic mo-fo IAmATeaf's Avatar
    Join Date
    Jul 2006
    Location
    South of the Watford Gap!
    Posts
    896
    Thanks
    0
    Thanked
    11 times in 11 posts
    • IAmATeaf's system
      • Motherboard:
      • Asus P5Q Deluxe
      • CPU:
      • Q6600@3.25
      • Memory:
      • 4 x 2GB Corsair 6400C5DHX XMS2
      • Storage:
      • 2 x 0.5TB 7200.12, 2 x 1.5TB 7200.11
      • Graphics card(s):
      • Gigabyte GTX460 OC
      • PSU:
      • Corsair HX520
      • Case:
      • Lian Li PC6089B
      • Operating System:
      • Windows 7 Pro x64
      • Monitor(s):
      • Samsung T240 24"
      • Internet:
      • 6Mb ADSL Max
    Can't quite remember if it's the same problem but I had a very similar problem when using the onboard NIC on an Abit IC7-G, this only seemed to happen for certain files, for me the solution was to use a normal PCI NIC card.

  5. #5
    Senior Member
    Join Date
    Jul 2003
    Location
    Reading, Berkshire
    Posts
    1,106
    Thanks
    48
    Thanked
    39 times in 26 posts
    • tfboy's system
      • Motherboard:
      • Gigabyte GA-Z77-D3H
      • CPU:
      • i5 3570K
      • Memory:
      • 16GB (4x4GB Crucial)
      • Storage:
      • 512GB OCZ Vector SSD for OS + 600GB WD Black Data
      • Graphics card(s):
      • 560 Ti
      • PSU:
      • Corsair RM 650W
      • Case:
      • CM Silencio 550
      • Operating System:
      • W7 Ultimate 64bit
      • Monitor(s):
      • HP LP2475w + Dell 2001FP
      • Internet:
      • VM 60Mb
    Well, looks like it's sorted now.
    I did try a different SATA cable, and used a different port, all to no avail. Sometimes, I'd just get a BSOD and not an error message (my first BSOD in Vista. Woohoo!)

    In the end, a BIOS update seems to have cured it. I should have anticipated that really, as I bought the board (K9N SLI) only a few months after it came out and so there were bound to be many updates since then. I think I jumped 5 or 6 versions in one go!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. External HDD enclosure causing nasty static noise
    By Jez in forum PC Hardware and Components
    Replies: 1
    Last Post: 29-10-2007, 11:16 PM
  2. HDD custom enclosure
    By masterkeith in forum Help! Quick Relief From Tech Headaches
    Replies: 0
    Last Post: 07-04-2007, 02:35 AM
  3. Eclipse 62 - Fan configuration & HDD Cage
    By Randell Floyd in forum PC Hardware and Components
    Replies: 2
    Last Post: 26-08-2005, 10:14 PM
  4. Need Help to TATTOO a PB IMEDIA 5090 HDD
    By TJam in forum Help! Quick Relief From Tech Headaches
    Replies: 0
    Last Post: 27-02-2005, 08:39 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •