HELP: Attempt to overclock WIPED OUT my hard drive! WTF!?!#!?@$

[Madcowz]

Okay so I popped in my P3 700E in my new CUSL2 and it's running along nicely at 700MHz. So I decide to bump it up a notch to 933 (I know it can do 933 b/c I ran it fine at 1050MHz on my old CUSL2) and boot it up. Windows loads and BAM, Blue screen of death!
"Fatal error...
Error: 0E:0028: C151F3F8"
I press a button and windows shows up but frozen. I press Crtl+alt+del and blue screen shows up again... I press a button again and repeat the same procedure and come up w/ nothing so I restart...
"An exception 0E has occured at 0028:FF0D3048 in VxD"
Same result... Restart again... Bios loads up and all of a sudden the screen flashes a different color and the computer freezes even before windows loads (don't remember if this happened before all of this, so this could not be the cause of the problem)

So I restart, go into bios, and bump down the speed back to 700MHz. The comp restarts and windows loads! Success! But WAIT, there's more! Guess what, there's nothing on my desktop! My ALL important folder that contains EVERYTHING (20GB's of mp3z, videos, install files) is GONE. My desktop files... GONE. I look in the start menu and all of the program shortcuts are DEAD. I look in their root folders and the files appear to be there but the programs don't run b/c they appear not to be installed... odd, very odd. I couldn't even connect to the internet b/c it said my modem was not hooked up properly. Well I check the system properties and it was working fine even after I did a diagnostics test. WTF is going on here!?!? How could this happen? How could overclocking wipe out my hard drive and how come it did not wipe it out completely?

Well at this point I am thoroughly fustrated. It first started off smoothly w/ my new system consisting of a P3 700E running smoothly at 1050MHz (room temp) on a CUSL2. I decided to go a step further by modifying my cooling (kryotech renegade coldplate) and I did myself in by snapping the left heatsink retention clip groove. So I buy a special heatsink clip that accomadates the 4 prongs on the socket and all of a sudden I run into problems. My motherboard doesn't seem to want to run my processor even at 700 MHz, it's stock speed. So I bump it down to 466MHz at which it is even burning hot (120 - 180F).

I decide to buy another CUSL2 to use while I send mine in for RMA service and now I get even MORE crap. Can anyone explain this to me? Could it be the hard drive? Could the stuff I lost be PERMANENTLY gone... is there any way to recover it?

 

[gamingbuddy]

Unless something else was written on your drive. The stuff is still there. Can you boot w/ a dos boot disk and see if your stuff is there? It might be just Windows acting funny. The best program i've found to get stuff back from your HD is lost and found.

 

[bmg]

I think "scanreg" is in windows/command. Copy it to a bootable floppy and try "scanreg /restore". Maybe it's just your registry that's corrupted. Windows normally keeps several extra copies of the registry.

 

[CAMS]

<<Could the stuff I lost be PERMANENTLY gone... is there any way to recover it?>>

The easiest way to recover it would be to load your backup copy. You do have a backup? No!!

All that important data on a computer that you where overclocking with no backup!

Excuse me a second.


HAAAAAHAAAAAHAAAA. Oh that is funny. Live and learn, as stated try to reload your registry.

 

[AngelOfDeath]

Hmmm it seems like the heatsink isn't attached properly to the cpu since it's getting that hot. Don't you have a retail heatsink you can try out with??

AoD

 

[BFG10K]

Congratulations! Now you know why I never overclock any of my system components.

 

[Paul]

Overclocking speeds up the system bus speeds and that does effect HD transfer speeds as well somehow. People have said to turn down your HD connection a notch in the BIOS if you overclock. Live and Learn. I've had it happen to me to, altough nothing important was lost. Format c: and start over.

 

[brian_riendeau]

Did you have your multipler set so the PCI bus was running at 33 when you did this? I lost most of an entire drive one just by using the 112 bus speed and had a PCI bus running at a very conservative 37 (33 is stock)

The files may still be there but there is no way to know until you look. Use a boot disk.

Sounds like your heatsink might not be on right too. Are the fans still spinning? Have you tried taking it off and putting it back on? It is possible you damaged your CPU as well. Overclocking is not risk free unfortunately.

 

[AngelOfDeath]

<< My motherboard doesn't seem to want to run my processor even at 700 MHz, it's stock speed. So I bump it down to 466MHz at which it is even burning hot (120 - 180F). >>

Either no one reads this or perhaps fully disagree with me, but doesn't it seem like a HS problem???.

AoD

 

[Madcowz]

Great... my floppy drive has been broken for weeks now. I didn't think I would have to use it, geez. Is there anything else I can try? I have a 2nd hard drive I can recover the files to... that is, if they are still there. Any ideas? Where can I find this lost and found program?

Also I'm almost absolutely sure it was the motherboard... perhaps the voltage was wacked out or whatever, but I at times even HELD down the coldplate/heatsink tightly onto the processor on that other CUSL2 and it still would not run stock speed. Just from the feel of it, the heatsink retention clip seemed to have it on secure enough anyways.

 

[Madcowz]

hey wait a sec, the PCI is at 33MHz stock speed when at 133FSB. My CUSL2 autosets it at 1/4 when the FSB is 133 and over. Regardless my hard drive ran at 38MHz before anyways so I don't think overclocked PCI speeds should be an issue here. Perhaps if it was an old crusty drive it wouldn't be able to handle the overclocked speeds, but I'm talking about a Maxtor DiamondMax 40 Plus ATA100 7200RPM drive here.

 

[Zab]

Boot to a dos prompt and try running scanreg from there.

 

[prontospyder]

Norton Systemworks has a file recovery utility.

 

[Looney]

Hm, if it was a HS problem, how could that cause his hdd problem? Unless he's had some seriously bad luck and the HS wasn't attached properly, and concurrently fvcked up his hdd at the same time while trying to overclock it... that seems a bit unlikely though. I would rather accept that he somehow fvcked up his motherboard bus system while trying to OC it.

BTW, i've seen with my own eyes a hdd frying due to OCing. I was with a friend when he swapped his Celeron with his bros computer, but the other computer hdd was a bit old (and Maxtor)... popped in the cpu, booted up the system, and started smelling smoke. Looked down at the open case which was laying down, and one of the IC on the hdd was ember red, with a thin trail of smoking rising out of it.

 

[Madcowz]

*ugh*... back into my system... when I come back I better see more suggestions!

 

[Doggiedog]

OMFG!!

I did the same thing last night!!

I had a safely overclocked Duron 950 which I tried to rachet up to 1.1Ghz when my PC just froze. When I rebooted it, it was back down to 600 but then said something about my registry being screwed up! I kept trying to fix the problem but it kept fatal erroring me. I thought I was so screwed because I had all my baby's digital pictures on that drive and when I tried to recover them, they were the only files I couldn't get. I finally tried my HD on my other PC under Win2K and was able to recover them. Holy crap. I would have been so screwed if I had lost them. I had to FDisk the HD and start again but at least I got my pics back.

That's the last time I ever do anything like that.

 

[Madcowz]

so wait, how did you recover those files?

 

[Doggiedog]

Since my HD was the master HD, I made it a slave then plugged it into my other PC. I got my other PC booted up then went to drive D (which was the messed up HD) and manually saved all the folders and files I needed.

Win98 was shot but all I cared about were my files. Afterwards I just FDisked and started over.

 

[Doggiedog]

Also, under Win98 on my other PC, it couldn't read some files on the messed up HD so I used Win2K which worked.

 

[blargyblarg]

can you get to the files from dos?

 

[Doggiedog]

Don't know but I suppose so.

 

[Madcowz]

Holy SH*T! I was looking on my hard drive and I noticed some weird directories in the C drive... namely, DIR00000, DIR00001, DIR00002 and so on up to 5. Well anyways, all my missing folders and files are IN those directories! Now how do you explain that? What's even odd'er is that all file names got cut short to 6 characters... like 1STSON~1, UCSCHO~1, etc. Hmm, this is going to be a Pain in the ass!

 

[Grminalac]

Heh,
Well that happens a lot when your memory is pushed beyond the limit. I have seen first hand registries being screwed and harddrives losing data on bootup because either the core voltage was too low or the memory was being pushed too far. On one occasion I destroyed my registry as well as my backup when I tried to run 100mhz sdram at 133. (live and learn) fortunetly I have been usuing norton ghost for some time. Its the best way to backup and then replace when overclocking.
Hopefully you made a backup copy of the registry; you should be able to replace the broken one.
As for the wierd file name, I am pretty sure than when scandisk attempts to repair your harddrive it will copy information from areas repaired to files with wierd names like you saw. Im my estimation the data in those are probably messed up, and I am not sure if you would be able to restroe them anyways. Someone else here probably knows how.

 

[Madcowz]

hey that could be it actually. I ran my rev 2 ram fine at 150MHz cas 2 on my old broken CUSL2 and since then I added a 2nd stick of ram, crucial 7E cas 2 (the good stuff)... as to why it won't do 2-2-2 @ 133MHz, I have no idea why, but I sure am PISSED

 

[novice]

MadCowz wrote: &quot;Holy SH*T! I was looking on my hard drive and I noticed some weird directories in the C drive... namely, DIR00000, DIR00001, DIR00002 and so on up to 5. Well anyways, all my missing folders and files are IN those directories! Now how do you explain that? What's even odd'er is that all file names got cut short to 6 characters... like 1STSON~1, UCSCHO~1, etc. Hmm, this is going to be a Pain in the ass!&quot;
I had a similar experience overclocking my Celeron 366 to 412, running the fsb at 75 MHz and the PCI bus at 37.5, and it puked my new Quantum Lct10 hard drive. I believe those funny named folders are scan disk files from the root directory that it no longer knows where they are supposed to be, so it set up new folders and keeps them in there. I don't know for sure that overclocking the PCI bus caused it, but I have run it at default speed ever since and the problem has not resurfaced. I had to painstakingly walk it through scan disk and Windows 98 reinstall to get it working again. Not fun at all. Good luck.
Chuck