Another case of crashing here. I had a stable .423 install on Windows 8 Enterprise (fully updated), then updated to .425. It lasted a day or so then crashed.
Same clr.dll error; same exception code 0xc00000fd.
More worryingly I couldn't get HS3 to restart and I'd changed a load of events between the backup I took when I upgraded and when the crashing started.
Eventually resolved by continually restarting HS3, disableing event processing and then disabling plugins as many as I could before it crashed again until they were all disabled, then cleared out all the running processes remaining in task manager, then restarted HS3 'clean'. Then re-enabled plugins slowly until all running and finally re-enabled event processing. Then all ok (for now at least).
I suspect an issue with the handling of an IP connection that isn't successful. Someone else reported crashing if an IP address couldn't be reached. I think I may have had 2 instances of Jon00SNMPMonitor.exe running when all the crashing happened, which may have 'trodden on each others' toes'?
Hopefully something that can be found and fixed fairly quickly...
Cheers,
Jon.
Same clr.dll error; same exception code 0xc00000fd.
More worryingly I couldn't get HS3 to restart and I'd changed a load of events between the backup I took when I upgraded and when the crashing started.
Eventually resolved by continually restarting HS3, disableing event processing and then disabling plugins as many as I could before it crashed again until they were all disabled, then cleared out all the running processes remaining in task manager, then restarted HS3 'clean'. Then re-enabled plugins slowly until all running and finally re-enabled event processing. Then all ok (for now at least).
I suspect an issue with the handling of an IP connection that isn't successful. Someone else reported crashing if an IP address couldn't be reached. I think I may have had 2 instances of Jon00SNMPMonitor.exe running when all the crashing happened, which may have 'trodden on each others' toes'?
Hopefully something that can be found and fixed fairly quickly...
Cheers,
Jon.
Comment