I'm not sure what's happening. Can you provide more details?
I'm not sure what's happening. Can you provide more details?
I often hear this idea for various issues, yet it hasn't helped me solve my own problems. It might be working for others, but it doesn’t seem to benefit mine.
1. Retrieve CPU-Z data and verify your memory operates at the expected speeds (DRAM Frequency x2 = 3600 Mhz) on Channel # Dual.
2. It's amusing to run a Cinebench R23; results should show around 17799 points in the multi-core test.
3. Scan your event viewer for numerous error messages.
4. Execute Prime95 to assess CPU and RAM stability.
5. Perform Furmark to evaluate GPU performance.
6. Execute both tests to ensure your PSU meets requirements and overall system stability.
updated bios and amd drivers crystal disk info indicated the drive was okay. Samsung Magician confirmed it was running the latest update. There are many event viewer messages, but most don’t help identify issues. Prime95 froze my PC completely on startup and only partially closed after a short period. I ran Furmark for 30 minutes without any problems. I’m currently testing the system in games to check if crashes will continue.
It didn’t take long for it to crash. Probably none of the options helped, so I’m stuck figuring out what to do next.
The reset process didn’t help either. I don’t understand the problem with my computer.
You're asking about the method for resetting Windows—whether it's a full reinstall or using an existing backup. If you've already done a later update, a fresh installation might be necessary.
It was a new setup, unfortunately. But I swapped out my GPU and installed another RAM stick, and it’s working fine right now. I’ll keep testing it until I’m more hopeful. I promise if it turns out to be bad RAM, this will be my second time in about two years dealing with that issue.
It looks like I've identified the problem. I swapped out the RAM sticks and re-seated my GPU, and since the games aren't crashing and performance is back to normal, it was the GPU positioning that caused the issue. I'll keep testing tonight and tomorrow, but I'm marking this as resolved now.