IRQL_NOT_LESS_OR_EQUAL, error 0x0000000a

Now have beta installed. Will have eset installed for now. Will leave machine on overnight as before reinstall that was always giving me this blue screen in the morning.

Will post back on outcome.

Thanks for the help.

BTW can you tell me which diagnostic you found the driver error in?

You're welcome.

I found that in the .dmp file, the only .dmp file you uploaded.

Not sure if you are running any cleaning programs or disk cleanup but they will delete dump files.

No. Can I view that in BlueScreenViewer somewhere?

I use Windbg to see that, it looks like your output from Bluescreenview was pretty generic.

Here's the output from Windbg,

Code:

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


Loading Dump File [C:\Users\Derek\AppData\Local\Temp\Temp1_COSMOS-13_05_2014_202225_83.zip\051314-18703-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*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.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c0d000 PsLoadedModuleList = 0xfffff800`02e506d0
Debug session time: Tue May 13 11:09:30.750 2014 (UTC - 7:00)
System Uptime: 0 days 0:54:36.656
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, fffff80002c97a55}

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+1c330 )

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

can i load windbg without all the other developer bloat?

Yeah, just select that only,



Then there a process of cmds for associating .dmp files, then your symbol path as well.

See if this thread helps you out,

Crash Dump files: Associate with WINDBG

Found this, thanks

Configuring the "Debugging Tools"l