from what i hear Ivan, its just the luck of the draw. but i think week 41+ have higher chances
Printable View
from what i hear Ivan, its just the luck of the draw. but i think week 41+ have higher chances
Can someone explain to me why when using .5 multi the Hyper transport
doesn't increase while upping the htt speed. In bios i set 4xhtt and i set my
memory to run 333mhz , using clockgen in windows i set 10.5x250htt but my
HT still remains 800 instead of 1000, 4x250htt. Right? Could it be that .5
multi locks the HT so it gives u the ability to only oc your memory and cpu
frequency.
plz need help :(Quote:
Originally Posted by j0j0
My NEO2 just went up in flames! Well, a small part of it only. A MOSFET next to the CPU socket to be exact.
Last night, I set my FX-55 (watercooled) to 2.8Ghz with 1.8v vcore. Played games for a few hours with that setting. I didn't switch off the PC and when I woke up this morning it was off. Went I switch it on, flames was shooting from the MOSFET! I saw it because the mobo was right next to me. Luckily the NEO2 was the only casualty.
My question is, what could have caused the MOSFET to burn? Vcore too high? Inadequet cooling on the MOSFET?
Next to the cpu, where exactly ???
Got any pics ?
I wouldn't mind if my board blew up... damn thing isn't stable @ 2.5Ghz and over :(
That's what you get with a 0409 :(
Hello Xtreme! So this is my first post here but I've read this forum for over 2 years :).
I have a problem with my 6 day-old board; when trying to put more vcore than 1.55+10% the comp won't post till end, it freezes after showed memory speed and settings. Why does this happen?? In windows with corecenter I can up vcore till 1.8 and it is very stable, although it does not help me very much to get higher mhz. I use 1.41mod bios, same problem with 1.36b bios. Is there any other program than corecenter to up vcore on windows? Corecenter does the upping upside down :D but who cares, but upping the vcore at the xp login automatically would be great. Now I'm stuck with 1.65vc.
I also noticed today that the common procedure to get the comp to boot by pressing Insert-key when booting works with Neo2 :). For example today I had to clear cmos every time after I tried over +10% but after I tryed the insert key I booted straight to safe mode, nice :)!
1. The first thing I would like to say is less of a question, more like an observation.
I have a 3200 Winchester /w Corsair HydroCool 200EX setup.
Prior to this setup I had a 3.0e Prescott P4 @ 3.5GHz.
Intel Setup Temps.
Idle on Water Block 26-28c idle
Idle 34-37c
Load 42c
Now with my A64 setup.
Waterblock idle 24.5-26c
Idle 40c
Load 43c
It almost seems like my CPU temp is almost 9c off?
I had/have Artic Silver 5 applied to both setups.
2. I have MBM installed per instructions on first page. I have 3 temps listed by having my mouse pointer hover over the taskbar icon.
Case 21c. CPU 40c Sensor 30c
What is the third reading of?
3. I tried seeing the hidden features in my bios per these instructions.
In the bios press and hold Shift+F2 and then press ALT+F3 to unlock "hidden" features within the BIOS
I don't see anything else in the bios? BTW, I have 1.3.
Thanks for any help
HAving huge problems...
I'm on bios 1.51 and ocz powerstream rails are like 12.20v on the 12v 3.35 on the 3.3 line and 5v rail is even 5v. I don't have a multimeter to test, but this is what I get from the bios, I'm not sure how acurate it really is. my cpu temps are around 35-39c load. 3 sets of tccd all work fine in memtest. but as soon as I overclock past stock and go into windows, problems occur. For example I tried 2.6ghz and lowered ht link to 3x. agp/pci lock is set at 66, but it seems to lock fine in clockgen. I am using sata 3and4 in raid0, and that seems ok. I ran prime 95 at stock almost 18hrs on small fft torture test, didn't get a single error, but I ran the same test after setting to 2.6 and passed up to test 3 and then system reboot and windows xp screen just hangs until I hold power button. Normally you would get an error and prime will automatically stop, but in this case system just randomly reboots itself. I am really out of ideas here and I'm begging for advice. neo2 is week 41 on nf3 chip. could this be a bad bios? or is board just shot from too much ddr booster? I never ran booster over 3.5v mostly it was between 3v and 3.3v. cooling is not really an issue here, so it's either bios, power flux., or faulty board. I thought it might be the cpu at first, but how do you explain 18hrs of prime with no errors f the cpu was at fault? i tried low vcore and vcore up to 1.72, fastwrites is off, everything else like nv/ati is disabled, I read the msi 939 thread and I'm following all the advice. I also lowered oc to 2.4 and 2.5 and adjusted ram voltage and vcore acordingly.
__________________
Necrosis, this motherboard does not report accurate tempratures
That is what I'd gathered so far by reading this thread, and various other sources. It just would be great to know by how much it really is off before I start OC'ing. I just put this thing together this past Sunday. Here are the rest of my specs.Quote:
Originally Posted by aonic
1 Gig OCZ PC4400
EVGA 6800 Ultra
Seagate 120 SATA x2
A2 ZS
Pioneer 108
LiteOn 48x24x48
Toshiba 16x
OCZ PS 520
and other odds and ends
I think maybe on the safe side I will adjust MBM by 7-8c.
From what i heard you have to set 67mhz on agp to lock it.Quote:
Originally Posted by trans am
idk if thats true or not, requesting conformation, but 1Mhz above spec doesn't like it will do much damageQuote:
Originally Posted by The Virus
Quote:
Originally Posted by DevilsRejection
Thats impossible, 1mhz more will not damage anything.
devilsrejection.. That is really quite funny. MSI made it so that it locks it when you set it to 67mhz. Its part of the way the board works. You can run pci bus a few mhz out of spec and it wont do anything. IN FACT.. the fluctuation allowed by the crystal that generates the mhz is probably within 1mhz. if you notice with cpuz sometimes your fsb will go up or down by .5 or so. well 1.0 isnt that far off.
Anyway, to quote the good doctor "its all within respectabe limits"
Guys, bios is 1.51. No need to set at 67 anymore to lock!!! if you don't believe me you can try it yourselves with clockgen.
you mean bios 1.51 beta? so how do you set the lock then?Quote:
Originally Posted by trans am
edit: where do you get the latest bios's
I got my AGP lock @ 66mhz on 1.4 :D
Can anyone confirm again , what Bios can lock PCI/AGP at 66Mhz ??
any bios after 1.37 I believe.. look in the 939 tips and tricks thread for the bios'sQuote:
Originally Posted by xs64
Quote:
Originally Posted by trans am
1.41 here, no need too, maybe newer stepping mobos don't need 67
Small FFTs only stress a small part of the CPU (I fergit -maybe just the float point parts?)
Blend starts by stressing the memory controller (1024M) and memory subsystem. 18hrs of small ffts means nothing (except that it can run 18hrs of small ffts....)
When I do custom, I go from 1024-4096 so as to burnin the memory subsystem in a more/different way than memtest can.......
(No I can't get prime to do it right @ 2650 either so there! (need nyeah smiley) :brick:
MSI K8N Neo2-939
TIP: bios 1.36b and 1.37 and modded variants seem to work best for bh5/bh6
Is bios 1.36b the same as 1.36 ?
I do not see a 1.36a :confused:
Dudes, the Insert procedure have today again saved me more than 10 cmos jumper clear hulabaloo does it work with your comps too? If it does work it should be a tip at the beginning of this thread as there is nothing about it written in the manual ;).
Saulous
Pretty much common knowledge :) But I don't see how adding it would hurt.
Gee.. finals be over, new CPUs be in-stock!
ALL
Will this board work with my 550W True Control?