I just build a new computer (specs below) to run FSX. After building it, I let it run for a week solid to burn in. Installed XP Pro and FSX. With SP1 & Acceleration. When I first turn it on, it doesn

Yes, this usually the result of overclocking issues. On Asus boards, cycling the power-switch on the PSU will reset the clocks back to default so you can get into the BIOS and `try again`. If your not intentionallly overclocking, I would get back into the BIOS and "set defaults" and work it from there. Also, some of the newer sticks of RAM require more volts than came with the JEDEC tables burned onto them. For instance, my Corsiar sticks default to 1.8v but they need 2.2v. I have to set that voltage manually before all other ajustments in the BIOS so I don't forget.Good luck...

I forgot to mention. I am running stock. LOL No over clocking. I will check out the RAM thing. They are OCZ? Something like that. A matched set. Thanks

John,By coincidence I have the exact same motherboard (Gigabyte P35C DSR3) with an Intel E6750 and Patriot RAM. While it is normally rock-solid, fast, stable and cool, I've had some startup issues from time to time, particularly on cold mornings. As a matter of fact, I had them more frequently when BIOS was set up to boot off the hard drive first. I suspected a slight timing issue and changed it to seek booting from USB, DVD, then Hard drive in that order, and that extra inspection time for bootup devices cured most of the problem - although on cold mornings (this morning being one of tem) I got some odd behavior. A push of the reset button cured the problem.The PC doesn't sit in a cold room and in fact is somewhat near a floor vent, but it does seem to be related to cold startup. Also this is not my first time building a PC by any stretch of the imagination and I'm positive everything is well-mounted, grounded, or isolated where need be.Overclocked it once (very mildly) using the Gigabyte utility just to see what it was like but went back to stock timing later the same day, that was some time ago.May not be the same thing but I thought it worth mentioning since it's the same mobo. Which in all other respects I think is a very good unit.

>John,>>By coincidence I have the exact same motherboard (Gigabyte>P35C DSR3) with an Intel E6750 and Patriot RAM. While it is>normally rock-solid, fast, stable and cool, I've had some>startup issues from time to time, particularly on cold>mornings. As a matter of fact, I had them more frequently>when BIOS was set up to boot off the hard drive first. I>suspected a slight timing issue and changed it to seek booting>from USB, DVD, then Hard drive in that order, and that extra>inspection time for bootup devices cured most of the problem ->although on cold mornings (this morning being one of tem) I>got some odd behavior. A push of the reset button cured the>problem.>>The PC doesn't sit in a cold room and in fact is somewhat near>a floor vent, but it does seem to be related to cold startup. >Also this is not my first time building a PC by any stretch of>the imagination and I'm positive everything is well-mounted,>grounded, or isolated where need be.>>Overclocked it once (very mildly) using the Gigabyte utility>just to see what it was like but went back to stock timing>later the same day, that was some time ago.>>May not be the same thing but I thought it worth mentioning>since it's the same mobo. Which in all other respects I think>is a very good unit.>You know, I JUST changed it a few days ago from booting from the CD/DVD. Figured it would boot faster.I will change it back and see.computers must be female!

Guys, I can't speak intelligently about the Gigabyt boards as it's been a few years since I've owned one. But, in my Asus BIOS, under the hard-drive detection menu on the main page, there is a seting something to the affect "dely seek start time". I think mine defaults to and remains 35ms. You might try tinkering with that setting. Also, are you running these drives in IDE, AHCI, or Raid mode (assuming they're a recent version of the Intel P965,975,35 chipset)? Even if you're running a raid, I still set it to "Raid" mode in the BIOS and then my drives appear "Raid Ready" in the Intel Matrix Storage software and take advantage of the southbridge sata controller with its performance advantages.Having just done a quick Google search, it seems there were issues with some Western Digitial hard-drives having boot issues, event "cold" boot issues such as you describe. I would download and execute WD's drive instpection/repair utility from their website. It's actually very good and revived a bad drive for me a year ago or so, and continues to work flawlessly to this day.Is your boot drive a SATA drive? Make sure it's connected to the proper (bootable) SATA connector (Asus has both master and slave SATA connectors) and only the Master (Red) connectors are supposed to be bootable. It has to be something in the BIOS settings/configuration or physical drive connection.You might also disable "quick boot" under the "boot" menu in the BIOS. This would give the drives time to warm/spin up while the memory and post checks are completed.Just a few more thoughts, sorry if this is just rambling and not very helpful.

