Skip to main content
Participant
August 27, 2024

GPU HRESULT Error in ChA with RTX4060 Laptop

  • August 27, 2024
  • 4 replies
  • 469 views

Version of ChA: 24.6 &  24.0

Operating System: Windows 11 Home 64-bit (10.0, Build 22631) (22621.ni_release.220506-1250)
System Manufacturer: HP
System Model: Victus by HP Gaming Laptop 16-r0xxx
BIOS: F.21 (type: UEFI)
Processor: 13th Gen Intel(R) Core(TM) i7-13700HX (24 CPUs), ~2.1GHz
Memory: 32768MB RAM
DirectX Version: DirectX 12
DirectX Database Version: 1.5.9

Card name: NVIDIA GeForce RTX 4060 Laptop GPU
Driver File Version: 32.00.0015.5599

 

Been working with Character Animator for about 2 weeks and it was working fine until this week when I keep getting a GPU error upon opening the program.  I also get the error when switching between Rig, Record and Stream.  The microphone is also stuck in Audio Level Too Low and the characterizer does not says there No microphone input detected when I try a new catpure.  I have rolled back GPU drivers and versions of ChA, Media Encoder, and Bridge.  This problem seems similar to this thread...https://community.adobe.com/t5/character-animator-discussions/character-animator-not-working-as-it-should/td-p/13701248

 

4 replies

Participant
December 22, 2024

I have %99 same laptop and the same problem ! I don't know how i can swap from nVidia GPU to Intel low-power internal GPU? Where is this setting in CA?

Participant
September 9, 2024
quote

Switching to the Microsoft Basic Display Driver seems to have fixed the issue with Character Animator. 

 


May I ask how this was done? I am encountering the same error all of a sudden.

Participant
August 28, 2024

Update:  After a second time with Adobe Support Chat.  The issues seems to be with the Internal Intel Display Driver NOT the Nvidia GPU.  Switching to the Microsoft Basic Display Driver seems to have fixed the issue with Character Animator.  I have only confirmed this on ChA 24.2.  If I run in to this issue agian I will let you know.

Participant
August 28, 2024

Update: reverted back to all the latest and "greatest" drivers (NSD 560.81 & ChA 24.6) and apps, and connected Adobe customer service.  The tech started the ChA as an admin and it started working.  I replicated it today both as admin and as a reg user.  Ultimately, the problem seems to be fixed, but don't understand what the problem was.