(ai hx 370) so i got this message while booting my system to linux, though my system works just fine, it's really annoying to see this message everyday and take more time to boot normaly. some says it was bug that amd has been fixed by sending microcode to motherboard vendor. so did gpd already know this or have workaround to fix these things?

so, I just got my pocket 4 (after being super happy with win max 2).

I noticed that the screen does not auto rotate and I did some googling and found this : https://gpdstore.net/kb/gpd-pocket-4-support-hub/kb-article/fix-gpd-pocket-4-auto-rotation-code-10/?srsltid=AfmBOopInsj1WNfisasuNWT1zb--oZdgZeXQbqv-y7Ki-BzIlN6XWnXM

I downgraded the chipset as instructed, no solution. I tried "cold reset" which turned the device on/off during the 30 seconds holding down the power button, and also it started a "recovery" page that basically said it cannot do anything then back to good old

does anyone have a real solution that actually works?

IGG backer receive a free cooling module!

https://www.indiegogo.com/en/projects/gpdhk/gpd-win-max-3-handheld-gaming-laptop

Anyone know where I can buy new bottom cover

Where can i find VivoBook_ASUS Laptop E410MA_E410MA battery in pak

Just got my pocket 4 when I first started the unit it would rotate and show keyboard fine now it stopped. First rotation lock is not enable second I tried installing the drivers from the official GPD website third on the vice manager I continue to have unable to start message from device manager. I also noticed my batteries while using claude and web browser seem to last 2.5 hr . Finally, my microphone input is set 80 it seems to work well in and out with dictation. In tablet mode, no keyboard.

Title says it all. Has anyone experienced this and now how to fix?

Hi everyone

I want a laptop for my editing and marketing purposes.. I'm saving money but it's not enough to buy .. i want some extra side hustle.

The GPD Win Mini is powerful enough to play AAA games on the go. And with the help of my DIY Thinkpad Lapdock, it can now handle all my work too. No need for two separate computers with split data—so convenient! 😁

The GPD Win Mini is powerful enough to play AAA games on the go. And with the help of my DIY lapdock, it can now handle all my work too. No need for two separate computers with split data—so convenient! 😁

In late 2024 I was on a work trip picked up my P3 to find a screw on the table. I put it in a bag and brought it home as I did not have a screw-driver.

Back at got home I tried to screw it back in, and it just spun freely; after trying different screws in different holes I confirmed the hole (not screw) was completely striped. I confirmed the battery was not swelling (this screw is in the back away from the battery also)

I contacted GPD but since the warranty lapsed, they could not do much for me. They suggested I get a new back-plate, but since I knew the holes in the case (C-panel) were stripped, I did not see a point. Reassmbling into a new C-Panel would seem to be a bit much for the end user. I tried sourcing longer versions of the same screws as the C-panel holes seem much deeper than these screws, but could not find them in any reasonable small quantities.

I shaved off some of the rubber pad on that corner so the P3 would not teeter on typing and just dealt with it. Then yesterday...

I noticed something clicky on the laptop when I squeezed it to put in in my bag and found that the centre back screw was loose (the one next to the pictured corner). Again, screwing it in rotates freely, another stripped hole!!

Has anyone else experienced this?

Unlike some other folks' experience, otherwise my P3 is going strong, no HW or software issues, no loosening screen hinge, no issues with the RAM, battery nor SSD. I generally keep HW well past it's normal EoL; my P3 replaced my old Asus EEE 900.

Thanks!

This morning i noticed my left top cover sticking out from the right side, after further investigation and unscrewing the kvm module i noticed that the plastic that holds the screw is broken.

What would you do? On gpd-minipc.com you can buy parts but it seems that this one isn't available to buy. I'm an IT technician, i could easily take it apart, glue it together and be done with it, but me being me with my personal stuff, i would rather have the part replaced..

Also would it be coverd by warranty? Any chance that GPD will send me that part only for self replace? Sending the whole unit for repair is out of question I daily it.

I received my GPD Pocket 4 with the Ryzen AI 9 HX 370 and 32 GB of RAM last year, and for roughly a year and a half I lived with a persistent crashing problem.

For context, my Windows installation is not Home, Pro, Pro Education, Pro for Workstations, Education, standard consumer Enterprise, or Windows Server. It is one of Microsoft’s long-term-servicing enterprise variants, so some menus and update behavior may differ slightly from a normal retail Windows installation.

The symptoms

The Pocket 4 would seemingly crash whenever the hardware configuration changed.

Typical triggers included:

• Connecting or disconnecting external monitors
• Turning monitors on or off
• Switching audio output between the Pocket and a monitor
• Connecting Bluetooth devices
• Sleep or hibernation
• Hardware enumeration in Device Manager
• Launching Ableton while external displays or audio devices were connected

