Posts with an empty body, only a link in the body, title copied into the body, and/or lack of information in the body Submissions consisting of the following are considered incomplete and will be removed: Please read our new rules page for more in-depth rules. Please do not submit the same issue more than once within 24 hours. Do everything you can to reduce the effort of the wonderful folks offering to help you.Īfter solving your problem, please mark it as solved by clicking 'flair' and confirming the 'solved' tag. State everything you have tried and all the guides/tutorials/sites you have followed as well as why they were unsuccessful. Try to research your issue before posting, don't be vague.
The subreddit is only for support with tech issues. Please include your system specs, such as Windows/Linux/Mac version/build, model numbers, troubleshooting steps, symptoms, etc. Live Chat ~Enter Discord~ Submission Guidelines Oooh okay.Check out our Knowledge Base, all guides are compiled by our Trusted Techs. So turn off that feature in each program. Most of these are not needed you can occasionally manually check for updates yourself. Windows does that automatically, the notorious Windows updates. Example: almost every program you install adds a "helpful" automatic update feature that loads on boot and checks to see if there are any updates for that program. > #2: carefully investigate everything that is loading into memory and sits there running.
> #1: add more memory and your problem disappears. There can be a boat-load of reasons for this, but a couple of the most common ones are: Obviously that is going to seriously slow the unit dramatically, but at least it prevents your whole system from crashing.
In common English, the memory is so loaded with data running that it must write to the scratch-disk to prevent your system from crashing.ĭefinition: "scratch disk": when the memory has limited-out because so much data or programs are running in it and there is no more memory to use, Windows will start writing to a section of your drive and "pretending" that is actually memory. This is a common occurrence, usually (but not always) on lower-end computers that have limited resources and/or computers that have too many loaders running in memory.
0 kommentar(er)
