You're not the only one! in fact, I was so stupid, I bought a mobo known to not break 300mhz.
Printable View
You're not the only one! in fact, I was so stupid, I bought a mobo known to not break 300mhz.
LOL that mobo sucks serial hehehe
Hey guys!
Thanks for all the answers!
I just got the multimeter and Im gonna do the vdroop mod so I wont have constants vdroops and fail orthos making me put higher voltages.
Also, I will lower the 1.2VHT and VTT, yes I know they are high but they looked like they helped a little bit.
Also, My memory is running at 800mhz at default voltages so it cannot be causing the problem.
Ill add my specs to my signature right now... also, why would the PSU be causing the problem? it has been running fine and its 600watts. I dont think my system would be using that much power. I dont have SLI and my current VGA is a 7900 GS KO just to let you know.
What Im trying to achieve is 400mhz with 9x multiplier. I want 3.6Ghz. At 3.6Ghz Ill be happy and satisfied. I dont care if it is 450mhz x8 or 400mhz x9.
I will disable Execute disable and make SPP MCP 200mhz, if XD is enabled will that make your OC inestable? I want to have some kind of protection thats why i left it enabled.
This board has weak dividers. If I put 1600, memory has to be at 800. If I put something like 1790 and memory at 800, for some reason, memory will run at 760 and that causes the motherboard not to post. So I have to be very carefull when increasing or decreasing the FSB with the Memory.
Im 100% is the CPU, I have ran Gromacs Core and it failed in 5 seconds and the PC restarted.
---
Now I have some question regarding the Multimeter. Which option out of the 20 that it has should i use? I see that this "wheel" in the multimeter can be switched to 1k, 200, 20, 2 200m 20M and has 5 sections: 1 V (with this thing over it ñ), 1 V with a line over it, 1 A with this thing ñ, the A with a line over it and there is another section with a symbol.
Can somebody tell me what option should I use to do the vdroop mod? I really want to do this ASAP.
Here is a picture to explain better what I mean.
http://img512.imageshack.us/img512/4215/picture1al7.jpg
Thanks to everybody!
The PSU can be a problem if its drooping on the 12v rail itself. This will cause a vdroop as well because the circuit that converts the voltage into around 1.4volts is fed by the 12v line on your power supply.
You want to use the 200k range when checking the resistance because I believe the normal resistance is 129.5k ohms, but check first as it may be different on your board. If its ~130k ohms to start with, then you should decrease to around 120k ohms and go down in 10k ohms steps. I can't really predict a number because its different on every board. For me I had to go all the way down to 10k ohms whereas others needed only to go to 77k or 105k.
When measuring voltage, measure in the 2v range (for CPU voltage). If you're going to measure anything higher than 2V (like the 12v rail), then you should set it at 20V.
Also, be sure to you dont short anything out with the multimeter...you don't want to accidentally connect something with the conductive end of the multimeter thereby causing a short circuit.
Kobalt, Am I suppose to use the red or the black stick in the resistor?
It doesn't matter for resistance, but for voltage you ground the black end and use the red end. It doesn't really matter that much though...if you do it opposite you'll just get a negative voltage. I usually put the black end inside the black molex pin for convenience.
Also, I forgot...the system MUST be off and DISCONNECTED from the power before you measure resistance. (For voltage it has to be on).
OK THANKS MAN!
Gonna do this NOW!
BRB! wish me luck
Measured!!!! I hope you guys can help me more now!
Vdroop resistor shows 63.00
Vcore resistor shows 92.7
Now, I would like to know, I have more pencils now. I have 4B pencils and 6B pencils, I heard it would be better to use 6B pencils. My question is, which one do you recommend me to use?
procedures
mark the resistor 3 times then measure, write results in a paper and compare them to the original values. Turn on the system and check the vcore in BIOS and windows. If vdroop stills severe, then I should repeat procedure...
Is this right?
Thanks!
Check original vdroop first so you can establish a benchmark. You know where to measure the vcore from right?
Basically what you want to do is lower the resistance around 8k ohms each time and keep checking vdroop. I can't really tell you how many times to mark the resistor.
vdroop the max i can get it is 57
vcore max i can get it is 88 i believe.
dont know what im doing wrong :(
for some reason marking them more is making them get higher, and also, why is this getting complicated?¨:(
57 what? 88 what? mV?
What was your original idle and load volts. And what are they now and with what resistance.
57 and 88 using 200k, i suppose 57ohms and 88ohms, this would be the resistance. I havent turned on the system yet.
what do i do to know my irignal idle and load volts? also, what do i have to do to know if my 12v rail psu is causing the vdroop?
I thought you were giving me voltages not resistance. Don't worry about the vcore mod now...lets try to get the vdroop gone first. What you need to do is boot windows and when its idle (0% cpu), measure the vcore voltage using your multimeter. Then run something that will make it 100% cpu usage and measure the voltage. The difference is vdroop and we want it to be close to zero. I don't know where the vcore measuring point is on the striker though.
I give up
I putted the black stick on the ground molex connector and when I putted the red stick in the vcore resistor, boom my computer shutted down. I wont do that again.
I think I wont be able to run 400mhz w/ 8x nor 9x :( Im using 7x and everything is going SUPER FINE at 1.42vcore (1.45000 in BIOS) booted and running small FFT orthos for like 7 minutes already.
If I could just bring the FSB to 430 to AT LEAST have 3.0Ghz it would be GREAT.
Why do I give up? First, DMM tells me vcore resistor is 96.6 and vdroop is 59.6, fine, so I start marking, vdroop goes down to 58 (after like 5 marks) and vcore wouldnt go down. Sometimes after giving more marks to vdroop, it would go up back to 59.6 so I got tired and I think Im just gonna run the 7x multiplier with the vdroop thing.
Im running 7x to see what is the dam problem. So far I hate both my CPU and my motherboard. MB because of vdroop and CPU because of power-hungry (which now has me thinking cuz it booted fine at 400mhz with 1.42v and is running orthos fine :S )
Thanks Kobalt anyways, I know you tried to help me, maybe in a couple of months with new BIOS releases I might be able to fix this vdroop thing.
Do you think I might have gotten a defective motherboard or something? something that I think is impossible cuz its been running fine, maybe one of those strikers with low OC capabilities.
Ummm...you dont measure vcore on the resistor. You measure it on one of the mosfets, but I don't know which one because I don't have your board and I cant google anything.
and youre probably not pressing hard enough or using a pencil with enough graphite. Yes sometimes the resistance goes up if you dont press hard enough because you take off some graphite.
And BIOS releases don't do anything to vdroop...its a hardware thing.
I think my CPU problem is a CPU strap, not a FSB strap.
Take a look at this, so far running nice orthos small FTT's
http://img142.imageshack.us/img142/1552/xsqs2.jpg
Take a look at the voltage, I know is running at lower frequency, but the FSB is the same, super lower VTT than before as well as 1.2VHT. NB core at default as well as SB core. This is better than any other multiplier.
Gonna see what can I do to try to overclock the highest I can :)
Ill try tomorrow. Gonna ask my friend if I can keep the multimeter 1 more day.
Illl try to do it harder. I noticed something...
It is very hard to get the resistance, for the vcore and vdroop resistors, I had to put the red stick in the border (where the silver metal part is) to get the measure, and even when doing that, the DMM sometimes went crazy with some numbers like 22, 40 then it would go up to 128 140 then come back to 30 and I had to find the right spot to see what my resistance was until I finally got it to 59 which was my latest number for vdroop and 96 for vcore.
the DMM wouldnt give me any number if I putted the red stick in the middle (black part) of the resistor. Maybe is normal or not, I never tried this so thats why im saying this.
Um you should probably take some alcohol and clean off you board completely then start over from the vdroop. But before you do any mods you probalby need to reinstall windows agian that looks pretty messed.
When you took the initial resistance measurements from the resistors it's already so low which means u didn't clean it off well enough.
Also make sure you try 401 fsb instead of 400 which might move up 2 the next strap.
hi Slim142
would you do me a favour and please try this:
!! put " all " voltages on auto except cpu(1,45-1,50) and ram(2,250-2,30) !!
sp-mcp 200-others 100-
" all " ram subtimings auto(trc too on auto)
go linked + sync
fsb 400x9
disable bit-on + thermal control-on(you can disable all too-doesn´t matter)
try to boot-afterwards please tell me if its stable or not -
(had similar experience with this mobo like you-my hair is grey now!)
good luck
greetings from austria
don´t do mods until you got stable-but this is only my opinion.
When putting all the voltages in AUTO except for vcore and memory, system wouldnt boot. I think lack of voltge for NB and VTT.
Sp-mcp is in 200 and pci-e in 100
linked + sync
455x7
disabled everything
Cant try the timings and subtimings BECAUSE..............................
Here is what happened
Something exploded on my PC. Yes, not a typo. All I know is I heard a clap and burning smell came from the case. I was doing the vdroop mod on my motherboard (this time I applied very hard marks of pencil 6B but after I finished, I blew some air to get rid of the graphite in the motherboard) and decided to turn on the pc, after 3 seconds, there was a sound like a clap, PAMMM! and then my room started smelling like something burned. Turned off the PC and disconnected the AC power cable ASAP. The burning smell was really (really) strong coming from the case, some from one of the heatsinks near the CPU and some from the vdroop mod. Then to make sure everything was fine, I decided to turn on the PC again after 3 mins. Everything was fine and I got to boot into windows. I went into internet, checked my email, chat a little bit for like 15 mins and everything. So everything was fine until I decided to run memtest 1.70 to test the memory timings at 4-4-4-12 and speed of 920mhz (because I wanted to make sure my timings and ram voltages were correct with no errors). When I came back after eating, the pc was off (like after 10 mins). Tried turning it on the pc again and it wouldnt turn on. Motherboard lights go on and fans as well, LCD screens turns on and the onboard leds go on too as well as the power on reset and clear cmos button, also the yellow light next to the text STRIKER EXREME. But I have noticed there is a strange sound coming from the Power Supply, like if there was a wire stuck on one of the two fans (but actually there arent any), Before the memtest test, everything was running fine so I think.....
The Power supply just went boom and I need to change it.
BTW, I just checked the 24pin connector and there are no black marks, will try to see if it is really defective with my pentium III.
Any comments?
BTW, no more pencil/v mods until I become an electrical enginner (hopefully someday)
Were you checking resistance after every stroke?
Yes, the minimum I got it was 55.4ohms in vdroop, vcore I didnt mark it that hard.
guess what! it was a BIOS Failure :S
still dont know whats gonna happen when I get to 400mhzx7 and Ill have to put 1.42v :S
Im really scare of that sound, but Im positive, Im thinking it was just some pencil graphite on the board that made the sound probably.
It anything related with vcore woulda been destroyed or burned, I wouldnt be using this computer right now.