Recommended Posts

Hey all,

I'm looking for a bit of advice about what might cause a graphics card to have a POST-style beep? I bought myself a PowerColor HD6950 2GB earlier in the year, and ever since installing it it has often made a god-awful beeping noise when I start the PC, like a POST beep, but varying lengths and sometimes not at all. At first I thought it might have been a PSU issue, but I've since replaced the PSU with an 850W modular supply, and the beeps continue.

For the most part, I've ignored it, since it's blasted through Furmark and has played both Crysis 2 and Battlefield 3 fine on high-ultra settings, except this morning. This morning when I turned my PC on, it got stuck in a boot loop pre-post (i.e. no beeps at all) which fixed itself when I removed the graphics card. After reseating the graphics card and some of the PSU pins (at both ends, modular PSU), it's come back to life, but now I'm a bit more worried about the beep, since it's the only GPU that I've had that's done it. So does anyone have any idea what it means?

Cheers,

Majesticmerc

Link to comment
https://www.neowin.net/forum/topic/1037185-why-would-a-graphics-card-beep/
Share on other sites

Are you sure its the video card and not the motherboard?

Have you tried contacting PowerColor?

typically beeps will represent an error of some sort...depending on the type of beep could indicate a certain type of error.

Not true. Most motherboards give a single POST beep to say 'all clear'. Thats the typical situation. Do they also give beep codes for errors? Yes, but thats a minority of the time that you'd be hearing error codes. My point is that beep != error automatically.

Not to mention that he clearly knew that when he posted.

typically beeps will represent an error of some sort...depending on the type of beep could indicate a certain type of error.

That is my thought too, but PowerColor's documentation is, well crap. They've got a general FAQ and that's about it. I'm also puzzled by the fact that the beep tends to be varying lengths, and sometimes doesn't sound at all :s

Are you sure its the video card and not the motherboard?

Have you tried contacting PowerColor?

I'm pretty sure it's not the mobo, since the POST beep and the "other" beep can occur simultaneously. I haven't contacted Powercolor yet, but I thought I'd try here first :)

I'm pretty sure it's not the mobo, since the POST beep and the "other" beep can occur simultaneously. I haven't contacted Powercolor yet, but I thought I'd try here first :)

Whats the mobo?

I've never heard of a video card beeping, or experienced it in person (I do IT, so I see more than my fair share of hardware problems). It could be that the power draw through the PCI-E slot is causing an error condition on the board.

Does the mobo have a second PCI-E slot that you can test the card in?

Also, have you tried using a different video card to see if the problem persists? Or try that video card in another PC?

Video cards do have a BIOS, so I suppose it is possible you are seeing some sort of error condition from that, but the only one I could see if the card works fine as you say is a power problem.

Whats the mobo?

I've never heard of a video card beeping, or experienced it in person (I do IT, so I see more than my fair share of hardware problems). It could be that the power draw through the PCI-E slot is causing an error condition on the board.

Does the mobo have a second PCI-E slot that you can test the card in?

Also, have you tried using a different video card to see if the problem persists? Or try that video card in another PC?

Video cards do have a BIOS, so I suppose it is possible you are seeing some sort of error condition from that, but the only one I could see if the card works fine as you say is a power problem.

It's a Gigabyte EP35-DS4, which is an Intel 775 board. It's about 2 and half years old now.

I haven't tried it in the other PCI-E slot, but mainly because if I do, I have to pull out most of the hard drives and sound card to make room. I don't have access to another PC, so I can't try it in one. My 9800GTX used the same PCI-E slot though, so it should be fine shouldn't it given that it plays games fine?

My concern is power too, but I've got all the necessary power connected, and the PSU should be able to handle it. Would it not also show symptoms of failure when I stress test it with Furmark if it was drawing too much power?

Now that you've reseated the card and the power leads, is it still beeping?

I agree that the beeping you're hearing is most likely coil squeal, usually from insufficient power or defect. Graphics cards typically don't have beep code speakers (I don't know of any, but I'm leaving myself open for correction).

