This is with the new system and FSX set to it's default/SP1 state except for AffinityMask=15.Have FSX installed on it;s own RAID 0 array and I dual boot to XP Pro and Vista Home Premium. Problem occurs with either OS and does not occur doing anything other than FSX including torture testing a four cores at 100%.Start FSX default flight engine already running - after a minute of flying I get a long (several second) beep from the *system* speaker, not the sound card speakers. Hitting Q does not silence it. After a few seconds, it goes away. Seems to occur randomly.It's not the stall horn nor the overspeed warning. I've run task manager and coretemp alongside and it's not an overheat issue. I did slew to FL30 and cut the engine and glided around for a while with no problem so I'm at a loss as to what it might be.I've only flown FSX 3 or 4 times while building the system and haven't had that happen so I'm a bit puzzled.Anyone ever run into this before?I plan on trying a flighty with the glider just to see if it's a sound issue but in both Vista & XP? And with the system speaker?Thanx,VicQ6600 G0 CPU 2.4 o/c 3.6Evga 680i A1 with P30 BIOS 2G XP2-8500 DDR2 1066FSB Mushkin 996535 RAM 5-5-4-12-2T320G 7200 HD partitioined for XP/Vista/Programs 2 - 74G Raptors in RAID0 500G 7200 HD for backup SATA DVD burner Evga 8800GTS 640 PCIx Kandalf LCS case w/ built in liquid cooling 850W Thermaltake power supplyVisit the Virtual Pilot's Centerwww.flightadventures.comRadar Contact Supporter: http://www.jdtllc.com/

Vic,Are you perhaps running one of those system monitor programs that comes with your motherboard that beeps if the CPU or system fan drops below a certain speed or the temp briefly spikes above a certain level? If so, try disabling the alarm feature of this program and see if it goes away. You may also want to consider that a beep from such a program is telling you something (like on my son's recently built computer that his ACF7P fan stopped working completlely after a few weeks, sending his CPU temp into the 70's :-eek).Gary

I'll double check but it seems to be only with FSX. If I run OCCT for 30 minutes with all four cores maxed at 100% my temps don't get above 54C - even FSX doesn't stress the system like that. BUT is *is* a system beep. Other than being annoying it's caused no issue so far. However, I will continue to test it out. After I set all the usual tweaks tha I like, it will be interesting to see if the beep goes away.Hmm - I didn't monitor the video card - need to check those temps too.VicQ6600 G0 CPU 2.4 o/c 3.6Evga 680i A1 with P30 BIOS 2G XP2-8500 DDR2 1066FSB Mushkin 996535 RAM 5-5-4-12-2T320G 7200 HD partitioined for XP/Vista/Programs 2 - 74G Raptors in RAID0 500G 7200 HD for backup SATA DVD burner Evga 8800GTS 640 PCIx Kandalf LCS case w/ built in liquid cooling 850W Thermaltake power supplyVisit the Virtual Pilot's Centerwww.flightadventures.comRadar Contact Supporter: http://www.jdtllc.com/

Yes I would take a look in the BIOS screens and see if I saw anything related to "system bell" or "system alert", "ring bell on alert"--those types of options.Could be a fan connector with no fan attached, etc.Let's hope that's all it is. That is a strange one...does it only do it when FSX is running?RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian

OK, I now know what the problem is but how to fix it?Seems the graphics system doesn't like the overclocked bus. If I drop back to stock- runs like a top - overclock get the beep. Spoke to Evga tech and it is the video card that is signalling low voltage.I see in the BIOS that the PCIx voltage can be adjusted but I've not read anything about it. If the card is complaining about low voltage I would think that bumping the voltage up to the PCIx slot would help. Anyone have any thoughts on htis and any idea of the safe limit to this type of overclock?At normal graphics usage there is no problem but intensive activity like 3D Mark or FSX cause an issue.VicVisit the Virtual Pilot's Centerwww.flightadventures.comRadar Contact Supporter: http://www.jdtllc.com/

Vic,If your PCI-E bus speed is set to auto in your BIOS, it may be scaling up with your overclock and causing this problem. Most motherboards nowadays allow you to lock the PCI-E bus to a specific speed. Tyr locking your PCI-E bus to 100MHZ.Gary

Gary - Thanx - I'll give it a shot. I also spoke to Thermaltake and they gave me some things to try with the PSU - if neither work - it's RMA PSU time.Onward & upward.Funny, had no problems during the benchmarks altho the graphics weren't set as high as my defaults or 3DMark.Oh well, live and learn. In over 25 years of building and working with computers, they still throw me a curve every now and then.VicVisit the Virtual Pilot's Centerwww.flightadventures.comRadar Contact Supporter: http://www.jdtllc.com/

Just a heads up on the continuing saga and a BIG kudo to Thermaltake. I called them yesterday and tech support decided to RMA my PSU. It arrived by UPS this afternoon! That's overnight - way to go TT!.Sadly, the problem was NOT the PSU, the tech didn't think it was nor did I but Evga tech support insisted the problem was the video card not getting enough voltage.Called Evga back and convinced them that it was pretty unlikely that I'd get two brand new bad PSU's in a row. Lo and behold they kicked my issue upstairs and the fellow I talked to researched and said it was a known issue when overclocking the Q6600 CPU on this motherboard. Seems on some boards it causes the speaker to trigger but has no performance hit.My options were to ignore the beeping(hah!), don't overclock(hah! hah!) or RMA the mobo. Guess which one I chose?? :)Hope I get one of those that doesn't beep!Once we nailed down the issue there was no problem getting the RMA.Now I wait and keep repeating "This is a fun hobby, this is a fun hobby, this is a fun hobby.................."VicVisit the Virtual Pilot's Centerwww.flightadventures.comRadar Contact Supporter: http://www.jdtllc.com/