Anyone know whats been updated?
I will try this out when I get time, perhaps tomorrow. :yepp:
Printable View
Does anyone else have problems with the built in Wifi on this board? It is super slow and I am even using the newest drivers off of the Asus website. I even tried a different connection other than mine (someone in the neighborhood) and its still worse than molasses. I connected my Abit Airpace Wifi card and all is good now. Is this a problem with all the P5K-Es or is it just mine?
No problem here, not as fast a a cabled connection but not that slow.
I also have 1004 but i have a feeling the vtt and GTL function in bios do nothing.
Changing these should provide some stability which i failed to find without raising Vcore.
Do you have the crappy Asus Wifi software from the CD installed? I can't remember what it's called but it's horrible for performance, if you have it installed, remove it.
After that, In Device Manager, right click on "Wifi" then "update driver" from the CD. Then use Windows to manage your wireless, it works much better.
I done the same, and I had the same result: no effect on stability..but : with IP35pro, I had oc problems with every ram modules, and I adjusted the ddr2 ref voltage( i.e NB reference voltage ), and with this I managed to overclock them about +50Mhz. It would be nice, that adjusting gtl refs had such effect on oc-ing my q6600:) but these BIOSes are like birdshxt on a black shoe.
I have a problem with my O/C'ing. I have a P5K-E WiFi Bios 1002 and one Wolfie E8500.
I do not manage to exceed the 440 of stable FSB!!:mad:
However I very tested: vNB with 1.55v and vSB with 1.20v as well as many adjustments...
I feel that my E8500 can go up very high since I boot to 4500MHz to 1.48v.:)
Moreover I am not stable with 7 * 500 same with 1.7v for NB.:shrug:
It is possible that this evening the bios 1002 because with the 0502 I went up rather high in FSB with my 65nm.
What think about it?
Thanks
Testing 1006 so far so good.
I'm curious, is it higher or lower (or trial & error) on the GTL that allows
you to turn down the vcore some while keeping the stability? I have it set
to the lowest value of 057x and I have been inching my vcore down and im
still stable.
Well this may be too soon for conformation but I think the GTL may be working.
I bumped my vcore down from 1.480 real to 1.456 real with GTL at 0.59x, and
so far stable. I actually bumped it down to 1.430 at one time and it crashed
immediately in prime95, I then bumped the GTL up to 0.61x (I think) and It
actually ran Prime95 for about 30min and then one core got a rounding error.
So maybe give it a try, I have not seen any negative results with 1006 as
of yet.
thanks
Cpu @ 4180Mhz (9.5 X 440) now
strap to 400 ? (9.5 X 400?)
NB @ 1.70v is any risk too important, to roast not?
No relation with the bios 1002 according to you?
Not to be able to exceed 440 stable FSB it is not current!
http://images.dr3vil.com//files3/84/e8400-1.jpg
Just bought a P5K-E from Newegg last week. It shipped with 0906 BIOS, I'm currently running at these settings:
FSB: 434 x 9 =3.9Ghz
vcore: 1.3875 (bios), in windows reads 1.28 (vdrop = .1, no vdroop at all)
everything on auto
except
vdimm: 2.1v
dram settings: 4-5-5-15
I have 2 problems.
1st, I can't seem to get it stable at 4Ghz, at least at under 1.4v in BIOS which is the max I want to give it.
2nd, and this is the biggie. I have sound popping, cracking noise.
I though maybe it was an issue with my old Audigy LS pci soundcard, so I tried the onboard soundmax & had the same issue. So I thought maybe the PCI bus was "dirty" and had some issue with signal distortion, etc.. So I got a X-Fi PCIe card and I'm still getting the popping noise. I tried using my speakers, headphones, etc... still the same issue. :( WTF, could it be that would affect 3 different soundcards? (Audigy PCI card, onboard Soundmax, and X-Fi PCIe card)
Could it been my powersupply or something supplying a dirty power signal?
Me also I have big problems with the bios 1002.
1004 works great cpu stable at lower voltage
New bioses, new problems: AI Nap doesn't work and errors in memtest... waiting for new one.