Asus Gaming Laptop

... posted this question in the laptop thread but since this thread ... post reminded me: Is an Asus ROG Strix G16 with an ... you factor in the laptop premium. It might have the typical Gaming Laptop Issues (tm) but I... look at is a framework laptop, since they're a lot more ...

Lan Già Quá said: View attachment 3723381 nhìn chuyên nghiệp vl. bật thêm laptop nữa thì còn gì chuyên nghiệp hơn. y như chây đờ. xài 2 màn hình, 2 chuột, 2 bàn phím, 1 laptop gaming Asus

... yer alan tüm ilanlar; 1 ASUS ROG FALCHION RX Low Profile... Gaming Klavye Satın Al 21 Temmuz 2026 11:44 1 1 ASUS... Beyaz Mekanik Red Switch Türkçe Gaming Klavye İlan açıklamasında gerekli tüm... ancak sonrasında konfigürasyon değişikliği yapıp laptop kullanmaya geçtiğim için ürünü yalnızca...

... solidity and stability of the laptop. Punchy performance ASUS Vivobook S 14 OLED isn’t .... By integrating ASUS Memory Allocation Management7, we ensure optimal memory resource utilization, thereby boosting performance in gaming, creating..., and AI applications. Furthermore, ASUS Vivobook S 14 OLED features ...

... z13 نسخه 2025 ASUS ROG Flow Z13 (2025) Gaming Laptop, 13” ROG Nebula...

... for the response. My laptop is an ASUS TUF Gaming A15 running Windows 11... * GPU: NVIDIA GeForce RTX 3050 Laptop GPU * Display: 144Hz The game..., and sometimes even restarting the laptop doesn't help. I'm using the ... usage or temperatures, and the laptop doesn't seem to be overheating. ...

... alan tüm ilanlar; 1 [REZERVE] ASUS Vivobook 14 Satın Al 20...:22 1 1 [REZERVE] ASUS Vivobook 14 Laptop Mart ayında satın alındı..., kırığı, sorunu yok. Yanında Asus Tuf Gaming mouse verilecektir. Fiyata dahildir. Kutusu...

لابتوب الألعاب Asus Tuf f16 النص الاصلي: Asus Tuf f16 gaming laptop

모델명 : ASUS TUF Gaming A18 fa808up-S8017 CPU : AMD Ryzen 7 260 그래픽카드 : NVIDIA GeForce RTX 5070 Laptop GPU 8GB GDDR7 VRAM 메모리 : 32GB 프리도스 이거 180 주고샀었는데 안쓰고 계속 방치만 해놔서 처분할려고 집근처에 중고기기 매입하는 곳 있길래 물어보니까 80부르던데 그냥 넘겨야겠지? 중고거래는 너무 귀찮거든

..., потому что моя родная 3070 laptop в пое 2, например, работала..., а нифига. У меня Asus tuf gaming f15 fx507zr-hq007, взял к нему...

...& Ergonomic Comfort: This adjustable laptop stand for desk features smooth..., Microsoft Surface, HP, Dell, Google, Asus, Lenovo, and more. It provides ... laptop stand improves airflow to help prevent overheating during long work or gaming ...sessions. By keeping your laptop cooler, it helps maintain...& Space-Saving Design: This foldable laptop stand easily collapses when not ...

... Independent Incidents – Custom Build (ASUS Z390) and HP Pavilion Author:...18, 2020 Motherboard: ASUS ROG STRIX Z390-E GAMING CPU: Intel Core ... 2 – Personal HP Pavilion Laptop 2.1 System Configuration Hardware...2026: The user started the laptop after a long period of... as the cause. The laptop had not undergone any changes ...hardware (HP instead of ASUS, different SSD, different configuration) proves ...

Amazon.com: ASUS ROG Flow Z13 (2025) Gaming Laptop, 13" ROG Nebula 16:10 2.5K 180Hz/3ms, the AMD Ryzen AI MAX 390 Processor, the RDNA 3.5 Graphics, 32GB LPDDR5X 8000MHz, 1TB PCIe Gen 4 SSD, Wi-Fi 7, Win 11 Home : Electronics https://www.amazon.com/ASUS-Nebul...3D%3D&t h=1

... series laptops on my 2025 Gaming Laptop List: https://listium.com/@GizmoSlipTech... help everyone find a laptop they will love! Laptop Risers for Increased Airflow...:11 - Internal Analysis - Asus Zephyrus G14 50:18 -... G14 01:03:38 - Laptop Control Software - Zephyrus G14...

.... I am running on a laptop (Asus TUF-16) that has an nvidia ... dual monitor setup, with the laptop screen not being used external ... idea how to enable linux gaming through steam on this machine...

Just placed order for 86.7k submitted by /u/Professional-Talk241 to r/LaptopDealsIndia [link] [comments]

