This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 26%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECD%3C/text%3E%3C/svg%3E)
Display Properties in Adapter show System Video Memory 0,
Is it recommended there to be some minimum or optimal value so as to supply proper configuration?
Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 37%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
I perused that page in MSDN, it 's on to some mobile implementation,
should I keep a line there about not intending in some contexts video memory to interfere with other memory processes?
Because it could be that genious behind it has decided to economize any pc in this way and I wouldn't disagree with it.
But how to know if this has to do with a microseconds problem or whether with unavailability of content due to copyrights and regional limitations? Or even with commercial policies about expensive & non-expensive clockworks?
(just checking, ok? IT and the Humanities? Building a PC? whatever)
Pardon, if I ask this question in Community, it rather falls outside the scope of that forum as proved before; then here? It looks like it either falls out of encyclopedic frames for the style, or it's also like dummy novice.. no?
See explanations in MSDN : Calculating Graphics Memory
It's good to know something is off with that zero,
however I 'd be looking for some specific string or instructive steps to simply change the arithmetic value there to other than zero;
(documentation appears to be composed solely on a meta-versed orientation)
Basically, because there's been a history with the present question,
it would be useful to be clarified whether video memory can be a windows-autopatch category tag?
Based on help hints, it was implicated that some deployments were missing a "postprocessing group" from the winRegistry which was related to a certain symptom in performance with regard to microseconds; then the same symptom seemed also relevant with the zeroed System Video Memory.
Could you possibly separate the one from the other? So as to determine what I may be, or not be, looking for?
Hi claus
The "System Video Memory" value of 0 in the Display Properties indicates that dedicated video memory is not allocated. Whether there is a recommended minimum or optimal value depends on hardware, software requirements, and specific graphics adapter capabilities. Consult documentation, consider application requirements, and test different allocations for optimal performance.
