Windows 8.1 Keeps crashing! Blue screens and I don't know why.

Question

My computer is crashing randomly. Happens once every few days or so. It started happening when I installed a new fan and heatsink. My cpu never goes over 50 C now so I don't know why it is crashing. Here is the dump file. Please help me :/
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff803`7a47e000 PsLoadedModuleList = 0xfffff803`7a754370
Debug session time: Tue Nov 25 22:05:18.738 2014 (UTC - 5:00)
System Uptime: 2 days 9:06:56.454
Loading Kernel Symbols
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7ffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
*                        Bugcheck Analysis                                   
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8037a52cba4, ffffd000220ab340, 0}
Probably caused by : win32k.sys ( win32k!SEMOBJ::vUnlock+2c )
Followup: MachineOwner
4: 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: fffff8037a52cba4, Address of the instruction which caused the bugcheck
Arg3: ffffd000220ab340, 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!KxWaitForLockOwnerShipWithIrql+14
fffff803`7a52cba4 48890a          mov     qword ptr [rdx],rcx
CONTEXT:  ffffd000220ab340 -- (.cxr 0xffffd000220ab340;r)
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000220abdf0
rdx=8848800000000000 rsi=0000000000000000 rdi=ffffd000220abdf0
rip=fffff8037a52cba4 rsp=ffffd000220abd70 rbp=ffffd000220abea0
 r8=ffffd000220abef0  r9=ffffe000da69ddb0 r10=ffffd000220abf80
r11=fffff90145b03ce0 r12=fffff90140ad53f8 r13=fffff90140a00830
r14=0000000000000000 r15=ffffe000d889d880
iopl=0         nv up di pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff803`7a52cba4 48890a          mov     qword ptr [rdx],rcx ds:002b:88488000`00000000=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd000220abdf0
rdx=8848800000000000 rsi=0000000000000000 rdi=ffffd000220abdf0
rip=fffff8037a52cba4 rsp=ffffd000220abd70 rbp=ffffd000220abea0
 r8=ffffd000220abef0  r9=ffffe000da69ddb0 r10=ffffd000220abf80
r11=fffff90145b03ce0 r12=fffff90140ad53f8 r13=fffff90140a00830
r14=0000000000000000 r15=ffffe000d889d880
iopl=0         nv up di pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010046
nt!KxWaitForLockOwnerShipWithIrql+0x14:
fffff803`7a52cba4 48890a          mov     qword ptr [rdx],rcx ds:002b:88488000`00000000=????????????????
Resetting default scope
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  AI Suite II.ex
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff8037a4d9f8c to fffff8037a52cba4
STACK_TEXT:  
ffffd000`220abd70 fffff803`7a4d9f8c : ffffe000`da69ddb0 00000000`0000001e 00000000`00000000 ffffe000`db793c30 : nt!KxWaitForLockOwnerShipWithIrql+0x14
ffffd000`220abda0 fffff803`7a4d93c2 : 00000000`00000000 fffff960`002172ec ffffd000`220ac002 fffff901`44ffe620 : nt!ExpReleaseResourceForThreadLite+0x64c
ffffd000`220abee0 fffff960`001da2cc : 00000000`00000000 fffff960`001a7ef2 0000207f`e204207f 00000000`00000001 : nt!ExReleaseResourceAndLeaveCriticalRegion+0x12
ffffd000`220abf10 fffff960`001d51a3 : fffff901`451e4ac0 ffffd000`220abfa0 00000000`00000000 fffff901`40ad53f8 : win32k!SEMOBJ::vUnlock+0x2c
ffffd000`220abf50 fffff960`001e49ad : 00000000`0000163c fffff901`44ffe620 00000000`00000000 ffffe000`da69ddb0 : win32k!GreSelectVisRgnInternal+0x173
ffffd000`220abfd0 fffff960`001ac21b : ffffffff`e204207f fffff901`00000d3a 00000000`00000001 ffffe000`da69ddb0 : win32k!ResetOrg+0x50d
ffffd000`220ac100 fffff960`001e5a5d : ffffffff`e204207f fffff901`452e23e0 ffffd000`220acb00 ffff6b78`f79a9a37 : win32k!UserSetDCVisRgn+0x17b
ffffd000`220ac140 fffff960`001ed3a4 : fffff901`40a58990 00000000`00000000 fffff901`40a58990 00000000`02000705 : win32k!zzzLockDisplayAreaAndInvalidateDCCache+0x14d
ffffd000`220ac1a0 fffff960`003149cf : ffffe000`db7b2ba0 fffff901`428f7a80 00000000`00000000 fffff901`40b00ff0 : win32k!xxxCreateWindowEx+0x1824
ffffd000`220ac4b0 fffff960`001ed82a : fffff901`428f7d28 00000000`00000000 00000000`00000000 ffffe000`db7b2ba0 : win32k!xxxCreateDefaultImeWindow+0x19b
ffffd000`220ac5b0 fffff960`001d6ab5 : 00000000`00000000 00000000`00000000 e000d889`78747355 fffff803`7a4d7bc8 : win32k!xxxCreateWindowEx+0x1caa
ffffd000`220ac8c0 fffff803`7a5d89b3 : 00000000`00000000 ffffd000`220ac940 ffffd000`220ac958 ffffd000`220ac968 : win32k!NtUserCreateWindowEx+0x4d2
ffffd000`220aca10 00000000`777f611a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0abbe758 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777f611a
FOLLOWUP_IP:
win32k!SEMOBJ::vUnlock+2c
fffff960`001da2cc ff158e023100    call    qword ptr [win32k!_imp_PsLeavePriorityRegion (fffff960`004ea560)]
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  win32k!SEMOBJ::vUnlock+2c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: win32k
IMAGE_NAME:  win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  54335e2a
IMAGE_VERSION:  6.3.9600.17393
STACK_COMMAND:  .cxr 0xffffd000220ab340 ; kb
BUCKET_ID_FUNC_OFFSET:  2c
FAILURE_BUCKET_ID:  0x3B_win32k!SEMOBJ::vUnlock
BUCKET_ID:  0x3B_win32k!SEMOBJ::vUnlock
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x3b_win32k!semobj::vunlock
FAILURE_ID_HASH:  {ec837e9a-fa14-dd77-d99c-f14b9fe89bf2}
Followup: MachineOwner

Answer 1

Hi,
In order to assist you, we will need the .DMP files to analyze what exactly occurred at the time of the crash, etc.
If you don't know where .DMP files are located, here's how to get to them:
1. Navigate to the %systemroot%\Minidump folder.
-- %systemroot% is the environment variable for your Windows directory. For example, C:\Windows.
2. Copy any and all .DMP files in the Minidump folder to your Desktop, create a new folder on the Desktop to put these .DMP files in, and then zip the folder. You can then either use a 3rd party tool such as 7-Zip/Winrar, or you can use Windows'
default method of zipping folders.
Compress and uncompress files (zip files).
Please note that any "cleaner" programs such as TuneUpUtilities, CCleaner, etc, by default will delete .DMP files upon use. With this said, if you've run such software, and your Minidump folder is empty, you will need
to allow the system to crash once again to generate a crash dump.
3. Upload the .ZIP containing the .DMP files to Onedrive or a hosting site of your choice and paste in your reply.
Preferred sites: Onedrive, Mediafire, Dropbox, etc. Nothing with wait-timers, download managers, etc.
4 (optional): The type of .DMP files located in the Minidump folder are known as Small Memory Dumps. In %systemroot% there will be what is known as a Kernel Memory Dump (if your system is set to generate). It is labeled MEMORY.DMP. The difference
between Small Memory Dumps and Kernel Memory Dumps in the simplest definition is a Kernel Memory Dump contains
much more information at the time of the crash, therefore allowing further debugging of your issue. If your upload speed permits it, and you aren't going against any strict bandwidth and/or usage caps, etc, the Kernel Memory Dump is
the best choice. Do note that Kernel Memory Dumps are much larger
in size due to containing much more info, which is why I mentioned upload speed, etc.
If you are going to use Onedrive but don't know how to upload to it, please visit the following:
Upload photos and files to Onedrive.
After doing that, to learn how to share the link to the file if you are unaware, please visit the following link -
Share files and folders and change permissions and view 'Get a link'.
If your computer is not generating .DMP files, please do the following:
1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for
all drives'.
3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the
system log'.
Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.
4. Double check that the WERS is ENABLED:
Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than
Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.
If you cannot get into normal mode to do any of this, please do this via Safe Mode.
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama