Errr bit OT, an50r has working pci/agp-lock ?
Printable View
Errr bit OT, an50r has working pci/agp-lock ?
yes with newest bios
modded versions out ?
I ran 3.3vdimm on my 3200+ for a month or so and no ill effects. I had a K8Npro with the +3.3v to cap mod on it. Then I picked up a K8NSpro and decided I wanted adjustable vdimm so did the normal VR to IC to ground. I need to run +3.6v on my 3.3rail just to get 3.2vdimm and again no ill effects.
You don't need a modded version as far as I know. The official one should do the job great. Perhabs this could be possible on other boards too? Let's see :)
@sai: where do you live in frankfurt? Big City ^^
not exactly in Frankfurt, about 15km away from frankfurt
does any of the two of you maybe know a girl named anne? shes around 22 and was in venezuela with me for 1 year with an organization called AFS. :D
lived in/around frankfurt , i know its a big city, hehe but hey its worth a shot ^^
I had for 3 monthes a Shuttle AN50R and 24/7 use with 3.3v Vddr was doing fine.
I also think 3.3v is quite the highest safest voltages. higher then that is for die-hard 1:1 OC and benches :D
Sometimes i tried 3.5-3.6v but somehow my pc keep shutting down and stay 3-5min down :confused:
Advise:
If you feel that your CPU is not OC'en good as before. Example: BSODS, bizar erros etc. ... Run STOCK speeds/voltages for a while.
so whats the deal with socket 939 boards? Do they suffer from these vdimm related deaths? DFI's 939 board goes upto 3.6v and so i just wanna know the latest news on the A64's deaths. Should have follows this more closely when it was happening but i was busy :(
Cheers.
where did you see 3.6vdimm for the dfi neologan. that is fantastic if true
http://forums.overclockersclub.com/?showtopic=28613
not sure its true but it's all i heard about the 939 boards so far.
Hello
I found this forum today, 7-26-04. Very interesting.
I HAD a Chaintech ZNF3-150 with a 3000+
BOTH died 2 weeks ago. They were only 5 months old.
And I DID NOT overclock or overvolt.
I got approved RMA's on both.
I bought a Gigabyte K8NS Pro 'cause Chaintech said it could be 10 days plus shipping time.
Thanks for the heads up.
Mark
i wonder if the VTT(bus termination controller) half vdimm voltage you know is too much for the A64 mem controller at 3+ volts if so maybe adding a higher value resister in the circuit would fix teh deaths issue
I believe it has to do with something other than VDIMM.. most likely VBT (chipset voltage).
Tomarrow i'll hopefully have some time to fire up an AN50R and 2800+ (cpu deceased!) and do some poking around on the back of the board to find out what voltages are actually making it to the CPU..
I was testing out some new BH5 sticks and sometimes it would start beeping when turned on after I set it to CL3 in bios. I then had to reset the CMOS.
This happened before with my Corsair BH5 sticks so I didn't think it was a big deal, but then after resetting CMOS for the last time, it started hanging after POST :(
Tried removing the bios chip 'n reflashed it on another computer, tried removing the volt mods, still nothing.
To the people who had dead mem controllers: what were your symptoms before the cpu totally died? Was it similar to mine?
I'm hoping its my mobo cuz I ordered a K8NS
BH/CH chips cannot do cas3
question...
anyone know how to tell if the mem controller or your motherboard has gone bad?
here's my problem...
using any ratio 1:1, 5:6, 2:3, and running at 200 mhz (w/ divider in place) memtest #5 looping passes with no problems...
210 mhz no problem
220 mhz fail
230 mhz fail
...
i have 2 sticks of bh-5 that i know can do 240 mhz with 3.2 volts easy
does this sound like my mem controller has gone bad or my mobo?
and if your mem controller does go bad, would my cpu even work?
Some memory just isn't compatible with some A64 chips or mobos. That's just one of the frustrations. Always good to have a different type of ram on you so that you can test for incompatibilty vs. a part that's bad.
stevil any luck with checking those voltages? cause if its the vbt thats killing them maybe we can find a workaround to solve this issue. i was thinking it wass the vtt as some boards didnt have vbt mods. but maybe its coupled somehow with the vdimm?
anyone?Quote:
Originally posted by shimmishim
question...
anyone know how to tell if the mem controller or your motherboard has gone bad?
here's my problem...
using any ratio 1:1, 5:6, 2:3, and running at 200 mhz (w/ divider in place) memtest #5 looping passes with no problems...
210 mhz no problem
220 mhz fail
230 mhz fail
...
i have 2 sticks of bh-5 that i know can do 240 mhz with 3.2 volts easy
does this sound like my mem controller has gone bad or my mobo?
and if your mem controller does go bad, would my cpu even work?
Like I said earlier, you need extra available hardware so you can swap out parts to isolate your issue. Did you try running a single stick of bh-5 to see it's FSB limits? Have you tried different ram? Different ram slots? What's your vdimm? Are your ram stick double sided or single sided?
i have single sided bh-5'sQuote:
Originally posted by BMORIN
Like I said earlier, you need extra available hardware so you can swap out parts to isolate your issue. Did you try running a single stick of bh-5 to see it's FSB limits? Have you tried different ram? Different ram slots? What's your vdimm? Are your ram stick double sided or single sided?
i ran 1 stick in each slot and still have problems
i ran 2 sticks in 1/2 1/3 2/3 and no good
vdimm is set to around 3.2 to 3.3 usually for any HTT i use.
i've tried my memory in other boards and the memory is fine.
i've tried another epox 8kda3j and was not able to hit 2.75 stable
anything else?
i've never heard of a chip not being able to hit it's highest overclock after installing a new piece of hardware
allm y problems started with an x800 (which is now dead due to a psu problem)
stuck an x800 into my system and system was not stable.... after sticking it in, it wouldn't hit 2.75 stable anymore... so i took it out and put in a 9600xt and it still wouldn't hit 2.75...
someone suggested a larger psu so i went from a 430 to a 520 and fixed some problems but still maxed out at 2.4 ghz...
couple days ago, my power supply crapped out and killed my x800 in the process....
so... is it the mem controller on my chip or is it the board?
the other board i sold off to someone else with mods intact and they have been able to hit 250 HTT (2.5 ghz) with their board and air cooling....
but i don't see how 3.3 volts could damage my mem controller and how my chip would still be working even with a damaged mem controller
thanks.
I ve killed a 3000+ with too high VBT , with pc3200 it didn't boot , but with pc2100 it will !!! lolll
Mem controller knocked out.
so you're saying that it worked... just not at pc3200 speeds?Quote:
Originally posted by misteroadster
I ve killed a 3000+ with too high VBT , with pc3200 it didn't boot , but with pc2100 it will !!! lolll
Mem controller knocked out.
interesting... maybe i do have a damaged mem controller then...
thanks misteroadster! :)
Well, that the first I've heard of a "damaged" mem controller. I've heard of various incompatibility issues and that's all. Shim, you need to try your chip in a different model mobo and/or try a different chip in your current mobo. In my opinio, it's worth buying a piece of hardware then paying a 15% restocking fee just to get it checked.
hmm... i see...Quote:
Originally posted by BMORIN
Well, that the first I've heard of a "damaged" mem controller. I've heard of various incompatibility issues and that's all. Shim, you need to try your chip in a different model mobo and/or try a different chip in your current mobo. In my opinio, it's worth buying a piece of hardware then paying a 15% restocking fee just to get it checked.
maybe i do need to try another board and another chip...
well.. i'm waiting for the dfi so i'll try it on that one for sure... and if i still have the same problems, then i'll get another chip...
but the chip works perfectly fine at stock settings though...
weird
People may be you can send me your broken CPU's ? For hardcore experiments
has anybody noticied if there are more C0 A64 deads than CG? i'm going to mod the vdimm directly to the 3'3 atx pin because I don't want to mod my 3'3 psu rail (my vdimm max is 2'93v).
Although I think my mem controller is already damaged... I can't boot with 2 sticks of memory pluggeds at sync mode (and async freezes at 230 htt), but with 1 stick i can do anything... (350 htt if i want). This problem appeared since 1 month.
I have killed my A64 3000+ NC CG. :( Got a 3200+ last weekend. Yesterday it did not boot into Bios. I had Vmod the Abit KV8 Pro VTT and Direct 3.3v Rail connected to VDimm. It was unstable. The next thing it won't boot. error No. 04 on the mobo.
Little question guys ,How much Vcore can the A64 handle before it breaks down ?
I dont increase Vdimm cos i know its bad for the CPU afther reading this treath...
I am using 1.7Vcore to get 2700Mhz and its running fine ,but for how long with only vcore mod ?
Don't worry about the vcore or the vdimm, it's not so much an issue now as it was with some of the early chips and early mobos. I still wouldn't push vdimm past 3.6v. I have run 3.6v on the vdimm and run about 3.3v 24/7. I keep my vcore at about 1.925v
I've bought ocz ddr booster and i'm running at 3'3v for 6 days... still no problems. (3400+ C0 year 2003).
This issue doesn't seem to be a problem with 250gb, CG stepping and so on.
I have run several hours of testing@3,7v and 24/7 on 3,4v, so I guess it's not a problem anymore.
so you people are saying i shallnt be worried of my a64 dying? ive got a gig of mushkin and a dfi UT on the way and i was thinking of getting a 2800 35w mobile chip. my 3.3rail is at 3.4 ish. should i be worried much about deaths? what vcore is considered "safe" meaning it wont kill the chip in a couple months time?
ok guys i think im going to be joining the dead a64 club im afraid... i was ocing my 2 day old DTR3400 proven 2900mhz cpu last night and i was trying to get up into the high ocs like the last guy was getting with the chip. well i was at 240x11 1.55v at 113% when i seen it wasnt stable so i went back into the bios and jacked it up to 1.55v @ 123% on the v-core and 3.1v on the memory and just for good measure i added 5mhz to the fsb! well i hit exit and save and it started to post it got past the memory count past the HD screen then when it was suposed to load windows it just went blk :shrug: nothing i do helps... soo does this sound like i smoked the memory controler or is there hope? im thinking i may have scrambled the bios but i got this 280 dollar feeling the chip is dead.... anyways what do you guys think?
peace perc,
exactly the same happend to me. i had my vtt at 1.65 and vdimm at 3.28, which would also comfirm what saaya said.Quote:
Originally Posted by htkm1
perc: so it doesnt boot at all? what about the psu or memory? is evap making good contact? you may need to remount it esp. on a DTR
me hopes your wrong perc, I've slammed the 1.33% into the chip and whatever's after that. And no problems. I've not seen the A64 problems like they used to be, Is it still very common place??Quote:
Originally Posted by Perc
I've been pushing 1.92v into this 3000+ newcastle you sent me back perc running It @ 2.8ghz And 3.1v to my Ballistix memory. No problems running 24/7 F@H non stop. I know it's running nice and toasty, No load my Vapo LS will show -57c, loaded right now with F@H running and plenty of volts it's down to -39 Celsius Which means i have really good contact. The 3400+ that's taking a nap on you right now was a little harder to get good contact i could tell.
unloaded temps were the same -57, but 100% cpu it only would pull down to -48 Celsius on the front panel. I had problems getting good contact with it. I used to have to pull the Vapo Hose to the left to get better contact and zip tie it a little..
Again Perc, i hope this chip wakes back up for you in the morning, I've seen many a chip of mine just somehow come back to life!!! And dam that was a good chip. I ran it @ 2.65ghz with a Zalman ALCU!!!! The extra 200 mhz using the Vapo and electric was hardly worth it.
I see what you mean now that im back with the newcastle chip and 512 cache, it does make a big difference. Especially on super Pi up above 2.8ghz!!!!
I guess i'll buy us a couple more, I seem to be lucky buying good chips.
Talk to you tomorrow Perc, good luck.
later
tedidne what do you think of IHS? should it be removed, and will zalman alcu still mount?
@tedinde
yeah i think it will man. i dont think its the cpu cause when this happen to me i only made it out of the bios and past the memory count screen then it went blk. i think it may either be a scrambled bios or a cold boot issue. i got a new bios chip comming my way this week so one i hve that ill be able to start working on it. the thing is right now i have one system and its hard to work on a broken system and not have internet to go and find answers too. i need a psu and a video card before i have enough parts to run a system and work on another. know what im saying? anyways i dont think the chip is dead either. after hearing from you on how much voltage youve given this chip theres no way i killed it with 1.875v and 3.1v to the memory... ill keep you posted....
peace perc,
i want that dead chip :D
Quote:
Originally Posted by reject
yeah i think i need to start over with this sytem. im going to rip it all out of the case and remount the damm mounting kit and pray like hell i can get it going. the more i think about this the more im convinced its not the cpu. i think its a cold boot issue cause when i first built this system i wouldnt boot just like its doing now. i think that at auto the bios is setting the v-core at 1.04v wich i think is the cause of all this but im not 100%sure..i have a spare bios chip just need to hot flash it in my intel rig. i hope that maybe a diff bios i may be able to get jump started again... ill keep you guys posted on how it turns out. thx for your replys guys.
peace perc,
Is my A3400+ NC dead too?
Or is it something else?
http://xtremesystems.org/forums/showthread.php?t=46292
I am running my ADA3700AEP5AR 0432 at 3ghz / ~1.8v. With 3.3v @ ~3.7v, 5v @ 5.2v, 12v @ 12.4v on the PSU(OCZ520W), vDimm @ 3.5v, and I haven't seen any problems so far. I have the DFI UT and AFAIK there haven't been any problems with the DFI and these failures, right? Is this a s939 issue only?
Only problems I have had was two dead DFI boards. First because of a 10 minute blackscreen limbo, caused by a 3.15ghz suicide run. It simply froze and I wasn't around to shut it down, 10 minutes later I return, the board never posted again. Second board died because of OCZ Booster, 2.8v read by the booster, 2.8v set inside BIOS, no OC on CPU @ 1.5v - worked for 12hours stable, then booted PC and black screen, board dead. I'll never, ever use the Booster again on a DFI UT. First board RMAed, I bought the second one(didn't even tried to RMA it). Lucky for me, the CPU has survived all of this and even more.
Is it for real, when AMD says no more than 2.6v vDimm is recommended? This can't be true, and the OCZ guys said they have never seen a dead CPU from high vDimm, but I wonder about the 3.3v rails.
I have seen spikes on the vDimm, but that was from reading the BIOS' readings, and I have been told that the DFI UT' voltage readings are attrocious. Another funny thing is, that sometimes vDimm voltage readings don't change in BIOS after a bootup.
It can be at 3.5v and I change it back to 2.8v, but after reboot it still says 3.48-3.5v as current vDimm. Only after another reboot, will the reading be correct, but still fluctuating up to +/-0.2v. I have had this issue with all three DFI boards. Anyone know anything about this?
I don't think I'll ever have a problem with my 3700+, because of the 3.5v vDimm or my 3.7v 3.3v line, but I'll report back if I am wrong :p:
up....is this still an issue??
I think this issue is way over exaggerated... I personally haven't come across any...
You probably weren't around when the Shuttle AN50R was "hot". :stick:Quote:
Originally Posted by A_X
so has this issue been resolved? for Socket 754
personally i think i will stop at 1.65 vcore and 3.1 for vdimm....but thats just me... :)
is this still a problem?
If breaking CPU's with too high voltage, or by some abuse is a problem, then yes it is a problem. :DQuote:
Originally Posted by Unhooked
Holy-chip!!!!!!!
Now THAT was a long n scary read, yep every post on all 11 pages!
I've been sitting on a A64 3000+, K8NS Pro and 3X512 since X-mas.
I did put together the mates to the cpu and mobo X-mas day for a former boss of mine,
He's had no problems other than slow boot, my quess is the not-brain wipe,(reformat)
he made me do cause he didn't buy an extra HD, and still won't even @ these current prices and his made some serious sounds back then!
Dam non-gamer's!!!
make us look crazy for needing newer n better when they can run with crap cause all they might do is pictures n type stuff!!!
Anyway I'm about done with "SUPER COMPUTER" Multi-loop water n chilled water system and did a search for my board and found this thread!!!!! Dam!
Well....
Its good to have extra puters and parts I quess.
Just hope I got a GREAT chip, cause I can remove some serious HEAT!!!
Yes,
I will be water cooling the chip-set, also the RAM and PSU as well, (Multi-loop)!
Thats because I can and I did the research!
Thanks for all the info in the forums!!!!!! cheers 2 all who post, good, bad or just a question!
Thats how this information super hi-way makes us all better!
Good DAY/Night
l8r
ff
my cpu been running at 1.72vcore for almost 9 months now on AIR - and it aint dead :p:
it doesnt need 1.72v for 2.6ghz (more like 2750mhz) but i dont like changing the voltages too much.