IRQL_NOT_LESS_OR_EQUAL, error 0x0000000a

[derekimo]

Are you trying to open the dump from that folder?

Copy it to the desktop and try again.

When you ran the commands to associate windbg with .dmp files did you get the confirmation in the cmd box?

That link should help.

 

[kevvyb]

Done it thanks. Hopefully won't need to use it again though!

 

[kevvyb]

IRQL_NOT_LESS_OR_EQUAL, error 0x0000000a, Malware Bytes driver

Have now uninstalled Malware Bytes Beta and advised becuase BSOD happened again last night. Windbg pointing to same cause.

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051514-19046-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e5b890
Debug session time: Thu May 15 03:06:47.871 2014 (UTC + 1:00)
System Uptime: 0 days 4:04:22.777
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
....................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff80002ca2a55}

Unable to load image \??\C:\Windows\system32\drivers\MBAMSwissArmy.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MBAMSwissArmy.sys
*** ERROR: Module load completed but symbols could not be loaded for MBAMSwissArmy.sys
Probably caused by : MBAMSwissArmy.sys ( MBAMSwissArmy+1d30f )

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