game freezes and starts beeping when i click/press keys on keyboard.

[squallypo]

this is pretty much happening on this game alone : batman arkham city
and also while emulating zelda windwaker on dolphin emulator

this is not my computer but im trying to help a friend that has a similar system than mine, his specs:

ryzen 5600x
rtx 4070 asus dual
psu xpg pylon 750w bronze
4x8 (32gb total) xpg spectrix 3200 ram
win 10 pro

videos of the problem:
do turn the audio so you get to listen to the beeping sound.

https://imgur.com/a/SjqdT6C

https://imgur.com/a/r6MnxJ0

if theres anything else to provide let me know.

 

[Hyderz]

is the system overclocked? drivers updated?

 

[squallypo]

is the system overclocked? drivers updated?

from what he told me he used to have it with curve optimizer on - on certain cores, but he also tried it on default mode meaning no curve optimizer and still the problem occurred, also drivers are updated yes.

 

[DarkDreams]

Never played the game, is it in the introductory cutscene? Because PCGamingWiki has a note about needing PhysX or disabling it

 

[squallypo]

Never played the game, is it in the introductory cutscene? Because PCGamingWiki has a note about needing PhysX or disabling it

I played it on my PC without a problem and as I've said we have similar systems, the only thing we have different is the PSU and the rams different models on both cases: I have 2x16 gb ram Kingston fury and a core reactor PSU.
I really don't understand this issue that he's having tbh.

 

[Bill_Bright]

It is important to determine where the beeping if coming from.

Does it come from the computer speakers or from inside the case? If inside the case, that is from the BIOS and the beeps indicate a system error. Note the pattern of the beeps - like 2 longs and a short beep, or 4 short beeps as examples.

 

[squallypo]

It is important to determine where the beeping if coming from.

Does it come from the computer speakers or from inside the case? If inside the case, that is from the BIOS and the beeps indicate a system error. Note the pattern of the beeps - like 2 longs and a short beep, or 4 short beeps as examples.

The beeping comes from the computer speakers not from the motherboard, this motherboard doesn't have the "speaker" device sound thingy.

 

[DarkDreams]

I played it on my PC without a problem and as I've said we have similar systems, the only thing we have different is the PSU and the rams different models on both cases: I have 2x16 gb ram Kingston fury and a core reactor PSU.
I really don't understand this issue that he's having tbh.

PhysX is software and this is most likely a software issue anyway. He can try downloading and installing PhysX from here.

 

[squallypo]

PhysX is software and this is most likely a software issue anyway. He can try downloading and installing PhysX from here.

I'll tell him to give it a try thanks

 

[XpanD]

Does your friend have any keyboard accessibility settings enabled in Windows? The beeps sound a bit too low in frequency for it to be that, but Sticky Keys/Toggle Keys tend to come up at the most inopportune times if enabled.

 

[squallypo]

Does your friend have any keyboard accessibility settings enabled in Windows? The beeps sound a bit too low in frequency for it to be that, but Sticky Keys/Toggle Keys tend to come up at the most inopportune times if enabled.

As far I know no, he doesn't have that enabled.

 

[Bill_Bright]

this motherboard doesn't have the "speaker" device sound thingy.

That's too bad - especially since all ATX format motherboards support a system speaker and at least some basic beep codes. And they have the necessary connector for one too. It is right there with the case's front panel power switch, reset switch and drive activity LED header on the motherboard. Takes a couple seconds to install. I always add one to our builds if the motherboard does not already have one.

They are so inexpensive too. See It is very inexpensive to add a System Speaker. Note that price is for 30 speakers!

Even if not concerned with beep "error" codes, I find that one, short beep, indicating a "successful" POST (power-on self test), reassuring.

 

[squallypo]

That's too bad - especially since all ATX format motherboards support a system speaker and at least some basic beep codes. And they have the necessary connector for one too. It is right there with the case's front panel power switch, reset switch and drive activity LED header on the motherboard. Takes a couple seconds to install. I always add one to our builds if the motherboard does not already have one.

They are so inexpensive too. See It is very inexpensive to add a System Speaker. Note that price is for 30 speakers!

Even if not concerned with beep "error" codes, I find that one, short beep, indicating a "successful" POST (power-on self test), reassuring.

this is Micro ATX though, i have a system speaker at my place i offered it to him, apparently he tested and again the sound comes from the computer speakers not the motherboard.

PhysX is software and this is most likely a software issue anyway. He can try downloading and installing PhysX from here.

apparently so far this has done the job for him, i told him to keep testing but so far no more of the problem, thank you

edit: nvm its still happening :/

 

[squallypo]

