does anyone know where to put the heatsinks that came with the board?
I'm imagining it's the little one's to the right of the cpu socket, looking down from top of board.
Printable View
does anyone know where to put the heatsinks that came with the board?
I'm imagining it's the little one's to the right of the cpu socket, looking down from top of board.
Put them on the mosfets near the CPU and mosfets near RAM. A nice touch for a "bargain board"Quote:
Originally Posted by okra
Been running mine for about a week now. I finally got my Patriot 3200+XBL. I haven't really pushed it, but have been running the RAM at 250 2.5-3-3-10 @ 2.7v for the last couple of days. CPU is at 2.5GHz @ 1.4v.
great, what's that cpu & stepping -- the good "surprise you got" @ 1.35V?Quote:
Originally Posted by SPQQKY
3200 .09
CBBID 0451MPM
My chip was cursed the minute I got it! CBBID and week 51. I guess I got lucky because with all that was against it, it turned out to be a good cpu.
Edit: Any good A64 Tweaker tips for the TCCD?
I just got one of theseQuote:
Originally Posted by SPQQKY
3000+ Retail
Local Shop
CBBHD 0449 MPM
Maybe good? My others are the dreaded CBBID
I can't seem to flash to this BIOS in DOS. I tired and ended up with this:Quote:
Originally Posted by okra
Award BootBlock BIOS v1.0
BIOS ROM checksum error
Had any problems with this BIOS?
Quote:
Originally Posted by TheReaper
Did you get a corrupted BOS with this message?
Award BootBlock BIOS v1.0
BIOS ROM checksum error :confused:
Hi
Well i tried updating mine 2 and got the same error and now I cant revive it it just says "unknown flash type" every .... time I try to flash it, anybody here who knows what might be the problem ?.
Menty
Hi
Well just a little update I hotflashed the chip in an nforce 2 board, now its fine again :), but im gonna make another chip before trying flashing this board eva again :).
Menty
i used the magic bios utility to flash it in windows, I hate flashing in DOS.
The DOS flash with the 2/22/05 BIOS always has failed and corrupted my BIOS. I had to do this to fix it:
http://forums.windrivers.com/showthread.php?t=64279
How did you do that?
Quote:
Originally Posted by Mentaly
Hi
well I started by booting up the nforce 2 board, booted to DOS, and removed the original bioschip put in my bad chip from the Epoxboard "while its still powered on and in dos", had the newest awdflash and the da3j5111.bin from epox ready on floppy, used these parameters to flash "awdflash8.exe bios.bin /f". the it all worked out for me again.
Menty
Quote:
Originally Posted by windwithme
Miss those great screenshots!?
Epox support was a joke, so I RMA'ed my board back to Newegg. I feel bad doing that, but I don't want to deal with epox's support. I'm hoping to get the new board next week.
Same board?Quote:
Originally Posted by TheReaper
Yes, I'll report back when it's installed. The first board ran great and was very stable. It overclocked very well too. Before the problem occurred, I did hear some faint popping and ticking. I thought it was a fan or something. It was running my fx53 @ 2500 (10x250) at the time with 1.7 vcore. The power mosfets and caps were smoking hot. Before that they ran pretty cool, witch supprised me. Their was no visible burn marks or bulging caps that I could see. That's why I RMA it.Quote:
Originally Posted by sauria
that doesn't sound fun at all!
I found I can run 2600mhz w/ this cpu in my 9nda3j, but needs a lot more voltage (1.5v to 1.525 v) than 2500 requires (1.375v to 1.4v). I booted into windows @ 2700 w/ same volts for 2600, it wouldn't bench, rebooted and found my Windows corrupted! :D
After reformat I'm back at 2500.
Thanks, Reaper. I look forward to your results. Did you have heatsinks on the mosfets?
Nope. I have some ready for it, but found they didn't run that hot. That was before things started to overheat tho.Quote:
Originally Posted by sauria
I see -- How do you lke this board in comparison to your MSI?
Can you explain wht the problem with this bug is?Quote:
Originally Posted by okra
Thanks! :confused:
yeah, it won't run 3d benches, turn it off & good to go.
Ok, thanks -- Auto would be "on"