hi, the same as in the title, swarm agent is crashing my pc.
I’m just starting to build light and pc is getting crashd, sometimes at the beggining very often at the end of light build. Today i tried to open swarm agent from desktop without building anything in ue4 and after 3 seconds of swarm agent running pc have crashed.
Im using i7 4771, 16 gb ram 2x gtx titan, 1200vat power. windows 8,1, unreal 4.9.2
Can you include the logs please?
which one and how to do that ?
sorry i’m a lil bit new to this…
Will leave the error to an expert… however will trade my PC with you… it runs fine 
(and is also WAY under the specs of yours)
Hello alchemik,
If you would provide some reproduction steps leading up to the crash.
Also if your editor crashes then you will see a crash reporter window asking for you to submit a crash report. If you would link your Machine ID that is listed on this crash report. This is so I can look through our database of reported crashes and find your crash logs.
Thank you,
there is no real way to reproduce swarm agent error window, because i saw it only once, i think i was lucky and swarm agent has faild to initialize fully to did the restart.
also when i recievie crash there is no bigger processor activity or something, i dont see any instant cpu usage, its working, building light 100 % complete and restart
sometimes its restarting on the beggining of light building, but usually at the end. And ofc when i manualy open swarm agent window, its like 3 seconds later
again… there is no crash report.
I only saw it once and it was showing me that i dont have enought memory to complete ligh build.
I’ve set manualy virtual memory number to 16000 and it was working for 2 tests one after another. Today its not working anymore. Like usually. Building light is woking correctly in most of the cases, untill the part when loading bar is showing 100 % complete then there are some progess bars that its aplying the textures or something, right after 100% of light building complete information, and in this part pc is restarting without any crashes. Sometimes pc is crashing on the beginning of light build, and also very often when swarm agent is starting to run and windows is asking me if i want to let swarm agent connect to internet. But its not askig me every time to do that. I have opened swarm agent window from unreal folder, and my pc have crashed 3 seconds later, just when i was watching this white swarm agent table with options etc.
I had the same problem in lower version of unreal, and a lil bit different pc configuration. The same processor, memory, just differen mother board and graphic card, it was an old gtx 750 back then.
I couldnt have 3ds max and unreal open in the same time. For working in viewport everything was ok, but when i tried to build light, pc was crashig. So i was turning off everything, web browser, 3ds max, only then unreal’s light build was working and it was usualy fine. Today i have installed 4.8.3 version to check it out, and light was build correctly, everything have been completed without problems, i could move around in viewport in unreal, but seconds later pc have crashed but not instant crash like swarm agent is doing, but by blue screen like my computer would be overloaded
again… there is no crash report. I only saw it once and it was showing me that i dont have enought memory to complete ligh build. I’ve set manualy virtual memory number to 16000 and it was working for 2 tests one after another. Today its not working anymore. Like usually. Building light is woking correctly in most of the cases, untill the part when loading bar is showing 100 % complete then there are some progess bars that its aplying the textures or something, right after 100% of light building complete information, and in this part pc is restarting without any crashes. Sometimes pc is crashing on the beginning of light build, and also very often when swarm agent is starting to run and windows is asking me if i want to let swarm agent connect to internet. But its not askig me every time to do that. I have opened swarm agent window from unreal folder, and my pc have crashed 3 seconds later, just when i was watching this white swarm agent table with options etc.
I had the same problem in lower version of unreal, and a lil bit different pc configuration. The same processor, memory, just differen mother board and graphic card, it was an old gtx 750 back then. I couldnt have 3ds max and unreal open in the same time. For working in viewport everything was ok, but when i tried to build light, pc was crashig. So i was turning off everything, web browser, 3ds max, only then unreal’s light build was working and it was usualy fine. Today i have installed 4.8.3 version to check it out, and light was build correctly, everything have been completed without problems, i could move around in viewport in unreal, but seconds later pc have crashed but not instant crash like swarm agent is doing, but by blue screen like my computer would be overloaded
im using just the basic side scroller template with starting content, but it doesnt matter cuz its always the same on every project. Project size is not important i think beacuse it is restarting my pc when im opening swarm agent without building the light. Just watching main swarm agent window
is crashing my pc like in 3 seconds. I bought today second hard drive and im gonna try to instal windows 8.1 again there, then im gonna check if this situation is still harrasing me. But im in deep hope (hole? :D) that you make something out with that, to avoid formatting pc. Thhanks 
ps its random screen from internet
Ok, from your description it sounds like you are overloading the processors of your computer. What is the size of your project that you are building the lighting on? I am almost afraid to ask the scope of project that is taxing a TITAN like this.
Are you able to build a new blank project with ue4 and run the lighting build or is it this specific project?
I have been unable to reproduce this issue on my machine. Did adding another hard drive and reinstalling windows 8.1 help? If not, as we cannot reproduce this issue, I will be marking this thread as resolved.