X38-DQ6 boot cycle

[SeniorShadeslayer]

I have found something that works for me - at least until I can RMA a mobo that I paid >$250 for and that shouldn't be doing this. After running fine for about 2 months, suddenly I am having the same problem with a configuration very similar to AmRanbo's:

Gigabyte X38 DQ6 with Crazy Cool removed per manual
Q6600 CPU
2GB (2X1) OCZ Platinum PC2-6400
Radeon 1900 XT (or XTX - tried both with same results)
500GB WD (X2 in Raid 0)
Cooler Master Real Power Pro RS-750 PSU
Windows Vista Home Premium

My problem started when I tried to reboot after I swapped out my video cards to check out a new VGA cooler I had installed on one of them. I have done this dozens of times without any problems, like most of us. Of course, initially I thought I had damaged something, although I take great care and ALWAYS wear a strap when I'm poking aroung inside my rig. I have found, after spending countless hours pulling my hair and trying pretty much everything the Gigabyte tech suggested (plust other stuff, including installing the latest BIOS) to wcsd45, that this really is a problem with the board not recognizing the memory. I finally got mine booted by installing a stick of RAM in DIMM slot DDR113 or DDR114 - or both. With RAM installed in either DDR111 or DDR112, it won't boot. Of course, I had followed DDR protocol and had originally intsalled my RAM in DDR111 and DDR113. Incidentally, I have found that my PCMark score is almost identical with RAM installed in DDR113 and DDR114 (non-DDR mode) as it was before(!). I have since read an article in the current issue of Computer Shopper that states that there is hardly a detectable difference between the two modes. This is certainly true in my case.

Anyway, as I stated earlier, I'm going to RMA mine as as soon as I get time because, even though it is OK now, I don't trust it. Also, I have 2 more sticks of RAM that I want to install to get to 4GB, which I can't do now. And - again - I paid a premium price for a mobo that I expect to work in all ways and all the time. As it is, I'm waiting for the other shoe to drop.

 

[SeniorShadeslayer]

A couple of followup points to my earlier posting. I don't think I would have ever found the solution without my son-in-law's help (whose username is Bolivar123). Although I had tried all the other stuff, including swapping RAM) I didn't think to try the RAM in a slot which would go against the User's Manual's instructions. To simplify - don't use the two DIMM slots nearest the CPU and you may fix your problem - at least temporarily.

He has also suggested that someone may be able to go back to an earlier version of the BIOS to see if this fixes the problem. The latest version, which is now installed on my rig, seems to not allow you to go back. The effects of various BIOS revisions on various boards are all over the place, judging from postings on other forums, so it's possible that one of the BIOS revisions broke an earlier one. If anyone can try this and post your results, it may help.

We are beginning to think that this may be a widespread problem that is just beginning to rear it's ugly head.

 

[wcsd45]

For what it's worth, stable for about 4 weeks now. My two 1G sticks memory installed in DDRII1/DDRII3. No further tweaking.

 

[rhansme]

I'm running Bios Ver F7 with the DQ6. 4 Gigs of G Skill DDR2 1000 - e6850 - 700W PS - Nvidia 8800GTS - 2 Raid Arrays - One on each controller - xFi PCI card - XPPro

This build has been very stable and I have overclocked with no issues. I have reset the CMOS a couple of times after reaching the upper limits of the board. It recycled about 3 times and then all was normal again. This board replaced a MSI P6N diamond which was full of problems, none of which were being addressed by MSI.

So Far I am very happy with this board.

 

[SeniorShadeslayer]

OK. My brilliant idea didn't work. And I'm not really surprised. As I stated in my original posting, I didn't trust it. And sure 'nuff, after about a week, the same boot cycle problem started again. I was able to get it running again (temporarily, I'm sure) by following the procedure provided by the Gigabyte tech as described by wcsd45, but even then, it will work only with the RAM in slots DDR113 and DDR114 as I described in my original post. It's RMA time.

 

[Fat_Bodybuilder]

I have also just gotten an X38 board, but it's a DS4. Most of you have the DQ6 I think and so now I think that we can confirm that it is actually the chipset. I should be returning the board tomorrow but I just hope they have the same board in stock because I can't afford any other parts, and this board is possibly the best value for money on the market. Great features and didn't cost an arm and a leg.

If this is a chipset problem then I just hope that the same board doesn't do the same thing.

Q6600 /TRU non Extreme
X38-DS4
2GB OCZ Special Ops Edition PC6400
2 WD Caviar 320GB
2 Opitcal Drives
8800GT w/HR 03 GT

Le Sigh...

 

[sngbrdb]

Forgive me for resuscitating an old thread, but I came across this thread looking for an answer to the same problem, and found a solution. Posting in case anyone still runs into this issue, like me.

The problem is that because the board cycles, you can't get into the Q-Flash or boot from a floppy to update the BIOS. The board starts, runs for a few seconds but has no video display, then powers off.

To break this cycle, do this: Power on the system, then press and hold the power button in for 4 seconds or until the power shuts off and stays off. Then hit the power button again to start back up. By forcing a shut-down, you break the cycle, and the board will now boot, with video display and everything.

Pretty simple, huh? 😉