alright incase anyone is wondering we found the culprit or what it looks to be so far after many test:
it was a Bluetooth receptor... after removing it, no more of the issue and it was tested many times just to be sure.
how the problem became alive? apparently when using the xbox controller with this particular game again i dont understand how this works and why just this game, but only with this game the problem came alive, we removed the receptor and tried another and no more issues, maybe someone can elaborate on why something like this can happen? and why only with this game.

 

[LabRat 891]

That noise happens from repeat/held keystrokes, IIRC.

Check accessibility options, make sure StickyKeys is off.

However, this is almost reminding me of how FEAR had an engine incompatibility with many Logitech HIDs.
Try unplugging the KB or use an entirely different KB. Maybe, even try a BT KB as a diagnostic step?

Edit:

alright incase anyone is wondering we found the culprit or what it looks to be so far after many test:
it was a Bluetooth receptor... after removing it, no more of the issue and it was tested many times just to be sure.
how the problem became alive? apparently when using the xbox controller with this particular game again i dont understand how this works and why just this game, but only with this game the problem came alive, we removed the receptor and tried another and no more issues, maybe someone can elaborate on why something like this can happen? and why only with this game.

Yup. Driver conflict I'd bet. Glad it's fixed.

 

[squallypo]

That noise happens from repeat/held keystrokes, IIRC.

Check accessibility options, make sure StickyKeys is off.

However, this is almost reminding me of how FEAR had an engine incompatibility with many Logitech HIDs.
Try unplugging the KB or use an entirely different KB. Maybe, even try a BT KB as a diagnostic step?

Edit:

Yup. Driver conflict I'd bet. Glad it's fixed.

it was some generic Bluetooth receiver, still one do wonder, why just on this game ? he has played other games while using this receiver with the xbox controller and never happend this issue till now.

 

[LabRat 891]

it was some generic Bluetooth receiver, still one do wonder, why just on this game ? he has played other games while using this receiver with the xbox controller and never happend this issue till now.

Not sure, but...
I've experienced USB-BT/WiFi interference on a Steam Deck.

Personally, I'd lean towards some weird HID driver incompatibilities.
You mentioned 1 particular emulated game does the same, and Arkham Asylum is a 'port' also. So, I'd presume its related to how input is 'adapted' into the respective game engines.

You might have some luck finding an answer in the emu community.
-not uncommon for devs and contributors to 'pipe in'.

 

[Mr_KayZ]

this is pretty much happening on this game alone : batman arkham city
and also while emulating zelda windwaker on dolphin emulator

this is not my computer but im trying to help a friend that has a similar system than mine...

This issue had been nagging at me for the past year and a half, and I had been trying to find a possible reason for this. I believe I might have finally cracked it.

Some background about me: I am an electrical engineer who has worked in a tech support role for a while, and am currently a sysadmin at my current workplace. Sometimes some workstations freeze up when running intense graphical applications (CAD rendering mostly) where these beeps have been noticed. None of the senior IT knew what was going on, initially, but this wasn't completely commonplace either. But when you have at least one machine a month acting up in this manner, a few eyebrows definitely will be raised.

So I went on researching, asking on forums, reading up on Microsoft documentation, etc. etc. Not a single reference to anything like this in any manner or form regarding this bizarre bug with the following symptoms:
- Frozen/Black screen (mostly frozen) - GPU driver failure that we can guess
- Moving the mouse causes beeps to occur for some reason

Naturally speculation of what could be the cause has been brought up here and there, with some suspecting that it's possibly a buffer overflow of sorts from the mouse (this was a real thing in the past when the keyboard buffer fills up, and beeps accordingly to indicate that future keypresses were missed by the system) when the GPU driver crashed, to beep codes from the PC. Neither claims however have sufficient evidence or proof to back it up, from a software and hardware perspective after all. But after running the GPU driver reset combination (Win +Shift + Ctrl + B), all of a sudden I heard that single beep. And it was the same beep as all other beeps from the original situation. That is what made me speculate the following reason as to why the beeps occur:

When trying to move the mouse on a frozen screen, the GPU tries to display that moving mouse but fails, so it auto resets and fails again, and keeps on reseting, but that just causes it to beep even more! And that is why you get the endless beeps.

I think this is what's going on, that's the most likely and plausible situation to me. Naturally, there are holes: Why doesn't it beep like normal during other driver crashes (i.e. black screen driver timeout messages, etc.)? The thing is it depends on the type of crash most likely from what I can see so far. All of the frozen screen situations cause the beeps to occur because perhaps for that failure mode, trying to reset the graphics drivers is the best way to fix it. I cannot fully say unless a senior driver software engineer chimes in.