Hey folks -- Best Buy wouldn't allow me to actual leave a negative review, so had to take it here. About 18 months ago, I bought an ASUS TUF Advantage Edition A16 with AMD Ryzen. It was my first new computer in 8 years -- I previously had a blue-screened ASUS Ultrabook that overall did great, so I figured I'd stick with the brand. That was a mistake. This laptop, especially as it neared the end of the warranty period, has physically started to fall apart. Here's just a few issues I've had: The rear screws came loose because the screen makes contact with laptop frame when opening, prying the computer body apart. The screw then got stripped when I tried removing it, so now it's floating and my laptop is half open. Games consistently crash and CPU/GPU Temps are way too high -- even when the computer is propped up to allow fans to work or on low graphics settings for older games. The trackpad works about 50% of the time. I've updated/reset drivers, reset the computer, etc -- doesn't matter. I can barely use the computer without a mouse now. This is an issue my old ASUS had after about 7 years, not after just 12 months. The screen just doesn't turn on half the time. When opening the laptop, it just doesn't register coming out of sleep mode and so I have to reset the computer to even use it most days. CPU is running consistently near 90 percent with a few Google Chrome tabs open. It runs slow and stutters constantly, I assume for this reason. Per usual like most Windows Machines I've used, it just stops updating for months at a time, struggling to download or install after multiple attempts. Battery life is probably at 30% of when I bought it. I don't leave it plugged in, I use low power mode and try to baby the battery but it's basically a brick at this point even for low-end tasks like web browsing. The build quality of every laptop I've owned since 2012 has been worse and worse and this is the cherry on top. It's mind blowing I paid $800 bucks on this thinking it was a good deal when I'm now feeling like I'll only get 3 years tops out of it. I'd say be way of ASUS, at least on budget models. submitted by /u/Lost_Bit_6955 to r/GamingLaptops [link] [comments]

After 8 years of using an old Asus Rog laptop filled with dust and sounding like a 10 year old base PS4, he finally got himself a new laptop.. and a new debt. submitted by /u/FeelDeadInside to r/pcmasterrace [link] [comments]

Hello everyone, my first post here,, looking to buy a laptop mainly for college work, some light-to-moderate graphic design on the side (Photoshop, etc.), and decent gaming like GTA V and similar titles. So I've come across ASUS GAMING V16 Graphics: NVIDIA RTX 4050. RAM: 16GB DDR5. Storage: 512GB SSD. Display: 16-inch, 144Hz. Weight: around 1.95 kg. The i5/Core 5 variant is around 83k and the i7/Core 7 is around 93k in Indian rupee. Since I won’t be doing heavy multitasking or long CPU-heavy work, I’m leaning toward the i5 because the GPU seems to matter more for my use case and the 10k difference feels hard to justify. My only concerns are the 1.95 kg weight, battery life, and whether the cooling/TGP is actually good enough for the RTX 4050 to perform well long term. Any suggestions on whether the i5 is the smarter buy, or any drawbacks of this model I should know before finalizing? If anyone has this then please advise me if it is a good buy? Thanks submitted by /u/Ill-Double-3942 to r/IndianPCGamers [link] [comments]

Been saving and overthinking this for so long, and now it’s actually here. First impressions: it looks solid, feels durable, and the performance is already a huge upgrade from what I had before. Still setting everything up and figuring things out. For those who have this laptop: – Any tips to maximize performance? – Must-do settings or tweaks? – How’s the thermals and battery life in the long run? Also open to game recommendations to really test this beast 👀 EDIT: I’m not really much of a gamer btw I mainly got this for work (civil engineering), but I might try some games on the side 😅 EDIT2: I’m new to this and keep seeing people suggest switching from AC to GHELPER. Is it really necessary to uninstall Armoury Crate, or is it fine to just keep using it? I’d appreciate your advice. Thanks! 😅 peace submitted by /u/Sea-Dig8956 to r/Asustuf [link] [comments]

Hi Guys I am planning to buy below laptop for work and gaming. ASUS Gaming V16 V3607VU-RP550WS - i5, rtx 4050 link I want laptop for long term. Last Laptop I purchased was of Dell I had purchased in 2017 My Budget is around 85-90k INR, if you have any other suggestions pls mention in the comments. I don’t have much knowledge, I tried searching in my own and came up with this. Now hoping on community suggestions submitted by /u/Routine-Gold6709 to r/GamingLaptops [link] [comments]

Disclaimer: I made basically this exact post on r/buildapc then immediately after was shown a post from this sub. So I figured I’d ask here too. This post went through many iterations, before posting, as I worked out my frustrations. I have additional information, a commentary on ASUS’ marketing, and lots of photos of the PC I could share as needed. Backstory: My friend bought the ASUS V500MV mini desktop PC at Best Buy. She wanted a PC to run games like Minecraft, Valorant, Genshin Impact, and Marvel Rivals to give you an idea of the gaming spectrum she plays. She didn’t do a whole lot of research, clearly, as this thing seems to be a glorified, proprietary laptop. My suggestion was straightforward - return it and I’ll help you spec and build a custom PC. She said she won’t or can’t? So instead I’ve been brainstorming ways to upgrade and I’m finally at my wits end and am turning to Reddit for help. Issue: ASUS’ website claims the V500MV can support up to an RTX 4060. But it has a 180W PSU that has two cables: a 6-pin and a 4-pin. I am operating under the assumption that if I replace the power supply then a 4060 could be slotted in and utilized. My questions: ⁠Has anyone ever seen a 6-pin used for the motherboard? I assume it is som sort of proprietary thing from ASUS? I’m used to the 24-pin motherboard cable. What are my options? Can I use any 6-pin cable from the PSU for the motherboard power and a standard 4-pin for the CPU? Follow-up: I know that fitting things in a small form factor and adding fans / maintaining adequate cooling will be another hurdle but from my current position if I can’t get an acceptable PSU nothing else really matters. TL;DR Friend bought pre-built PC (ASUS V500MV) and wants to game on it. She won’t/can’t return it anymore so we’re doing a Hail Mary and attempting to upgrade. Main Question: Is there a PSU/adapter that uses 6-pin for the motherboard? It has: * No GPU (but does have space for one), * a 180W PSU (with only 6-pin and 4-pin connectors for Motherboard/CPU), * The CPU cooler is the only fan (and only fan header on the motherboard). Help :’) submitted by /u/Trivial_Hamster to r/PcBuildHelp [link] [comments]

