Computer Specs:
OS: Windows 8.1
GPU: GTX 660m
CPU: Intel Core i7-3630QM CPU @ 2.40GHz
RAM: 8GB
Storage: 900 - 1000 GB
Problem:
Ever since I downgraded from windows 10 to windows 8 my computer has been reporting that it has been using 80%+ RAM. At first I didn't think it was a problem as many people have said it's suppose to use a lot of RAM and not leaving it idle, but then Windows started force closing programs I was using to save RAM. Not to mention things are taking an crazy amount of time to open or close.
FAQ:
Have you run anti-virus scans: Yes, I have multiple times with different anti-viruses.
Have you tried restarting your computer/reboot: Yes.
Do you have screenshots: (RamMap) http://i.imgur.com/YsGdv1i.png || (Resource Manager) http://i.imgur.com/xLr0KDa.png
Quick Note:
- I am a computer novice, I may not be familiar with certain terms or things, so please be detailed with your directions and don't get to frustrated with me! Thanks in advance!
- This also isn't my first post about this issue, I found a temporary fix but that seemed to run out.
OS: Windows 8.1
GPU: GTX 660m
CPU: Intel Core i7-3630QM CPU @ 2.40GHz
RAM: 8GB
Storage: 900 - 1000 GB
Problem:
Ever since I downgraded from windows 10 to windows 8 my computer has been reporting that it has been using 80%+ RAM. At first I didn't think it was a problem as many people have said it's suppose to use a lot of RAM and not leaving it idle, but then Windows started force closing programs I was using to save RAM. Not to mention things are taking an crazy amount of time to open or close.
FAQ:
Have you run anti-virus scans: Yes, I have multiple times with different anti-viruses.
Have you tried restarting your computer/reboot: Yes.
Do you have screenshots: (RamMap) http://i.imgur.com/YsGdv1i.png || (Resource Manager) http://i.imgur.com/xLr0KDa.png
Quick Note:
- I am a computer novice, I may not be familiar with certain terms or things, so please be detailed with your directions and don't get to frustrated with me! Thanks in advance!
- This also isn't my first post about this issue, I found a temporary fix but that seemed to run out.