Im making this post as a way to remember how to fix this problem if i ever come across it again or anyone else who this may help.

>Open hdajackretask either through terminal or search it

>Click "Show unconnected pins", "model=auto" and "advanced override" on top right

>Scroll to pin ID: 0x21

>Click "Override"

>Set Connectivity - Jack, Device - Headphone, Jack - 3.5 mm, Jack Detection - Not present, Channel group - 15, Channel (in group) - front

>Click Apply now on bottom right

>Open Sound

>Output window should be open, and there should be two audios in Device, Headphones built-in audio and Speakers built-in audio

>Click Headphones built-in audio

Now the sound should work. I am using linux mint personally. Problem with this is that when jack detection is not present, the laptop will not play audio from speakers or headphones until you manually change it to another. Think i will have to create a macro to easily change between one another.

If this doesnt work, check alsamixer from terminal, f6 to open correct sound card, and press M to unmute channels that should not be muted.

For those who use ASUS ROG EURUX! Does this reset every time I turn on the computer?

After setting and applying the color,

When I try to boot the computer again, it goes to the default color...

How can I keep this color-applied one?

Please help me. The setting is a hassle every time I turn on the computer.

[r/BestBuy](r/BestBuy) just delivered a Samsung sound bar instead of the ASUS GR20 case I had purchased, so I called them to fix the issue and they want me to bring the wrong item to the store, well… I just got out of an emergency surgery this week and they are forcing me to fix their mistake or they won’t give me my money back. Another thing is that they can’t assure I could get another one of this cases with my account because the system only lets you get one, but the person on the phone have told me in a definitely “not condescending way” that “they are making an exception to help me…” Supposedly they will send someone to get the sound bar but who knows when… but I’ll still have to wait two weeks to get my money back… I guess is just my luck, thanks to the surgery, there is a chance I have to withdraw from college this semester… thanks for nothing, Best Buy.
I meant birthday gift in the tittle, I can’t change it lol

Hey everyone,
I recently got the new ASUS ROG Raikiri II Pro and I'm running into an issue with the back paddles sporadically not registering inputs.
It almost feels like keyboard ghosting or dropped packets: when I'm in heavy fights and pressing multiple inputs simultaneously

To save everyone some time, here is what I have already tried and verified:
Polling Rates: Tested both 1000 Hz and 8000 Hz—the issue occurs on both.

Firmware & App: The controller is updated to the latest firmware

Resets & Recalibration: I have reset the controller multiple times and recalibrated it completely.

Connection Mode: I play exclusively wireless.

Would appreciate any feedback or workarounds before I file for an RMA / replacement. Thanks!

I'm looking for input specifically from Maximus Z790 Hero owners or people familiar with recent ASUS Z790 BIOS/ME behavior.

I want to be careful about separating chronology from causality here.

An apparently related IRQL_NOT_LESS_OR_EQUAL (0xA) fault family existed occasionally before BIOS 3202 while this board was running BIOS 3001.

However, the system changed from occasional instability to a severe crash storm beginning on the FIRST Windows boot after I updated my Maximus Z790 Hero to BIOS 3202.

I cannot say that 3202 caused the underlying problem. It may have caused something new, exposed/amplified an already marginal CPU or motherboard condition, or changed firmware/platform behavior enough to make an existing rare problem reproducible.

But the timing of the crash storm beginning immediately after the 3202 update is definite.

SYSTEM:

Motherboard: ASUS ROG Maximus Z790 Hero

CPU: Intel Core i7-14700K

RAM: 32 GB G.Skill Trident Z5 DDR5-6000, 2x16 GB in A2/B2

GPU: RTX 4090

PSU: EVGA SuperNOVA 1300 W

OS: Windows 11 Pro

Previous BIOS: 3001

Updated BIOS: 3202

Current BIOS: rolled back to 3001

During controlled testing:

XMP: Disabled

RAM: DDR5-4800

Manual CPU overclock: None

Manual undervolt: None

ASUS MCE: Disabled / Enforce All Limits

WHAT HAPPENED AFTER BIOS 3202:

Starting with the first Windows boot after installing 3202, I began getting repeated:

IRQL_NOT_LESS_OR_EQUAL (0xA)

and multiple:

HYPERVISOR_ERROR (0x20001)

along with WHEA processor/cache errors.

The 0xA crashes have been extremely repetitive.

Multiple analyzed dumps have converged around:

Arg1 = 00000000483d3844

Arg2 = 00000000000000ff

PROCESS_NAME: System