sorry if this is just rambling and not very helpfulJordan,that makes perfect sense...nothing to add, it's just my name appears as the last post on the first 3 posts of this forum so I thought I'd make it one more!!RegardsJim

>nothing to add, it's just my name appears as the last post on>the first 3 posts of this forum so I thought I'd make it one>more!!:-beerchug - Jim, have you been drinking again, LOL...

Hi John,I too have seen this behaviour. I have an ASRock 939Dual-SATA2 MoBo with WD Caviar SE16 250GB (WD2500KS) SATAII HD.Normally the problem goes away when I press the Reset button.My own feeling is that it is nothing to worry about (once you've worked around the problem, that is!) and it has something to do with the spin-up time of the WD drive. When it happens I have noted that Active SMART 2.51, which I have configured to report any changes to the SMART parameters at initial load, always reports a reduction in the spin-up time of this device. My guess is that the act of pressing the Reset button simply allows the correct reading of the boot sector on a drive that has already spun up or has not yet slowed to a stop during the moment the Reset button is pressed and the reboot starts.On my system this boot failure only occurs once in a while and in between remains trouble-free. I've got into the habit of watching the lights on my keyboard at boot - when they blink as the keyboard initializes I know the boot will be successful and I can safely go away and return later.One last point. My BIOS has an option whereby you can change the 'SATA Driving' to 'Strong'. Prior to this setting being changed the BIOS frequently had problems detecting the WD drive!! This is a known issue and I was advised to make the change by ASRock Support. Since then I have had no problems other than the occasional boot failure as described above. This is consistent behaviour and I have long since stopped worrying about it.Hope this helps and reassures you a bit.Mike

Hello everybody,I'm the (formerly proud) owner of a P35C-DS3R from Gigabyte. I've had boot issues since the first day I started using my new computer.These were cold start:First start: blank screen, no beep at all. I press reset switch...Second start: computer stops before booting Windows I press reset switch again...Third start: Windows boots, but shows Blue Screen of Death just before showing desktop (not specifying kind of problem) I press reset switch again...Fourth start: I get to run Windows, but it shows some serious problems (Windows shuts down random processes from time to time)I Googled for a while, came to read this thread and Jordanal gave me a good tip:>For instance, my>Corsiar sticks default to 1.8v but they need 2.2v.I entered M.I.B. in BIOS and added +0.3V to RAM voltage. It ALMOST fixed my boot problems.Not that my Kingston need a higher voltage... I guess that's not the trouble. It looks like the motherboard doesn't yields enough voltage when it starts from cold. Let me advise you:1 - Get up early in the morning,2 - Stretch a little :)3 - Switch on your computer, and enter BIOS.4 - Go to PC Health, and look at DDR2/DDR3 voltage.If I leave the default Voltage in Motherboard Intelligent Tweaker, I can see it reads 1.7 Volts... but if I let it run for a while, it will raise to 1.8 Volts. ;-)So I decided I would raise it +0.3 Volts, so I didn't had to wait for my brand new computer to heat up like it was a crappy old car.If it will help you, I'm listing my hardware:MoBo: Gigabyte P35C-DS3R rev. 2.0 - BIOS revision: F8Memory: 2 modules of 1GB Kingston DDR2@800MHz, 1.8VProcessor: Intel Pentium E4500 Core 2 DuoHard Drive: Seagate 500GB SATAIIGraphic card: Gigabyte 256 MB 8600GTS Passive cooling (needs 450W+ power supply)Power Supply: Gigabyte Odin 550WGuess you are about to fall asleep. Thank you and good luck!!P.S.: and happy new year!!