Jump to content

smids

Members
  • Content Count

    102
  • Joined

  • Last visited

About smids

  • Rank
    Member
  1. I don't know for sure, but could it be related to unstable RAM at all?
  2. I was talking about the difference between 2x and 16x. The bottom will default to 2x unless he sets the jumpers. There is virtually no difference between 8x and 16x - I'm insane, but I'm not that insane!
  3. No It depends on the card how bottlenecked it is . 9600 from a 7800GT is very hard!!! Anyway, 8x is fine for any graphics card, I was referring to x2 which necks top end cards. Also, this is what I have seen on another forum. One guy had very low 3DMarks, change slots and his 05 score went up by 2000, that is where I made my quote from. OK, it's not scientific but you get the picture. I think the point is de facto you will lose some performance in the lower slot, whatever the figure is.
  4. There seems a good RAM table on this. I've had a chance to play with it and can say it does indeed clock as well as my 704-2BTA did (actually I lost 5mhz!! ). 15h prime stable @ 10x280mhz. 11x went out of the window with this BIOS, however 10x was unworkable on the 704-2BTA so they have just swapped!
  5. It's hard to say. There might be a general concensus that a BIOS is a good clocker etc but it really depends on your own hardware. Personally I found the 623 an excellent BIOS, however, the 704-2BTA and the 329 (2006 latest) are better. I don't know which of the latter two is better but for me, they both were more stable than the 623 which I had RAM issues with on all except 623-2.
  6. You need it connected according to DFI specs. Just buy a small converter - should cost only a few $ to convert molex to FDD.
  7. The nF4 ones should be yellow, but I'm not sure on the SiI ones on the expert. EDIT: Oh gawd, they are all yellow . The 4 nearest the fan are the nV ones .
  8. Hey Scoobie. I still find that the 704-2BTA is THE best O/C BIOS for this board (excellent RAM tables etc) but this one is better than 623 which didn't get anywhere near 2.8 when I used it. Still priming @ 2.8 - about 5 hours so far.
  9. Following on from my post above. Strange behaviour with this BIOS and my X2. Before I used the 11x multi x 255 to get my 2.805ghz stable 16h prime. Anyway, I tried a similar thing with this BIOS - now not all BIOS's clock the same, I know that but weird results. It failed prime after 6.5 hours with 11x255 on a 9:10 divider. Memtest didn't detect the RAM frequency properly and only Everest could do so - even CPU-z was wrong. It should 215mhz on a 9:10 from 255mhz - clearly wrong, should have been about 229mhz. Anyway, I thought I would use a conventional divider in 166mhz (5:6) and this was detected as 200mhz. Everything said it was 200mhz, even Everest. This is wrong as it should have been 213mhz. Now I know dividers do not show exactly the right frequency but this is 13mhz out. I primed again (same 1.49v as the 704-2BTA) and it crashed sometime after 10 hours (complete lockup). Now I'm running the 10x multi (10x280) and it's priming away however things to note: -no longer do I suffer from the very slow boot (even at stock on the 11x multi, it would take ages to show the boot screen [logo disabled]. Having dropped onto the 10x, it boots without any delay. Odd, and no longer does it search for my optical drives before even showing the boot screen, which it did before. Also, all RAM frequencies are now detected as they should be on any divider. Anyway, I hope this helps someone out - it's not scientific, it's not conclusive but it is my finding.
  10. It's a weird bug thing. I think I read at Xtremesystems (though don't quote) it affects the E4 cores far more than E6 (quite how so, I don't know). I have never experienced any gaming problems with my Toledo (E6) with the /usepmtimer switch, but I installed the hotfix anyway and still see no problem. Games I play: HL2, CS:S, DOD:S, FarCry, CoD2, UT2004 umm those are the current main ones.
  11. *Cough* Bull**** *cough* I've had an X2 for almost a year now and have not seen any problems in any of the games I play on a DC. As long as you have the switch /usepmtimer in your boot.ini, then you will be fine. Windows does a very good job of assigning processes itself.
  12. Actually MCE is Pro based - minus one or two things. 6.70 driver package is what you should be using.
  13. Hmm, perhaps the RAM took a hit of ESD and died? Have you memtested them since? Also, try removing the PSU connectors entirely and re-attaching them all - all 4 mobo connectors connected properly? I saw one guy on another forum who lost his overclock after recasing and it turned out one of his power connectors had not been put back in properly. One big thing to check, remove the mobo from the case, make sure nothing is shorting it and replace. Are you using spacers? Shorting out of something would cause that I'm sure.
  14. Have you tried the 623-3 official BIOS. These boards are EXTREMELY fussy with memory and different DIMMs. I'd try that first and then see if the problem persists.
  15. You don't mention which port disconnects, nV or Marvell (perhaps PCI card?).
×
×
  • Create New...