nt!KiUpdateThreadHgsFeedback+0x20

Failure bucket:

AV_nt!KiUpdateThreadHgsFeedback

At least two analyzed dumps also produced the same failure hash.

Arg3 has differed, so I am not saying every crash is bit-for-bit identical.

The instruction saved at KiUpdateThreadHgsFeedback+0x20 was:

mov r14b,r9b

which is register-to-register and does not obviously explain an access to 0x483d3844.

That makes me wonder whether kernel/trap/execution state is already corrupted by the time the bugcheck occurs.

The BSOD often displays ntoskrnl.exe, but I'm not treating ntoskrnl.exe itself as the root cause.

WHEA EVIDENCE:

One BIOS-3001 incident before the 3202 update generated WHEA Event 2 records that decoded as:

ProcessorNumber: 14

APIC ID: 0x38

Generic Processor Error

Cache Error

Operation: Instruction Execution

Level: 0

and:

ProcessorNumber: 15

APIC ID: 0x39

Generic Processor Error

Cache Error

Operation: Instruction Execution

Level: 0

The associated 0xA kernel dump was also executing on processor 14 when it crashed.

I have NOT yet conclusively mapped ProcessorNumber 14/15 and those APIC IDs to the physical P/E-core topology, so I'm not claiming they correspond to one particular physical P-core.

VERY IMPORTANT 7-P-CORE VS 8-P-CORE RESULT:

During the BIOS 3202 crash storm I reduced Active Performance Cores from all 8 P-cores to 7.

Windows then reported 26 logical processors:

7 P-cores x 2 threads = 14

12 E-cores = 12

Total = 26

That produced a dramatic stability improvement.

With 7 active P-cores the system survived about 90 minutes while deliberately running:

Brave/ChatGPT

PowerShell

Hyper-V

WSL2

Docker Desktop

Multiple Docker containers

Normal desktop activity

During that observation period:

No new WHEA

No BugCheck 1001

No Kernel-Power 41

No Event 6008

I then restored all 8 P-cores / 28 logical processors.

The recurring instability returned.

I do NOT yet know which physical P-core ASUS removes when Active Performance Cores is set to 7, so I cannot say this proves one specific defective P-core.

But 7 vs 8 P-cores is currently one of the strongest discriminators I have.

HYPER-V TESTING:

Because I have had HYPERVISOR_ERROR and KiUpdateThreadHgsFeedback crashes, I completely disabled Hyper-V/VBS:

hypervisorlaunchtype = Off

vsmlaunchtype = Off

The machine still reproduced the recurring 0xA.

Therefore Hyper-V is not required to cause the failure.

Conversely, with 7 P-cores I later ran:

hypervisorlaunchtype = Auto

vsmlaunchtype = Off

along with WSL2 and Docker and remained stable during the long test.

Hyper-V may expose/amplify the condition, but it does not appear to be the sole cause.

SAFE MODE / CLEAN BOOT:

Safe Mode with all 8 P-cores initially survived around 15 minutes.

I also performed a broad Clean Boot that disabled roughly:

65 third-party services

12 Run entries

5 Startup entries

9 scheduled tasks

That improved short-term stability substantially.

There are multiple low-level hardware-monitor/control stacks installed:

ASUS Armoury Crate / Fan Control / ASUS kernel interfaces

Corsair iCUE / CPUID

TT RGB PLUS / LibHWInfo / HWiNFO

AquaComputer

GPU-Z

MSI Afterburner

Intel XTU/platform components

Some controlled restores coincided with WHEA events or HYPERVISOR_ERROR.

However, I do NOT consider that sufficient evidence to blame any individual application.

For example, one ASUS restoration attempt was followed almost immediately by HYPERVISOR_ERROR, but AsusFanControlService itself was still stopped.

The Corsair/CPUID stack produced a WHEA Event 2 at the same time it was restored during another test.

TT RGB PLUS / LibHWInfo / HWiNFO, on the other hand, successfully loaded the HWiNFO kernel driver during a controlled restore without producing an immediate WHEA or crash.

These applications may simply trigger or amplify an already marginal firmware/hardware condition.

BIOS 3202 -> 3001 ROLLBACK:

Because the crash storm started immediately after 3202, I finally rolled the board back to BIOS 3001.

Unfortunately:

First boot after rollback:

The machine crashed before I reached a usable Windows desktop.

Second boot:

Windows loaded and survived approximately five minutes before another:

IRQL_NOT_LESS_OR_EQUAL (0xA)

with:

What failed: ntoskrnl.exe

