Argh!!!

[Jeffro64]

I HATE F#@&%$! MICROSOFT!!!! I should put them in the Hall of Shame!:mad:

Just went in the bios on my everyday rig... the one in my sig to tighten up my ram timings a bit more, and touched nothing else and it boinked windows. :argh::argh::argh:

Why is it just because a setting won't boot that it has to corrupt windows almost every time?!?! Well, maybe it's more like every 10th time or just when you get everything setup just the way you want it... but still.:mad:


OK.... I'm better now.:D

[Jeffro64]

BTW.... I'll most likely be re-installing windows and everything else for the rest of today and maybe tomorrow after work, just incase i'm not on here later. Don't worry... I promise not to take the puter out and run it over with my truck. :D

[Kal-EL]

Well, if you do run it over with the truck, I DEMAND VIDEO!!!!!!!!:crazy:

In other notes, its always mem settings that cause a os corruption. Sometimes if you just let the rig sit for a bit, it miraculously recovers. What type of no-go error are you getting?

[Jeffro64]

I can't remember... something about no boot disk or other. I already got everything I needed of the drive and it's formatting. 1.5 TB takes forever to format... should have done the quick format LMAO!

[Kal-EL]

Prolly even faster if you just format 40 gig partitions or smaller. Then use a disk cloning software to clone that partition in case it goes poopoo then u just need to re-install the image with all the software and proggies already there.

[Jeffro64]

I keep wanting to do that but just never get around to it. Besides...every time i've tried that in the past, whenever I went to use it to restore the image was almost always corrupt for some reason and it didn't work anyways.

Thats yet another beef I have with Micro$haft... Windows has these so called restore points, but when you go to use it there never seems to be one. It's like they just magically dissappear.