BSOD IRQL_NOT_LESS_OR_EQUAL while playing SW:TOR and idling

Alright, just played a game of SW:TOR and after 3 minutes into a Warzone, BSOD happens and it's a system service exception BSOD.

I hope this minidump helps.

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\XplicitMind\010820113\Windows_NT6_BSOD_jcgriff2\010812-17050-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a49000 PsLoadedModuleList = 0xfffff800`02c8e670
Debug session time: Sun Jan  8 21:15:18.983 2012 (UTC - 7:00)
System Uptime: 0 days 0:29:14.170
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880014027a4, fffff880083eee10, 0}

Unable to load image MpFilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for MpFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for MpFilter.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff880014027a4, Address of the instruction which caused the bugcheck
Arg3: fffff880083eee10, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
MpFilter+27a4
fffff880`014027a4 f00fc1417c      lock xadd dword ptr [rcx+7Ch],eax

CONTEXT:  fffff880083eee10 -- (.cxr 0xfffff880083eee10)
rax=00000000ffffffff rbx=fffffa8006bed2a0 rcx=0000000000100000
rdx=fffff880083ef868 rsi=fffff880083ef868 rdi=0000000000000000
rip=fffff880014027a4 rsp=fffff880083ef7f0 rbp=fffffa8004ccf730
 r8=fffffa8006bed2a0  r9=0000000000000000 r10=fffffa8005819c20
r11=fffffa8004ccf818 r12=fffff98017a88c10 r13=fffffa8004ccf600
r14=fffff88001119a00 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
MpFilter+0x27a4:
fffff880`014027a4 f00fc1417c      lock xadd dword ptr [rcx+7Ch],eax ds:002b:00000000`0010007c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  CamRecorder.ex

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 00000001000f24a6 to fffff880014027a4

STACK_TEXT:  
fffff880`083ef7f0 00000001`000f24a6 : fffff8a0`02d6ac70 fffff980`17a88c10 fffffa80`04ccf680 fffffa80`04ccf680 : MpFilter+0x27a4
fffff880`083ef7f8 fffff8a0`02d6ac70 : fffff980`17a88c10 fffffa80`04ccf680 fffffa80`04ccf680 fffff880`0110a288 : 0x1`000f24a6
fffff880`083ef800 fffff980`17a88c10 : fffffa80`04ccf680 fffffa80`04ccf680 fffff880`0110a288 fffff980`17a88fb0 : 0xfffff8a0`02d6ac70
fffff880`083ef808 fffffa80`04ccf680 : fffffa80`04ccf680 fffff880`0110a288 fffff980`17a88fb0 fffffa80`04ccf838 : 0xfffff980`17a88c10
fffff880`083ef810 fffffa80`04ccf680 : fffff880`0110a288 fffff980`17a88fb0 fffffa80`04ccf838 00000000`00000000 : 0xfffffa80`04ccf680
fffff880`083ef818 fffff880`0110a288 : fffff980`17a88fb0 fffffa80`04ccf838 00000000`00000000 fffffa80`04ccf680 : 0xfffffa80`04ccf680
fffff880`083ef820 fffff880`01108d1b : fffff980`17a88fb0 fffffa80`04ccf7d0 fffffa80`04ccf838 fffffa80`05819c20 : fltmgr!FltpPerformPostCallbacks+0x368
fffff880`083ef8f0 fffff880`011076df : fffffa80`05810b60 fffffa80`05810b60 fffffa80`05810b00 fffff980`17a88c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x39b
fffff880`083ef980 fffff800`02f6bc16 : fffff980`17a88c10 00000000`00000002 fffff980`17a88c10 00000000`00000000 : fltmgr!FltpDispatch+0xcf
fffff880`083ef9e0 fffff800`02dce21b : 00000000`00000001 fffffa80`07c40400 00000000`00000001 fffffa80`04b72280 : nt!IovCallDriver+0x566
fffff880`083efa40 fffff800`02dd8c83 : fffff980`17a88ff8 fffff880`083efca0 fffffa80`07c40400 fffffa80`07c40474 : nt!IopSynchronousServiceTail+0xfb
fffff880`083efab0 fffff800`02ac4ed3 : 00000000`74662401 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x7e2
fffff880`083efbb0 00000000`74662e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`068febd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74662e09


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002ac53fa - nt!KiExceptionDispatch+1fa
	[ 30:20 ]
1 error : !nt (fffff80002ac53fa)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

STACK_COMMAND:  .cxr 0xfffff880083eee10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Probably caused by : memory_corruption

BUGCHECK_STR: 0x3B

PROCESS_NAME: CamRecorder.ex


My guess is this is webcam related... Try disabling your webcam or any software for it to test.

writhziden said:

Probably caused by : memory_corruption

BUGCHECK_STR: 0x3B

PROCESS_NAME: CamRecorder.ex


My guess is this is webcam related... Try disabling your webcam or any software for it to test.

I just did some research and found out that CamRecorder.ex is from Camtasia software. I'm guessing I should uninstall this program?

XplicitMind said:

writhziden said:

Probably caused by : memory_corruption

BUGCHECK_STR: 0x3B

PROCESS_NAME: CamRecorder.ex


My guess is this is webcam related... Try disabling your webcam or any software for it to test.

I just did some research and found out that CamRecorder.ex is from Camtasia software. I'm guessing I should uninstall this program?

Probably a good idea since it caused a blue screen error. :)

Heres the thing: I JUST installed this program after the 7 minidumps I uploaded. So maybe along with SW:TOR, having this program on probably caused the BSOD so it may be connected to my webcam as well? I hope that make sense.

Lol as soon as I finished typing my earlier post, it BSOD saying memory management. This is getting frustrating. Personally I think it's my RAM, despite the fact that it said that it passed.

Went to double check the RAM overnight and came out with 8 Passes. Even with the passes and no error, can it still be the RAM? I feel like I'm out of ideas. Most of the time, the BSOD usually occurs during gameplay and sometimes idling.

I still see nothing to indicate that these were due to Verifier running. Can you post a screenshot of the drivers being verified following Screenshots and Files - Upload and Post in Seven Forums

I also note something that may be part of your problem...

Faulting application name: Regutility.exe, version: 4.1.1.8, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17651, time stamp: 0x4e211319
Exception code: 0x0eedfade
Fault offset: 0x0000b9bc
Faulting process id: 0xafc
Faulting application start time: 0x01ccce8a94dac98e
Faulting application path: C:\Program Files (x86)\RegUtility\Regutility.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: d3c64cd2-3a7d-11e1-98c7-485b39c633e8

Registry cleaning tools are not needed in Windows 7. Windows 7 takes care of its registry much better than its predecessors, and any registry cleaning tools can cause more issues than they fix.

Yes I've already uninstalled that and everything else that I felt like that was unneeded.

Here is the screenshot of my verifier. These were all the drivers I could choose from that were not from Microsoft.