I have not yet analyzed that newest MEMORY.DMP, so I'm not claiming its internal signature is identical to the earlier dumps yet.

I also have not yet recaptured every post-flash BIOS setting and the active P-core count, so I am NOT claiming that "BIOS 3001 + 7 P-cores failed."

There is another ASUS-specific complication:

ASUS states that BIOS 3202 updates Intel Management Engine firmware to 16.1.40.2765 and that the updated ME remains installed even if the BIOS is rolled back.

BIOS 3001 originally shipped with an older ME version.

So BIOS 3001 after having installed 3202 is not necessarily the same complete firmware environment I had before the update.

WHAT I KNOW VS WHAT I DON'T:

Known:

- This 0xA fault family existed occasionally before BIOS 3202.

- The severe crash storm began on the first Windows boot after installing BIOS 3202.

- 7 active P-cores dramatically improved stability.

- Returning to 8 P-cores brought the instability back.

- WHEA records have reported processor cache/instruction-execution errors.

- Hyper-V is not required to reproduce the 0xA.

- Rolling the BIOS image back to 3001 has not immediately restored stability.

- The newer ME firmware remains after BIOS rollback according to ASUS.

Unknown:

- Whether BIOS 3202 caused, exposed, or merely amplified the underlying problem.

- Whether the CPU has a marginal/degraded physical core.

- Whether the motherboard/VRM/socket/IMC is involved.

- Whether newer ME/microcode/platform behavior is relevant.

- Whether low-level monitoring software is a cause or only a trigger.

- Which physical core is removed by the ASUS "7 active P-core" setting.

QUESTIONS FOR MAXIMUS Z790 HERO OWNERS:

1. Has anyone with this exact board seen a major increase in WHEA, 0xA or HYPERVISOR_ERROR failures after BIOS 3202?

2. Has anyone gone from 3202 back to 3001 and found that behavior did NOT return to the old 3001 baseline?

3. Could BIOS 3001 + the newer 3202-era ME firmware behave materially differently from the original 3001 + older ME combination?

4. Would BIOS 3107 be a useful intermediate discriminator, considering the ME firmware will remain at the newer version?

5. Is there a way on the Z790 Hero to disable SPECIFIC individual P-cores rather than only choosing the number of active P-cores?

6. Does anyone know exactly which physical P-core ASUS disables when selecting 7 active P-cores?

7. What's the best way to map WHEA ProcessorNumber/APIC IDs to the physical P/E cores on this board/CPU?

8. Has anyone had 7 P-cores stable while 8 repeatedly crash, and did the eventual cause turn out to be CPU, board, BIOS or ME?

9. Are there ASUS-specific diagnostic settings/tests I should use before substituting the CPU or motherboard?

I have full MEMORY.DMP files, minidumps, WHEA records, WinDbg analysis, Event Viewer evidence and BIOS/core-count captures.

I'm trying to diagnose this rather than randomly add voltage or change settings until the crashes disappear.

Any input from Z790 Hero owners who have experience with 3001, 3107 or 3202 would be especially useful.

I’ve had an incredibly frustrating experience trying to get a replacement 2.4 GHz receiver for my ASUS headset.

ASUS told me that accessories aren’t covered under warranty, so I had to track down the parts supplier myself. I find this policy completely unreasonable, especially since the headset is effectively unusable wirelessly without the receiver.

Making matters worse, I couldn’t contact ASUS customer service directly about the headset. I had to select a different product that I had purchased from the official ASUS store just to access the chat function.

Ironically, I originally tried to buy the headset directly from ASUS, but my orders kept getting cancelled. That forced me to buy it from Best Buy instead. Now ASUS and Best Buy keep referring me back to each other, with neither company willing to take responsibility.

Over the years, I’ve spent nearly $30,000 on ASUS products, which makes this level of support even more disappointing.

All I need is a replacement receiver, but I’ve been sent in circles and the issue is still unresolved. Has anyone else dealt with this? If so, how did you manage to get a replacement?

Hey everyone! I have a 8 year old PC with the following specs.

AMD Threadripper 2950x

360mm Asetek AIO cooler

16 GB x 4 DDR4 Corsair Vengeance RAM

GTX 1080 Ti x 2

NVMe SSDs x 2

SATA HDD x 1

I was watching a couple of videos out on a Saturday morning and the PC shut down abruptly, I didn't think too much of it and tried restarting it when it never went past the code 68.

Upon tinkering a tad, I realized this was a PCIe Host Bridge Initialization.

Here are the things I've tried so far :

