Computer beeps when turned off.


Recommended Posts

I had an Asus P5W DH Deluxe, then the BIOS got screwy, so I RMA'd it.

I got my new one about a month ago, and for some reason, when I turn it off, it emits a beep.

It's something odd too, because if I cut power via the PSU while the system is on, it beeps. If I shut down normally, it beeps. If my CPU overheats and it turns off the computer, it beeps.

As far as I know, the MB doesn't have a speaker on it, nor did I attach one (my case doesn't have one, Antec P180B).

Although it's a minor problem, I'm confused at what's making it. And there is a small basis for me to be worried.

Still, my MB doesn't beep on post, so I know it's not an internal speaker.

It's also not my normal speakers, which were disconnected, and the beep comes from the MB, presumably.

Specs:

MB: Asus P5W DH Deluxe

CPU: Intel Core 2 Quad Q6600 (B3)

GPU: eVGA nVidia GeForce 8800GTX

RAM: 4x1GB Corsair XMS2

HDD: 2x 500GB Seagate Barracuda (7200.10)

Case: Antec P180B

CPU HSF: Thermaltake V1 (was using stock earlier, when the beep still rang)

Any ideas? Is this something I should be concerned about?

Link to comment
https://www.neowin.net/forum/topic/578333-computer-beeps-when-turned-off/
Share on other sites

chasis intrustion jumper on default

Well, the beep isn't the only thing odd with the motherboard.

When I turn on my psu, everything starts running (fans,etc), but nothing shows up on the screen, and powers down a few seconds later. To turn on my pc, I hit the power button.

Any more ideas? :x

chasis intrustion jumper on default

Well, the beep isn't the only thing odd with the motherboard.

When I turn on my psu, everything starts running (fans,etc), but nothing shows up on the screen, and powers down a few seconds later. To turn on my pc, I hit the power button.

Any more ideas? :x

Turning your PSU on sends a short signal (good) to your mobo to "test" things. The only time you should turn your PSU off is: When going away for more then 3 days. When a lightening storm is very very close. When working on the computer. Otherwise, it could damage the PC by turning that on and off again and again.

The beep could be that the mobo is just faulty - ask for another RMA. It's a PITA, but, it could clear the problem. If not, contact ASUS support.

I turned my psu off to change the internals and such.

I really do not wish to wait a few weeks to get this motherboard RMA'd as it is my only computer that I can use at the moment.

-edit

I don't really mind it, but is it something I should be really concerned?

Also, my motherboard beeps when it turns off from the 'on' state, meaning OS, etc. When it's on its 'standby' mode, where the mb is getting power but not really doing anything, and I turn off the PSU, it doesn't do anything.

I don't want to damage my hardware, so is this something really bad? ><

default off.

To clarify, the beep is a pretty long one, and dies out toward the end.

it might be the HDD's, but I doubt it. I'll look into it.

I had the same MB before I RMA'd it, and it didn't beep. I just put everything back when it came, so I'm really confused. This includes the HDD and that's why I don't think it's the HDD..

Also, the mb I had before I RMA'd didn't turn on when the psu switch was first turned on, but this one does. Kind of odd, but I don't think there's a problem in that.

My computer never made this beep before until i got my new drive. I tried to record it as best i can with my phone... the beep is at the 12s mark.

edit: i just noticed you said it was a long beep... this one is about the same as the POST in duration.

Recording.wav

i have a SOYO motherboard

and last couple of days its been doing weird ( i know its the ABR function) so i disabled that... and now windows says a couple of times its too hot (108?C and suchs but cooling is like cold) anyway the beeping came from ABR funtion

I asked Asus: http://vip.asus.com/eservice/techmailstatu...708071020397301

They said:

This doesnt sound like anything that I have seen or heard before. It does not sound like it should be anything to be concerned with at this time. It sounds most like something loosing its charge as the system looses power. it does not sound like a large problem unless what ever is making the sound is going bad. testing this would just require multiple shutdowns listening closely to teh hardware to pinpoint where the sound is coming from.

Typically and RMA takes 10 Business days from the time we receive the board.

Thank You for using our technical support deparment. Our goal is 100% customer satisfaction from our valued customers. Please take just a moment to fill out our customer service survey. With these reulsts we can improve our customer satisfaction and provide you with better service the on your next call. Thank you for taking your time to complete this survey.

Please do not respond to this email. If this does not solve your problem, or if you need further assistance, please have your case number ready, then contact Technical Support at 812-282-ASUS (2787) (M-F 8:30 AM - 8:00 PM EST).

Sean Reck

Support Engineer

Asus Technology

Http://usa.asus.com

Phone: (812) 282 ASUS (2787)

I guess I should keep it for now

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      467
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!