Continuous siren-type beep code...K7D Master.

[SLO_N8]

I bought a refurb K7D Master from newegg which has been great to date except for 1 problem. I bought dual 1700+ Tbred's & SK-7's for it & currently have the 1 chip in w/o the L5 mod running @ 12.5x150 & 1.725vcore fully Prime95 stable. I used a fresh 256MB stick of Crucial PC2100(unbuffered) in this setup as I had just gotten it back from RMA.

My problem is a siren alarm that I get out of the case speaker when NOT in windows. This only happens when I have both the mult & fsb turned all the way up, I can run 12.5x133 or 9.5x150 w/o a single bug. It also doesn't happen all the time...fairly random. I'd attribute it to memory instability @ 150FSB but I've run Prime, cpuburn, & sandra loops on this thing while in windows @ 12.5x150x1.725v & have not been able to crack it. Is this something to be expected due to not running registered memory? I'd hate to drop the cash on registered memory & risk it not running 150FSB like my current memory is if its not the problem. I haven't found any articles anywhere on an Award "siren" type beep other than this page which states that "continuous beeping" is a memory problem. What I don't understand is how it could be so stable inside of windows if this is the case :)
http://www.pcguide.com/ts/x/sys/beep/award.htm

Any input would be greatly appreciated :D

[FunkDaMonkMan]

The only time I have received a continuous beep from this bios, is when It detects a change in the MBR, and prompts the user to press "y" before continuing.

Does it cause your system to hang, or does it just beep?

if it does not cause your system to hang, just disconnect the speaker.

[SLO_N8]

Thanks FunkDaMonkMan,

It just beeps, I can boot into windows & everything while its doing this. I would just unhook the speaker but it also kills MBM when it does this....it can't read temps. Originally I thought it might be temperature related, but how could it be? Its completely stable in windows, I've disabled CPU temp warning in the BIOS, & my load temps are around 60c. :)

I guess I'll just have to unlock the L5's & get both CPU's in there to see if its still doing it and then decide what to do...unless any1's got any more ideas :D

[FunkDaMonkMan]

eh! ... those load temps are high.

double check and make sure you have every temp monitor disabled. That's probably your problem.

Also, i hope you realize that temps will go up once you get another cpu in there.

[FunkDaMonkMan]

also.. try lowering your voltages. I can have my xp1600's at 1575mhz and the vcore at 1.5 volts. This dropped the temps 10-14C :eek:

[SLO_N8]

I have high temp alarm disabled. My temps & voltage are high because I've got the CPU running at 1875MHz & its a Tbred A, not a Palomino :)

I'm shooting for max stable OC, not coolest running CPU, hehe ;)

[cmcquistion]

The siren beep is a temp monitor thing. It does this when it thinks your CPU's are too hot. You said you've got temperature monitoring disabled?

Are you running BIOS 1.5?

[FunkDaMonkMan]

yea... i think something with the temp alarm is causing the beep. Even though you say its disabled, something may still be going.

[FunkDaMonkMan]

Right now i'm messing with my adjustable fans, and when i lower the fan speed... sometimes MBM will flip out and report 80º temps. I'm guessing that it doesn't like seeing the fan speeds change so much. But anyway, I'll get that continuous beep.

[cmcquistion]

Could be from RPM's monitoring. Some low speed fans with RPM monitor are screwy with some motherboards. The adjustable 80mm Enermax is a prime example. I've had more than one motherboard that wouldn't boot at all if the fan speed was cranked down, and/or, would go screwy if I lowered the fan speed, when the computer was on. My solution, cut the RPM wire.

[SLO_N8]

Thanks for the answers guys...got me puzzled then :)

I had the temp monitoring set to alarm at 70c, but I've never come close to that temp as far as the BIOS says. Its since been turned off, but if it is a temp alarm it must be whacked out because if I can get it to boot into windows w/o getting the alarm then it won't sound, in fact its been up for 2 days now folding on 1 CPU & 60c load temp & not a single siren.

Odd behavior here...now I'm hoping that its something to do w/ loading the mobo up good w/ only 1 CPU & when I get the other 1 in this behavior will stop. I reckon we shall see ;)

[cmcquistion]

Yeah, I had a weird experience with one of my K7D's, with the temp monitoring. I kept hearing this occasional chirp. Not the full-fledged siren, just a chirp....chirp.............................chirp.

Couldn't figure out for the life of me what was causing it. I could tell it was coming from the motherboard speaker, though. My temps were below 40C and I had the alarm set to 50C. I tried several things. Finally, I changed the CPU alarm temp to 53C, booted up, and I've never heard the chirping again.

Strangley, this didn't start until after I had put in a new RAID card in a 66 MHz slot and had changed to new, better heatsinks. I don't know if this had anything to do with that, but they are the only changes I had made to the system.

[SLO_N8]

I hear ya...I have a feeling the CPU temp you see in the BIOS & the CPU temp that the alarm reads are not calibrated with each other :)

Now if I could just get it to properly disable ;)

[cmcquistion]

I now have a rig that starts off the siren at 45C, when I have it set to go off at 50C. I just raised it to 56C in the BIOS and all seems well, now. I think the calibration is just off and I think it has to do with newer BIOSes, because I remember when I first got this board and was running one of the older BIOSes, that it went off right at 50C, every time.

[SLO_N8]

Yea, I never fixed this problem. I just never reboot, always shut down then start back up, & then it doesn't do it :)

[Kopfab]

MBM doesn't report accurate temperatures on my rig (K7D-Master L) - it doesn't detect any sensors ! The only thing I got to display something believable (cept the BIOS) was Fuzzy Logic 4.
YMMV of course

[cmcquistion]

I have three K7D Masters and all report the temps perfectly with MBM, using the sensor guidelines from the MBM website.

[Jon]

Originally posted by cmcquistion
I have three K7D Masters and all report the temps perfectly with MBM, using the sensor guidelines from the MBM website.

Same here with mine.

[poopygood]

Originally posted by cmcquistion
I now have a rig that starts off the siren at 45C, when I have it set to go off at 50C. I just raised it to 56C in the BIOS and all seems well, now. I think the calibration is just off and I think it has to do with newer BIOSes, because I remember when I first got this board and was running one of the older BIOSes, that it went off right at 50C, every time.


What multi/FSB are you running these 3 K7D's at and NOT getting the siren alarm? Also what CPU/memory?

[cmcquistion]

On my main rig, I run dual XP1600's (AROIA) @ 12 * 150 @ default voltage, using 2-512 MB sticks of Samsung Registered ECC PC2700 (I love this RAM and can't recommend it enough) with all the RAM settings tweaked pretty high (16,16,6,2,2,2,3). On my wife's dually, I run dual XP1600's (AGOIA) @ 11.5 * 150 @ 1.675 Vcore, using 2 - 512 MB sticks of Samsung unbuffered PC2700. Same RAM settings as the previous rig. On rig three, I run dual 1.2 GHz Morgan Durons @ 12.5 * 105 @ 1.725 Vcore with 128 MB :( of Crucial unbuffered PC2100 (soon to be upgraded to 2 - 256 MB sticks of Crucial unbuffered.)

For heatsinks, I use SLK-800's with Panaflo L1A fans on my main rig and my wife's rig. These keep temps very low, even overclocked. On the duron rig, I use SVC GC68's with Panaflo L1A fans. These work great and keeps temps below 105F on the Durons, and are good enough for stock speed cooling on XP's but aren't powerful enough for massive overclocking with XP's.

I have the alarm set to go off at 56C on all machines.