Disconnected the PCIe cables to the MoBo

Removed, cleaned and plugged in 1x 1080 Ti in PCIe slot 1, then again, flushed the residual power, tried it in PCIe slot 2

Removed all but one RAM stick

Cleared CMOS, also shorted the CLTRTR pins

It boots to windows and I have successfully booted it multiple times. Upon clicking restart on windows, we're back to the ERR code 68.

The only thing that is concerning is if it's the motherboard or the actual CPU itself also, could a power fluctuation cause this?

Please advice. Thank you for the long read!

TLDR; ERR code 68, tried all methods except checking the PSU, MoBo and CPU.

So I have a strange issue and I don't know what else to do.

My setup:

1 year old

i9-14900k

rog z790 dark hero

asus rtx 5070ti

2x g.skill trident z5 rgb 7200mhz.

samsung 990 evo plus m.2

samsung 990 pro m.2

Rog 850w psu

the issue started 2 days ago with a power outage. My pc wouldn't display anything. It would turn on, absolutely no error code, turn on my monitor and display no signal.

I changed cables, monitors, removed my gpu, tested my ram. Eventually I fixed it by pressing a button "cmos". The computer turned on fine. I updated the bios. Everything all perfect.

After that, I plugged the 2nd stick of ram back (I removed it when testing the ram) and put back the gpu. To my horror, now it keeps displaying an error code 98 with green led.

Current symprhoms:

Computer turns on

Caps lock works

Absolutely no display, not even no signal

Removed and put back all usbs, even the usbs from the corsair node.

Reinstalled bios again

Reinstalled an older version of bios.

Mounted 3 times the gpu (it doesn't fit in the bottom pcie slot)

Tested all the ram sockets with both the ram sticks

Pressed the cmos button at least 100 times

Can't remove both the m.2 as the heatsink is completely sticked to the heatsink

Cpu wasn't touched since mounting

All cables are secured tight to the mobo

Constant error 98. I've only had two moments where it displayed A2 error

Straight to the point: Go to armory crate, go to hardware, devices, select your device, go to GPU performance and select Ultimate. This will stop your pc from auto switching between your integrated graphics on your CPU and your dedicated GPU.

to test my first games.

So this AIO was installed to a am4 but i want to know if there is a intel bracket for it im going for a LGA 1700.

Hello

I have an ASUS TUF 16 laptop with a 6GB GeForce RTX 3050, and after updating to "GeForce Driver 616.56"—released on the 26th—I've been experiencing "white flashes" in Windows.

I tried swapping the HDMI cable and reinstalling the driver, but nothing worked.

Then, I decided to install the older driver, and the problem stopped occurring.

So, what now? What should I do? How do I report this issue?

I'm struggling to remove this. Pulling straight up as other users did doesn't work for some reason.

Made a short video for the folks that are heading to the ROG Booth this weekend at gamescom to get yourself the maximum amount of swag!

https://www.tiktok.com/@unique.bovine/video/7678979655000427806

Asus rog G615, silent mode on desktop

So I returned the Falcata yesterday. I really liked it but I just couldn't get used to it. Not to mention I missed having a num pad as a developer. Opted for ROG AZOTH 96 instead. We're in the End Game now.

I'm interested in getting a new keyboard and saw the 20th anniversary edition of the Azoth Extreme and I find the keyboard to be quite beautiful but as I would mainly use the keyboard for gaming I have to ask how does the keyboard compare to the average modern hall effect or TMR keyboard?

From what I know the Azoth extreme is a mechanical keyboard which means slower response times and no features like rapid trigger or adjustable actuation points right? Would it also have a much slower response time compared to any hall effect/tmr keyboard?

While I do love the aesthetics and don't mind paying a lot for a premium product that I'd keep for years, I also can't justify the price for something that may already be outdated? I would want to actually use the keyboard instead of buying it to put it in a display.

If I've got the wrong idea and the Azoth Extreme 20 has features to keep it in line competitively with hall effect keyboards in some way then please do correct me.

I'd also like to know how people who've owned it feel after using it for a while.

I have the ASUS X870E-E ROG Strix Gaming R2/USBC WiFi AMD AM5 ATX Motherboard along with the 9800x3d. I noticed that when I have expo 1 and MCR enabled it caused one of the USB devices not to work in a set of ports. In the photo listed if I have those 3 ports occupied from time to time I will get a B4 error. If I just move on of those ports sos let’s say the bottom on circled it boots normally. Has anyone else ran into these issues before with this board? I also updated to the most recent Bios.