Asus ROG Strix SCAR 16 with a 5090 and 64GB in it. For me it's the most buttery-smoothiest kickassiest PC I've ever managed to get my grubby hands on. A "mobile desktop", really -- I only go unplugged on board airplanes or going from one room to another. It eats every game I own at max settings whole, and I'm totally smitten. submitted by /u/the2belo to r/GamingLaptops [link] [comments]

Hey guys! Planning to buy my first Asus laptop when I came across the V16 model. Since it’s fairly “new”, does anyone have experience with this model? If so I would love to hear your thoughts. My previous laptop died due to GPU overheating and keyboard issues. (MSI Prestige 15) So I don’t plan to make the same mistake again. I will mainly be using for: -Running on Adobe programs (Lightroom, Photoshop, Premiere Pro) for photo and video editing -Play games like Forza Horizon 4, GTA V, NFS Heat. (Potentially also play the new FH6 and GTA VI) -Browsing on the web, YouTube, Netflix and emails Overall how does the laptop perform and will there be any overheating issues? Is it very underpowered? I also heard the screen is very dim 300nits and the sRGB is low. The configuration is in the photo above. Any help is appreciated. Thanks! :D submitted by /u/fflawsomee to r/ASUS [link] [comments]

So after my Asus Vivobook of 7+ years finally broke down my mom gave me this laptop as an advance birthday present. Asus ROG Strix G16 (2025) G615. RTX 5050 Intel i7-14650HX (2.20GHz) 32GB RAM 2x1TB SSD. This is my first ever gaming laptop and I’m so happy. any tips on how to better take care of this? This costed her around 1650 USD-ish? (taxes included). submitted by /u/SnooHamsters9965 to r/GamingLaptops [link] [comments]

Been using predator triton 300 since uni. Upgrading from i5-9300h gtx 1650, to a strix g16 u9-275hx rtx 5080 laptop. My wife decided to buy me a new laptop for my birthday gift as my previous laptop broke down a while ago. Couldn't be much happier. First time start up. Any tips for me? This laptop is bought at Malaysia at a price of RM 12,099. I think around 2800USD? submitted by /u/Penguin_pippy to r/GamingLaptops [link] [comments]

It’s an Asus ProArt I had never seen before for a price I couldn’t pass up. It has a 3200 x 2000 OLED display with an RTX 4070 (130-160w?) & an i9-13980HX 24 core cpu. This thing is insane to use coming from what I’ve had before. I benchmarked it too: 24917 on fire strike, 12538 on timespy EDIT: The knob is called and asus dial, which is a shortcut tool that I can program to do up to 7 shortcuts per program. Very useful for high shortcut apps like editing software and the adobe apps which I use submitted by /u/Admirable_Resort8466 to r/GamingLaptops [link] [comments]

