Random BSOD (and SSD issue), dm log files included

Good evening, I have attached the latest info for my last BSOD to make it a bit easier as well as the .zip for the other BSOD I have had. I am at a loss and really not sure what the issue is. They appear random in nature, either I am just surfing the net or I am playing a game (considering I really only do those 2 things I would consider them random since it happens no matter what I am doing). I'm running a Prime95 test as we speak and for the last couple of hours and it has been stable. Chkdisk comes back fine. Memtest comes back fine as well. These BSOD have been happening for months.. I'm just now fed up with them and ready to throw money at my machine so before I do that I would like to make sure I'm throwing money at the correct hardware. All of my drivers are up to date that I am aware of.

Another major issue that I am also having is when I BSOD (except for the one that I have attached info for, this issue did not happen) the SSD will disappear from my BIOS and the only way I can get it back is if I unplug it, reboot my machine with it still unplugged, turn it off once the boot fails (because there is no OS on my second HD) then plug it back in and it will show up fine in the BIOS and boot up fine. This also happens occasionally when I shut my computer down for the night and go to turn it on the next day the SSD will disappear and I will have to do my routine that I stated above for it to boot properly. Also my mouse and keyboard will randomly stop working and I will hear the sound when you unplug / plug in a new USB device, they will stop working for a few seconds up to maybe 15-20 then it will make the sound like I plugged in a new USB device and they will work again. I've tried different plugs.

Keep in mind with the .zip (no clue if it will show current temps) that I am running a prime95 as I type this so the temps will be high. They usually hover around 40C idle.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF9600025C9ED
BCP3: FFFFF88008FBC110
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\022815-70715-01.dmp
C:\Users\Tanner\AppData\Local\Temp\WER-77579-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Code:

WARNING: Whitespace at end of path element

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols

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 Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element

************* 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;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03050000 PsLoadedModuleList = 0xfffff800`0328de50
Debug session time: Sat Mar  7 22:03:22.298 2015 (UTC - 5:00)
System Uptime: 0 days 5:44:04.157
Loading Kernel Symbols
...............................................................
................................................................
........Page 394b99 not present in the dump file. Type ".hh dbgerr004" for details
.....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdf018).  Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000124283, fffff88008b87030, 0}

Page 3a9c12 not present in the dump file. Type ".hh dbgerr004" for details
Page 3f7d3c not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )

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: fffff96000124283, Address of the instruction which caused the bugcheck
Arg3: fffff88008b87030, 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: 
win32k!HmgLockEx+a3
fffff960`00124283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

CONTEXT:  fffff88008b87030 -- (.cxr 0xfffff88008b87030;r)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800d252b60
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000124283 rsp=fffff88008b87a00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88008b87a68 r12=00000000039eca00 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`00124283 0fb7430c        movzx   eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Last set context:
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800d252b60
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000124283 rsp=fffff88008b87a00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88008b87a68 r12=00000000039eca00 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!HmgLockEx+0xa3:
fffff960`00124283 0fb7430c        movzx   eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff960002dc6b0 to fffff96000124283

STACK_TEXT:  
fffff880`08b87a00 fffff960`002dc6b0 : fffff900`c2b4f510 00000000`00000001 00000000`02120ec2 fffff900`c1ea7010 : win32k!HmgLockEx+0xa3
fffff880`08b87a70 fffff960`002dbbae : fffff900`c2b4f510 00000000`00000000 00000ec2`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`08b87aa0 fffff960`002dcab3 : 00000000`00000000 00000000`02120ec2 fffff900`c2b4f510 00000000`039eca00 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`08b87ae0 fffff960`002395ff : 00000000`00000000 fffff900`c0109010 fffff900`c2b4f510 00000000`00000000 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`08b87b20 fffff960`0025a908 : 00000800`00000001 00000000`00000001 fffff880`08b87c60 fffff960`0025a760 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`08b87b60 fffff800`030bf953 : fffffa80`0d252b60 00000000`0391f8b0 000007fe`f553d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`08b87be0 000007fe`fe094efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0391f308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe094efa


FOLLOWUP_IP: 
win32k!HmgLockEx+a3
fffff960`00124283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!HmgLockEx+a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

IMAGE_VERSION:  6.1.7600.16385

STACK_COMMAND:  .cxr 0xfffff88008b87030 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_win32k!hmglockex+a3

FAILURE_ID_HASH:  {8f81bb6a-de67-bc4d-99db-3f117a68551c}

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

Thanks for the response. Windows shows 3 important updates, 1 being a Service Pack from 2/15/15. I will install those. I typically never bother with the "optional" ones of which there are maybe 15. Your wording of "a lot" makes me believe that I am missing something...

Yes my SSD is the latest firmware of 2.25.

What would my next step be to identify why I am getting those BSOD?

Thanks again for your reply.

Update:

After I restarted my computer for the 3 important updates it said 2 of the 3 failed for what ever reason. I clicked the Windows Update again to install updates and this time the list populated with 127 important updates... so I am installing those as well. Strange.

Any other info on the BSOD or SSD issues would be great. I have researched the SSD issue many times and basically concluded that because it is a first generation vertex 3 they have issues and a lot of people are complaining of the same thing I am encountering. The firmware was supposed to fix it but obviously for me it hasn't. I'm no good at reading dump files so unless there is more info there I suspect some of that money I plan to throw at my computer will be going towards a new SSD. Also I suspect my video card is giving me some issues as in the event viewer there are ati (atillk64,atidgllk) errors that I have seen for probably a year now even with different driver updates. Strangely enough I have never seen it before but there was a punkbuster and apple mobile device error from today as well. Unrelated, probably.

Again hopefully something about that will be in the dump files. Thanks guys.