Please help with minidump - Windows 7 64 bit

Question

Hi,
I recently reinstalled Windows 7 and since reinstalling, I've been having a problem with BSODs when running Freemake Video Converter which was working flawlessly before the reinstallation.  No hardware changes have been made, nor any BIOS changes.
I was getting various different BSOD messages and they seemed to point to Kaspersky 2013 so I uninstalled that, ran Kaspersky's uninstallation tool but still kept getting BSODs when running Freemake.
So I formatted and reinstalled Windows 7 64bit again and installed MSE instead of Kaspersky. 
I am still getting BSODs using Freemake though and it looks like a driver problem but that's as far as I can guess!
My system consists of an Intel 2600k, 16GB RAM, Ati HD5450 VGA, 250GB Samsung 840 Pro SSD, Asrock Z68Extreme7 motherboard, various SATA storage drives, Pioneer DB-206K Blu-ray writer.
Could someone please help?  I have installed Windows Debug and here is my latest minidump:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030414-9313-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c91e90
Debug session time: Tue Mar  4 02:26:40.038 2014 (UTC + 0:00)
System Uptime: 0 days 0:09:52.787
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                   
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002ae88a4, fffff880072ffd00, 0}
Probably caused by : Unknown_Image ( nt!KeReleaseSemaphore+1e4 )
Followup: MachineOwner
1: 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: fffff80002ae88a4, Address of the instruction which caused the bugcheck
Arg3: fffff880072ffd00, 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!KeReleaseSemaphore+1e4
fffff800`02ae88a4 0fb6462b        movzx   eax,byte ptr [rsi+2Bh]
CONTEXT:  fffff880072ffd00 -- (.cxr 0xfffff880072ffd00)
rax=0000000000000037 rbx=fffffa8010760580 rcx=fffffa8010760620
rdx=0000000000000000 rsi=0a1001c9ea0fd64d rdi=0000000000000000
rip=fffff80002ae88a4 rsp=fffff880073006e0 rbp=fffffa8010760688
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff8a00a3e3130 r12=0000000000000001 r13=fffff880009ec180
r14=fffff880009b3101 r15=fffffa8010760948
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
nt!KeReleaseSemaphore+0x1e4:
fffff800`02ae88a4 0fb6462b        movzx   eax,byte ptr [rsi+2Bh] ds:002b:0a1001c9`ea0fd678=??
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  FreemakeVC.exe
CURRENT_IRQL:  2
LAST_CONTROL_TRANSFER:  from fffff80002dd7d60 to fffff80002ae88a4
STACK_TEXT:  
fffff880`073006e0 fffff800`02dd7d60 : fffffa80`00000000 fffff8a0`00000001 00000000`00000000 fffff8a0`0a3e3000 : nt!KeReleaseSemaphore+0x1e4
fffff880`07300760 fffff800`02dd954e : 00000000`00000000 00000000`00000000 03030303`00000000 00000000`00000000 : nt!AlpcpCompleteDispatchMessage+0xa10
fffff880`073007f0 fffff800`02dd6e4f : 00000000`00010002 fffff8a0`024ae648 00000000`00000000 00000000`00000000 : nt!AlpcpDispatchNewMessage+0x24e
fffff880`07300850 fffff800`02da1d53 : 00000000`00000030 00000000`00000000 00000000`00000000 fffffa80`0f137900 : nt!AlpcpSendMessage+0x4ad
fffff880`07300950 fffff800`02da2465 : fffff880`00000000 00000000`051fe600 fffffa80`0f137900 00000000`00000000 : nt!PspExitThread+0x223
fffff880`07300a50 fffff800`02da2575 : fffffa80`0f137990 00000000`00000000 fffffa80`0f137990 00000000`7ef01000 : nt!PspTerminateThreadByPointer+0x4d
fffff880`07300aa0 fffff800`02acb8d3 : 00000000`00000000 fffff880`07300b60 00000000`7ef01000 00000000`00000000 : nt!NtTerminateThread+0x45
fffff880`07300ae0 00000000`76e2184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`051fe668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e2184a
FOLLOWUP_IP:
nt!KeReleaseSemaphore+1e4
fffff800`02ae88a4 0fb6462b        movzx   eax,byte ptr [rsi+2Bh]
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!KeReleaseSemaphore+1e4
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP:  0
STACK_COMMAND:  .cxr 0xfffff880072ffd00 ; kb
BUCKET_ID:  INVALID_KERNEL_CONTEXT
MODULE_NAME: Unknown_Module
Followup: MachineOwner

Answer 1

Lemental2
Both of these were inconclusive and were different error codes (BCC).  Though Freemake was the active process I think there is an underlying issue.  Please run driver verifier as instructed in this wiki.  It will give a much better chance
of "catching" the mis-behaving driver.
Please run this test to find which driver is causing the problem.  
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
Driver verifier (for complete directions see our wiki here)
Co-Authored by  JMH3143
Wanikiya and Dyami--Team Zigzag