I know you say not to bump or duplicate post, but my post even got picked up as forgotten by a bleeping computer helpbot, I posted a new log, and still nothing. Did it go to the back of the queue again for some reason?
If the reason noone has bothered to help is that on reviewing the logs I posted helpers think my problem is solved, then please, can you actually let me know, that would be really helpful ! I had to try and progress some resolution myself (by reading other peoples solutions and running tools myself), as I needed to use the PC, but I would still appreciate someone reviewing the logs to tell me whether they think the problems are solved, whether there are any other problems I am not aware of, and whether I am OK to clean up and removal the tools used, and any advice on how to do this.
I think the problem with the firefox shockwave plugin crashing I have solved, so I do not think it is a symptom of some residual malware issue:
"Warning: Unresponsive Plugin
Shockwave Flash may be busy, or it may have stopped responding. You can stop the plug now, or you can continue to see if the plugin will complete."
I noticed plugin-hang-ui.exe running under processes list on Task Manager. I did not disable this, which is what some chat on the forums suggests. I identified that the space on the c drive was low. It still had gigabtyes free, but not many. Disk space free was between four and five GB, but I have RAM of 8GB.
I noticed the event viewer showed this: "Error: volmgr  - Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory." and wondered whether the lack of C drive space had anything to do with the flash plugin hitting problems also. Having ensured that space on the C drive is now around 12GB, the problem with the shockwave plugin stopping responding has gone away. When videos are maximised and minimised there still can be a brief pause, but there is no crash.
I noticed after solving the plugin issue myself, others have noted the problem: https://support.mozilla.org/en-US/questions/955286
However despite this issue being solved, I would still appreciate someone looking over the logs I previously posted to see if conduit has been successfully removed, and whether any other issues are present, and suggest what clean up actions to take to remove the tools I have run in my previous post.
Edited by dolphin6476, 20 November 2013 - 07:03 AM.