BSOD on XP Pro SP3 0x0000000A IRQL_NOT_LESS_OR_EQUAL

[dwynne]

A Dell Latitude D620 running XP Pro with all the latest patches started getting stop 0x0a BSOD errors about a couple of weeks back. Does not fail every day just from time to time. Checkdsk, memory test, virus / malware scans show nothing wrong. Using the 4th parameter from the crash 0x804F11E1 and pstat it looks like the problem is in ntkrnlpa.dll. The other params at crash were 0x00000008, 0x00000002, and 0x00000001.

Attached are some recent DMP files, can someone look at them and help me figure out the problem?

Thanks!

 

[Route44]

Four of five minidump files cite the McAfee driver mfetdik.sys as the cause of your issues. We've seen a number of problems over the years with McAfee.

Try updating to the latest version.

You might want to look at this link: http://service.mcafee.com/FAQDocument.aspx?lc=1033&id=TS100507

 

[dwynne]

Thanks for the quick reply. That laptop was runing McAfee Enterprise 8.7i with all the latest patches and updates. I went ahead and move it to 8.8 Enterprise which does not have a system file called mfetdik.sys on it. We should know in a few days if that fixed it or not.

What do you use the read the DMP files and is it available to the public?

Thanks again!
Dennis

 

[Route44]

Yes, please keep us updated. And, yes, the tool is quite free to the public to read minidump files. It is called Windows Debugger. What takes a lot of time are the Symbol Packages that come with it that you must download for 2000, XP, Vista, and 7 and in all their flavors.

 

[dwynne]

Yes, please keep us updated. And, yes, the tool is quite free to the public to read minidump files. It is called Windows Debugger. What takes a lot of time are the Symbol Packages that come with it that you must download for 2000, XP, Vista, and 7 and in all their flavors.

We can mark it closed, no more BSOD in nearly a week of running the newe McAfee.

I got the symbols and WD program installed and ran a couple of the dmp files through, it found:

SYMBOL_NAME: mfetdik+6408

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: mfetdik

IMAGE_NAME: mfetdik.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b2ab61c

FAILURE_BUCKET_ID: 0xA_mfetdik+6408

BUCKET_ID: 0xA_mfetdik+6408

as you said it would. So next time I can try to analyze the dmp file myself before I post it

Thanks again!