The Issue, You own a high-end ASUS ROG laptop perhaps a Strix, Scar, or Zephyrus. It's specifications are impressive: an RTX 30/40 series GPU, a top-tier Intel processor, and plenty of RAM. Yet, it stutters during basic tasks like watching a YouTube video, audio crackles and pops on Discord calls, the mouse cursor freezes for a split second, just long enough to be infuriating. You've likely tried all the conventional fixes: Updating every driver imaginable, multiple times. Performing a "clean" reinstallation of Windows. Disabling every conceivable power-saving option. Manually tweaking processor interrupt affinities. Following convoluted multi-step guides from Reddit threads. Even installing Linux, only to find the problem persists. If none of that worked, it's because the issue isn't with the operating system or a driver. The problem is far deeper, embedded in the machine's firmware, the BIOS. Initial Symptoms and Measurement The Pattern Emerges The first tool in any performance investigator's toolkit for these symptoms is LatencyMon. It acts as a canary in the coal mine for system-wide latency issues. On an affected ASUS Zephyrus M16, the results are immediate and damning: CONCLUSION Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. HIGHEST MEASURED INTERRUPT TO PROCESS LATENCY Highest measured interrupt to process latency (μs): 65,816.60 Average measured interrupt to process latency (μs): 23.29 HIGHEST REPORTED ISR ROUTINE EXECUTION TIME Highest ISR routine execution time (μs): 536.80 Driver with highest ISR routine execution time: ACPI.sys HIGHEST REPORTED DPC ROUTINE EXECUTION TIME Highest DPC routine execution time (μs): 5,998.83 Driver with highest DPC routine execution time: ACPI.sys The data clearly implicates ACPI.sys. However, the per-CPU data reveals a more specific pattern: CPU 0 Interrupt cycle time (s): 208.470124 CPU 0 ISR highest execution time (μs): 536.804674 CPU 0 DPC highest execution time (μs): 5,998.834725 CPU 0 DPC total execution time (s): 90.558238 CPU 0 is taking the brunt of the impact, spending over 90 seconds processing interrupts while other cores remain largely unaffected. This isn't a failure of load balancing; it's a process locked to a single core. A similar test on a Scar 15 from 2022 shows the exact same culprit: high DPC latency originating from ACPI.sys. LatencyMon It's easy to blame a Windows driver, but ACPI.sys is not a typical driver. It primarily functions as an interpreter for ACPI Machine Language (AML), the code provided by the laptop's firmware (BIOS). If ACPI.sys is slow, it's because the firmware is feeding it inefficient or flawed AML code to execute. These slowdowns are often triggered by General Purpose Events (GPEs) and traffic from the Embedded Controller (EC). To find the true source, we must dig deeper. Capturing the Problem in More Detail: ETW Tracing Setting Up Advanced ACPI Tracing To understand what ACPI.sys is doing during these latency spikes, we can use Event Tracing for Windows (ETW) to capture detailed logs from the ACPI providers. # Find the relevant ACPI ETW providers logman query providers | findstr /i acpi # This returns two key providers: # Microsoft-Windows-Kernel-Acpi {C514638F-7723-485B-BCFC-96565D735D4A} # Microsoft-ACPI-Provider {DAB01D4D-2D48-477D-B1C3-DAAD0CE6F06B} # Start a comprehensive trace session logman start ACPITrace -p {DAB01D4D-2D48-477D-B1C3-DAAD0CE6F06B} 0xFFFFFFFF 5 -o C:\Temp\acpi.etl -ets logman update ACPITrace -p {C514638F-7723-485B-BCFC-96565D735D4A} 0xFFFFFFFF 5 -ets # Then once we're done we can stop the trace and check the etl file and save the data in csv format aswell. logman stop ACPITrace -ets tracerpt C:\Temp\acpi.etl -o C:\Temp\acpi_events.csv -of CSV An Unexpected Discovery Analyzing the resulting trace file in the Windows Performance Analyzer reveals a crucial insight. The spikes aren't random; they are periodic, occurring like clockwork every 30 to 60 seconds. ETW Periodicity Random interruptions often suggest hardware faults or thermal throttling. A perfectly repeating pattern points to a systemic issue, a timer or a scheduled event baked into the system's logic. The raw event data confirms this pattern: Clock-Time (100ns), Event, Kernel(ms), CPU 134024027290917802, _GPE._L02 started, 13.613820, 0 134024027290927629, _SB...BAT0._STA started, 0.000000, 4 134024027290932512, _GPE._L02 finished, -, 6 The first event, _GPE._L02, is an interrupt handler that takes 13.6 milliseconds to execute. For a high-priority interrupt, this is an eternity and is catastrophic for real-time system performance. Deeper in the trace, another bizarre behavior emerges; the system repeatedly attempts to power the discrete GPU on and off, even when it's supposed to be permanently active. Clock-Time, Event, Duration 134024027315051227, _SB.PC00.GFX0._PS0 start, 278μs # GPU Power On 134024027315155404, _SB.PC00.GFX0._DOS start, 894μs # Display Output Switch 134024027330733719, _SB.PC00.GFX0._PS3 start, 1364μs # GPU Power Off [~15 seconds later] 134024027607550064, _SB.PC00.GFX0._PS0 start, 439μs # Power On Again! 134024027607657368, _SB.PC00.GFX0._DOS start, 1079μs # Display Output Switch 134024027623134006, _SB.PC00.GFX0._PS3 start, 394μs # Power Off Again! ... Why This Behavior is Fundamentally Incorrect This power cycling is nonsensical because the laptop is configured for a scenario where it is impossible: The system is in Ultimate Mode (via a MUX switch) with an external display connected. In this mode: The discrete NVIDIA GPU (dGPU) is the only active graphics processor. The integrated Intel GPU (iGPU) is completely powered down and bypassed. The dGPU is wired directly to the internal and external displays. There is no mechanism for switching between GPUs. Yet, the firmware ignores MUX state nudging the iGPU path (GFX0) and, worse, engaging dGPU cut/notify logic (PEGP/PEPD) every 15–30 seconds. The dGPU in mux mode isn't just "preferred" - it's the ONLY path to the display. There's no fallback, and no alternative. When the firmware sends _PS3 (power off), it's attempting something architecturally impossible. Most of the time, hardware sanity checks refuse these nonsensical commands, but even failed attempts introduce latency spikes causing audio dropouts, input lag, and accumulating performance degradation. Games freeze mid-session, videos buffer indefinitely, system responsiveness deteriorates until restart. The Catastrophic Edge Case Sometimes, under specific thermal conditions or race conditions, the power-down actually succeeds. When the firmware manages to power down the GPU that's driving the display, the sequence is predictable and catastrophic: Firmware OFF attempt - cuts the dgpu path via PEG1.DGCE Hardware complies - safety checks fail or timing aligns Display signal cuts - monitors go black User input triggers wake - mouse/keyboard activity Windows calls PowerOnMonitor() - attempt display recovery NVIDIA driver executes _PS0 - GPU power on command GPU enters impossible state - firmware insists OFF, Windows needs ON Driver thread blocks indefinitely - waiting for GPU response 30-second watchdog expires - Windows gives up System crashes with BSOD Bugcheck Code Stack Trace The crash dump confirms the thread is stuck in win32kbase!DrvSetWddmDeviceMonitorPowerState, waiting for the NVIDIA driver to respond. It can't because it's caught between a confused power state, windows wanting to turn on the GPU while the firmware is arming the GPU cut off. Understanding General Purpose Events GPEs are the firmware's mechanism for signaling hardware events to the operating system. They are essentially hardware interrupts that trigger the execution of ACPI code. The trace data points squarely at _GPE._L02 as the source of our latency. A closer look at the timing reveals a consistent and problematic pattern: _GPE._L02 Event Analysis from ROG Strix Trace: Event 1 @ Clock 134024027290917802 Duration: 13,613,820 ns (13.61ms) Triggered: Battery and AC adapter status checks Event 2 @ Clock 134024027654496591 Duration: 13,647,255 ns (13.65ms) Triggered: Battery and AC adapter status checks Event 3 @ Clock 134024028048493318 Duration: 13,684,515 ns (13.68ms) Triggered: Battery and AC adapter status checks Interval between events: ~36-39 seconds Consistency: The duration is remarkably stable and the interval is periodic. The Correlation Every single time the lengthy _GPE._L02 event fires, it triggers the exact same sequence of ACPI method calls. GPE & Battery Notifications The pattern is undeniable: A hardware interrupt fires _GPE._L02. The handler executes methods to check battery status. Shortly thereafter, the firmware attempts to change the GPU's power state. The system runs normally for about 30-60 seconds. The cycle repeats. Extracting and Decompiling the Firmware Code Getting to the Source To analyze the code responsible for this behavior, we must extract and decompile the ACPI tables provided by the BIOS to the operating system. # Extract all ACPI tables into binary .dat files acpidump -b # Output includes: # DSDT.dat - The main Differentiated System Description Table # SSDT1.dat ... SSDT17.dat - Secondary System Description Tables # Decompile the main table into human-readable ACPI Source Language (.dsl) iasl -d DSDT.dsl This decompiled ASL provides a direct view into the firmware's executable logic. It is a precise representation of the exact instructions that the ACPI.sys driver is fed by the firmware and executes at the highest privilege level within the Windows kernel. Any logical flaws found in this code are the direct cause of the system's behavior. Finding the GPE Handler Searching the decompiled DSDT.dsl file, we find the definition for our problematic GPE handler: Scope (_GPE) { Method (_L02, 0, NotSerialized) // _Lxx: Level-Triggered GPE { \_SB.PC00.LPCB.ECLV () } } This code is simple: when the _L02 interrupt occurs, it calls a single method, ECLV. The "L" prefix in _L02 signifies that this is a level-triggered interrupt, meaning it will continue to fire as long as the underlying hardware condition is active. This is a critical detail. The Catastrophic ECLV Implementation Following the call to ECLV(), we uncover a deeply flawed implementation that is the direct cause of the system-wide stuttering. Method (ECLV, 0, NotSerialized) // Starting at line 099244 { // Main loop - continues while events exist OR sleep events are pending // AND we haven't exceeded our time budget (TI3S < 0x78) While (((CKEV() != Zero) || (SLEC != Zero)) && (TI3S < 0x78)) { Local1 = One While (Local1 != Zero) { Local1 = GEVT() // Get next event from queue LEVN (Local1) // Process the event TIMC += 0x19 // Increment time counter by 25 // This is where it gets really bad If ((SLEC != Zero) && (Local1 == Zero)) { // No events but sleep events pending If (TIMC == 0x19) { Sleep (0x64) // Sleep for 100 milliseconds!!! TIMC = 0x64 // Set time counter to 100 TI3S += 0x04 // Increment major counter by 4 } Else { Sleep (0x19) // Sleep for 25 milliseconds!!! TI3S++ // Increment major counter by 1 } } } } // Here's where it gets even worse If (TI3S >= 0x78) // If we hit our time budget (120) { TI3S = Zero If (EEV0 == Zero) { EEV0 = 0xFF // Force another event to be pending! } } } Breaking Down this monstrosity This short block of code violates several fundamental principles of firmware and kernel programming. Wtf 1: Sleeping in an Interrupt Context Sleep (0x64) // 100ms sleep Sleep (0x19) // 25ms sleep An interrupt handler runs at a very high priority to service hardware requests quickly. The Sleep() function completely halts the execution of the CPU core it is running on (CPU 0 in this case). While CPU 0 is sleeping, it cannot: Process any other hardware interrupts. Allow the kernel to schedule other threads. Update system timers. Clarification: These Sleep() calls live in the ACPI GPE handling path for the GPE L02, these calls get executed at PASSIVE_LEVEL after the SCI/GPE is acknowledged so it's not a raw ISR (because i don't think windows will even allow that) but analyzing this further while the control method runs the GPE stays masked and the ACPI/EC work is serialized. With the Sleep() calls inside that path and the self rearm it seems to have the effect of making ACPI.sys get tied up in long periodic bursts (often on CPU 0) which still have the same effect on the system. Wtf 2: Time-Sliced Interrupt Processing The entire loop is designed to run for an extended period, processing events in batches. It's effectively a poorly designed task scheduler running inside an interrupt handler, capable of holding a CPU core hostage for potentially seconds at a time. Wtf 3: Self-Rearming Interrupt If (EEV0 == Zero) { EEV0 = 0xFF // Forces all EC event bits on } This logic ensures that even if the Embedded Controller's event queue is empty, the code will create a new, artificial event. This guarantees that another interrupt will fire shortly after, creating the perfectly periodic pattern of ACPI spikes observed in the traces. The Event Dispatch System How Events Route to Actions The LEVN() method takes an event and routes it: Method (LEVN, 1, NotSerialized) { If ((Arg0 != Zero)) { MBF0 = Arg0 P80B = Arg0 Local6 = Match (LEGA, MEQ, Arg0, MTR, Zero, Zero) If ((Local6 != Ones)) { LGPA (Local6) } } } The LGPA Dispatch Table The LGPA() method is a giant switch statement handling different events: Method (LGPA, 1, Serialized) // Line 098862 { Switch (ToInteger (Arg0)) { Case (Zero) // Most common case - power event { DGD2 () // GPU-related function ^EC0._QA0 () // EC query method PWCG () // Power change - this is our battery polling } Case (0x18) // GPU-specific event { If (M6EF == One) { Local0 = 0xD2 } Else { Local0 = 0xD1 } NOD2 (Local0) // Notify GPU driver } Case (0x1E) // Another GPU event { Notify (^^PEG1.PEGP, 0xD5) // Direct GPU notification ROCT = 0x55 // Sets flag for follow-up } } } This shows a direct link: a GPE fires, and the dispatch logic calls functions related to battery polling and GPU notifications. The Battery Polling Function The PWCG() method, called by multiple event types, is responsible for polling the battery and AC adapter status. Method (PWCG, 0, NotSerialized) { Notify (ADP0, Zero) // Tell OS to check the AC adapter ^BAT0._BST () // Execute the Battery Status method Notify (BAT0, 0x80) // Tell OS the battery status has changed ^BAT0._BIF () // Execute the Battery Information method Notify (BAT0, 0x81) // Tell OS the battery info has changed } Which we can see here: Notifications Each of these operations requires communication with the Embedded Controller, adding to the workload inside the already-stalled interrupt handler. The GPU Notification System The NOD2() method sends notifications to the GPU driver. Method (NOD2, 1, Serialized) { If ((Arg0 != DNOT)) { DNOT = Arg0 Notify (^^PEG1.PEGP, Arg0) } If ((ROCT == 0x55)) { ROCT = Zero Notify (^^PEG1.PEGP, 0xD1) // Hardware-Specific } } These notifications (0xD1, 0xD2, etc.) are hardware-specific signals that tell the NVIDIA driver to re-evaluate its power state, which prompts driver power-state re-evaluation; in traces this surfaces as iGPU GFX0._PSx/_DOS toggles plus dGPU state changes via PEPD._DSM/DGCE. The Mux Mode Confusion: A Firmware with a Split Personality Here's where a simple but catastrophic oversight in the firmware's logic causes system-wide failure. High-end ASUS gaming laptops feature a MUX (Multiplexer) switch, a piece of hardware that lets the user choose between two distinct graphics modes: Optimus Mode: The power-saving default. The integrated Intel GPU (iGPU) is physically connected to the display. The powerful NVIDIA GPU (dGPU) only renders demanding applications when needed, passing finished frames to the iGPU to be drawn on screen. Ultimate/Mux Mode: The high-performance mode. The MUX switch physically rewires the display connections, bypassing the iGPU entirely and wiring the NVIDIA dGPU directly to the screen. In this mode, the dGPU is not optional; it is the only graphics processor capable of outputting an image. Any firmware managing this hardware must be aware of which mode the system is in. Sending a command intended for one GPU to the other is futile and, in some cases, dangerous. Deep within the ACPI code, a hardware status flag named HGMD is used to track this state. To understand the flaw, we first need to decipher what HGMD means, and the firmware itself gives us the key. Decoding the Firmware's Logic with the Brightness Method For screen brightness to work, the command must be sent to the GPU that is physically controlling the display backlight. A command sent to the wrong GPU will simply do nothing. Therefore, the brightness control method (BRTN) must be aware of the MUX switch state to function at all. It is the firmware's own Rosetta Stone. // Brightness control - CORRECTLY checks for mux mode Method (BRTN, 1, Serialized) // Line 034003 { If (((DIDX & 0x0F0F) == 0x0400)) { If (HGMD == 0x03) // 0x03 = Ultimate/Mux mode { // In mux mode, notify discrete GPU Notify (\_SB.PC00.PEG1.PEGP.EDP1, Arg0) } Else { // In Optimus, notify integrated GPU Notify (\_SB.PC00.GFX0.DD1F, Arg0) } } } The logic here is flawless and revealing. The code uses the HGMD flag to make a binary decision. If HGMD is 0x03, it sends the command to the NVIDIA GPU. If not, it sends it to the Intel GPU. The firmware itself, through this correct implementation, provides the undeniable definition: HGMD == 0x03 means the system is in Ultimate/Mux Mode. The Logical Contradiction: Unconditional Power Cycling in a Conditional Hardware State This perfect, platform-aware logic is completely abandoned in the critical code paths responsible for power management. The LGPA method, which is called by the stutter-inducing interrupt, dispatches power-related commands to the GPU without ever checking the MUX mode. // GPU power notification - NO MUX CHECK! Case (0x18) { // This SHOULD have: If (HGMD != 0x03) // But it doesn't, so it runs even in mux mode If (M6EF == One) { Local0 = 0xD2 } Else { Local0 = 0xD1 } NOD2 (Local0) // Notifies GPU regardless of mode } Another Path to the Same Problem: The Platform Power Management DSM This is not a single typo. A second, parallel power management system in the firmware exhibits the exact same flaw. The Platform Extension Plug-in Device (PEPD) is used by Windows to manage system-wide power states, such as turning off displays during modern standby. Device (PEPD) // Line 071206 { Name (_HID, "INT33A1") // Intel Power Engine Plugin Method (_DSM, 4, Serialized) // Device Specific Method { // ... lots of setup code ... // Arg2 == 0x05: "All displays have been turned off" If ((Arg2 == 0x05)) { // Prepare for aggressive power saving If (CondRefOf (\_SB.PC00.PEG1.DHDW)) { ^^PC00.PEG1.DHDW () // GPU pre-shutdown work ^^PC00.PEG1.DGCE = One // Set "GPU Cut Enable" flag } If (S0ID == One) // If system supports S0 idle { GUAM (One) // Enter low power mode } ^^PC00.DPOF = One // Display power off flag // Tell USB controller about display state If (CondRefOf (\_SB.PC00.XHCI.PSLI)) { ^^PC00.XHCI.PSLI (0x05) } } // Arg2 == 0x06: "A display has been turned on" If ((Arg2 == 0x06)) { // Wake everything back up If (CondRefOf (\_SB.PC00.PEG1.DGCE)) { ^^PC00.PEG1.DGCE = Zero // Clear "GPU Cut Enable" } If (S0ID == One) { GUAM (Zero) // Exit low power mode } ^^PC00.DPOF = Zero // Display power on flag If (CondRefOf (\_SB.PC00.XHCI.PSLI)) { ^^PC00.XHCI.PSLI (0x06) } } } } Once again, the firmware prepares to cut power to the discrete GPU without first checking if it's the only GPU driving the displays. This demonstrates that the Mux Mode Confusion is a systemic design flaw. The firmware is internally inconsistent, leading it to issue self-destructive commands that try to cripple the system. Cross-System Analysis Traces from multiple ASUS gaming laptop models confirm this is not an isolated issue. Scar 15 Analysis Trace Duration: 4.1 minutes _GPE._L02 Events: 7 (every ~39 seconds) Avg. GPE Duration: 1.56ms GPU Power Cycles: 8 Zephyrus M16 Analysis Trace Duration: 19.9 minutes _GPE._L02 Events: 3 (same periodic pattern) Avg. GPE Duration: 2.94ms GPU Power Cycles: 197 (far more frequent) ASUS WMI Calls: 2,370 (Armoury Crate amplifying the problem) What Actually Breaks The firmware acts as the hardware abstraction layer between Windows and the physical hardware. When ACPI control methods execute, they run under the Windows ACPI driver with specific timing constraints and because of these timing constraints GPE control methods need to finish quickly because the firing GPE stays masked until the method returns so sleeping or polling inside a path like that can trigger real time-glitches and produce very high latency numbers, as our tests indicate. Microsoft's Hardware Lab Kit GlitchFree test validates this hardware-software contract by measuring audio/video glitches during HD playback. It fails systems with driver stalls exceeding a few milliseconds because such delays break real-time guarantees needed for smooth media playback. These ASUS systems violate those constraints. The firmware holds GPE._L02 masked for 13ms while sleeping in ECLV, serializing all ACPI/EC operations behind that delay. It polls battery state when it should use event-driven notifications. It attempts GPU power transitions without checking platform configuration (HGMD). All these problems result in powerful hardware crippled by firmware that doesn't understand its own execution context. The Universal Pattern Despite being different models, all affected systems exhibit the same core flaws: _GPE._L02 handlers take milliseconds to execute instead of microseconds. The GPEs trigger unnecessary battery polling. The firmware attempts to power cycle the GPU while in a fixed MUX mode. The entire process is driven by a periodic, timer-like trigger. Summarizing the Findings This bug is a cascade of firmware design failures. Root Cause 1: The Misunderstanding of Interrupt Context On windows, the LXX / EXX run at PASSIVE_LEVEL via ACPI.sys but while a GPE control method runs the firing GPE stays masked and ACPI/EC work is serialized. ASUS's dispatch from GPE._L02 to ECLV loops, calls Sleep(25/100ms) and re-arms the EC stretching that masked window into tens of milliseconds (which would explain the 13ms CPU time in ETW (Kernel ms) delay for GPE Events) and producing a periodic ACPI.sys burst that causes the latency problems on the system.The correct behavior is to latch or clear the event, exit the method, and signal a driver with Notify for any heavy work; do not self-rearm or sleep in this path at all. Root Cause 2: Flawed Interrupt Handling The firmware artificially re-arms the interrupt, creating an endless loop of GPEs instead of clearing the source and waiting for the next legitimate hardware event. This transforms a hardware notification system into a disruptive, periodic timer. Root Cause 3: Lack of Platform Awareness The code that sends GPU power notifications does not check if the system is in MUX mode, a critical state check that is correctly performed in other parts of the firmware. This demonstrates inconsistency and a lack of quality control. Timeline of User Reports The Three-Year Pattern This issue is not new or isolated. User reports documenting identical symptoms with high ACPI.sys DPC latency, periodic stuttering, and audio crackling have been accumulating since at least 2021 across ASUS's entire gaming laptop lineup. August 2021: The First Major Reports The earliest documented cases appear on the official ASUS ROG forums. A G15 Advantage Edition (G513QY) owner reports "severe DPC latency from ACPI.sys" with audio dropouts occurring under any load condition. The thread, last edited in March 2024, shows the issue remains unresolved after nearly three years. Reddit users simultaneously report identical ACPI.sys latency problems alongside NVIDIA driver issues; the exact symptoms described in this investigation. 2021-2023: Spreading Across Models Throughout this period, the issue proliferates across ASUS's gaming lineup: ROG Strix models experience micro-stutters TUF Gaming series reports throttling for seconds at a time G18 models exhibit the characteristic 45-second periodic stuttering 2023-2024: The Problem Persists in New Models Even the latest generations aren't immune: 2023 Zephyrus G16 owners report persistent audio issues 2023 G16 models continue experiencing audio pops/crackles 2024 Intel G16 models require workarounds for audio stuttering Conclusion The evidence is undeniable: Measured Proof: GPE handlers are measured blocking a CPU core for over 13 milliseconds. Code Proof: The decompiled firmware explicitly contains Sleep() calls within an interrupt handler. Logical Proof: The code lacks critical checks for the laptop's hardware state (MUX mode). Systemic Proof: The issue is reproducible across different models and BIOS versions. Matthew Garrett had commented on this analysis, suggesting the system-wide freezes are likely caused by the firmware entering System Management Mode (SMM), highly recommend also checking this out for additional context and understanding: https://news.ycombinator.com/item?id=45282069 Until a fix is implemented, millions of buyers of Asus laptops from approx. 2021 to present day are facing stutters on the simplest of tasks, such as watching YouTube, for the simple mistake of using a sleep call inside of an inefficient interrupt handler and not checking the GPU environment properly. The code is there. The traces prove it. ASUS must fix its firmware. Update 1: ASUS NA put out a short statment: https://x.com/asus_rogna/status/1968404596658983013?s=46 Update 2: Reply from ASUS RD received; repro info sent over Update 3: Testing Asus beta BIOS. Report linked here:* Github submitted by /u/ZephKeks to r/ASUSROG [link] [comments]

