My hardrive might be boned.. please advise..bluescreenblues
My hardrive might be boned.. please advise..bluescreenblues
Looks like ive got the blue screen of death blues. I walked away from the computer for about 4 hours, came back, and it was the blue screen. Restarted several times, and got blue screen. The error message fluctuated each time.
I have tried to re-install windows from the original cd, and each time i get an error : "setup cannot copy the file: scresrv.dll". It then gives me an option to skip the file which doesnt work.
I have retried several times and each time it stops at a different message : "setup cannot copy the file:...."
I have tried two different windows xp discs at this point.
Is she gone fellas? The disc is partitioned and the other side of that partition is important as fu*k. Any way I can salvage anything out of this?
The only upside of this is that Im in the process of upgraging. But damn, It would still suck to lose some of the data on that other partition.
Any advice would be great.
RL
I have tried to re-install windows from the original cd, and each time i get an error : "setup cannot copy the file: scresrv.dll". It then gives me an option to skip the file which doesnt work.
I have retried several times and each time it stops at a different message : "setup cannot copy the file:...."
I have tried two different windows xp discs at this point.
Is she gone fellas? The disc is partitioned and the other side of that partition is important as fu*k. Any way I can salvage anything out of this?
The only upside of this is that Im in the process of upgraging. But damn, It would still suck to lose some of the data on that other partition.
Any advice would be great.
RL
- Nestor
- Posts: 6683
- Joined: Tue Mar 27, 2001 4:00 pm
- Location: Fourth Dimension Paradise, Cloud Nine!
This is always the same, we all try not to get involved with trying the hardware out, because we have to disconnect everything and rebuild the system later. But honestly, the best way of doing it, is as Gary says, plugging things in “other” computers to see if they work or not. This is, despite all the hassle, the fastest way of checking a system. All the trials you could do within the same system, may lead you to error… Go to the point, and try all the pieces an parts in a second computer, it is apparently time consuming, but in fact, it is the most secure and less time consuming way of testing your hardware.
*MUSIC* The most Powerful Language in the world! *INDEED*
blue screen usually indicates hardware failure.
your original windows partition is now gone because of trying to install windows, no?
if so, just get another drive and try to install a fresh os. in the meantime, you can freeze the drive. wrap it up really well(airtite) in plastic and throw it in the freezer for a day or two. if the lifespan is limited and complete failure is immenent, you will gain some extra operating time this way(a little help the first time the platter spins up because the tolerances are a little looser when frozen), and with a usb interface or, just connected as an additional drive inside the computer, you should be able to retrieve the data you're trying to save.
if another drive doesn't help, and you're sure that the dvd/rom isn't to blame, then, it's probably the motherboard or memory. there are standalone apps to test both.
your original windows partition is now gone because of trying to install windows, no?
if so, just get another drive and try to install a fresh os. in the meantime, you can freeze the drive. wrap it up really well(airtite) in plastic and throw it in the freezer for a day or two. if the lifespan is limited and complete failure is immenent, you will gain some extra operating time this way(a little help the first time the platter spins up because the tolerances are a little looser when frozen), and with a usb interface or, just connected as an additional drive inside the computer, you should be able to retrieve the data you're trying to save.
if another drive doesn't help, and you're sure that the dvd/rom isn't to blame, then, it's probably the motherboard or memory. there are standalone apps to test both.
Hey Raztalove, if you have another PSU spare (or that you can take from another system), I'd try swapping that out first. If it's not that, my next call would be to try swapping out the graphics card. Those 2 items are the ones that have given me the most trouble with crashed, blue-screening systems over the years!!
As Gary says, it could also be memory or mobo, but I'd honestly look at the PSU before those.
I didn't read every single word in the thread here, so apologies if I'm repeating what someone already suggested.
regards,
S
As Gary says, it could also be memory or mobo, but I'd honestly look at the PSU before those.
I didn't read every single word in the thread here, so apologies if I'm repeating what someone already suggested.
regards,
S
we fried 3 or 4 boards in a row (P4P800, same ICH5). it probably happened while connecting things to the not properly grounded ports on the case front. so we disconnected everything going to the front panels and use the ports on the back with extender cables only.stardust wrote: The asus p4c800e southbridge ICH5 is famous for being very sensitive to static on USB port.
btw, whenever a board went to silicon heaven that way, it died all of a sudden with a "no screen at all" screen. there's still hope you didn't manage to roast it like we did...
if you still suspect the hard disk, there are specific tools from the manufacturers to test them. you can mostly download and put them on a floppy or even burn an iso to a bootable cd and run tests with it.
I'd do a backup, nevertheless, before. an usb2(s)ata adapter and a linux rescue cd of your choice (I'm pretty sure a PE based cd like BartPE would do as well) can do wonders here.
if you didn't overclock your machine and cared for proper cooling, I would not suspect the ram at first look. but there's memtest86 to check for that.
also the optical drive should not be the reason for producing bluescreens all of a sudden (or was it while it was heavily in use?). I would probably not expect the "cannot copy xyz" to be the effect of a broken drive only, in your special case. it could, nevertheless, add additional problems to what you experience...
the psu at least is a worthy candidate, imho.
-greetings, markus-
--
I'm sorry, but my karma just ran over your dogma.
I'm sorry, but my karma just ran over your dogma.