This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
The description for Event ID 1 from source amd3dvcacheSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
amd3dvcacheSvc
CreateHelperUserProcess - WTSQueryUserToken Failed failed with 1008
The message resource is present but the message was not found in the message table
CPU: 7800X3D
GPU: 7900XTX
Windows 10
32G DDR5-6000 CL36
This is a fresh build and I'm looking for some help with a few errors. One of which is the above. Any help would be appreciated.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I had a kernel error too ID 41 (63).
However, only when I turned on the PC, it was displayed in the log, see picture. However, after I turned off FAST STARTUP in windows the problem disappeared.
Otherwise I have limited VDDCR_SOC voltage to 1.140 V
I'm trying your fix now. I turned off FAST STARTUP, and I limited the VDDCR_SOC to 1.140. Hopefully, this fixes everything.
This was from overnight. Hopefully, the fix MichalBrousek mentioned is the key.
This was from overnight. Hopefully, the fix MichalBrousek mentioned is the key.
I don't understand what the image you're showing is trying to say?
Fwiw, the new Bios that supposed to clear up all of these issues is supposed to be released sometime in August.
If I remember correctly, I still set PBO enabled, all cores negative 30 according to the person in this thread
this was before the release of bios version 1415, but I stayed on it after.
I hope this helps you.
I was just showing that I had the error in the last 24 hours. The new BIOS didn't fix the issue for me.
This was from overnight. Hopefully, the fix MichalBrousek mentioned is the key.
I don't understand what the image you're showing is trying to say?
Fwiw, the new Bios that supposed to clear up all of these issues is supposed to be released sometime in August.
