amd3dvcacheSvc is causing errors, help needed

Update: AMD replaced the chip with no problem. ASUS also replaced the board(finally). Both were defective. They didn't go into details. I received a refurbished ASUS board. AMD is sending a new chip. Maybe the original error is a sign of damage. Maybe not. They are pretty locked on explanations. So far there hasn't been an amd3dvcacheSvc error and the kernel 41 critical error since the chip and mobo swap. Hope this helps. Maybe some can try the RMA process to fix this issue. I know this isn’t the most graceful fix that some have been searching for. Good luck everyone.

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.

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.

After trying the beta bios and crashing, I set my ram frequency from Auto to 6000mhz. Didn't crash all night.

Likely not the solution, but little changes seem to make it stable for a short while, before the crashing begins again.

For the record, tried this beta bios update, but still crashing.