Desktop freezes often (2-4 times a day)

Jan 12, 2020 4:59AM PST

Hi Guys,

I have a similar problem to the user in this thread here:

However, he didnt report back to what solved his problem. :Happy

Im having random freezes, and its usually a bit worse when playing a game like Battlefield 5. I notice that especially when a map end and it has to progress into a loading screen, it freezes.
Also, when I have had a freeze, it is usually likely to freeze a several couple times more soon after (like 45 mins after).
In the past it said that the Radeon Wattman settings were restored. But it didnt do so all the time.
I tried to enable memory dumps of the crashes but the system doesnt save them (probably because of the unexpected shutdown).
I upgraded my BIOS too, but didnt help.

In Event Viewer I get the following Error events :

The AMDRyzenMasterDriver service failed to start due to the following error:
The system cannot find the path specified.

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

Here is my speccy:

Anything else I can do?

Help is greatly appreciated!

Discussion is locked

Reply to: Desktop freezes often (2-4 times a day)
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Desktop freezes often (2-4 times a day)
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
Sorry but as this is a pre-450 motherboard.
Jan 12, 2020 10:44AM PST

I don't think there is a cure for all of those. I've seen way too many months trying to save such machines and at the shop we won't take such a machine in unless the owner allows us to change the motherboard.

In short, the outlook of a solid fix using this gear is grim.

Let's try the usual and hope.

1. The BIOS IS CURRENT. Good to see.
2. The memory timing looks to be DEFAULT. Lockups due to memory are very common on pre-450 and even after but moreso pre-450 boards. I'd ask two questions of the motherboard maker.
a) What memory settings should I be using? (Hint: Try XMP)
b) Is this memory compatible?

3. XenSource Citrix Indirect Display Adapter,
This adds another dimenstion to problems. I'd remove this.
In short we head back to as stock as can be as well as the next item.

4. The OS is not an OEM, retail and may be from other than Microsoft. I've run into such before and have shown the owner that a clean install with a copy from Microsoft worked fine. I do not have the time as well as don't get paid to find out why this happens. In short the OS is not one you usually see. Again, you head to a clean stock setup fast on such PCs.

So here we have the usual pre-450 Ryzen, some oddities in the display and RAM and the OS. Looks like we have some chance of improvement before the motherboard is changed out.

- Collapse -
I've tried some things.
Jan 13, 2020 2:07AM PST

Thanks for your reply.

I have removed the XenSource Citrix Indirect Display Adapter and set the memory settings to a pre-existing XMP profile in the BIOS.

Haven't had the time to test this extensively, but I had played Battlefield 5 for 45 minutes without crashing yesterday. This looks promising, as normally, a crash would have been highly likely. Will report back soon, and thanks again.

- Collapse -
That's good to hear.
Jan 13, 2020 11:06AM PST

While I don't expect such to be crash free, any improvement could make it a PC you can get by on.

- Collapse -
It definitely improved
Jan 13, 2020 12:21PM PST

Yes, I'm running now for about 2 hours and zero crashes. It seems the problem is fixed. Thanks man!

CNET Forums

Forum Info