BSoD CMUSBDAC.sys Thread Exception Not Handled

Zirixo

Prominent
Mar 26, 2017
2
0
510
Hello. Over the past few months issues have been happening with my computer. It is a very odd issue. The issue is a Blue Screen of Death (BSoD). This issue happens while playing CS:GO (a video game), but I doubt that this is the cause of the issue. On occasion, whenever I unplug my Blue Snowball microphone on accident or even touch the microphone slightly (sometimes I will even stand up and the microphone moves a tiny bit), the computer gives me a BSoD. The error specifically tells me that the system "thread exception not handled". The driver causing this error was found to be cmusbdac.sys. According to the internet and when I checked the drivers on my computer, this is an audio driver. I downloaded a program called whocrashed to read the dump files, because I have no idea how to do that myself. After it analyzed these files, it came to a problem with that same driver and gave me the website of that company (which is a third party company, Cmedia). It also said that the driver was an audio usb driver, which would explain why the Blue Snowball microphone has problems, (it is plugged in via usb). If you want the full results of the analyzed dump file I would be happy to give it to you. I went to the website and looked in their downloads section and no driver matched the one that I had. I emailed the company in regards to that, but I need further help from here. Any suggestions will be appreciated and feel free to move this thread to another section etc. (I am new to this website).

Here is the analzyed dump file results for the most recent crash:

On Sat 3/25/2017 9:50:52 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\032517-28437-01.dmp
This was probably caused by the following module: cmusbdac.sys (CMUSBDAC+0x387047)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8068D107047, 0xFFFFC601167E50B8, 0xFFFFC601167E48E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\cmusbdac.sys
product: C-MEDIA CMUSBDAC Audio
company: C-MEDIA
description: C-MEDIA CMUSBDAC Audio Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cmusbdac.sys (C-MEDIA CMUSBDAC Audio Driver, C-MEDIA).
Google query: C-MEDIA SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Here are my specs (minus the ones that aren't important)
Windows 10
MSI 970 Gaming Motherboard
AMD FX8350 CPU (watercooled with Corsair h100i)
Ballistix 8gb ddr3 RAM
NVIDIA Geforce 650
(I am not entirely sure about the power supply, but can check if necessary)
 
Solution
the cmedia device is a OEM product, sometimes you can look at the name of the device, and google to find out which chipset it is using then go to the cmedia website and download the chipset driver. Or you might be able to remove the driver and use the default one from windows. (kind of depend on the driver date/ time stamp)
you might also find that changing the properties in device manager so the device can not be turned off might help. Old drivers just did not provide proper functions these calls to work.



Driver used a bad memory address. I would guess the device gets disconnected and and there is a driver bug.
I would update the bios, the motherboard usb 3 drivers, the cpu chipset drivers and the actual audio driver. Note the sound driver can have conflicts with your motherboard sound driver and your gpu sound driver. You might want to update them all and disable the ones you do not use.

You might also put the microphone on a usb 2 port and maybe disable any usb extensions in bios if you can not update the bios and usb drivers
https://www.cmedia.com.tw/support/download_center
 


Thank you! I will try these solutions and write u back with my results, as for that cmedia driver, it isn't available on their website.
 
the cmedia device is a OEM product, sometimes you can look at the name of the device, and google to find out which chipset it is using then go to the cmedia website and download the chipset driver. Or you might be able to remove the driver and use the default one from windows. (kind of depend on the driver date/ time stamp)
you might also find that changing the properties in device manager so the device can not be turned off might help. Old drivers just did not provide proper functions these calls to work.





 
Solution