P6N Diamond & SLI controller sanity check

what i would like is a sanity check please from community before RMA is done, i've already contacted both MSI and supplier and have RMA status enabled but before shipping would like to do an opinion from more professional/ experienced people here please
MSI reports that SLI controller is bad and to RMA... so ya i probably will but just want doctor 2nd opinions
thanks in advance!
testing past few days and having major problems with SLI.
mainboard: P6N Diamond MS-7320 v1.0 BIOS 1.2
processor: Intel Core2 Duo E6850
graphics cards: SLI NX8500GT TD256EH (x2) PCIx16 (both in white slots )
memory: Corsair CM2x 1024-66400C4 (800mhz, dual channel) (total 2GB)
drives: WD1600AA (?) SATAII 3.0GB (raid 0, hardware dipswitched)
power: rosewill RX750-S-B Xtreme 750W ATX12V v2.2 EPS12V v2.91 (voltages per bios in spec)
I have performed several tests including:
memtest86+ : 25 iterations on memory over 8 hour period = PASS
ntune stability test : nx8500GT (card #1) in pcix16slot#1 = PASS
ntune stability test : nx8500GT (card #1) in pcix16slot#2 = PASS
ntune stability test : nx8500GT (card #2) in pcix16slot#1 = PASS
ntune stability test : nx8500GT (card #2) in pcix16slot#2 = PASS
ntune stability test : card#1 in slot#1 & card#2 in slot#2 = FAIL (sli mode on)
ntune stability test : card#1 in slot#1 & card#2 in slot#2 = FAIL (sli mode off)
ntune stability test : card#1 in slot#2 & card#2 in slot#1 = FAIL (sli mode on)
ntune stability test : card#1 in slot#2 & card#2 in slot#1 = FAIL (sli mode off)
no overclocking
CPU temperatures ~22 celcius
SYSTEM temperatures ~38 celcius
GPU1&2 temp idle ~63 to 66 celcius
GPU1&2 temp stress ~72 celcius
all hardware tests ok, no power surges, power supply is adequate and in specs.
only problems occuring when both cards are in system and operate in either SLI or non-SLI mode.
all microsoft latest security updates applied
following hotfixes applied:
KB940105
KB936710
KB930833
KB932471
KB945149 (latest per request)

Quote from: BOSSKILLER on 07-December-07, 04:33:29
What kind of problems you have?
Have you tested in XP?
PSU details.
Latest drivers from Nvidia installed?
Power cables to both VGA's connected?
SLI Bridge connected?
Hi,
Answers best I can below:
Q: Have you tested in XP?
No, sorry.. I only have Vista x64 platform to use and test (license only )
Q: PSU details.
posted above, but here you go...
Rosewill RX750-S-B Xtreme 750W ATX12V v2.2 EPS12V v2.91 (voltages per bios in spec)
Q: Latest drivers from Nvidia installed?
Yes (data from dxdiag for you)
Driver Version: 7.15.0011.6375 (English)
DDI Version: 9Ex
Driver Attributes: Final Retail
Driver Date/Size: 10/4/2007 17:14:00, 4993024 bytes
WHQL Logo'd: Yes
Q: Power cables to both VGA's connected? & SLI Bridge connected?
Interesting point With this particular setup, these MSI NX8500GT TD256EH cards do not have SLI bridge and do not require power plugged into video card. SLI option has onboard bridge controller and is recognized by nvidia drivers and nTune control panel (i am actually able to enable SLI this way w/o a bridge) yes, I had to rub my eyes too a few time while researching this configuration.
Mainboard supports ATX 24pin powerconnector (ATX1) and a ATX 12V (JPW1) 8 pin connector. The power supply supports these types of connections to mainboard. I will need to reboot after this post and do a visual inspection of reported BIOS voltages for you though and will do so.

Similar Messages

P6N Diamond, SLI question: where does the 2nd card go?

As per title, I have a P6N Diamond motherboard with 4 video card slots (four PCI-e x16), two yellow + two white. I have a single GPU/card in the first slot as usual, but I got a 2nd GPU/card today. Where does it go so I could get 16x16 SLI? Manual is unclear.
2nd white slot (third PCI-e x16) or the yellow (second PCI-e x16) ?
I ask because this motherboard has non-standard color coding. Even the RAM slots are not color coded (channel-wise). Instead of A-B-A-B color arrangement on the RAM slots as every other motherboard out there, this motherboard has A-A-B-B arrangement.

Update: First of all, the case connectors on the motherboard are in the way for SLI purposes. They are too tall and block the insertion of the second card. On my old ASUS moterboard the case pins were on the bottom of the PCB, out of the way, but on this MSI motherboard they are on the side, lined up with the PCI-e x16 slot. Really dumb design! It might be fine for short video cards like 9600GT or similar, but for extended length dual slot video cards like GTX260 (which what I'm using) they are in the way, so much that the second card can't be inserted into the slot at all.
I spent two hours modding the connectors. I had to snap and break the plastic plugs, remove the metal pins and mod them so they are only 3mm tall, instead of 9mm. I know this motherboard is old so MSI couldn't plan for GTX260/280 and other long cards, but cards like 7950GX2 and similar did exist and predate this motherboard so there is no excuse for MSI for placing the connectors in that position.
Anyways, warning for any P6N Diamond owners: if you have extended length or longer dual slot video cards like GTX 260, GTX 280, and 4870x2 you will have problems with clearance and would need to do some severe modding or get a different motherboard.

Any News (MSI) P6N Diamond (680i) SLI Motherboard

Any one know about the release of (MSI) P6N Diamond (680i) SLI Motherboard

Quote
honestly, if it's not for SLI, I think I'll wait for ATI, ops, AMD RD600 chipset mobo instead.
I complete agree with that. Just getting bored with the Opteron system. I have an insider I am getting a e6600 from for 1/2 price this week, so I was looking at boards. Think I want to try the 680i over the 975, and while the RD600 looks like it will be a winner it's still a ways out.
MSI had stated end of December for the P6N and that time is upon us.
Honestly after the last purchase I swore I would never buy another MSI, but I kind of crave pain that way, after about a year of mods on this current board, and emails with the MSI BIOS crew I think the K8N SLI was the 2nd best Nforce 4 board made out there. Plus it gives me another forum area to read here beside the Nvidia, and overclocking sections.

P6N Diamond - 8GB of PC2 6400 - OCZ SLI RAM - OCZ2N800SR4GK

Hi folks, could someone help me here....
I'm not able to boot up when I install my 4x2gb ocz chips onto my board.
It will boot up with 6gb, but not 8gb. What could possibly be the problem with this? Anyone have a clue?
P6N Diamond
4x2GB = OCZ SLI Ready RAM - OCZ2N800SR4GK
Q6600 Quad Core
I think that's the relevant information.?

Please provide information about:
- current BIOS Version
- Memory Voltage set in BIOS
- Memory Timings set in BIOS
- Memory Frequency set in BIOS
- PSU specs
Is your system overclocked?
Is Spread Spectrum disabled in BIOS?
Have you tested all your Memory Modules with Memtest86+ to make sure they are alright?

Sli-bridge incl with P6N Diamond??

Ive just orderd a new mobo, P6N Diamond. And was wondering if the SLI-bridge is incl in the box? I cant find anything about that. Mayby a stupid question here for all tech-heads.....sry for that

Quote from: flobelix on 16-October-07, 21:10:52
You don't need to. As it is a board with a sli chipset MSI has to add a bridge. The reminder doesn't pertain to the bridge. Any retail MSI board with sli chipset comes with a bridge, no matter the area where it is sold.
Because nVidia don't ship SLI bridges with their cards.

New PC build w/ P6N Diamond - won't read DVD's?

The P6N Diamond, hard drive, memory, and OS are new. DVD drive and power supply worked fine in old system (yesterday!). Clean install of XP MCE on new hard drive. All MSI drivers installed off CD-ROM. Ran online updates till all hardware and OS were happy.
I just realized the DVD drive I did all the installs from reads CD's fine but won't read data or video DVD's. I checked Device Manager and the DVD drive is listed correctly but I noticed the IDE controller is listed as Standard Dual Channel PCI IDE Controller. It has Microsoft drivers loaded. Shouldn't the driver be from Nvidia? It's a stretch but I'm wondering if this could be a driver issue? I can put the old system back together to verify the optical drive works but it would be a real pain...

I was hoping someone with the same board would look in Device Manager and see what drivers show as installed. I can find drivers but I believe the P6N has a 680i North bridge with an older South bridge chipset and I'm not sure Nvidia made reference drivers for this combo. I noticed MSI lists system drivers by North bridge/South bridge combination.
I'll swap drives between a couple of my pc's when I get off work and see if the problem follows the drive or stays with the pc, then I'll probably try reloading drivers. It's either hardware, drivers, or OS and I really don't look forward hours of updates if I re-install XP.
edit: I got lucky, it was the drive.

P6N Diamond: RAID ISSUES!

Hi,
I recent purchased a P6N Diamond, no matter what i do (and yes the bios has been updated), when i enable the RAID on either the ports 1-5 or the mirror on 6 & 7, the motherboard comes up wit an error for each raid device saying "no enough memory to copy PCI option ROM", besides the obvious gramatical & spelling errors through out the BIOS and Manual hehe... this problem is really annoying me.
Heres some more info
1.Product Type: P6N Diamond
2.BIOS version: 1.2
3.External VGA Type: 7800GTX, 8600GS, 8600GS, 8600GS (4 video cards running 7 monitors)
4.CPU Type: Intel Quad Core 6600
5.Memory Type: 4x1G G.Skill (Dual Channel Mode, 2x2 Matched pairs)
6.Power Supply Type: 950w Thermaltake
7.Operating System: XP PRO
8.Problem Description: RAID ISSUE
Every time i enable raid in the bios, it says
'no enough memory to copy PCI Option ROM'
I require all the onboard LAN/Sound etc
and i also have 1xPCI IDE controller and 1xPCI raid controller for extra HDD space.
Please help
Thanks in advance;
Michael T

Copied from another site:
Quote
The cause of the problem is that in order to be PC Compatible, the Option Rom space is limited to 128K. This is true for any motherboard with PC compatible BIOS.
In the common configurations, a newer AGP card (such as a Geforce 4) will require 64K of option ROM space, so you have only 64K of option ROM space left to work with. Many SCSI, NIC with PXE, IDE RAID etc. can easily use another 40-64K of option ROM space.
By design the option ROM should shrink down to a smaller run time code after the initialization code has run. For example, some Adaptec cards will require 32K to initialize. Then they shrink down to 12K at run time; whereas some Geforce 4 cards require 64K to initialize and never release it. Please check with the device manufacturer for the latest firmware upgrade or ask if they have a smaller option ROM available. Again, this is a limitation of the PC compatible specifications and not a failure of the motherboard BIOS.
So it's the four video cards causing the problem.

P6N Diamond "Motherboard Resources" Conflict

Hello,
I just got my second P6N Diamond (First one was DOA) and I loaded Win XP on it and all of the updates from MS including SP2.
After I loaded the drivers from the MSI CD I noticed a few peculiar things in the device manager:
The floppy disk controller showed a yellow exclamation next to it, even though I had disabled it in the BIOS. I have since disabled it from within the Device manager
There were yellow exclamations next to both NVIDIA nForce Networking Controllers
There was a yellow exclamation next to Microsoft UAA Buss Driver for High Definition Audio. Under properties it said the following:
"Your computer's system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. (Code 35)
Click Troubleshoot to start the troubleshooter for this device."
After looking through the device manager I found that the System devices/Motherboard resources item had the following conflicts:
Input/Output Range 2D00 - 2D3F used by:
NVIDIA nForce PCI System Management
Input/Output Range 2E00 - 2E3F used by:
NVIDIA nForce PCI System Management
Input/Output Range 2F80 - 2FFF used by:
PCI standard PCI-to-PCI bridge
I then went to MSI (http://global.msi.com.tw/index.php?func=downloaddetail&type=driver&maincat_no=1&prod_no=1168) and downloaded the latest nForce and X-Fi drivers.
The nForce drivers loaded fine and I rebooted, I then tried to load the X-Fi drivers but got the following error message:
No supported device found
Went back into the Device Manager and still had the same yellow exclamations, minus the floppy since it is disabled and shows a red X on it. I have updated the BIOS to 1.2 and still no luck.
Can any one help me get my NICs and my sound running? Thank you.
Here are my system specs:
CPU: Intel E6850 (not overclocked)
RAM: 2 x 1GB OCZ DDR2 PC2-6400 / 800MHz / NVIDIA® SLI™-Ready Edition / Dual Channel
Motherboard: P6N Diamond (1.2 bios)
Hard-drive(s): 250GB (WD2500JD)
Video: EVGA Nvidia 7800 GT
Power: Thermaltake 700watt
O/S: Windows XP

Thanks AaronYuri,
I clicked on your link but it was dead. I did do a search for the file name and found it. Installed it, rebooted my PC and I still have the same problem. Following is a link to an image of my device manager.
http://www.badongo.com/pic/1506438
Here is a another link http://www.badongo.com/pic/1506493 to an image of my Motherboard Resources Properties showing the conflict.
I did install the X-Fi drivers from my original CD but they did not work.
Let me know what else I should try.

P6N Diamond: Problems, Issues, or just trials & tribulations?

P6N Diamond: Problems, Issues, or just trials & tribulations?
I've had some issues with my new pc (see my sig). I initially finished it about a month ago. It was running just fine
until 10 days ago. On 11/10, I finished the evening by adding 2 gb of material to Oblivion & then defragging w/Diskeeper 2k7
(the 3rd defrag that week). The next morning I turned the pc on & it posted normally but then the screen went blank,
except for the words "missing operating system". I restarted the pc a couple of times, which didn't help, I then checked
the bios, & the drive was properly listed. Next, I tried to repair the boot record w/Vista's Recovery Console (RC), however the
RC didn't see an OS, even after loading sata drivers. While pointing the RC to the drivers, I tried to access the C:, the RC
said that drive needed to be formatted. I took that to mean the drive was toast, so I ordered the Seagate (still tried to
fix the boot record through the command prompt using Dos repair commands-no luck), which arrived on 11/15.
That evening I loaded the new hdd & then Vista, after which came the vista updates, drivers, then some of my other basic
programs (diskeeper, firefox, foxit, etc.) & then I defragged. One thing that seemed odd to me about this new install was
that the 'bubbles' screensaver seemed sluggish, that is, less energetic than the first time through. After defragging I was
going to shutdown when another vista upgrade popped up, checked to see if it was important or recommended-it was important.
I clicked to install & it started to install & then the pc got hung up. I tried C-A-D, but it didn't work so I hit the reset
button, got back to the windows desktop, everything looked fine, so I decided to put the pc to bed & do the rest the next
day, the pc turned off gracefully.
11/16. I turned on the pc & it posted properly, but then went to a blue screen. I don't remember what the message was, something
about windows being unable to start, I think. I then hit C-A-D & then loaded the RC. The RC was able to see an OS this time,
so I clicked on it & the repair started. After a couple of minutes the repair finished & asked to restart, which I did. The
pc posted just fine again, but then went to another blue screen, but with a different message, as I recall. I did the RC thing
again, though this time after the repair was going for a few seconds, I was asked if I wanted go to an earlier restore point,
which I did. I was asked to restart again, I did & the pc booted all the to the desktop. I spent the rest of the day checking
out data corruption & diskeeper 2k7, I did find some forums where that was discussed. Though there was also mention of bad
memory causing data corruption as well-more to think about. The pc shutdown gracefully at bed time.
11/17. When I turned on the pc this day I didn't pay close attention, since I figured my pc problems were over, however when
I looked the screen it was black, no messages or anything. A point to the good was that the fans were running & the stylized
light on the XiFi card was lit. Still, a big '' was bouncing about in head. It seemed the pc didn't post. What was wrong:
the motherboard; the videocard; the ram; or, maybe the new hdd? So, I thought about the situation for while. Should I go to
a pro? Should I test my other, unused, ram stick? And, where did I put that damn diagnostic bracket that came with the mobo?
After a couple of hours, I decided to start the fixing process by hitting the reset button. Perhaps the pc did post earlier,
or at least partially, because the pc performed a partial post this time, with the message 'checksum bad' under the partial
component list. At the bottom of the screen was 'press f1 to setup.' I pressed f1 & got into the bios. In the bios, I
noticed several differences, particularly the sata controller being disabled & the boot list was messed up. I corrected
those & saved & exited. I then loaded the RC to see if any more repairs were needed, but none were. I restarted the pc &
it booted & loaded into vista quickly & cleanly. The pc has continued to boot cleanly the past three days while I've been
watching for hardware problems, mainly ram or cmos battery errors.
11/20. So, now what? I'm seriously considering reinstalling vista once more. I think my hardware is alright, I suspect
Saturday's problem was a conflict between the restore point & the bios. I'm ambivalent about diskeeper, I've bought it,
but I didn't buy it to beat myself over the head with.
If you've read this far would you do me the additional favor of telling me your opinion? I've noticed a fair amount of wisdom in this
forum & I think I could use a little extra input. Happy Thanksgiving!
Thank you all,
tryggvi

...The saga continues...
11/24. PC posted & went right to vista. I decided to test a different set of vid drivers so I installed th geforce 169.12 betas to see if that would eliminate the screensaver sluggishness I mentioned above-it did, the driver has been stable but I haven't pushed them either. PC ran fine all day & it shut down normally at the end of the day.
11/25. PC posted & went right to vista. I installed several programs (including auslogics defragger) & attached 3 sata (1 optical & 2 ext.hdds). Defragged in the middle of the afternoon & pc ran fine the rest of the day & shut down normally that night.
11/26. PC posted but the I got the "missing operating message." Damn! So, now I'm thinking defrag corruption, bad sata controller, or failing cmos battery. I tried to fix the vista install w/recovery console, but it couldn't even find an os. I also checked the bios during this time, everything was fine except that the time was off by a couple of hours. I did a clean install of vista again on a lean machine & then some basic programs. I turned of the pc a couple hours later and added 2 sata drives, the pc posted & loaded vista just fine.The pc shut down normally at the end of the day.
11/27. No apparent post. I hit the restart button, the pc then posted w/a 'checksum bad' message at the bottom. I got into the bios & found the following entries changed: time & date; full screen logo display; boot sequence; on board sata controller; and, boot from other devices. I reset these entries & saved & exited. The pc booted into vista just fine & ran normally the rest of the day, shutting down normally as well.
11/28. No apparent post again. Repeated the immediate above, the same entries were changed, so I reset them & the pc posted & vista loaded just fine. With the same changes happening 2 days in a row, & all the bad things happening after the pc being off over night, the problem seems fairly certainly to be a bad or failing cmos battery, especially since I haven't tried to flash the bios or shut down the pc improperly. In my research of cmos battery problems, it was recommended that you try to recharge the battery by leaving the pc on 24-48 hours before replacing the problem, so I'll leave the pc on until the evening of the 30th.
11/29. 36 hours plus & the pc is doing fine. Sorry for the journal, but it helps me think & gives others a clearer idea about what's been going on. Does anyone have any other ideas? My cmos battery is a 'KTS lithium cr2032', if need be can I replace this w/any other cr2032? Especially since I can't find a KTS one.
Thanks all,
tryggvi

P6N Diamond ran perfect but now wont post / no display

Like those here I built many a computer in my day using all the right tools and precautions. But this one really has made me mad. I don't have much money, so believe me when I say I saved my pennies...cause I sure did for this rig although nothing special. Enough of the sob story on with the program. I had it running fine...all temps voltages were up to spec and fine. No over clocking what so ever not even the ram. When I would shut the computer down and left it off for more then a few hours it would not post. The D-Bracket leds showed that it was freezing on the ever so wonderful:
"Initializing Video Interface
This will start detecting the CPU clock, checking type of video onboard. Then detect and initialize the video adapter"
So cussing like a sailor I ran through the onslaught of checking every component on and off different settings ect.
I tried:
- Reseting the CMOS
- Removing all peripherials
- Setting the board up outside the case
- Switching graphics cards with known graphics cards
- Swapping the memory
- Starting it with a pin (instead of the case switch)
- Reseating the processor
you name it and I tried it...I read through as many posts as I could....tried the tricks and yet nothing. I'm ready to RMA it...cause I'm past the Newegg 30 days by 9 days.
My system Specs:
-MSI P6N Diamond
-Core 2 Quad Q6600 SLACR (stock speeds)
-2 gig Patriot DDR2 800MHz kit (2 X 1GB) PDC22G6400LLK 2.2v (Stock latency)
-Antec p182 case
-2 SATA Drives (1 maxtor 160 and 1 Seagate 160)
-1 SATA DVD Burner Liteon
-Ultra 500 Watt ATX Power Supply ( SLI Ready) (if you need voltages I'll post)
Thank you for any and all help.

Quote
The 8600GT doesn't have a power connector to it.
Quote
+5V/30A +3.3V/30A +12V1/16A +12V2/18A -12V/0.6A +5VSB/2.5A
This could be the cause of your problem. Your PSU has two seperate +12V rails that cannot accumulate their power output.
If your video card does not have its own power connector, it may be trapped on one of the two rails together with your quad core and other system devices.
I believe this is a very possible explanation at the moment.
If you are going to try a different PSU, it will be best if you try one that has just one strong +12V rail. Around 30A should be fine. If your system won't boot up a proper PSU, the problem is somewhere else.

P6N Diamond reboots with E6850 CPU (Kernel-Power)

I hope I give enough information to possibly help with my issue. I recently changed my CPU from a Pentium D 3.4GH to the Core™2 Duo CPU E6850 Conroe 3.00GHz. I can't run for more than two hours before I get a sudden reboot. I checked the event viewer and there is a critical event: Kernel-Power. I'm not trying to overclock (although I'd love to learn how too). I've listed my specs below and thought I'd mention that I don't have a heatsink and fan on the CPU. I'm using the Corsair liquid cooler. I have fans blowing on the heatsinks to keep the heatpipe cool. Checking it with a Fluke IR Thermometer I get 45c on the 680i heatsink and 50c on the 590i heatsink. This temp is comparable to when I had the Intel heatsink and fan on the cpu. I use the Cooler master CM Sniper for my case and there seems to be adequate air flow. I just did a reinstall (cleaned the hard drive) using the Pentium D and have been adding and updating one driver at a time to see when the problem would start. As soon as I added the E6850 CPU the reboots started. I changed back and the reboots stopped. The Any help and/or ideas would be appreciated.
CPU: Intel ® Core™2 Duo CPU E6850 Conroe 3.00GHz
CPU Cooling: Corsair Hydro Series H50 Liquid Cooling system (MSI Dual Core Center utility shown CPU temp at 24c at idle and gets up to 28/30 under higher loads)
Motherboard: MSI P6N Diamond LGA 775 NVIDIA nForce 680i SLI ATX Intel Motherboard
Ram: OCZ 4GB (2 x 2GB) PC26400
Power Supply: Corsair TX650W
Hard Drives: Western Digital 150GB x2 (Raid 0)
Video Card: Nvidia 9600 Gt 1GB (x2 SLI) (MSI cards)
Sound Card: I have the onboard sound disabled at this time
OS: Windows 7 64-bit

Hello and welcome,
What bios do you have?
If its 1.0 its possibly not fully supporting your cpu and you probably need to flash your bios.
If you need to flash, read here on how to safely:
https://forum-en.msi.com/index.php?topic=113295.0
And go here for biosfiles:
http://global.msi.eu/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1168
Take 1.3 it incorporates all previous fixes.

P6N Diamond Issues

My specs are listed in my signature. I have a P6N Diamond with the latest BIOS update, v1.3.
Recently, I have been having problems with my setup.
My IDE devices are no longer detected. I've changed the cable. I've tried different drives and nothing on the IDE bus is detected at all. The IDE controller is enabled in the BIOS. The BIOS doesn't detect the devices at all either.
I am unable to shutdown my computer. Once the OS is finished shutting down, the screen goes black but the motherboard stays fully powered. 80% of the time, I can't get the comp off by holding down the power switch on the case. I have to use the power switch on the PSU to get it powered off. If I hit the power switch on the case while it's behaving like this, it sounds like it's power cycling and it goes through the sequence as per the reading on the D bracket.
I have tried re-flashing the BIOS as I thought that the problem was that the BIOS may have gotten corrupted. This failed to produce any positive results.
My problem almost sounds like the one that this user was experiencing:-
https://forum-en.msi.com/index.php?topic=116788.0
The only recent changes that I have made was to replace my PS/2 Keyboard and Mouse with USB ones. I tried plugging back up the PS/2 ones but that didn't seem to help much. Do I need to reset the CMOS after re-adding the PS/2 devices? Or is there some other solution to this problem?
Any help to figure this out would be very much appreciated.
Thanks in advance.

Quote from: Mike on 25-May-09, 22:05:13
Okay, so you've set the Power Management for the power button in the BIOS to off/on, correct? Have you also set in windows' Power Options? What operating system are we discussing here? Is the power button in Windows' Power Options set to turn OFF the computer?
Do an experiment for me. Turn off the computer. If this means putting it to sleep and then turning off the PSU, so be it. With the computer completely turned off(pulling the plug if necessary and then re-plugging and turning on the PSU), boot up the computer and rapidly hit the DEL key to get into the bios. Once you are in the bios, check to ensure that the power button is set to Off. If it is not, set it to off and save and exit--then start from the beginning of this paragraph, "Turn off the computer" again. Check that the setting stuck, power button to off. If it is set to off, hit the power button now--this should shut down the computer. If this shuts down the computer, your problem is OS based and not hardware.
I performed the instructions. The power button is still putting the computer into sleep mode.
One interesting thing that I did note is that when I reset from the BIOS interface to "Optimized Defaults", the BIOS can detect all SATA and all USB devices that are connected to the motherboard. Before this problem arised, the BIOS could only detect one single USB storage device that was connected to the motherboard. I could have 2 USB storage devices connected to the motherboard and only one would show up in the F11 Boot interface. I was perplexed by this initially but never paid too much mind to it.
I think that the motherboard itself is botched. I think that the IDE interface on the motherboard is dead. I can even unplug the hard drives connected via IDE while an OS is booted and the system won't crash at all.
Thanks a lot for all the help guys. It's very much appreciated.

P6N Diamond and built in X-Fi trouble

Hi i just purchased a spanking new pc setup which included the p6n diamond (for the built in x-fi).
I've cleanly installed windows xp 32bit with sp2 onto the raid 5 array (3x76gb) harddrives. I installed the nvidia nforce motherboard drivers (latest windows signed driver) and the latest windows signed nvidia gfx card driver. also installed direct x 9c and enabled sli on the gfx cards.
I've done nothing else to the system..everything is fine...except... there is a pci device in device manager which i thought was my built in creative x-fi card... however, when running the msi creative x-fi installer, it says "no supported device found"....weird. So i went into my bios to check it was turned on and it was. just to make sure though, i turned it off and low and behold the pci device dissapeared from device manager. I've since turned it back on (which again popped it into the device manager) and tried installing the drivers from the creative website...which also did not find a x-fi card to install onto. i then extracted the creative .exe driver file and tried forcing the install by telling device manager i "have disk" and pointed it to the extracted files.... it installed the card "sound blaster x-fi xtreme audio", but the device "cannot start" and has an exclamation mark next to it (i had also previously tried forcing the msi drivers in the same way, but they didnt even allow me to select a driver that way (after doing the "have disk" thing)).
the bios version is 1.1 (came that way) - although i am contemplating a downgrade to 1.0 (asking you lot first
Im kinda lost as to where to go from here and i really really really really dont want to have to dismantle my newly built pc, sent it back to ebuyer to have them tell me "the x-fi card is fine" or something along those lines... and get into a long drawn out phone battle with their support team (which is normally inevitable).
I work in IT, so give me all the options you think i have no matter how remote and i'll give them ago before losing my pc for weeks on an RMA.
spec:
e6600 dual core
2 x 7900gs using sli
corsair hx 620w psu
2 x 1gb ocz vx2 pc2-8000 ram
3 x 10k 76gb raptor (using nvidia raid 5 built into the mb)

Ok... after installing all the windows updates (i already had sp2 installed mind you) something strange happened... the pci device was detected as an HD audio device (thanks for the tip maesus).
Thing is... after installing as a HD audio device, the pc then detected it as an creative x-fi, then it detected it as a hd audio device again, then an xfi card again...over and over in some weird "found new hardware device" loop.
and again on reboot, i got a non-functioning device in device manager (the exclamation mark again).
sooooo.... I re-installed windows (again!)...but this time i ran ms update until it ran out of updates then tried running the creative installer...... at last... it installed!
i have sound
So it seems you need to install a particular ms patch before installing this device... (and if you try to install the device before then...you may have to re-install the OS). It would be very nice to know exactly what patch was needed, but at the moment i am experiencing great relief that i wont have to send this back to the supplier.
phew. cheers for the help guys... and i hope this helps others in the same predicament.

P6N Diamond New Problem: Second HDD Randomly Starts/Stops Since recent Update

Howdy All,
Continuing problems with the P5N Diamond.
This one's new.
Previously I had the same problem as many others with the cold boot issue. Somehow, someway, it just stopped: cold boot or not, one day it just started booting fine....go figure.
However, I recently (about 3 weeks ago) did the MSI live update that included something or other pertaining to the E-SATA....support for it or something to that end. Although I don't use the E-SATA, I installed it thinking I might at some point and since installing it, I have discovered a new problem: my second drives (in RAID 0) just opens/closes randomly. It seems to mostly occur when operating demanding programs: gaming, watching a video, that sort of thing.
Everytime it does this, it takes me to desktop and asks me what program I want to use to open the program......which when I do, is nothing more than my second (D drive) HDDs in RAID 0. I then get the yellow pop up message in the bottom toolbar from Windows saying it's experienced a write failure problem. It hasn't done any damage that I can tell and I've lost nothing, but being taken to desktop perpetually is a major issue. This problem is driving me absolutely up the wall. No sooner than I start to do something and wham.....I'm at desktop being asked what program I want to use to open up the second HDDs. I've also tried just leaving it open but to no avail: it just randomly continues to open and close.
I have my O/S on the C drive and 2 more HDDs in RAID O for back up on ports 6 & 7. Since doing the MSI update that included the E-SATA whatever, this new problem almost prevents the computer from being usable: certainly nothing in gaming is possible along with anything that requires uninterruption.
Here's my system:
M/B: P6N Diamond
CPU: E6850
RAM: Corsair XMS PC-8500, 2 x 1 gig
HDD: 1- WD 150 Raptor
HDD: 2- WD 5000AAKS in Raid 0
Vid Card: EVGA 8800GTX
PSU: PC Power & Cooling 750 Silencer
ODD: Sony DRU 830A
FDD: Sony Floppy
Misc: Scythe fans x 5
O/S: XP Pro w/ SP2
Running BIOS 1.2
So, being fairly certain the MSI update created the problem, my question is, how do I undo the MSI's most recent update to remove it? When I go into Add/Remove Programs, nothing is listed there. I'm not sure this is the source of the problem but I do know I didn't have it beforehand.
I'd greatly appreciate any help with this....even any ideas. While I have some computer knowledge, I'm not as tech savvy as most here, but this problem is, apart from driving me up a wall, making the computer almost unusable. FYI, I haven't done a System Restore because I've installed several things since and don't want to lose them if I can isolate the problem, but I will if that's what you all recommend.
Again, sorry for what may be a noobish question, but I'm not sure where else to go. After dealing with MSI's tech support, I'd rather talk to a wall.
Thanks greatly.
Pepper1

Mark,
Forgive me for asking, but I am a bit confused. Is your "cold boot issue" now solved? If so, do you think that the new drives are the key?
Lev
Quote from: MarkJohnson on 17-December-07, 14:21:23
Sorry for late post.
After setting up the HW RAID (2500YS) for booting the system still cold boots. strangely this time the reset (Ctrl+Alt+Del) doesn't seem to work. I must of did it two dozen times and it would never clear. I then just powered off after the other 2 drives on the nvidia SATA cleared and seen the HD LED light up and stay on for a few seconds(seems stuck on the 4723 checks of the drive) and then powered down and powered right back up with no cold boot issue. It has worked this way every time for the last week or so and I tested it like 20 or so times(3-4 times a day). These drives are listed as being compatible after the firmware update (and I did that already) so I guess it is either the MB BIOS needs updating or it's the way the nvidia chipset runs this setup is wacky. This is assuming the 4723 HD compatibility list is correct.
here's a summary of the drives so far.
36GB Raptors (old revision) - can take forever to boot properly and corrupted my disk in 3 days of testing (scrambled my directory structure)
105GB Raptors - Just reset(Ctrl+Alt+Del) 1-4 times after the HD LED goes solid for a few seconds. worked for two months no errors.
250GB Caviar RE(2500YS) - have to power off (power button) when HD LED goes solid. so far no problems for a week.
80 GB SATA II Hitachi Deskstar (HDS728080PLA380 - May 2005) - same as 150 GB Raptors, just a reset or four, only did a days worth of testing with no errors.
well, I was hoping for those 2500YS to work properly. Now it makes it really hard to track the problems with so many different errors and 3 different places it can go wrong 4723/nvidia/msi/HD Manufacturer. wait, that's 4. Oh boy!
Hopefully this gets resolved soon. I've already had to move this MB to my secondary system, and for other reasons than this. I didn't mind hitting the reset button to get this to run. I get the feeling that MSI has abandoned this board on us. with the new P7N being released it will be even harder to get anyone to mess with this thing.
-=Mark=-

K8N Diamond SLI Creative Sound Blaster 24-bit

I have a problem with My MSI K8N diamond SLI 's integrated Creative SB 24-bit sound.
The sound is unaffected by the speaker configuration in control panel>sounds and audio devices>advanced.
For example when playing a 6 channel sound through my stereo speakers, the center channel does not get split between front channels. This means I can hear no voices as they are only on the center channel!
Can anyone with the K8N Neo4 platinum or diamond sli confirm this or does anyone know a solution?

If it is a grounding problem it would be within the PCB of the motherboard, the wiring there that either are not connected directly to ground. Or the problem that a ground plane / trace runs to close along a signal trace, causing induction of a signal to what should be a no-signal ground.
As you say, a lack of voltage could also be the problem, if the powerfeed to the chip is fed from the same source as the IDE (as it correlates with IDE activity). Any rapid drops in Voltage (voltage spikes) could result in just the phenomenon as we hear it and as I measured it. But it is less likely than a ground related problem. If there was such a load on the trace to deliver voltate to the chip and some other component, that the voltage would drop, we would see this on the motherboard. The amps would spike and we most likely would have seen a burned out trace.
So it is more likely that there is a matter if impure voltage feed to the circuit. But this is also much less probable than the ground issue. It is not uncommon to get ground issues in audio circuitry, especially in applications and environments where you have PCB traces in which high frequency signals travels close by. (a phenomenon not only contained to audio circuitry, as you probably have seen motherboards with traces run in circles, to get rid of similar problems).
I would not blame creative for this. I have had to deal with many soundcard issues in 10+ years as a computer tech. And I will leave it at that. I have much more to say about the quality of MSI products than the quality of any soundcard from any manufacturer, but that is also something that I will not rant about here.
If you do not get it to work with a stand alone sound card, I would check your PSU so that you do not have any bad or impure voltage there (measured with an oscilloscope, if you know what you should look for during load). I would also check so that the computer really are attached to a grounded outlet to reduce problems with interference. Third I would place the soundcard as far away from the GPU/s as possible (a good source for interference).
In my experience, only soundcards that has been faulty has produced similar sound issues as this motherboards onboard sound produce. Especially bad caps (do not even have to be the leaking kind) tend to induce this behaviour.
But the last part is something I have ruled out on this motherboards onboard audio. If there were bad caps there would be telltale spikes in the the measured signals and voltages. There are none (except for previously noted discreprancy in the output signal when accessing IDE).
I do not have a reciever, so I can not try the Spdif out, to see if that works as it should or not.
Also, I have not tried to remove the IDE devices and use only my SATA drives to see if that removes it problem (I guess it does, but that is a bad solution).

P6N Diamond & SLI controller sanity check

Similar Messages

Maybe you are looking for