If it happens after a restart, it must be one or more Windows process in the background, which runs after a restart/boot, e.g. update check. The issue is RAM related as you thought. How long do you usually wait before you start launching the programs? Wait moreuntil the system is fully loaded and all background Windows processes finished their thang. While 32 GB of RAM is plenty, but 57 programs are a lot to run, they can get only 500 MB each. Maybe consider adding more RAM.
If you don't want to start all those programs manually everytime, make a batch file with all of them and don't forget to put delays between starts or use the "pause" command: https://stackoverflow.com/a/5535154
Open task manager then click on performance tab and open performance monitor.
do that when it starts up, and watch the memory usage, disk activity and processor.
look out for either the available ram going to zero, the processor maxing out or the disk queue peaking at 10 or more. Then you might pinpoint the issue.
I must admit though it sounds like graphics, and possibly the graphics is using some of the ram and the ram is running out causing the graphics to struggle? It may just be that on start up, many processes are consuming ram and perhaps not releasing it quickly enough, hence it running out.
but then once you close and re-open the programs, it’s only the program usage rather than programs SND other startup tasks.
anyway, I’d definitely be looking at performance monitor first off.
idk what everyone else above me said but as a computer repair specialist, its hard to say with that info you gave but I think it would be lucky to say you have a cpu heatsink thermal paste bond problem or the Hard drive/ssd you're running has a problem. I'd start with that and if you are running windows, do a quick defrag https://www.google.com/search?q=how+to+run+a+defrag
Edit: After reading everything above me I would suggest not clicking on 57 programs when starting, try to go in groups of 5-10 but holy heck dude who runs 57 programs. check your ran and wait like 2 mins between opeining each group. maybe like set us a script to do so.
You should be good. It just sounds like you are chocking the ram when starting up and opening all of those.https://smallbusiness.chron.com/ram-affect-fast-computer-starts-up-69760.html
tl;dr: check ram as starting programs and/or wait like 5 mins after you computer fully starts
Checking if there was any graphics driver update. I had some what similar issue and i found out there was a new buggy update from nvidia that was causing one of my monitor to go blank.
It happens, because you max out the RAM by starting that many programs in a short time frame, when it disappears, the RAM usage is normalized, the FF instances finished the launch process and they're idling waiting for you to start the macros. If it disappears at all and you don't have to restart the machine again. lol Programs usually use a lot more RAM, when launching compared to when idling or sometimes even when running a task. Plus if you don't wait for the system to fully load, Windows processes will require some RAM too until they finished, whatever they're doing after booting. They occupy the RAM and induce a high disk usage, now if you launch a lot of programs on top of this, that's when all hell breaks loose.I wish I knew what happens with the black screen to put the computer in gear...?
Start FF1
Start FF2
Start FF3
Start FF4
Start FF5
Pause
Start FF6
Start FF7
Start FF8
Start FF9
Start FF10
Pause
....and so on
Modern systems have many programs running in the background. The vast majority must be Windows processes and some belong to drivers, if you didn't install anything else and your system is not infected. Look for them with the name of the .exe on Google, you can find out what those are and whether it's safe to kill some of them and remove them from the startup programs. But it shouldn't make too big of a difference honestly. You have 32 GB of RAM, the system uses maybe 2 GB, so this is not the issue.And if anyone can tell me why are those processes/threads/handles at such numbers?
This graphics driver could not find compatible graphics hardware."
Update your drivers. (You should do this regularly anyway, e.g. with DriverMax Free).
i think it is best to download drivers from the official site and don't use 3d party..https://www.drivermax.com/download.htm
It happens, because you max out the RAM by starting that many programs in a short time frame, when it disappears, the RAM usage is normalized, the FF instances finished the launch process and they're idling waiting for you to start the macros. If it disappears at all and you don't have to restart the machine again. lol Programs usually use a lot more RAM, when launching compared to when idling or sometimes even when running a task. Plus if you don't wait for the system to fully load, Windows processes will require some RAM too until they finished, whatever they're doing after booting. They occupy the RAM and induce a high disk usage, now if you launch a lot of programs on top of this, that's when all hell breaks loose.And that's why it only happens, after a system boot/reboot.
Those are browser instances you're starting. You have 32 GB RAM total and you run 57 instances, that's roughly 500 MB per instance, the system uses some RAM too. Browsers are notorious RAM consumers, without you noticing, they can use a lot more RAM than half a giga, multiple times that.
I think, the solution was already posted: start the instances either one by one leaving the needed delay between starts or start them in smaller batches, start only 5 at the same time, wait for them to fully load and only then start the next batch. 32 GB RAM should be able handle that. If it works like this, try 10 instances maybe and when you found the safe number, which doesn't cause black screen, make a batch file of starting x instances at the same time, then insert a pause command:
Code:Start FF1 Start FF2 Start FF3 Start FF4 Start FF5 Pause Start FF6 Start FF7 Start FF8 Start FF9 Start FF10 Pause ....and so on
The pause command is there, so you can check, if the instances are fully loaded and just after that start the next batch. If you create this batch file, you make your life a lot easier, because you only need to run the .bat file compared to starting 57 browsers manually.
Modern systems have many programs running in the background. The vast majority must be Windows processes and some belong to drivers, if you didn't install anything else and your system is not infected. Look for them with the name of the .exe on Google, you can find out what those are and whether it's safe to kill some of them and remove them from the startup programs. But it shouldn't make too big of a difference honestly. You have 32 GB of RAM, the system uses maybe 2 GB, so this is not the issue.
It happens, because you max out the RAM by starting that many programs in a short time frame, when it disappears, the RAM usage is normalized, the FF instances finished the launch process and they're idling waiting for you to start the macros. If it disappears at all and you don't have to restart the machine again.
Recent data read from the hard disk are cached in RAM, because there is a good chance that they will be read again soon. This reduces the need to read from the physical disk. Over time these cached data are replaced by other data, that has been read more recently. But if you re-open a program right after closing it, most or all of the data from the disk is in the cache, so it comes in much more quickly than reading it off the disk itself.when I reopen them after the black screen I can open them faster than before, they open faster, they load faster, it all works better. But why?![]()
Recent data read from the hard disk are cached in RAM, because there is a good chance that they will be read again soon. This reduces the need to read from the physical disk. Over time these cached data are replaced by other data, that has been read more recently. But if you re-open a program right after closing it, most or all of the data from the disk is in the cache, so it comes in much more quickly than reading it off the disk itself.
Yea, try that. It should work.FUCK! YES! Forgot about the cache. That's it, you're right.
So we have a diagnosis, what's the cure? Taking my sweet time opening the programs?
Here's what I'll do. On the next restart in 2-3 days I'll really take my time between opening the programs. I mean, I'll do 30+ seconds in between each program. Then the black screen issue shouldn't arise. If it does, well, anyway I'll try it and report back when I do with the results.
Cheers![]()
Yea, try that. It should work.
Yea, try that. It should work.