C0kkie 0 Posted October 3 Share Posted October 3 Hello, since a few weeks i encour the problem that the disk use on startup is very high and slow downs my computer. After the disk usage is normal again it works without problems until the next restart How can i locate the problem? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 3 Administrators Share Posted October 3 Startup scans are run with low priority so they should not take a noticeable amount of system resources. Moreover, they basically scan only files that in autostart locations and on your desktop. Couldn't it be that you have a lot of archives or executables in a folder on the desktop? Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 3 Author Share Posted October 3 Hi, thanks for your reply. What means "a lot" for you? I would say i dont have many Quote Link to comment Share on other sites More sharing options...
SeriousHoax 83 Posted October 5 Share Posted October 5 As Marcos said it could depend on the number of files you have. Also, if it's a HDD then some higher disk usage is expected. It has almost no impact on SSDs. Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 5 Author Share Posted October 5 Its a ssd and there are not many files Quote Link to comment Share on other sites More sharing options...
SeriousHoax 83 Posted October 5 Share Posted October 5 4 minutes ago, C0kkie said: Its a ssd and there are not many files In that case, I'm not sure what's causing this. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 5 Administrators Share Posted October 5 Does temporarily disabling startup scan tasks in Scheduler actually make a difference? Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 9 Author Share Posted October 9 Hi, even with startup scan disabled eset uses a lot of disk usage on startup Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 9 Administrators Share Posted October 9 We only load the modules and scan files that the operating system or other applications access on system startup. Please generate a Procmon boot log. Stop logging about 2-3 minutes after the system starts when the issue was manifesting. Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 10 Author Share Posted October 10 Hello, sadly there are 3 generated bootlog files where 2 are too large (270mb and 240) how can i send you the logs? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 10 Administrators Share Posted October 10 Please compress them first. If still too big to upload them here, upload them to a safe location (OneDrive, DropBox, etc.) and drop me a personal message with a download link. Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 10 Author Share Posted October 10 Sended you in pm the onedrive link Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 12 Author Share Posted October 12 @Marcos Any news? Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 17 Author Share Posted October 17 Any news? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 18 Administrators Share Posted October 18 Do you see a bigger difference if you add C:\ProgramData\Digieffects\Uninstallers\Digieffects-Damage-3.0.0.exe to performance exclusions and reboot the machine? Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 19 Author Share Posted October 19 Hello, i deleted the whole file now and still nothing changed Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 19 Administrators Share Posted October 19 According to the Procmon log, excluding the above file (41 MB archive) could save about 10s. Please provide another Procmon boot log created with the file excluded. Just to make sure, does the problem cease manifesting if you temporarily disable the startup scan task run after module update? Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 21 Author Share Posted October 21 (edited) @Marcos sended you the new logs via dm and yes with that disabled its faster Edited October 21 by C0kkie Quote Link to comment Share on other sites More sharing options...
C0kkie 0 Posted October 26 Author Share Posted October 26 any idea? @Marcos Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted October 27 Administrators Share Posted October 27 Unfortunately the log didn't yield anything unusual or suspicious, all files were scanned quickly (dozens of miliseconds at most). Does any of the following make a difference? 1, Temporarily adding C:\Users\Florian\AppData\Roaming\* to performance exclusions. 2, Temporarily disabling archives and self-extracting archives in the Startup scan setup: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.