Jump to content

Hi, I've been having a lot of blue screens recently and I've concluded that is when my Memory's Commit charge reach 100%.

 

I'm working on a huge Illustrator file right now and having it open for too long increase the commit charge with time. I am not familiar with "Commit charge", "Standby" and "Free" Physical Memory in the Resource Monitor, but I just know I have to watch out when it reach 100% to re-open Illustrator. Occasionally I open Photoshop, After-effect and Media Encoder, but this happen with only Illustrator open.

 

I've read someone that it might be because of Overclocking the RAM and I've actually did, but I didn't thought it would be so impactful. My RAM is 32GB(4 sticks) of XPG Gammix D10 DDR4 3600MHz.

 

By default, the RAM was set to 2666MHz and I thought it's max capacity would be able to accept 3600MHz, so I've OC it in the BIOs. Would it help to tune it town to 3200MHz or another number?

 

Is there something else I could do to prevent Commit Charge from reaching 100%?

 

Thank you for enlightening me!

 

 

CommitCharge.png

CommitCharge.png

Link to comment
https://linustechtips.com/topic/1320379-100-commit-charge-crash/
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×