Big Problem - Came out of nowhere

[mato7742]

well i've had my barton overclocked now for about 3 weeks. i had the processor originally running at 214 fsb, though i had a restart (after i scored successfully on p95) so i lowered it to 210. Well i've had it at 210 for about a week now very p95 stable, and today i was playing the ut2k4 demo and it just crashed. i restarted and lowered the fsb to 200, and it wouldn't start again. so i went to raise vcor, and selected to raise it 5%. I also put my memory back to normal specs since they were running at 2-3-2-6 (supposed to run that fast anyway) w/ aggressive timings.

well after that, i tried to restart, but my monitor light just blinked, and i couldn't get a screen at all. i tried to restart 3 or 4 times, but the same thing kept happening, so i took out the mobo battery and kept it out for about a minute and then replaced it. this finally let me get into the bios at least. i tried starting out again at 200 fsb. and it restart itself. so i went back down to 166. this finally let me in, and that is where i am now. WELL, the question i have now is i'm asking for a diagnostic from anyone out there on what happened, and what has happened? have i damage my equiptment? will i ever be able to go back to the same stats i had before? my cpu was never hot at the time of the shut off either (only about 46C). well if anyone can help me, i need all the different opinions i can get. thanks.

 

[mato7742]

well i just got my memory back to 6-2-3-2.0. so i guess the memory isn't screwed. i've also tried raising the fsb back to 200, and that won't work. currently i have it down to 180. when i tried to raise it to 200, it went through everything until right before the windows screen, when all i got was a blank, black screen. nothing else, not even an error message. when i restarted after that and went back into the bios my memory had been raised to 9-4-4-3.0. i'm really scared i just ruined my cpu.

 

[mato7742]

sorry, have to add one more thing, i just tried to raise my fsb to 190, and the cpu wouldn't even post. everything turned on but there was no screen at all. i took out the mobo battery again and got in. but yeah, i think my cpu is FRIED. should i raise the vcore to 1.8?

 

[Dustswirl]

Is your ram's timings set to auto or by spd? try setting them to user define (if you didn't already do it) and type the numbers yourself. 6-2-3-2.0 (the 3 should be RAS to CAS delay). try upping the Vmemory to 2.7V and set the CPU's Vcore to whatever it was before the problem (i'd recommend beginning with 1.675V). if your cpu was ruined it wouldn't start and you'd be smelling burned silicon. if your problem persists try every ram stick by itself jsut to check if they are fine.

good luck!

Ah new input:

Try setting everything back to stock. Everything! if it works then all is ok!

 

[mato7742]

my ram timings are set by spd, but i had it in manual and adjusted the timings myself (as i had before this all happened) - so should i put it on auto instead of spd even though it worked with spd before?

 

[Dustswirl]

if by spd is what you want then by spd is ok (6-2-3-2.0) if you want to change anything or want it a lil different then it's by manual. also when overclocking fsb up the Vmem a lil notch (2.7 is ok)
i hope everything works fine!

 

[mato7742]

nothing in my bios says vmem, there's vcore, vdimm, and vagp (vcore = processor, vdimm =i think vmem?, and vagp = the vpu). should i up the vdimm 1 point?

 

[Dustswirl]

yepp Vdimm is Vcore if you are planning to get back on running overclocked 214fsb with your memory running at the same speed (214mhz) then yes up it if it's 2.6V (from 2.6 till 2.7V) not 1 volt! just 0.1volt! what is the multiplier of your cpu? still x11?

 

[mato7742]

yeah it's 11, yeah i meant .1 haha, 1.. that would be pretty bad. um, how can i tell what my vdimm currently is?

 

[mato7742]

i just raised the vdimm 1 point, raised the cpu vcore +5% and raised the fsb to 190, and it wouldn't even post again. any suggestions?

 

[Dustswirl]

