Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Computer shuts down following many short beeps

  • Please log in to reply
No replies to this topic

#1 simonhans


  • Members
  • 1 posts
  • Local time:06:52 AM

Posted 23 September 2009 - 03:10 AM

Hi there, first post. I'll be as specific as I can. However I'm an absolute beginner re computers so let me know if there is more you need from me.

(MS Windows XP home SP3 // Intel Celeron M Processor 1.40 ghz)

Thanks in advance this is driving me nuts. A series of four or five short beeps then the system shuts down completely, straight to black. I can restart immediately, it beeps twice at startup and then continues on until again soon after normal operation the same thing happens. Some times it doesnt happen at all but runs very slow. After cleaning it out with CCleaner it sometimes runs a bit better, sometimes even runs as quick as it used to.

Eset 4.0 detects literally nothing (and has recently stated an error on startup, with egui.exe) and Spybot detects nothing wrong. Tea timer was active. Have since removed Spybot.

About two months ago, when the issue began, Spybot would always beeep and then shut down when I ran the scan; same happened for Kapersky. This makes me think its a virus, not power supply or other. Have since removed Kapersky and now only run Eset 4.0.

Have run Eset in safe mode and it detects nothing. Had run Spybot in safe mode in the past and the error persisted, beeps, shut down. Followed by anger and resentment.

Folks, any help you can give would be great. I am at a total loss! This just isn't my department at all. Thank you. And if you have any instructions please spell it out for me...


EDIT: Moved to more appropriate forum

Edited by garmanma, 23 September 2009 - 09:33 PM.

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users