Cause of BSOD X3B System_Service_Exception?

I was doing some pretty serious multitasking when I received the above mentioned BSOD, and I'm curious what the cause could be.

From what I'm reading ("0x0000003b" Stop error when the memory usage of memory-mapped file is high in Windows 7 or Windows Server 2008 R2), it sounds like it was due to very high RAM usage, but that is really just an educated guess and I'd definitely appreciate other opinions.

What Happened: I was web browsing with Comodo Icedragon (a Firefox variant) within a sandbox, downloading a torrent into the sandbox, and had a word doc open. RAM useage was 98%, CPU peak useage ~30% (The browser and antivirus can be system hogs).

The browser page went to black, the screen flashed, and several messages popped up. 1 was detailing over a dozen errors Sandboxie encountered. The other mentioned something about NVBackend not responding, and an issue with nvapi.dll (sp?) within Windows. Thinking it was BS about an app hang, I payed little attention and closed the window. I then noticed that Windows had switched from aero to basic. Realtemp then popped up. It was the wrong size (DPI), and told me the CPU was at 130F. Then the PC got the BSOD.

BSOD Details (from Bluescreenview):

SYSTEM_SERVICE_EXCEPTION 0x0000003b
Parameter 1 00000000`c0000044
Parameter 2 fffff800`02eae7fc
Parameter 3 fffff880`09a8f150
Parameter 4 00000000`00000000
Caused by Driver ntoskrnl.exe
Caused by Address ntoskrnl.exe+75bc0

Other Details: A fresh install was done recently (~2 weeks ago) after a total wipe of the HDD via write zeros. This is the first BSOD on the new installation.

The OS is up to date, as is the antivirus (Comodo) and the GPU. Other drivers are not up to date, as I cannot find any updates on Intel's site, though IOBit Driver Booster swears there are quite a few available. Realtek and LAN/ethernet drivers are not updated; they couldn't be bothered to create a list of changes in the new driver, so I was unconvinced there would be any benefit.

The PC would seem to be virus free. I ran a full scan with Comodo, Malwarebytes, TDSS Killer, Spybot, and Superantispyware.

The system is overclocked but appears stable. RAM is at XMP (I have overclocked it in the past on a previous OS install, and found no benefit). No RAM errors found when running Memtest 12hours, Aida, and P95. CPU is at 4.5ghz and passes Aida/P95/OCCT stress tests. GPU passed Heaven, MetroLL bench, 3DMark, Aida, OCCT, EVGA OCScanner, and gaming (been playing Saints Row IV and Rage without issue). Specs should be in my profile, but I can post them if it is helpful.

Temps are pretty good. ~80F idle CPU, ~90F GPU. 160F peak load temperatures for both when gaming. HDD temp never exceeds 95F. VRMS/MOBO/other temps seem normal.

Probably unrelated, but I moved the location of Sandboxie's Default sandbox from partition C to A about an hour before the BSOD.

Any opinions would be greatly appreciated. Thank you for your time.

PS: The attached file was generated from the SF Diagnostic tool.

Hi SenileAnimal.

Apparently the BSOD is caused by COMODO Internet Security Sandbox Driver,
c:\windows\system32\drivers\cmdguard.sys

Code:

fffff880`09a8e8d8  fffff880`056a39f6Unable to load image \SystemRoot\system32\DRIVERS\cmdguard.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cmdguard.sys
*** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
 cmdguard+0x109f6

Better you uninstall it.

Thank you so much for the reply.

Later last night, I replicated the same environment in which the system crashed, and the same BSOD occurred. I've attached the new minidumps etc from the SF Diag. Tool, if you or anyone else would be so kind as to have a look at it.

I wonder if Sandboxie is not playing nice with Comodo since I moved the sandbox location? That is the only significant change I've made to the PC in about a week. I'm going to try reverting it back to the original location, on a hunch, but this is definitely making me think of going back to Avast.

Sorry for the double post.

I looked into how to debug, downloaded Windbg and looked over the dumps with it, and both dumps suggest sandboxie as at least a partial cause of the issue, as far as I can tell.

Do you mind me asking where you found information pointing to cmdguard.sys? I don't doubt what you say is legit; just want to learn and I'm perplexed why I can't find that information anywhere.

UPDATE: I ran memtest for ~12 hours again with no issue. I moved sandboxie's sandbox back to drive C, but afterwards, the system locked up immediately with a custom P95 stress test with 6gb of ram (displayed as 99% usage), however that only happened once. Repeated tests with the a sandboxed browser both open and closed have caused no crashes today. Note that I have done similar, high stress P95 tests repeatedly in the past as well with no issue.

It seems extremely unlikely that this is an overclock issue, but I'm going to revert the CPU to stock to be certain.

Tutorials may be there after is issue is over :)

Memtest or prime95 etc were not suggested.

If you dont take the suggestions and do the random stuff, then we will be at a state of stagnancy.