ASUS TUF A15 (R9 5th gen, 3060) died absolutely randomly a day or two prior. Have stripped it completely trying to look for cause of death. Absolutely no signs of life, deduced to most likely having a capacitor malfunctioned on the motherboard. This thing cost me a good fortune around 3 years back, was expecting it to support me for many years to come, but ASUS disappointed me (and quite a few of my friends who have had the exact same issue with this model). I can not afford to repair this, and my love for gaming might have come to an end. No idea why i uploaded this, maybe just to put things off of my chest. submitted by /u/Sgt_Testiclecancer to r/pcmasterrace [link] [comments]

I see a lot of people claiming that Asus tuf is bad in price-relation because of refrigeration and motherboard issues. is it true? submitted by /u/BraveFee6577 to r/GamingLaptops [link] [comments]

Hey all, local nutjob here, saw this gaming laptop, what seems to be an asus tuf A16 advantage edition for practically 30Aud, and got curious, its definitely a scam, but then the number of sales and reviews got me curious, so i caved in to curiousity and bought one. It should be coming in the 15-26, ill keep yall updated on wether or not if this is a ripoff, or would they send me something strange, or maybe id get the actual tuf a16, who knows? Btw rest assured all ive bought this thing with a couple of other items ive been meaning to buy so theres a discount on it, makes my money a little bit more worth it. submitted by /u/too-much_caffeine to r/GamingLaptops [link] [comments]

