BSOD with MxMkm64.sys in Nonpaged Area

Uninstall McAfee Using McAfee Removal Tool. Uninstall any Websense (I dont know what is it) product, too. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

I am unware about Maxtor graphics, too; but you need to search for any possible update to it. Welcome to Matrox
Is it a graphics card, BTW? It seems that you have two of them.

And Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know for any further BSOD after doing those.
_____________________________________________

Code:

BugCheck 3B, {c0000005, fffff88004da2bc0, fffff8800800e780, 0}

Probably caused by : cwNep.sys ( cwNep+abc0 )

Followup: MachineOwner
---------

Code:

BugCheck 50, {ffffffff80c0ebac, 1, fffff88004a49d83, 5}

*** WARNING: Unable to verify timestamp for MxMKm64.sys
*** ERROR: Module load completed but symbols could not be loaded for MxMKm64.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys

Could not read faulting driver name
Probably caused by : MxMKm64.sys ( MxMKm64+1acd83 )

Followup: MachineOwner
---------

Ben3 said:

thanks for the reply. We have 5 of the systems in question with same apps and configurations and only two with BSOD. We are not able to remove McAfee, corporate standard, not allowed to use any other virus protection. The Matrox M9188 Graphics cards have had the drivers updated and the firmware updated. The Windows start up is optimal for the 5 systems configured for these users.
If you have other suggestions I would be glad to consider. Hopefully we can find a root cause.
Thanks

Go to your IT department.

Ben3 said:

Thanks and I am the IT department trying to find a cause for this problem.

The causes are disclosed above, which you cannot consider.