This is the error code I get (along with a blue screen). I have read that this can be attributed to using McAfee - any thoughts or suggestions?
As per the header rather than your first line I assume you mean worker_thread_returned_at_bad_irql rather than worker_threat ?
This isn't a particular trait of any McAfee software as far as I know but can be caused by (for just 2 examples) DaemonTools and Alcohol 120% software, or so my Google searches tell me
You've posted under Virtual Technician which is just a small repair tool. Could you advise what McAfee software we are talking about here?.Message was edited by: Ex_Brit on 29/10/12 6:22:37 EDT PM
Thank you, Ex_Brit. Yes, I did mean worker_thread.
I am using McAfee Security Center. I thought I posted under a General Discussion! Sorry about that!
OK, I moved this to SecurityCenter. I searched the forums and we haven't seen this at all as far as I can tell. You could call Technical Support I guess and ask them. They are linked under Useful Links at the top of this page.
According to what I read in Google Search it was caused by those 2 software and possibly others and especially in Windows 7.
.Message was edited by: Ex_Brit on 09/11/12 3:19:18 EST AM
I created an account just so I could answer this question.
2 months ago I purchased a Lenovo Ideapad laptop with a trial version of McAfee preloaded on it. I've repeatdly recieved the same message almost from the outset, sometimes as many as 10 times a day. I've researched this repeatedly, checked my drivers, etc. and the problem has continued. 2 days ago I uninstalled the trial version of McAfee because I hadn't intended to keep it anyway. This is the only change I've made to this laptop and the problem has completely stopped. I haven't seen the message and the BSOD for 2 days and this is the very first time that has happened since I purchased this laptop.
I hope this puts an end to your frustration too!
In other similar cases the culprit appears to be the McAfee firewall driver "mfewfpk.sys". What to do about it though I don't know. Perhaps Ex_Brit might recognise the driver name from an older thread.
It would help if you had the minidump from the last BSOD, because with Nirsoft's BlueScreen View that would give a snapshot of the system at the point the Stop Code was generated (and neither poster has given any information about the Stop Code or the associated parameters, which doesn't help).
See these two Microsoft forum threads -Message was edited by: Hayton on 09/11/12 05:06:18 GMT
The only thing I can add is that trial versions provided by Lenovo and other 3rd parties are possibly modified in such a way as to cause this. They do alter the code often to fit in branding etc., even sometimes to trim off certain features.
Technical Support are the best avenue for support here I feel.Message was edited by: Ex_Brit on 09/11/12 3:30:38 EST AM