The Asus ROG Zephyrus G16 Intel Core Uktra 9 32gb DDR5 RTX 4090 2TB SSD Which game(s) should I play on this first?! Also purchased the Logitech G915 TKL and G Pro X. Likely getting a PS5 DualSense controller. Anything else I need to purchase? Going to YouTube some videos for caveats. Please let me know if you can provide insight in advance as well. Thanks all!! submitted by /u/gswcowboy to r/GamingLaptops [link] [comments]

Hi everyone, I recently switched from a MacBook Air to this Zephyrus M16. I downloaded all the drivers, uninstalled Asus AC and downloaded Ghelper and have it set up nice but on Mac, I used safari. Now that I’m on windows, wanted to get some recommendations. Don’t have any prerequisites. Just wanting to see what everyone else is using. I have Firefox and Edge on my taskbar for testing but want everyone’s opinion. Thank you! submitted by /u/Remarkable-Ad-1546 to r/GamingLaptops [link] [comments]

CPU: Ryzen 7 7800X3D CPU Cooler: NZXT Kraken 280 Motherboard: MSI B650 Gaming plus WIFI GPU: EVGA FTW3 Ultra Gaming 3080 10gb SSD: Samsung 970 Evo 1tb RAM: Corsair Vengeance DDR5-5600 2x16gb PSU: Corsair RM850x 850w Case: Corsair 4000D Airflow submitted by /u/vindictive-ant to r/pcmasterrace [link] [comments]

I decided to go the mobile route, and switched from my desktop to a laptop, purely for gaming. Rig specs: CPU: Intel Core i9-13980HX 24C/32T RAM: 32GB DDR5 4800MHz RAM SSD1: 1TB NVMe SSD2: 1TB NVMe Evo Plus GPU: NVIDIA RTX 4080 12GB Laptop LAPTOP DISPLAY: 18" ROG Nebula QHD+ (1600p) 240Hz EXTERNAL DISPLAY: MSI 32" 4K 144Hz Quantum Dot MOUSE: Roccat Burst Pro KEYBOARD: Redragon Noctis HEADSET: Roccat Syn Pro Air Wireless submitted by /u/StickFigureRunner to r/GamingLaptops [link] [comments]

submitted by /u/fightthapower to r/gaming [link] [comments]

submitted by /u/chris8816 to r/Amd [link] [comments]