A few preliminaries:A. The following system was purchased on February 10, 2007, Assembled, and has been running just fine since that time (How time flies!). Specfications are attached. The only thing I have changed since experiencing the problem I describe below is to update to the new 270.61 NVIDIA drivers. With display sliders maxed out and at KJFK with the PMDG 747 and ASE weather, movement is smooth as silk. However, I really did not notice any problem with the previous drivers.B. I realize that there are more opinions as to what temperatures should be than ways to sharpen a knife, and that what I am seeing is above normal for some folks and normal for others. However, for four years my system has been stable and has run without any problems with Nick's recommended settings. The max. shutdown temp for my CPU is listed as 100 degrees by Intel. At idle she normally runs in the 50's C. In FSX full blown under maximum complex conditions she usually runs in the mid 60's C to mid 70's C. Rarely I have seen a spike to 80 degrees C. My ambient room temperatures are normally from the low 70's F to rarely low 80's F. I run three monitors (Two of which are old 21" CRT's), two computers, and two printers so room temperature is a bit of an issue during the peak of summer. For this reason, I have added a small window air conditioner to the room in question (not installed yet for this summer).C. I have waited for about three weeks before posting this scenario to make sure that everything is back to normal and stable. However, I sure do wonder what caused this to happen and wonder if anybody else has had this experience and/or knows what might have caused it.Scenario:1. About three weeks ago while running FSX, my computer suddenly shut down. The shutdown was instantaneous without warning of any kind as if the plug had been pulled and after 4 years of problem free operation this was the first time this happened.2. Restarted computer and got a three beep warning (Believed to indicate GPU but it probably was four beeps).3. Restarted again and got a four beep warning indicating a hardware failure (Makes me doubt how I counted beeps on the previous attempt).4. Waited a few minutes and tried another restart. The computer booted up normally with no problem.5. Brought up "RealTemp" and checked temperatures. Idle was running in the 70's C to 80's C, about 20 degrees above what has always been normal.6. Cranked up FSX. CPU temp went up to 100 degees C and as expected, I got another shutdown.7. Restarted the computer and went into the BIOS setup.This is where I made the discovery of the culprit. Something had changed my BIOS setup. While my CPU Ratio Setting was still at [30] for an OC of 4.0GH, Frequencies, DRAM Timing Control Information, and voltages had been reset to default automatic values.I edited and reset all values back to Nick's recommended settings, temperatures returned to normal, and everything is again working fine. The settings that work for me are as follows:Configuration System Performance SettingsAi Overclock Tuner [Manual]CPU Ratio Setting [30]Intel ® SpeedStep ™ Tech [Disabled]BCLK Frequency [133]PCIE Frequency [100]DRAM Frequency [DDR3-1600MHz]UCLK Frequency [3200MHz]QPI Link Data Rate [Auto]DRAM Timing Control1st Information: 7-7-7-20-4-59-8-6-16-0 (Grayed Out)DRAM CAS# Latency [7]DRAM RAS# to CAS# Delay [7]]DRAM RAS# PRE Time [7]DRAM RAS# ACT Time [24]DRAM RAS# to RAS# Delay [Auto]DRAM REF Cycle Time [88]DRAM WRITE Recovery Time [Auto]DRAM READ to PRE Time [Auto]DRAM FOUR ACT WIN Time [Auto]DRAM Back-To-Back CAS# Delay [Auto]2nd Information: 1N-57-59-62 (Grayed Out)DRAM Timing Mode [1N]DRAM Round Trip Latency on CHA [Auto]DRAM Round Trip Latency on CHB [Auto]DRAM Round Trip Latency on CHC [Auto]3rd Information: 6-6-14-9-9-9-7-6-4-7-7-4DRAM WRITE To READ Delay (DD) [Auto]DRAM WRITE To READ Delay (DR) [Auto]DRAM WRITE To READ Delay (SR) [Auto]DRAM READ To WRITE Delay (DD) [Auto]DRAM READ To WRITE Delay (DR) [Auto]DRAM READ To WRITE Delay (SR) [Auto]DRAM READ To READ Delay (DD) [Auto]DRAM READ To READ Delay (DR) [Auto]DRAM READ To READ Delay (SR) [Auto]DRAM WRITE To WRITE Delay (DD) [Auto]DRAM WRITE To WRITE Delay (DR) [Auto]DRAM WRITE To WRITE Delay (SR) [Auto]CPU Voltage [1.28]CPU PLL Voltage [Auto]QPI/DRAM Core Voltage [1.35]IOH Voltage [Auto]IOH PCIE Voltage [Auto]ICH Voltage [Auto]ICH PCIE Voltage [Auto]DRAM Bus Voltage [1.70]DRAM DATA REF Voltage on CHA [Auto]DRAM CTRL REF Voltage on CHA [Auto]DRAM DATA REF Voltage on CHB [Auto]DRAM CTRL REF Voltage on CHB [Auto]DRAM DATA REF Voltage on CHC [Auto]DRAM CTRL REF Voltage on CHC [Auto]CPU ConfigurationConfigure advanced CPU SettingsModule Version: 3F.11Manufacturer: IntelBrand String: Intel ® Core ™ i7 CPU 975 @ 3.33GHzFrequency: 4.00GHzBCLK Speed: 133MHzCache L1: 128 KBCache L2: 1024 KBCache L3: 8192 KBRatio Actual / Value:30CPUID: 106A5CPU Ratio Setting [30.0]C1E Support [Disabled]Hardware Prefetcher [Enabled]Adjacent Cache Line Prefetch [Enabled]Intel ® Virtualization Tech [Disabled]CPU TM Function [Disabled]Execute Disable Bit [Disabled]Intel ® HT Technology [Disabled]Active Processor Cores [All]A20M [Disabled]Intel ® Speedstep ™ Tech [Disabled]Intel ® C-STATE Tech [Disabled]Specs. for the primary computer in question:ASUS P6T Deluxe V2 LGA 1366 Intel ATX MotherboardIntel Core i7-975 Extreme Quad Core CPUScythe SY124010L CPU Fan6GB (3x2GB) 240 Pin DDR3 1600 OCZ3P1600LV6GK MemoryWinXP Pro 64 BitEVGA 01G-P3-1180-AR GeForce GTX 285 1GB 512 bigt DDR3 Video Graphics Card23" HPw2338h Primary Monitor21” Viewsonic Pro Series P815 Secondary MonitorNvidia version 270.61 drivers for GTX 285 Video Card1 Western Digital Velco/Raptor WD3000HLFS 300 GB 10000RPM WATA 3 GB System Harddrive1 Western Digital Velco/Raptor WD3000HLFS 300 GB 10000RPM WATA 3 GB FSX Harddrive1 each Segate 320GB SATA FS9 Harddrive1 each Segate 320GB SATA Backup / Utility HarddriveStd. Floppy Drive2 Each CDRW/DVDRWPlusDeck 2C Audio Tape Player/RecorderKonica Minolta magicolor 2400W Laser PrinterCH Pro USB PedalsCH USB FlightSim YokeMicrosoft FFB2 USB JoystickLogitech Keyless KeyboardLogitech cordless mouseHigh Speed Cable Internet/email Service with RouterCorsair HX1000W Modular 1000 Watt Power SupplySuperPower ATX Full Tower Case with sides Customized for more ventilationNote: Keyboard and Mouse are shared with a secondary Core 2 Duo Computer for WinXP Pro 32 bit programs, WideFS6 (FS9) and Wide FS7 (FSX). Implementation is by Synergy Free Software.Note: CPU Overclocked to 4.0. GPU is not overclockedSpecs. for Secondary Computer:ASUS P5N-SLI MotherboardIntel E6600 Core2 Duo CPUZalman CNPS7700-CU RT CPU Fan4 GB KST DII800 MemoryWinXP Pro 32 BitNVIDIA Evga Geforce 8400GS 512MB DDR PCI Express x16 Video Card21” Viewsonic Pro Series P815 Primary MonitorNavidia version 182.50 drivers for Video Card1 each Segate 250GB UIDE Harddrive1 Each Segate 80GB SATA Harddrive1 each Maxtar 40GB UIDE Harddrive Std. Floppy DriveCDRW/DVDRWWINTVHP 4315v Printer/Fax/Scanner/CopierEpson Perfection 2480 Photo ScannerMicroTech Z!O! Flash Card ReaderAudigy 2 ZS Platinum Sound to Creative Inspire 5.1 5200 SpeakersBFGR 1000 Watt Power SupplyNote: Keyboard and Mouse are shared with a primary i7-975 Computer for WinXP Pro 64 bit programs, WideFS6 (FS9) and Wide FS7 (FSX). Implementation is by Synergy Free Software.Any ideas?Thanks:RTH

A slow buildup of dust and grunge will do this RTH - at least - it's the first thing I would try.

A slow buildup of dust and grunge will do this RTH - at least - it's the first thing I would try.

+1. Dust buildup will slowly increase the thermal resistance of all your heatsinks. Another is grunge gathering for a convention around the axles of your fans slowing them down, as well as around the holes of your PC Case's input and output vents.And a Final Theory From Deep Space ("oo-weee-oo-weee"): Your flash memory where the BIOS resides was hit by a cosmic ray from some supernova eplosion in a far-away galaxy and changed some bits in the BIOS to some unacceptable value for CMOS, triggering a safety routine that reset the CMOS access parameters. Seriously, this is not a joke, this stuff does happen. Even FMCs are not immune!Cheers,- jahman.

Thanks for the reply Paul:I do occasionally blow out "dust and grunge" from my computer case and agree relative to gradual temperature increases,, but none were noticed in this scenario. However, I did not expect an impact on BIOS settings.Jahman, interesting theory, but somehow I somewhat doubt that UFO's are the cause of my problem.Thanks again guys:RTH

A slow buildup of dust and grunge will do this RTH - at least - it's the first thing I would try.

Something had changed my BIOS setup. While my CPU Ratio Setting was still at [30] for an OC of 4.0GH, Frequencies, DRAM Timing Control Information, and voltages had been reset to default automatic values.

Hmmph.. all your bios settings look fine, RT: how they would suddenly revert to the 'Auto' setting is pretty strange I'll admit. Could have been disastrous. The 1kw psu looks adequate, though I might go for a higher rating, seeing those four drives, but with only a 285 there's nothing that would suggest 1kw isn't enough, is there? It's not as if you're running a pair of 580's or 5870's X-Fired.... Strange. I suppose you could have taken a spike through the internet connection.. It used to happen with the dial-up connections with modem cards, but that stuff was twenty-five years ago.

They're those who believe that ""the particles"" helped the San Francisco Giants win The World Series last year."Seeing and believing are both often wrong" -Robert McNamara ...Yeah, I'm a quantum activist <VBG>off topic again, but I do hope you get your stuff worked out soon.Ken

Jahman, interesting theory, but somehow I somewhat doubt that UFO's are the cause of my problem.

IBM seems to think otherwise. Did you actually follow the link I provided?Cheers,- jahman.

They're those who believe that ""the particles"" helped the San Francisco Giants win The World Series last year.

Yeah, and there's those, like the Australian Transport Safety Bureau, that believe cosmic rays were a factor in sending a Quantas A-330-303 into two terrifying dives (also here).Cheers,- jahman.

"there's only two ways the plane could've done that: 1- the aircraft was bad or 2- the pilot was bad." -Ally McBeal Season 1 Episode 12 (The Blame Game)

"there's only two ways the plane could've done that: 1- the aircraft was bad or 2- the pilot was bad." -Ally McBeal Season 1 Episode 12 (The Blame Game)

Oh, yeah, and these guys here and here are full of it, right?Cheers,- jahman.

Oh, yeah, and these guys here and here are full of it, right?Cheers,- jahman.

Probably not nearly as much as me. :-)

