Start Up Bios Beep

[BadHairSpray]

Hi Guys,

At start up this morning on my Laptop (VGN-NR360D), twice, I got constant beep... sort of 1-1-1-1-1-1. This was right at pressing the power button before the bios screen came up.
The Third time it went into windows...

the bios is a Phonix bios. I m trying to find some info on the error codes but the constant 1-1-1-1-1-1-1 beep seem to have diverging views on what exactly could mean.

Any thoughs appreciated

 

[Lemur]

Two sites for beep codes, but I couldn't find one definitively for Sony Vaio...

Beep codes Definition from PC Magazine Encyclopedia

Computer Post / Beep codes

 

[Lemur]

Duh... Phoenix

BiosCentral - Phoenix BIOS Beep Codes

BIOSCHIP.COM :: PHOENIX BIOS beep codes

 

[TVeblen]

These also:
Sony VAIO Notebook BIOS Beep Codes

A series of single beeps like that is unusual. Are you sure there is not a pause between them?

 

[BadHairSpray]

Thanks for the quick response Lemur and TVeblen. Much appreciated

Yea it completely caught me off.. it was amost like a "fire alarm" just simply a constant 1-1-1-1-1..

 

[Lemur]

Can you record it/send it?

 

[TVeblen]

You know, I recalled (whilst stuck in traffic) that I once was trying to run a True Image CD with a Linux boot loader on a laptop with an IDE drive and would'nt boot the disk and I tried some things and it then it froze up and started beeping something like that - BEEP-BEEP-BEEP-BEEP and would not stop. Scared the crap out of me!

1) Do you have something in the DVD drive?
2) Did it do it just that once (twice), or does it do it every time you try and boot?

 

[spyknee]

Bad ram or maybe bios change concerning ram. Pull all sticks but 1, leave in lead slot. See if POST happens. If so enter bios and double check ram settings. They should be manually input if possible. Manufacturers voltage and timings only. Or set to "AUTO".
If no POST, cycle thru each stick and see if POST happens. If no POST, do same process with each ram slot in turn.
You could have 1 failing stick of ram. Mobo slots failing.?????????????

Its ez with a desktop, a laptop hmmmmmmmmmmmmmm.

 

[strollin]

Any chance a book or something else was resting on the keyboard? If not, could be a stuck key.

 

[Wishmaster]

May sound silly, but do you have a key on Keyboard stuck down?

 

[BadHairSpray]

Thanks for taking time out to respond everyone. Its very much appreciated.

The beeping happened twice this morning. (and on the third occassion it booted into windows) Since then I restarted it once more and it has been normal.

As for the keyboard - I do use an external keyboard attached to the laptop for conveninence. There was definitely nothing in the DVD drive and no book or anything etc. As for the key being stuck, I didn't really notice anything at that point (but early morning anything is possible!!) but I ll defnitely keep a look out keep a look out.

One thing i did notice was that a couple of days ago, there was an update that came via Windows Update for the keyboard. The update changed the graphics etc of how the volume key works so I would presume it was something of a "substantial nature" the keyboard is always attached to the comp so could it be something with that? I always make it a point to remove any external HDD etc...but yea the keyboard is always attached.

If it does continue to start as normal should I still do the RAM test specified above or let it be? I can manage the ram removal - testing and putting it back...but anything more physical with the MB will probabaly be out of my league to be honest which I wouldn't wanna attempt it on my own..

And you are right I did have my camera ready to record it and upload it when I re-started..(seriously does sound like a fire alarm!! that s what scared the crap outa me in the morning....kinda like imminent doom here it comes noise - if u get my drift!!)

 

[spyknee]

If the machine POST'ed get, an DL memtest 86. You will make a bootable disk with your puter, go into bios and select cd rom as primary boot device. Reboot with memtest disk and have it run. You could let it run all night and see if you get ram errors. W7 also has a mem diagnostic option if you can get to OS boot and schedule it.
Many drive manufaturers have diagnostic boot disks. You could also check your drive.
Hell the ram sticks could just need re-seated. You rough with it or drop it?

With my Gigabyte UD3R/P45, that beep code meant some type of voltage error. In my case default voltage settings did not like the rams required voltage settings.
Got POST with 1 stick and set bios and good togo.

 

[TVeblen]

OK. More clues!

A couple of ideas:

• Remove the second external keyboard and run in that way for a while to see if the issue disappears. You could try simply unplugging it, disabling it and unplugging, or removing it from Device Manager.
• Do a system restore to a point before you installed the Windows Update for the keyboard (Hopefully, you do not have Windows Update set to automatically install updates). Run in that way for a while to see if the issue disappears.

Lets see if we can identify or eliminate the keyboard as the cause. That will give us more clues to go on.

 

[BadHairSpray]

Done......the issue hasn't cropped up since the time it actually happened...which is strange to say the least...but I'll gladly accept that!!!! which makes me wonder...early morning half a sleep/wake...could I have had part of my hand or something on the key as suggested??!!! Anyways to be on the safe side...I ve done what you suggested. Shall run in in this way for a half week/week or so and report back.

Thanks again for taking time to think about the issue everyone.

 

[BadHairSpray]

Ok I thought I d report back with the progress. Glad to say I ve not had the issue crop up again. I ve reconnected the keyboard and the issue has not come back.

Something that did come up a couple of days after I made the above post was an error that read "Display Driver Graphics Accelarator for Windows stopped responding " . The log showed that this happed 23 times!!. Anyways on that day...i had the laptop running almost the entire day without the cooling pad under....this happened literally towards almost 1am so...I m thinking maybe it was heat related? I m not sure...anyways ever since I ve made sure the cooling pad is running and also it thankfully hasn't come up again..

I guess if something does crop up I ll be back.

Thanks again everyone for taking time to look into the issue and post.