BSOD Seemingly At Random, error KMODE_EXCEPTION_NOT_HANDLED

k4nc3r mate, its really very nice to see that your issue is cured now. We dont have the donation option, as our site is very grown up nowadays; but its your goodness that you wanted to do it :) Thanks for it :)

For any further issue, let us know :)

Some Ntfs corruptions are noticed ... but not showing any details.

Use driver verifier for one more time?

As far as I can say, if you format the HDD and start afresh, it will be the best option.

If you plan to do it, a nice guide is there: Clean Reinstall - Factory OEM Windows 7

It will give you the perfect windows reinstall.

It is a stop 0x3B BSOD, which is sticky type of nature. Caused by drivers mainly, and as the BSOD is not showing any particular reason, I am suggesting you to go for a clean reinstall. If not, enable Driver Verifier to monitor the drivers and expect that it may show any cause of the BSODs. .
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_______________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800032a540e, fffff88002f419d0, 0}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+1ae )

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

0: 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: fffff800032a540e, Address of the instruction which caused the bugcheck
Arg3: fffff88002f419d0, 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: 
nt!MiUnlinkPageFromLockedList+1ae
fffff800`032a540e 410fb6491b      movzx   ecx,byte ptr [r9+1Bh]

CONTEXT:  fffff88002f419d0 -- (.cxr 0xfffff88002f419d0)
rax=0000000000000003 rbx=fffffa800160f9e0 rcx=01000000001d2d6e
rdx=0000000000000003 rsi=0000000000000003 rdi=fffff800034cfcf8
rip=fffff800032a540e rsp=fffff88002f423b0 rbp=0000000000000000
 r8=fffff88002f423e0  r9=2ffffa80057884a0 r10=fffffa80065d2320
r11=0000058000000000 r12=0000000000000000 r13=0000058000000000
r14=0000000000000001 r15=2aaaaaaaaaaaaaab
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!MiUnlinkPageFromLockedList+0x1ae:
fffff800`032a540e 410fb6491b      movzx   ecx,byte ptr [r9+1Bh] ds:002b:2ffffa80`057884bb=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800032a540e

STACK_TEXT:  
fffff880`02f423b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiUnlinkPageFromLockedList+0x1ae


FOLLOWUP_IP: 
nt!MiUnlinkPageFromLockedList+1ae
fffff800`032a540e 410fb6491b      movzx   ecx,byte ptr [r9+1Bh]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+1ae

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d9c6

STACK_COMMAND:  .cxr 0xfffff88002f419d0 ; kb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x3B_nt!MiUnlinkPageFromLockedList+1ae

BUCKET_ID:  X64_0x3B_nt!MiUnlinkPageFromLockedList+1ae

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

Please do follow the post #67. :)