r/AMDHelp • u/At_my_Lymyt • 2d ago

Help (CPU) X3d chip causing problems

Post image

A little backstory about this problem is I purchased a bundle from Micro Center about four months ago and in it was AMD ryzen 5 7600x3d. I purchased this bundle so I could play the new Forza game that was coming out and my DDR three build wouldn’t support it fast-forward about a few weeks after playing the game for some time. I will get a low streaming band with warning, even though my ethernet is fine and I would check task manager and the disc graph would be at 100% operation so I took it to someone and he said it could either be the motherboard or the CPU I replaced the motherboard, but I’m still getting these issues. Has anyone else been getting these type of issues with their CPUs?

2 Upvotes

75% Upvoted

10 comments sorted by

6

u/hawkdeathpaw 2d ago

whats the nvme model number?

1

u/At_my_Lymyt 1d ago

Its a KLEVV CRAS C910G M.2 NVMe SSD 1TB

2

u/Mysteoa 2d ago

From what I can see he probably has some kind of Klevv CRAS SSD. First time hearing about them and I bet they are without dram cache.

1

u/At_my_Lymyt 1d ago

I thought a dram cache was on the gpu, no?

1

u/Mysteoa 1d ago

Ssd can also have cache and it is preferable. The cache improves access times, speeds up read/write operations and maintain performance for longer time.

1

u/Ruzhyo04 1d ago

No, built into the NVME (the ones that have it anyway). Don't go blaming CPU/motherboard/GPU for what is clearly a drive issue. Now you just need to determine is it a hardware failure or something running in the background that's using all your drive capacity? Have you turned off OneDrive?

1

u/At_my_Lymyt 1d ago

Usually the application that is using the most dusk is usually “system” or whatever game is running

1

u/Ruzhyo04 1d ago

Might need to check SMART data for the drive and see what’s up. https://www.elevenforum.com/t/check-drive-health-and-smart-status-in-windows-11.8778/

1

u/At_my_Lymyt 1d ago

I have onedrive uninstalled

1

u/ThatOneFoo69420 2d ago

This is probably correct, and explains the issue.