New
#11
A screenshot of msconfig StartUp tab needed as Layback Bear asked for.
Also open Resource Monitor (button on the screenshot of Task Manager) and switch to Memory tab, sort by Working Set and post another screenshot.
A screenshot of msconfig StartUp tab needed as Layback Bear asked for.
Also open Resource Monitor (button on the screenshot of Task Manager) and switch to Memory tab, sort by Working Set and post another screenshot.
Here is the Startup tab as well as Resources sorted on Working
Hmm, can't see anything wrong. Try running RamMap - https://technet.microsoft.com/en-us/.../ff700229.aspx
Check working set for Processes, and File Summary for Active files (non-Standby).
So far I see nothing that indicates why a slow boot (7 min.)
Uncheck your nVidia and Steam in the Startup. Restart and then Shut Down.
From a cold boot check the boot time.
I noticed that I don't see a anti virus installed.
What anti virus do you use and is it installed?
Sorry if you have tried this before, run in elevated cmd:
If corruption is found, then also run:Code:sfc /scannow
and attach the sfcdetails.txtCode:findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >"%userprofile%\desktop\sfcdetails.txt"
A Fresh install (Clean Install) should not need sfc /scannow but it can't hurt and it's free.
Some errors were found. I'm attaching the document.
I'm no sfc log expert but that seem like a lot of repairs for a Clean Install.
Reboot and run sfc /scannow again and see if their are any more problems.
The reason you reboot after running sfc /scannow when their is a problem. Windows 7 at times does the repairs during the reboot when things are not running.
***What anti virus are you using?***
You should not go on line with this computer without a anti virus program installed and updated. You can get infected in a few m/s and that will also slow things down and other bad things.
I don't currently have an anti virus installed, but these problems persisted before the computer ever connected to the Internet.
UPDATE: Installed Trend Micro
Last edited by iamspugeddy; 31 Aug 2015 at 11:24. Reason: update
Here's the new set of errors that were reported.