Official MSI P7N Diamond (780i) Discussion/Review/Overclock/Guide/BIOS Thread

[BababooeyHTJ]

That xfi card can indeed cause issues. I tried it in the last slot and it doesn't play well for me there. I use the xfi card that came with the P7N in another motherboard now and I'm using a cheap usb audio adaptor that works fine for what I need. BTW apologies if I seemed harsh earlier or offended anyone but there are a lot of answers to some of the most often repeated questions in this thread. I'm going to put an e8400 in this P7N later today and try some high fsb. All my quads hit a wall at anywhere from 450-470fsb. Hopefully I'll have screenshots. Have I said I like pics?

Nice! Please post some screen shots. I havent seen many wolfdale results on this board. Im sure I helped trigger the rant quite a bit myself. Thanks for all the help (seriously). Ive read through most of this thread and learned ALOT, but I just havent seen very many wolfdle users on here.

[Fiskbit]

malik22: I'm currently using using the 1.2B1 beta, although I think they're up to 1.2B2, unless they've put up a new BIOS and no one mentioned it. I'd recommend going for either of those, as they fix various issues with multipliers, stability, and settings (voltage settings are now displayed in voltage rather than cryptic numbers). Chances are the newer the BIOS the better off you'll be. I think there's also a video corruption fix that's implemented on 1.2B1 and onward which sounds kind of important.

panheimer: I haven't changed any RAM timings yet and wasn't planning on it until I've overclocked stuff and got things running stable, so everything's running at stock settings (save RAM speed, which is at 588 for 1:1 with FSB). I've been looking in Everest for information on RAM settings, but can't find it (I find Everest to be a really confusing program, and as I'm using a trial version, parts of it are locked. The memory benchmark also appears to be locked or broken for me, as its colors are messed up in such a way that it's unreadable). Would a timing issue like this present itself as an error in MemTest86+?

Thanks for the help.