wow reading your motherboard's manual is hard, am not used to gigabyte.
anyway there should be something telling you bout your Vdimm voltage in the BIOS under PC HEALTH STATUS.....DDR25V
what does it read?

 

[Duvie]

What originally did you have the vcore set to??? That is odd you would have killed the cpu with under 1.8v in less then 3 weeks...


My money is on a power supply going south or the mobo is toast and going out...

For testing purposes drop the memory ratio so that the cpu would be 400/ and ram 333....See if it post...

Also try to reset cmos. Maybe someting in the bios got corrupt...

 

[Dustswirl]

hmmm have you tried pressing ctrl+F1 in the bios? i bet it could let you "in" for changing ram timings

 

[mato7742]

my vcore was originally set to normal (1.7v on the ga-7n400 pro2).

"For testing purposes drop the memory ratio so that the cpu would be 400/ and ram 333....See if it post...

Also try to reset cmos. Maybe someting in the bios got corrupt..."

how do i reset the cmos and drop the mem ratio so that the cpu is 400 and the ram is 333?

 

[Dustswirl]

no ratios in the bios it's on the motherboard. dip switches

just set everything back to stock and see if it works.

Advanced shipset feature:

system performance..............[Normal]
FSB Frequency ........................[133]
Memory Frequency...................[By SPD]
AGP Frequency ........................[Normal]

and put all voltages back to stock (Vcpu, Vdimm).

could it be your dual bios kicking in? this motherboard has tons of features!

As Duvie stated clear the CMOS
it's simply by turning off pc, removing the battery, wait 30s, but it back then power up. (page 30 manual)

 

[mato7742]

oh yeah, i've had to clear the cmos 4 times now. everytime i've tried going up to 190fsb, it won't restart, and i've had to clear the cmos.

 

[mato7742]

maybe duvie is right, the problem may just be either my mobo or my psu. i hope it's not the mobo... and i certainly hope it's not the memory or the cpu.

 

[slaves123]

but the partial damages are uncommon, if it's run perfectly at stock and u can't overclock as before probably something has phisically cahnged, i recommoend you to revise all the capacitors on the MB also the CPU pins, the memory pins and perhaps the PSU, you can also use some spetial light or liquid toidentify thermal problems or short circuits... as the problems come with overclock perhaps something is really more sensible to pushing it up, perhaps you find something interesnting,

best luck

 

[mato7742]

yeah perhaps

 

[Dustswirl]

I've been reading your motherboard's manual nice board btw.

Have you tried checking your dualbios options in Dual Bios Utility V1.** in the bios? (page 69 in your manual)
could it be that some protection function kicked in?

i just need to know if your system is working on default everything... otherwise i put my moeny with Duvie's suggestion about a dying PSU

 

[myocardia]

Mato, you have a partially damaged bios, and resetting it isn't going to fix it. All resetting a bios does is resets the parameters to stock values. I had the identical problem as you, with my Epox 8RDA3+, after a failed OCing attempt. I reloaded the latest bios as if I were upgrading it, even though I had the latest bios installed already. That was the last problem I had. Try it, and see if it doesn't work for you also. I bet you a dollar that it does.

 

[mato7742]

ok this thread is DEAD!!!! i figured out the problem, i wasn't running my memory in sync with my fsb, so it was resulting in less leeway between the two. so in case anyone ever has that problem, there's your answer! it worked like a charm. thanks for all the other input though guys! :beer:

 

[mato7742]

oh yeah, myocardia, you owe me a dollar! :evil:

 

[FelixDeCat]

This is the reason I stick with Intel. Twice in the past 10 years I went AMD and would up running back to Intel. AMD chips do last long overclocked. Sure for awhile you get lucky. Then one day you turn on your compter and -BOOM. The CPU gets damaged from high FSB settings and you are then lucky to get stock.

Others times its the chipset, mobo, etc.

No more AMD for this boy....maybe forvever. Those two adventures cost me several hundred dollars.....