BSOD

Jonathan_King · 10 Jun 2010

I agree with Tom--update these old drivers:

Code:

LMouFilt.Sys Fri Feb 29 05:08:31 2008 
LHidFilt.Sys Fri Feb 29 05:08:27 2008
AmdTools64.sys Mon Apr 28 13:03:39 2008

Those are your keyboard drivers, so update them.

Remove AmdTools.

danrb · 11 Jun 2010

Well I used Driver Genius to make sure all my drivers were up to date and I still get a BSOD. Attached is the latest and yes I see MacAfee is at the top of the stack. I already tried removing MacAfee and still got BSODs. If there is nothing obvious, the only thing I can think of trying is to swap my drives between my two boxes and see if they continue. It's the only thing I haven't tried swapping and would prove they are caused by hardware or software.

Dan

JMH · 11 Jun 2010

danrb said:

Well I used Driver Genius to make sure all my drivers were up to date and I still get a BSOD. Attached is the latest and yes I see MacAfee is at the top of the stack. I already tried removing MacAfee and still got BSODs. If there is nothing obvious, the only thing I can think of trying is to swap my drives between my two boxes and see if they continue. It's the only thing I haven't tried swapping and would prove they are caused by hardware or software.

Hello Dan

This crash was probably caused by mfefirek.sys which I believe is the McAfee Core NDIS Intermediate Filter. I would remove McAfee to test and re-install or replace with Microsoft Security Essentials.

Let us know if you need any additional assistance.

Jan

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun 11 16:09:29.992 2010 (GMT-4)
System Uptime: 0 days 19:55:17.069
BugCheck D1, {38, 2, 0, fffff8800738123c}
*** WARNING: Unable to verify timestamp for mfefirek.sys
*** ERROR: Module load completed but symbols could not be loaded for mfefirek.sys
Probably caused by : mfefirek.sys ( mfefirek+3523c )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  collatz_2.00_w

Jonathan_King · 11 Jun 2010

I agree with Jan. Remove McAfee. BSOD work is dominated by guesswork, probability, and trial-and-error.

If you get BSODs after taking a particular suggestion, upload the new dmps and we will see what the new dmp suggests.

Since McAfee is at the top of the stack, and notorious for causing BSODs, it should be removed, and this removal tool run: http://download.mcafee.com/products/...tches/MCPR.exe

danrb · 11 Jun 2010

Guys. Take a look at all the BSODS in my first post. Many different causes. Suggest hardware. I already tried removing Macafee and things still crashed.

JMH · 11 Jun 2010

danrb said:

Guys. Take a look at all the BSODS in my first post. Many different causes. Suggest hardware. I already tried removing Macafee and things still crashed.

I note that Capt Jack Sparrow on page 1 & Jonathan King on page 3 advised using the McAfee uninstall tool. Did you use that when uninstalling McAfee?

Have you tried using MSE to see how you go?
Might be worth investigating.

Jan.

reventon · 12 Jun 2010

danrb said:

Guys. Take a look at all the BSODS in my first post. Many different causes. Suggest hardware. I already tried removing Macafee and things still crashed.

If it is hardware; there is not a lot we can suggest you do apart from swap parts out until it works.

As that is a costly exercise we try to run through all the software possibilities, no matter how far-fetched they seem, first.

Regards,
Reventon

danrb · 12 Jun 2010

Yes I did remove MacAfee as Sparrow suggest and still got a BSOD. I have two similar boxes and swaped out all components, but the HD and PSU. Today I'll try the HDs and see what happens.

What is MSE?

Dan

Jonathan_King · 12 Jun 2010

MSE- Microsoft Security Essentials. Here is a link: http://www.microsoft.com/security_essentials

Please upload any new dmps after you removed McAfee.

danrb · 12 Jun 2010

Well thanks all for the help and advice. I just confirmed that the problem is hardware. I swapped the drives between my two windows 7 machines (OS and all) this morning. Just got a BSOD on the same box. The only components that I didn't swap out and try are the Motherboard and PSU. I'm RMAing the motherboard. This is the third MSI P55-65GD that I've had to send back.

Thanks again,

Dan