BSOD while running MSE

Just received my first BSOD in a very very long time. Was just running an MSE scan and BSOD and reboot.

Attached is zip.

koolkat77 said:

Cause by Sound Blaster HDAudio driver

Maybe you should revert to an older driver version.

Sometimes drivers remain and do not get completely uninstalled.

 Driver Removal Process:

• Download Driver Sweeper to the desired location.
• Extract the files from the zip.
• Uninstall the driver Program & Features - Control Panel.
• Run Driver Sweeper, check the drivers you want to uninstall or clean registry leftovers of.

Link to full tutorial: Drivers - Clean Left over Files after Uninstalling

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\CHRIS-LAPTOP-Wed_11_19_2014_104311_91\111914-17035-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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 Personal
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`01c1f000 PsLoadedModuleList = 0xfffff800`01e62890
Debug session time: Wed Nov 19 22:38:50.871 2014 (UTC + 6:00)
System Uptime: 0 days 0:04:04.371
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880196d8927, fffff8801b889cc0, 0}

Probably caused by : cthda.sys ( cthda+16927 )

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

5: 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: fffff880196d8927, Address of the instruction which caused the bugcheck
Arg3: fffff8801b889cc0, 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: 
cthda+16927
fffff880`196d8927 488b8d90000000  mov     rcx,qword ptr [rbp+90h]

CONTEXT:  fffff8801b889cc0 -- (.cxr 0xfffff8801b889cc0)
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8801b88a6c0
rdx=0000000000000000 rsi=fffff8801b88a6c0 rdi=0000000000000001
rip=fffff880196d8927 rsp=fffff8801b88a6a0 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000063 r10=fffff880197c4b20
r11=fffff8801b88a820 r12=0000000000000000 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
cthda+0x16927:
fffff880`196d8927 488b8d90000000  mov     rcx,qword ptr [rbp+90h] ss:0018:00000000`00000090=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  CtHdaSvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880196d8927

STACK_TEXT:  
fffff880`1b88a6a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cthda+0x16927


FOLLOWUP_IP: 
cthda+16927
fffff880`196d8927 488b8d90000000  mov     rcx,qword ptr [rbp+90h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cthda+16927

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cthda

IMAGE_NAME:  cthda.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  542a1795

STACK_COMMAND:  .cxr 0xfffff8801b889cc0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_cthda+16927

BUCKET_ID:  X64_0x3B_cthda+16927

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

5: kd> lmvm cthda
start             end                 module name
fffff880`196c2000 fffff880`197c9000   cthda    T (no symbols)           
    Loaded symbol image file: cthda.sys
    Image path: \SystemRoot\system32\drivers\cthda.sys
    Image name: cthda.sys
    Timestamp:        Tue Sep 30 08:38:13 2014 (542A1795)
    CheckSum:         00111C00
    ImageSize:        00107000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Okay I will run this and report back.