| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 91066 | 2008-06-25 03:48:00 | BSOD when copying file from one HDD to another? | braindead (1685) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 682207 | 2008-06-25 03:48:00 | This one has me stumped. I'm attempting to copy files from an existing HDD on an XP SP2 system to a new HDD configured as a secondary slave on the same system. A few seconds into the copy process I get a BSOD. Thinking it might be a bad HDD, I installed another one and it did the same BSOD thing. It is copying something across with the correct filename but the copied file is incomplete or broken. The STOP errors I get begin with 0x0000008E. I've trawled through Google but my exact error is not found. Both slave HDDs check out fine with no errors. Been through the RAM/Video card stuff but the problem does not seem to be in that area. The Minidump does not tell me anything I can understand. Can anyone please help me get a handle on this one? Much appreciation!! |
braindead (1685) | ||
| 682208 | 2008-06-25 03:59:00 | Not a fix - but zip the file, copy it, unzip it - see if it still BSODs. Have you scanned it for viruses? Have you done a chkdsk? Post the result of the minidump if you can, someone here may be able to pick up something you may have missed. ;) |
wratterus (105) | ||
| 682209 | 2008-06-25 04:03:00 | I dont think the dmp file can be read unless you have the MS debugging program Otherwise it may show up as garbage text If you had SP3 I could have checked it out, as I've got the debugging program and the symbols from the MS site. To see what the cause maybe ( I used it for the other PC here, which has SP3 on it). Altho it may work if this thing / the symbols inc SP1 and 2 as well You could try sending the dmp file to me , send an email...in here. I'll see what this debugging program says when I load the dmp file |
Speedy Gonzales (78) | ||
| 682210 | 2008-06-25 04:29:00 | Thanks guys. Yes, CHKDSK'ed everything and no virii. Speedy G - happy to send you a minidump but couldn't figure out how to do that within the forum. |
braindead (1685) | ||
| 682211 | 2008-06-25 04:39:00 | Wratterus... Tried copying a small RAR file = no problem. RARed the big 175Mb file and copied = no problem. Renamed the un-RARed file from its long file name to an 8-letter file name and copied = no problem The long file name has no 'illegal' symbols in it. BTW, It is an *.avi file. Go figure :) |
braindead (1685) | ||
| 682212 | 2008-06-25 04:46:00 | Ah you may have to configure your email settings in here. Usually you left mouse on a nick/name here then select send email. Your name hasnt got the send email option |
Speedy Gonzales (78) | ||
| 682213 | 2008-06-25 04:54:00 | Wratterus... Tried copying a small RAR file = no problem. RARed the big 175Mb file and copied = no problem. Renamed the un-RARed file from its long file name to an 8-letter file name and copied = no problem The long file name has no 'illegal' symbols in it. BTW, It is an *.avi file. Go figure :) Bit strange yeah! :confused: If you can be bothered finding out why this is happening, try renaming another one of your .avi files the same name and see if it BSODs when you try and copy it. |
wratterus (105) | ||
| 682214 | 2008-06-25 05:55:00 | Well, it appears the previous successful transfer of the bigger file by renaming it first with a short file name may fall into the category of 'witchcraft'. I tried the same process with another file about 350Mb and it BSOD'ded. In the course of my searching I did come across this file: bsod.pdf (www.sun.com) which may be useful to someone...just not me :) It explains in slightly more understandable detail what causes BSOD's. |
braindead (1685) | ||
| 682215 | 2008-06-25 07:25:00 | What system are you running? What format on your drives? NTFS or Fat32? Is there enough free space on the destination drive? Could freeze the files with Acronis and restore them to the other drive. |
mzee (3324) | ||
| 682216 | 2008-06-25 08:25:00 | NTFS. Yes, plenty of space. | braindead (1685) | ||
| 1 2 | |||||