Ok i have heard both opinions on this and want to let you guys duke it out so we can see the real reason. is the lock a. b/c of the proc. b. b/c of the mobo and the dfi fixes it???
(sounds like mobo problem but i just want to clear up any remaining doubts)
I haven't come across any posts wherein a user is running a DFI nF4/Winchester combo at sub-zero temperatures. I'm curious to know this as well.
My winnie worked on sub-zero with MSI NEO2 (after a bios update) and now with DFI SLI-DR it doesn't... only with tricks so it can't reach -20ºC
->Dual 2.8 Xeon * PC-DL Dlx * 2gb Kingston DDR400 * Connect3D X850Pro@XTPE
HEATWARE
hmmm thats annoying.
so i guess we dont have an answer yet.
Last edited by JSU; 03-03-2005 at 10:12 AM.
i need to know the same thing....
i have a 3000+ and i want to phase change it on a neo2 and my dfi. air/water just isnt enough for the scores we want.... i might have to buy a newcastle
Dell Studio XPS16... no desktop
yes i have AIM, yes you can send me a message. EvilSpork3 i dare you.
I've tried 4 winnies 3500+ in 4 diferente mobos (Giga NF3U, MSI NF3U, MSI NF4U and DFI SLI D) none of them work with my vapo ls.
have you updated the bios's??
if hes had that many mobos and that cpu i would assume he did.Originally Posted by JSU
Dell Studio XPS16... no desktop
yes i have AIM, yes you can send me a message. EvilSpork3 i dare you.
any other opinions???
my dfi board works great with subzero. it even displays the temp correctly. on the evap my temp is -40C and the mobo says the chip temp is -27C which is believable.
i believe OPB posted an updated bios that fixed these issues with winnies. anyone test that bios out?
this is starting to sound good
For the DFI's??? Where?
->Dual 2.8 Xeon * PC-DL Dlx * 2gb Kingston DDR400 * Connect3D X850Pro@XTPE
HEATWARE
no, it was for the old MSI
http://www.xtremesystems.org/forums/...ad.php?t=47840
which makes me think it's a problem with the bios (well, actually, the hardware that reports to the bios, but the bios can be changed to fix the error).
I think the problem is that the temp chip that recieves data from the thermister on the CPU does not have a table to look up values for negative temperatures, causeing it to output weird temperatures such as +255'C. The bios then reads this and shuts down the CPU to try and save it, since it's temperature is so high. Just a theory though...
Sorry for late answer, yes in the neo2 also tried 1.5x that suposed to solve the problems.
The problem its the cpu, and not the mobos, Newcastle works fine on sub0.
I think the only way to put them to work its dont go under -10, at this all of them work.
Last edited by MJRL; 03-04-2005 at 09:26 AM.
thats more or less exatly whats happening i think. but its the thermister in the cpu outputting bogus data
Dell Studio XPS16... no desktop
yes i have AIM, yes you can send me a message. EvilSpork3 i dare you.
The answer from a AMD rep is that its a mobo problem and not the wenny.
then i say:
on with the freakin bios updates!
Dell Studio XPS16... no desktop
yes i have AIM, yes you can send me a message. EvilSpork3 i dare you.
If i was a rep from Amd i would do the same, and the problems with prime95 are caused by the software...
Why the newcastle work?
Posting Permissions
Reply With Quote
Bookmarks