Demonbuddy Freezing computer

[flexkres]

Hi! Been running Demonbuddy without any flaws lately, and so included version 118.

But tonight about 01:00 UTC+1, 6-18-2012, it started after about "10-15" minutes to cause my computer to seize, then i started using the version before 118 "i always keep 3 versions back", and from what i can see, no problems at all.

Is there any changes done to the navigation server AFTER the release of 118 that could cause some memory leak?

I also tried "the one time the whole computer didnt freeze" taskkill /f /im demonbuddy.exe

and the process refused to go away. There is nothing in the logs, its just as if it was doing its normal buisness then stopped logging / working and froze my computer. And as i said, no problems with previous version.


Thx in advance, and if u need me to do a memory leak check just tell me or anything else

 

[Tony]

have you tried a PC restart?

 

[flexkres]

have you tried a PC restart?

i was sortof forced to about 7 times thats what i mean with Seize the computer froze COMPLETLY but only with 118

 

[Tony]

trya new .125 installation from scratch and let me know

 

[flexkres]

trya new .125 installation from scratch and let me know

My Apologies, it was 125 that i had ^^, and 118 is working sorry ur guys so fast its hard to keep up with you

Well im using:
Plugins: Icools Sarkoth Helper V1.0, Relogger
Profile: Demon Hunter Sarkoth Farm V1.4 - Icool edited by ikw
And im using the demonhunter vault cc from zoinx.

Possibility OFC that im just having a freak of nature issue, time will tell i guess if more report it Just thought i might as well report it.

I will try the .125 fresh install tomorrow, time for bed right now 2:12 am here

 

[Tony]

ok,let me know

 

[flexkres]

ok,let me know

what seems to appear in my logs before computer crashes is the following and im just assuming it has something to do with the bot? since i never had this issue before.

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

 

[Tony]

what seems to appear in my logs before computer crashes is the following and im just assuming it has something to do with the bot? since i never had this issue before.

Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.

can you give me that log file plz?

 

[flexkres]

can you give me that log file plz?

Sure, ill attach it to this log what i have noticed now that i examined the logs... is that software protection starts and stops right before the computer stops... Im gonna look into that...

 

[flexkres]

Update, disabling software protection in services made the bot start alot faster and with alot less fuss, im gonna run for a little while and report back if this solved it, because as i said, each time i see a gap in the timeline of my logs from yesterday when the bot crashed, software protection from windows started/stopped.

*edit*
Added the wmi log

*edit2*
I wont scream WHOHOO yet... but it does seem promising...

I will report back in 1 hour, and if no hickups, disabling software protection, and putting startup to manual, has fixed it

*Edit3*
Tony, i wont take up more of your time atm, it didnt fix it, you have more important things to do, i will however, not rest till this god damn thing works

Ill report back on what the problem was incase someone else gets it.

Thx for your attention

*Edit 4*
Mr Derp le derp "me who feals like a derp" found a little peice of code in a relogger plugin, using thread sleep 10000.

Trying without it, will report back.

*Edit 5* Still no problems, seems like the issue was the sleep timer...