I have connected a beeper to my CPU fan power. It's designed to sound an alarm if the fan isn't working. It makes a short beep when I turn the computer on while the fan spins up.

I think that your graphics card is just beeping while it powers up. It doesn't indicate an error and can be safely ignored.

Reseating all of the power connectors in the computer every year is probably a good idea. It makes sure you have a good connection to all of the devices.

1. Check the power cable for the graphics card is connected

2. Install HWMonitor and you can check on the temperature of the graphics card

3. Make sure it's not the motherboard beeping and if it is check the manual as it will show the beeps codes for you

4. One beep usually means all is well, 2 or 3 beeps would indicate some kind of error.

I think it is definitely your motherboard, and also power related.

I found this text on page 29 in the pdf supplied by AMD on the Power Cooler website for your card...

The computer beeps and the boot process stops. Make certain that the graphics card is properly connected to the internal power supply and the motherboard.

PDF can be found here...

http://www.power-color.com/Manual/090106/Radeon_HD_6900_Series_ENG.pdf

Now obviously you do not have the boot process stop, at least not all of the time, but all signs point to an issue with the power.

It doesn't seem like a seating/placement issue if the computer has cycled before with the card installed, and it beeps. From past experience it's mostly probably an issue with the card not getting enough juice. Have you tried alternating the 8-Pin PCI-E power connectors that came with your PSU? It could be a duff cable. Make sure the connectors you are using are two of these badboys:

http://www.playtool....ctors/pcie8.jpg

Also it wont hurt if you temporarily remove your sound card and lie your hard drives on the case to test the card if the card beeps when connected to your secondary PCI-E slot. I have an older Asus board which is similar in age to yours. It has two PCI-E slots, one is x1 and the other which is at the bottom of the case is x16 so give it a go in the hard to access PCI-E slot on your board.

My final suggestions would be to flash your BIOS & clear CMOS by removing your motherboard battery for a little while

Are you sure it's a "beep" and not a noisy fan? I've tossed out old Video cards before because the fan becomes noisy, sometimes squealing when cold and then stops making noise when they warm up.

Take the side off your PC and power on, if the beeping starts, stop the fan with your finger or something, see if that stops the "Beep".

Spadman

interestingly, it failed to boot again this evening, and after having removed the graphics card, it continued to fail to boot, so it looks like the graphics card is not in the wrong. I've been through and reseated the graphics card, sound card, and RAM, and it seems to be working. I'm suspecting now that one of the RAM sticks that was causing the issues. It's also been rebooted twice since, and the beeping has seemed to have ceased as well! Is it possible that the RAM just needed refitting?!

Very confused :s

Have you fiddled around with the RAM voltages in BIOS or installed new RAM? I'm sceptical how your existing DIMMS have developed a 'fault' soon after installing the new card :s

The graphics card has been installed for about 3 months now, it's just that the beeping started after I installed it, but my PC only started failing properly in the last week or so. My first guess was that the graphics card failed (since it came back to life after reseating it), but the second time it was still dead even after removing the graphics card, so I'm inclined to think that it never was the graphics card (as others rightly said).

It's possible that the motherboard is just acting weird. My old motherboard wouldn't boot unless I put the ram in certain specific configurations, the ram was good, it was just the motherboard. I went through hours of diagnosing and there was little reasoning to be done, it was just picky with what ram slots I used.

Your video card beeping would probably signal a power issue though. A power issue could cause a lot of weird things to happen.

I'm suspecting now that one of the RAM sticks that was causing the issues. It's also been rebooted twice since, and the beeping has seemed to have ceased as well! Is it possible that the RAM just needed refitting?!

Very confused :s

^ Yes.

If you get in the case, and change something, you can slightly knock the RAM, or video card off -- sometimes the cables too.

Reseating parts often fixes a problem.

This topic is now closed to further replies.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!