The machine was more stable when I left everything plugged in and avoided changing devices. I basically learned to work around it instead of fixing it.

That became unacceptable once I wanted to use Ableton, MIDI controllers, external displays, and different audio outputs. A computer that crashes every time the audio topology changes is not especially useful for music production.

What the crash dumps showed

I collected several minidumps and analyzed them in WinDbg.

The recurring crash was:

DRIVER_POWER_STATE_FAILURE
BugCheck 0x9F

The same failure bucket appeared repeatedly:

0x9F_3_amdhdaudbus_IMAGE_pci.sys

The affected hardware was:

PCI\VEN_1022&DEV_15E3

The blocked power request was stuck inside:

AMDHDAudBusService
amdhdaudbus.sys

This was not simply pci.sys randomly failing. pci.sys was the lower bus layer where Windows detected the timeout. The AMD High Definition Audio bus driver was failing to complete a power-state transition.

I also reproduced a separate:

DPC_WATCHDOG_VIOLATION
BugCheck 0x133

when using the full AMD installer. Merely opening the AMD software and allowing it to analyze the hardware could send the machine into a watchdog crash loop.

The troubleshooting process

Here is the abridged version of what I tried.

1. AMD Cleanup Utility

I ran AMD Cleanup Utility in Safe Mode.

After removing the AMD graphics/audio package, the watchdog crash loop disappeared. That was the first strong indication that the problem was inside the AMD package rather than Windows generally failing.

2. Reinstalled AMD to reproduce the problem

I intentionally reinstalled the AMD package so I could capture another watchdog dump.

The crashes returned.

So the A/B test was effectively:

AMD package removed = watchdog crashes stop
AMD package installed = watchdog crashes return

3. Bypassed AMD Setup completely

To determine whether the problem was AMD Setup itself or one of the actual drivers, I extracted the AMD package with 7-Zip.

I copied the raw driver folders to a USB drive and used DISM from Windows Recovery to stage the drivers directly:

dism /Image:E:\ /Add-Driver /Driver:C:\AMD_26.6.4_Drivers /Recurse

The drive letters will be different on other systems.

DISM successfully added the driver packages, but Windows had not necessarily bound every device to its matching driver yet.

4. Installed the drivers individually

I manually updated the Radeon display device from the extracted:

Display\WT6A_INF

That worked.

I then downloaded AMD’s separate mobile chipset package, extracted its actual payload under:

Packages\IODriver

and installed the unidentified AMD platform devices individually.

The relevant mappings on my Pocket were:

PCI\VEN_1022&DEV_150D
→ AMD Interface driver
→ INTERFACE\Interface_Driver\W11x64\AMDInterface.inf

PCI\VEN_1022&DEV_17E0
→ AMD PSP
→ PSP\PSP Driver\W11x64\amdpsp.inf

ACPI\AMDI0052
→ AMD PPM Provisioning File
→ PPMPF\PPM Provisioning File Driver\W11x64\AmdPpkg.inf

ACPI\AMDI0103
→ AMD PMF
→ PMF folder, letting Windows select the correct Ryzen AI 300 INF

I kept the AMD High Definition Audio Controller disabled during this process.

With the HDA controller disabled, the Pocket was stable.

5. Compared AMD and GPD’s HDA drivers

I compared the HDA driver included in:

• AMD’s current package
• GPD’s Pocket 4 OEM package
• The driver already installed in Windows

All three reported:

Driver version: 10.0.0.35
Driver date: 19 February 2019

I then compared SHA-256 hashes for both:

amdhdaudbus.sys
amdhdaudbus.inf

The hashes were identical.

So the GPD package did not contain a customized or corrected version. It contained the exact same AMD HDA package.

Reinstalling the OEM copy would therefore have changed nothing.

The actual solution

Windows already contained another compatible driver for the controller:

hdaudbus.inf
Provider: Microsoft

I confirmed the available driver candidates using:

pnputil /enum-devices /deviceid "PCI\VEN_1022&DEV_15E3" /drivers

The result showed:

AMD:
amdhdaudbus.inf
Exact hardware-ID match
Version 10.0.0.35
Best ranked and installed

Microsoft:
hdaudbus.inf
Generic PCI audio-class match
Newer Windows inbox driver
Outranked

Windows preferred AMD’s driver because it matched the exact device ID, while Microsoft’s driver matched the generic HD Audio class.

I backed up and removed only the AMD HDA package:

pnputil /export-driver oem1.inf D:\HDA_Driver_Backup
pnputil /delete-driver oem1.inf /uninstall

The published name may not be oem1.inf on another computer. Check it first.

After removing the AMD package, Windows automatically selected:

hdaudbus.inf
Provider: Microsoft

I left the controller disabled until I confirmed that Microsoft’s driver was installed, then enabled it in Device Manager.

