forked from xCuri0/ReBarUEFI
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why is my BAR1 Memory always occupied? #89
Comments
have you figured it out? mine does the same |
Interesting, I'm observing this too:
Since I'm unsure of the source of that value, it could have a different meaning than what we are attributing to it. Windows' task manager shows a normal vram usage (as well as GPU-Z). |
Same issue here. |
Anyone figure this out yet? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I successfully enabled Resizeable Bar a few days ago, but I found that my BAR1 usage is different from everyone else's, my BAR1 is always in a run-out state, even though i'm not running any programs.
My BAR1 usage:
Other people's BAR1 usage:
The text was updated successfully, but these errors were encountered: