Has anyone had this happen on a Via board?
Printable View
Has anyone had this happen on a Via board?
I´m starting to have exactly the same problem. Have vcore and vdim mods done.Quote:
Originally posted by bowman1964
it starts with lots of windows errors and then it wont reload a fresh copy of windows. one the gigabyte it would almost make it to the desktop and then it rebooted...
Problem started when I tried to increase vdim from 3V up
MOBO: K8N Pro
CPU: A64 3000+
I can only confirm tomorrow night if CPU is KO or not
I hate to say it, but it's pretty obvious that these chips don't like high voltage like the Athlon XP did. So if you want to keep your chip and not hose your system, keep the voltages down.
i'v benched with mine 3200+ with +3.3v @ 3.8v and with v-dimm @ 3.5+- several times and it's all ok
i'v tested with asus k8v and gigabyte k8n np
i'm waiting for a 3.4+ let's see if it lives :S
regards
Well, when I get my K8N Pro or AN50R I'm not going to volt mod it because I can't afford to buy even one extra cpu.
Will the maximum voltages that are allowed in the K8N/AN50R bios not kill the cpu?
.
mine was due to being stupid, smoldered my board, litterally. i rma'd it.. no prob.. and if my cpu dies.. id rma that too.. not cost out of pocket but 5 bucks for shipping, which i will do from work, for free. after reading this i sure as hell am goign to turn my rails down tho =)
curious tried useing memtest86 3.0 and memtest86+ 1.0 with these dying or dead cpus when they showed these windows booting symptoms ? - just trying to get an idea of memtest reported errors/symptoms.. as i don't load windows with my systems until i can get memtest errror free for a few days hehQuote:
Originally posted by bowman1964
well i have posted in a few threads about mine....
but i dont have time alot to check the threads at work.....i do have to work...not play all day...so i hope that wasnt directed to me...:confused:
i ran accoss this one by accident....and i am still not sure on the death issue.....i have 3 boards so i am not going back to the chaintech until i get chaintech to take a look at it...i have emailed the company direct.
all i know for sure it is the mem control going out..not the basic cpu.
it starts with lots of windows errors and then it wont reload a fresh copy of windows.i pulled 2 chips from the chaintech after the first errors accured.and one just contunied to reboot....all the time..one the gigabyte it would almost make it to the desktop and then it rebooted...in the shuttle it just rebooted constantly...
the other chip started just getting errors in my wndows until i rebooted it one more time..and then i got the black screen of a64death...
so they are fun to play with...and yep i have depleted my funds...i got caught up in getting one to bench with,,and the mader i got the more determaned i got to get one going...and the more i purchaced....
after my chips come in next week i want to weed out the weeker ones and keep one setup...sell off the rest at reduced price to get something back..
and yes...the chipset voltage is the only thing the chaintech has that the shuttle and gigabyte dont/
so i am leaning towards high chipset voltage doing it...since that is directly connected to the hypertransport..
Ive had one died on me and I think its the same reason as MrIcee, toasted memory controller.......at that time I was using the stock cooler and 1.7v and ran my vdimm to around 3.5v..... during 3dmark, it died on me....... my second one with my chiller cooling it is still alive and has done benches at 4v vdimm and 2v on the vcore...... if you guys are planning to run some high vdimm, make sure your cpu is cooled well.......
It´s not a cooling problem I guess. Mine was cooled by promy @ R404a.
looks like there are good and bad chips...
Remember, that the 3.3v rail is generally used for the system I/O, I'd guess a high 3.3v rail could easily kill the I/O of the chip, I.E. the memory controller, makes sense to me.
yeah, much like high vDIMM. Also with the chipset being linked directly to the Hypertransport bus, high chipset voltage can cause problems, as bowman has proved.Quote:
Originally posted by Walrusbonzo
Remember, that the 3.3v rail is generally used for the system I/O, I'd guess a high 3.3v rail could easily kill the I/O of the chip, I.E. the memory controller, makes sense to me.
*Interesting thread, hits subscribe button*
I'm sceptical of High VDimm.... VDimm should only affect the RAM's voltage, I can only think that on the boards that people have done VDimm mods it must be affecting another voltage, I.E. Hypertransport.
Definitely though, high chipset V, high hypertransport V and high 3.3v, DONT DO IT :)
Well, so far, it seems to safe to say that it's not the wisest thing to raise the chipset voltage or the 3.3v rail.
But one thing none of use will ever stay safe on is vdimm - no matter the risk, lol. There some guys running extreme vdimm with no problem yet. I'm thinking this may have more to do with the stepping on the 3200+ than we think.
I'm also very curios about the 3400+. I know not many have this chip yet, but it doesn't seem anyone has killed this one yet. Has anyone used the 3400+ with a high 3.3v, Vchipset, & vdimm?
LUIHED, was there a difference in stepping between the one you killed and the one you currently have that is running strong along with a 4v vdimm?
Has anyone experienced this with the FX?
YEP i killed one 2 days after they hit....:(Quote:
Originally posted by BMORIN
I'm also very curios about the 3400+. I know not many have this chip yet, but it doesn't seem anyone has killed this one yet.
.
I asked about the FX wondering if it's the memory controller that's burning up.
Quote:
Originally posted by Jeff
No offense Bowman but... maybe you should try a new hobby. :stick: ;)
...[/i]
you got that right.......i sure do need to go back to bass fishing...but spent money on that too.;)
I still do both but it is realy stretching the budget! I'll trade you a guided day on Buggs Island for one of those dual evaps!Quote:
Originally posted by bowman1964
you got that right.......i sure do need to go back to bass fishing...but spent money on that too.;)