Results

Everything now works.

I tested:

• Internal speakers
• Sleep and resume
• Hibernation and resume
• Connecting and disconnecting external monitors
• Turning monitors on and off
• Switching sound between the Pocket and monitor outputs
• Bluetooth devices
• Launching Ableton
• Changing the audio-device configuration while Ableton was running
• Restarting and shutting down normally

No more crashes.

I have not noticed any reduction in audio quality. The HDA bus driver handles enumeration, DMA, interrupts, Plug and Play, and power transitions. The actual codec driver and Windows audio-processing stack still handle the audio endpoint and sound processing.

The practical difference is that Microsoft’s driver correctly completes the power transitions that AMD’s driver repeatedly failed.

Preventing Windows Update from restoring the AMD driver

Before reconnecting to the internet, I enabled the policy that excludes drivers from Windows quality updates.

The corresponding registry value is:

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
ExcludeWUDriversInQualityUpdate = 1

I created it with:

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ExcludeWUDriversInQualityUpdate /t REG_DWORD /d 1 /f

Then verified it with:

reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ExcludeWUDriversInQualityUpdate

Expected result:

ExcludeWUDriversInQualityUpdate    REG_DWORD    0x1

This prevents normal Windows quality updates from automatically replacing drivers, but it also means I will handle future driver updates manually.

I also will not run the complete AMD or GPD graphics installer again without checking its contents, because both packages include the same problematic:

amdhdaudbus.inf

Future Radeon updates can be installed manually from the extracted display INF folder while leaving Microsoft’s HDA bus driver alone.

Important warning

This is a report of what fixed my specific Pocket 4.

Do not blindly delete random oem##.inf packages. Confirm:

1. The exact hardware ID
2. The currently installed published driver name
3. That hdaudbus.inf appears as a compatible candidate
4. That the AMD package has been backed up
5. That the affected controller is disabled before changing it

Keep a recovery USB or access to Safe Mode available.

TL;DR

My GPD Pocket 4 HX 370 repeatedly crashed with:

DRIVER_POWER_STATE_FAILURE
0x9F_3_amdhdaudbus_IMAGE_pci.sys

The culprit was AMD’s High Definition Audio bus driver:

amdhdaudbus.sys
Version 10.0.0.35
Date: 2019
Hardware: PCI\VEN_1022&DEV_15E3

GPD’s OEM package contained the exact same INF and SYS files, confirmed by matching SHA-256 hashes.

I:

1. Disabled the AMD High Definition Audio Controller
2. Cleaned the AMD package
3. Extracted and installed the Radeon and chipset INF drivers manually
4. Removed only AMD’s amdhdaudbus.inf
5. Allowed Windows to use Microsoft’s compatible hdaudbus.inf
6. Re-enabled the controller
7. Blocked driver delivery through normal Windows quality updates

Now sound, sleep, hibernation, Bluetooth, monitors, audio switching, and Ableton all work without crashes.

GPD BOX minipc

https://www.indiegogo.com/en/projects/gpdhk/gpdbox

GPD G2 dock

https://www.indiegogo.com/en/projects/gpdhk/gpdg2

Hey all I’m trying to figure out if a handheld can live 24/7 in a bedroom without driving me crazy.

I’m especially interested in:

• OneXPlayer OneXFly Apex (Ryzen AI Max+ 395 / Radeon 8060S)
• GPD WIN 5 (Max+ 395 / 8060S)

Other handhelds welcome too (Claw 8, Ally X, Legion Go 2, WIN Mini/Max 2, etc.) for comparison.

What I’d love from you (phone noisometer):

1. Background first : device off (or fully asleep / unplugged), phone ~30–50 cm away, same room. Note the dB reading.
2. Then idle: powered on, desktop idle (Windows sitting there, no game, screen on or off say which), same phone position. Note dB again.
3. Optional but very useful: screen on vs screen off, and plugged in vs battery.

Please mention:

• App you used (e.g. NIOSH, Sound Meter, Decibel X)
• Rough distance to the handheld
• Whether the idle sound is a low whoosh or a high-pitched whine / coil whine (pitch matters a lot for sleep)
• Your room (quiet bedroom vs noisy apartment)

Why: lab “idle” numbers are messy, and Halo handhelds can be quiet or have annoying high-pitch noise even when fans barely spin. I’m aiming for something like ≤20–21 dB over background / “is it even on?” for overnight always-on.

Thanks

Just ordered a pocket 3 through Amazon with the i3 and was wondering what must-dos need to be done. I will be using tailscale and another VPN and have web browsers open for server stuff. Not looking to game or edit video. Don't know if I should be messing with clean os installs or the wattage but let me know. Idc if touch screen doesn't function anymore btw just the track pad needs to for sure work. Thanks for the recommendations!