HELP!

[=CJW= Zweistein000 (W)]

Ysterday I reinstalled my win7, OCed the CPU from 2.80Ghz to 3.09Ghz, and forced my DDR2 800 RAM to run in 400Mhz insted of 200, the bios suggested. It was all ok till I started getting the following problem:

http://www.youtube.com/watch?v=9xi0W9v0sy0

I have been fighting Vorises lately, but I perfirned a full format of my HDD, also I updated my BIOS lately, but there were no problems till now.

Help 

[SquareSphere }12thVR{]

sounds like the bios doesn't like those settings, just reset them to default and see if it boots up.  In your video, the small bit i could make out, i it looked like it couldn't find the boot device or something that.

Your MOBO should have jumper to set the board back to factory settings if you can alter them in the bios.

[=CJW= Zweistein000 (W)]

cant find my jumper!

EDIT: toad said it should be right next to  my  battery

found the jumper, it didn't help.

http://www.youtube.com/watch?v=tn8m85aQeHM

[attachment deleted by admin]

[SquareSphere }12thVR{]

i see it, its right next to the battery on the right, it's called CLRCMOS and it's blue

[PapaFade]

Might not be useful, but the Asus clear CMOS procedure involves you moving the jumper over 1 pin and removing the battery for 10 secs. Don't know if you've tried it already.

[(TLL)KitLightning]

Did you look up your mobo on the manufactures homepage? Most have either an on-line manual to all mobo's in their production. Also make sure that your ROM is flashed to the latest version though that is a rather tricky thing if you have never done that before.

[SquareSphere }12thVR{]

Might not be useful, but the Asus clear CMOS procedure involves you moving the jumper over 1 pin and removing the battery for 10 secs. Don't know if you've tried it already.

yep that's exactly right.

[GB-72AT Talon]

Might not be useful, but the Asus clear CMOS procedure involves you moving the jumper over 1 pin and removing the battery for 10 secs. Don't know if you've tried it already.

yep, power down pc, carefully remove battery (looks like a nickel sized watch battery) from board, move jumper for clearing CMOS (refer to motherboard manual for that), let it sit a minute or so, move jumper back, replace battery, power on pc

you will most likely have to hit delete to get into the bios and set everything back up like time, date, boot order, etc....but all the settings you changed should be back to stock

you really shouldn't be overclocking at your skill level i assume, no offense, but its not just "that simple"

[=CJW= Zweistein000 (W)]

Well i tried all of that and t turned out that forcing my mobo to rune DDR2 800 Ram on 400Hz when it was designrd only to run DDR2 667 on 333Hz ram is a bad idea. It's fried (I smelled that something is frying up smell, but I just discarted it, because my win was running ok, 1 hour later this happened). The good thing is that my RAM survived, my HDD survived, my CD-rom  survived and my Graphics card survived, also my RAM and possibly graphics card is still under warranty, so I migh be able to refound those.

[=CJW= Namarah (W)]

Fingers crossed they are. depends on how long the warranty is on those devices. just don't tell them what happened in too much detail. or they may revoke it.

[GB-72AT Talon]

Well i tried all of that and t turned out that forcing my mobo to rune DDR2 800 Ram on 400Hz when it was designrd only to run DDR2 667 on 333Hz ram is a bad idea. It's fried (I smelled that something is frying up smell, but I just discarted it, because my win was running ok, 1 hour later this happened). The good thing is that my RAM survived, my HDD survived, my CD-rom  survived and my Graphics card survived, also my RAM and possibly graphics card is still under warranty, so I migh be able to refound those.

um yeah....if you mean your motherboard only supports DDR2 667 and you stuck DDR2 800 memory in it, that would indeed be a bad idea

i figured you were just changing a setting in the bios, not putting in non-compatible memory

[Bill]

Haha, yeah that would likely do it.

[Freeborn_Toad]

Nothing makes the memory incompatible other than the speed it's rated run at. It can be run at lower speed, and was until Zweistein changed the memory ratio. I suspect the board was on it's way out already and the added stress of the overclock just accelerated that processes. Chipset cooling looked pretty weak to begin with.

Anyway, seems like it was a learning experience, so not a total loss.

[GB-72AT Talon]

Nothing makes the memory incompatible other than the speed it's rated run at. It can be run at lower speed, and was until Zweistein changed the memory ratio. I suspect the board was on it's way out already and the added stress of the overclock just accelerated that processes. Chipset cooling looked pretty weak to begin with.

Anyway, seems like it was a learning experience, so not a total loss.

different classes of memory also run at different voltages though, especially when you get into enthusiast memory, there are low voltage memories and high voltage memories, etc......although it should not have been the main culprit you're right, but there was a pretty large jump there that the system couldn't handle for some reason

[=CJW= Zweistein000 (W)]

Nothing makes the memory incompatible other than the speed it's rated run at. It can be run at lower speed, and was until Zweistein changed the memory ratio. I suspect the board was on it's way out already and the added stress of the overclock just accelerated that processes. Chipset cooling looked pretty weak to begin with.

Anyway, seems like it was a learning experience, so not a total loss.

Indeed. Well I would like to thank ALL o you for your help (this also incloudes my clanmates). It is now up to my cousins boyfriend to figure out the rest.