Sorry Jahman:As I often do, I spoke before all the gears were in place and I paid attention to what you really said. Really has nothing to do with UFO's.Thanks for setting me straight.RTH

IBM seems to think otherwise. Did you actually follow the link I provided?Cheers,- jahman.

Update:On another forum, a suggestion was made that may have credibility, A dying MB battery. It does seem reasonable that if this is the case, BIOS settings would go back to defaults. Even so, it appears that everything did not though as the OC remained while other settings defaulted. I guess if the battery was only on the way out, strange things could happen.Time will tell:Happy flying:RTH

Sorry Jahman:As I often do, I spoke before all the gears were in place and I paid attention to what you really said. Really has nothing to do with UFO's.Thanks for setting me straight.RTH

No problem at all! :-)

Update:On another forum, a suggestion was made that may have credibility, A dying MB battery. It does seem reasonable that if this is the case, BIOS settings would go back to defaults. Even so, it appears that everything did not though as the OC remained while other settings defaulted. I guess if the battery was only on the way out, strange things could happen.Time will tell:Happy flying:RTH

That's easy to check: Se if the clock is on time when you power-up.Cheers,- jahman.

Time and calendar are correct when I power up. Also as stated earlier, it now has been over three weeks since the problem occured and everything has been back to normal and stable since that time.I think what was suggested was that the battery might possibly be weak and approaching the dying stage but possibly not totally dead yet. Not sure what might happen under those conditions, but I suspect that you are right and that this really was not the problem.Other suggestions have been that there could have been a power blip, failed bootup, hardware crash or something of the sort.Hopefully this will be one of those things that never raises its head again.Thanks for the comments:RTH

No problem at all! :-)That's easy to check: Se if the clock is on time when you power-up.Cheers,- jahman.