So, I had the same error Kernal-Power 41 (63) twice after the new build, but this time without the amd3dvcacheSvc error to follow. I could use the beta BIOS for the MSI Godlike motherboard, which fixed everything. Crazy how I had the same issue with all the new parts. AMD wrote me this morning and approved the RMA for the other chip(I'm not sure if they found something in the files I sent them that made them suspect the CPU was faulty, Or maybe they are just playing it safe. I would say it had something to do with the amd3dvcacheSvc error, but people say their computers are still functional with this error. Either way, that earned points with me as a consumer and makes me feel like AMD cares enough about these issues.) I hope this helps. As I said before, I will keep everyone updated. Apologies that I couldn't be more help.
amd3dvcacheSvc is causing errors, help needed
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.
Windows for home | Windows 10 | Performance and system failures
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.
118 answers
Sort by: Oldest
-
Anonymous
2023-07-24T13:28:30+00:00 -
Anonymous
2023-07-27T19:21:58+00:00 OK so, I just went 8 days straight with no crashes. Played a rediculous amount of star citizen.
Anyway, it started crashing again today.
It was the first day it's been above 18 degrees Celsius outside.. as my pc usually lives in the attic, add a few more degrees for trapped heat, I'm suspecting these cpu's (or something in the pc) is fragile when it comes to a bit of warmth.
Took my pc back downstairs where its a bit cooler, and is working fine again.
-
Anonymous
2023-07-27T22:00:59+00:00 Could be right. Since replacing parts everything has worked fine. No crashes or shutdowns. I'm glad that your PC is fixed.
OK so, I just went 8 days straight with no crashes. Played a rediculous amount of star citizen.
Anyway, it started crashing again today.
It was the first day it's been above 18 degrees Celsius outside.. as my pc usually lives in the attic, add a few more degrees for trapped heat, I'm suspecting these cpu's (or something in the pc) is fragile when it comes to a bit of warmth.
Took my pc back downstairs where its a bit cooler, and is working fine again.
-
Anonymous
2023-07-28T08:38:10+00:00 Which parts did you replace?
And which part do you think was causing the problem?
-
Anonymous
2023-07-28T18:46:41+00:00 Which parts did you replace?
And which part do you think was causing the problem?
I started problem-solving, aiming to identify and rectify a persistent issue plaguing my computer three months ago. I started with RAM replacement, using multiple sets from the QVL, followed by a GPU swap, largely a shot in the dark, considering I had an extra one at hand no big deal.
Subsequently, I replaced the motherboard, transitioning from one ASUS model to another(same board x670e crosshair extreme), but this change failed to resolve the issue. Not one to give up, I then swapped the ASUS motherboard for an MSI variant( MSI x670e Godlike , along with a native PCIE 5.0 MSI MEG Ai1300P PSU, and ultimately RMA'ed the CPU with AMD.
Despite these comprehensive component changes, the issue stubbornly persisted, albeit with a small but noticeable alteration: the original error, termed amd3dvcacheSvc, stopped occurring. While this error has been reported by users without system shutdown issues, it continued to be a nuisance for some of us.
In a final effort to eradicate the problem, I installed a BETA BIOS update for the MSI motherboard(I think ASUS had a BETA BIOS but they removed it? I could be wrong). Remarkably, since this update, the problem has ceased to exist.
Reflecting on this exhaustive troubleshooting journey, my speculative diagnosis, albeit potentially far from accurate, is that an out-of-date motherboard BIOS and a possibly deteriorating PSU may have been the elusive culprits, potentially causing collateral damage to other parts.
Apologies if this conclusion doesn't provide the unequivocal answers some might have anticipated. Nonetheless, I believe the collective wealth of information and experience within this thread can serve as a potent resource for others battling similar gremlins. It serves as a testament that relentless troubleshooting, paired with a dash of luck, often holds the key to unlocking stubborn tech issues. AKA carpet bomb the problem with parts and hope for the best. Certainly not the best, possibly the worst troubleshooting experience I have ever experienced. I'll keep contributing to the thread as long as it's open. Good luck to everyone with this issue. Try the beta BIOS if your motherboard manufacturer has it and nothing else has worked. I know of one person in the thread that said it didn't.