BSOD on start up with different errors each time

So I have an iMac (boo hiss) that is around 4 months old. I have been getting BSODs on start up for a couple of months now in Windows 8.1 originally. I figured it was a bad driver that isn't compatible with 8.1 so I downgraded to 7. It worked fine for the first few reboots. I fear that a driver may be the cause, but apple supply the drivers for the motherboard etc. I have only installed one driver on top of the basics installed by the apple wizard which was for a razor naga mouse. I am getting various errors on the BSODs including kernel panics, NTFS errors, random .sys file errors.

I had noticed one of the sys files was indeed related to my razor mouse "rzfilter.sys" so I have downgraded from razor synapse 2.0 which is known to cause problems, and installed an older more lightweight driver for the mouse.

I have tried booting with nothing but my keyboard connected which doesn't have a driver and it still BSODs.

I fear it may be a memory problem too and haven't ran memtest yet as I'm busy with work. I have 32gb of memory in the system that I installed myself, although that was from day 1 and problems didn't start occurring till around a month after I had the system.

I am not sure how the memory.dmp works but from an iOS developers point of view you'd need my symbols to desymbolocate the crash log? I have installed the windebug program from the windows sdk package and opened the memory.dmp file. Here's what I get:

Code:

 
Microsoft (R) Windows Debugger Version 6.3.9600.17029 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
 
 
************* 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 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`02c59000 PsLoadedModuleList = 0xfffff800`02e9ee90
Debug session time: Sat Jul 12 10:34:22.314 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:16.110
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 24, {c08a5, 0, 0, 0}
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
Followup: MachineOwner
---------
 
16.3: kd:x86> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
 
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
 
Debugging Details:
------------------
 
 
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
 
BUGCHECK_STR: 0x24
 
CURRENT_IRQL: 0
 
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
 
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000
 
STACK_TEXT: 
00000000 00000000 00000000 00000000 00000000 0x0
 
 
STACK_COMMAND: kb
 
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
 
FOLLOWUP_NAME: MachineOwner
 
MODULE_NAME: Unknown_Module
 
IMAGE_NAME: Unknown_Image
 
DEBUG_FLR_IMAGE_TIMESTAMP: 0
 
IMAGE_VERSION: 
 
BUCKET_ID: INVALID_KERNEL_CONTEXT
 
FAILURE_BUCKET_ID: INVALID_KERNEL_CONTEXT
 
ANALYSIS_SOURCE: KM
 
FAILURE_ID_HASH_STRING: km:invalid_kernel_context
 
FAILURE_ID_HASH: {ef5f68ed-c19c-e34b-48ec-8a37cd6f3937}
 
Followup: MachineOwner
---------

I have also ran your exe file and attached the included logs.