The fix for entering bios setup was fixed by me and cd1986 before murdok also. The latest Nfm bios has the fix. Funny that he ignored my post when i first posted the issue weeks ago. :p:
Printable View
The fix for entering bios setup was fixed by me and cd1986 before murdok also. The latest Nfm bios has the fix. Funny that he ignored my post when i first posted the issue weeks ago. :p:
I just read your pictures in msi user forum. Strange i dont get those issues at all maybe its the venice ?
Anything over 1.45 doesnt have an effect maximum setting for my san diego is 1.45 +10 percent which gives me 1.63 volts.
The setting is different in corecenter than the reading but thats because of the newcastle venice thing. Thats why newcastles can use 1.7 volts instead of 1.6 volts with the same bios.
Also maybe its the bios i havnt used murdoks version try using nfm's 1.98 mod and see if its the same.
@ Curroption lol you should of listed the voltage settings from about 1.4 to the max we don't really need to know about vid settings under 1.4vcore.
Also has anyone noticed that under load the vcore goes up? quite a bit also, clockgen says something about startup vid... and max vid... seems like under load vid jumps up another 50mvs.
It was really late and I was a zombie when I listed the settings. The lower VID settings can be useful when using over 10% overvolts.Quote:
Originally Posted by 4rory
I've noticed that vcore jumps a little bit when the cpu is under load. I don't trust Core Center or any other software for reporting voltage. If you want to be sure what voltage you're putting through your core, then use a digital multimeter....that's what I do.
All the 1.9 beta and mod BIOSes seem to be giving me really bizarre temp readings. I've seen some mention here and there of this here and there, but i'm not sure if people are having these issues specifically with the 1.9+. Could be a CPU issue? Dunno, I only get it on overclocking attempts - but I haven't done a lot of non-OC attempts yet either, to isolate.
I get negative temps, and sometimes crazy high (like 115C+). water lines seem warm but not hot, and the chip runs when I get these readings. don't know what to make of this. any ideas?
here is a screen
1.9 still in bios, no other bios offically supports x2, I'm sure if your contact is fine that ur perfectly safe just a software issue,
@Corruption where do I test with dmm on the boad for vcore?
weird. You get these readings with other programs as well like mbm or speedfan ?Quote:
Originally Posted by angra
haven't tried mbm or speedfan yet. Will do so if it would be helpful for diagnostic.
everest home and corecenter report the same readings.
I am becoming tempted to try and embed a thermistor between my cpu and waterblock to see if I can tell what the actual temps are, but I am not so sure it's a good idea to try something like that - afraid uneven pressure might risk damage to CPU...
The 2 pins on the cpu that transmit core temps are on the very edge of the cpu, it's pretty easy to attach wires to them, put the wires in the socket and install cpu, but you have to use very thin wires, like the ones on thermistor, could try cutting off the sensor and using the wire. This way you get core reading, maybe it's the sensor on the core thats bad, then you could probably rma it.
But you say its only with 1.9 version bios's? 1,8 gives constant temp readings?
There is definitely some sort of issue with the sensors and the 1.9 bios as i cant get any readings in the bios at all i have to use a modded bios to remove the options from the bios or the bios setup wont even load.
All the windows based temperature monitors give me constant results though.
Wizzard has just added a neo 2 profile to systool which gives the most accurate results from the sensors try and use that see what happens. systool
here it is under 1.8.
I am not 100% positive it doesnt happen under 1.8 yet. I had a strange unstable boot when I rebooted after flashing back to 1.8. I will run @ stock speeds and 1.8 for a while to see if I get any odd behavior.
screen under 1.8
will try systools shortly.
the attachment is speedfan, running under 1.9b8 (leftover attachment from aborted post earlier)
well it did it under 1.8
I guess all signs point to bad CPU at this point, huh? I'll try swapping my venice back in to see if if that clears things up.
I can not for the life of me figure out how to get the hidden bios up. I've done the whole shift +f3, then alt +f2.
I am running 1.8 offical
Hye guys, im purching one of these in two days and a 3000+ vience. Ill report back with my problems!
- Michael.
hey guys I have a question, since I rma'd my cpu to AMD I was wondering how a 4000+ clawhammer would be (since they're out of stock of any sd's) also what about a 4000+ San Diego? I heard the lower multipliers were locked?
I'm thinking of just getting the 4000+ clawhammer and either using it for awhile or selling it and just buying another 3700SD
The lower multis arent locked on the 4000 sandy because ive seen posts with people using lower multipliers.
I wouldnt personally bother with a clawhammer because it wont clock as well unless your using a cascade or something:p
cant you get a refund and buy a 3700+ sandy else where?
AMD doesn't do refunds, also I was wondering about a 4400+ dualcore, how well have those overclocked?
what I really think I'll do is just sell the 4000+ clawhammer from AMD since it'd be new in box and just buy a 3700SD from newegg again
Quote:
Originally Posted by angra
All your temperatures are messed up though not just the cpu. Id suspect the motherboard sensor rather than the cpu. I think it could be that the bios messes up the sensor rather than breaks it as i have had issues sometimes when i flash a bios.
To cure it i reflash using winflash clear cmos take out power lead for at least 30 seconds boot into windows and flash again if it hasnt cured it.
The dual cores seem to clock really well. Similar to the san diegos in clock rate. If you can afford it.Quote:
Originally Posted by uniacid
Ask for 2 x 3200 venice cpus find the best clocker and sell the other maybe :p:
I am astonished the you fellas are even trying an X2 or San diego with this motherboard. the new mobo's are the only ones that are gunna work.
This board is never gunna work properly with the Venice san diego or X2. no bios can fix the issues as they are hardware related not software. A bios can only mask them or work around them to a certain degree.
that being said i have a simply question.
Clockgen allows you to run the 183mhz memory which is the 9/10 divider that DFI uses.
We all know that that value in the bios is labelled as reserved. so why if clockgen allows it hasnt anyone actually enabled it via a bios mod ? I've seen the bios hex. and it says *reserved* yet the ability to make it 183 is there.
now somehting funny is that the 1.98beta mod bios(im not sure if the unmodded beta has it) actualy has 213 233 and 250 mhz in the dram freq, lol thats funny cuz its worthless. The mobo doesnt support preset ram over DDR400. yes you can raise the freq via HTT but not force the ram to run at 250mhz if its ddr500.
mine is ddr500 and i set it to 250mhz. POST says DDR500 but once you get into windows and or memtest its 100mhz. actually anything over 200 defaults the memory back to 100mhz.
I hate the way this venice is treating the voltages im setting in the bios i never know what its set to unless i set it reboot and go into PC Health and look there.
im not brave enough just yet to go attaching sensor wires onto the chip lol but does anyone have a picture of this ? id like to atleast see it.
also same for checking vcore and vdimm with a meter. im not much for using a meter as i never have had the need although i do have one. can anyone provide a link to a "how to" for doing this ?
i sure hope there is a way via a bios mod to address the venice issues i really cant afford to upgrade my mobo at this time. :\
which board are you using/would you use with a X2, Lestat?Quote:
Originally Posted by Lestat
I don't know of too many mobo that have come out since the X2 did. I can see what you are saying, but it's not immediately obvious what mobos "should" work with x2 and which shouldn't.
my neo2 has been great with the venice.
I have a san diego running at 3ghz on my neo 2. Pc is prime stable pc never crashes in what way does it not work?Quote:
Originally Posted by Lestat
Lestat maybe you messed up your vcore regulators when you were pumping 12.5 volts into the 12 volt line.
http://www.swjka.com/k8nneo2bios//vcore.jpg
http://www.swjka.com/k8nneo2bios//Vddr.jpg
Just tested vcore with dmm, wow I was tense lol 1.6 set in corecenter, 1.450 +5% in bios cpu-z shows 1.524 idle to 1.544 Load dmm shows 1.560 idle. Whats safe for venice again on air 1.65? 1.75 kills?
You guys know the earliest revision bios that will run venice?
i had tried all the way back 1.36 it works.... any earlier i dunnoQuote:
Originally Posted by urbanfox74