for the past day or so I've notice that when I left the bot run for a while and come back my computer had restarted. Is there any reason for this bot to have caused this restart or is it something else?
Very strange Problem :-\
I've discovered this to be a result of the bot AND warpack. I checked my event log on my computer and it caused a critical system error which resulted in a shutdown/restarting of the computer. Why would this cause such an error and how to fix this an error of this type?
I am unable to run the bot while I go to sleep which is counter-productive.
Should I post the event log I get to show you the error exactly?
it's BSOD?
no it is not blue screen of death error message. It simply "restarts" and what I think is happening is there are TOO MANY client server calls from the bot client and it is hanging the cpu causing it to overheat and restarting the system. It does not do this when i run any other thing and the pc is in good health running a quad core.
it is definitely warpack.exe / warpack.dll and dniwebot.exe . It mostly does it when I run the bot for 15 minutes or more.
My GPU: Perfect health
My CPU: Good health (CPU runs hot when I run the bot and warpack@ 70c-75c on all four cores and 50c-60c when I run anything else)
System: Perfect health and no errors in Check Disk
My PC memory: Good health and no leaks
Virus Scan: Malwarebytes scanned and showed no virus and I've added Warpack.exe, warpack.dll, dniwebot.exe and guibot.exe to the exclusion list. Windows firewall is off.
Privileges: I run all programs with Admin. Privileges
In-game graphics setting: Minimum, even though that should not matter it's done anyway.
I've run the usual error checking methods and the system is stable. I've ran HW monitor and GPU monitoring during this critical error and my System event log tell me there was a problem with "warpack.exe" and usually only occurs when running dniwebot.exe and I think it singles out warpack because it uses the executable to "authenticate my login via their servers".
*Still need support*
I don't even know what to tell you, im use a bot on two different systems, and the problem of this kind I have never met
Problem solved, topic closed.