Windows 10: Random BSODs caused by cm11264.sys.

Hi, i recently started having issues with my computer crashing. I will provide the dump files. I've looked up what cm11264.sys was connected to and it was my pair of Sennheiser 363d. I have since then tried multiple driver versions, and now have switched to a different port. My last crash was at 9:00pm cst. 11/2/16 Can anyone help?Attachment 108725

:)

 

DPC WATCHDOG VIOLATION

BugCheck 133, {0, 501, 500, 0}

*** WARNING: Unable to verify timestamp for cm11264.sys

*** ERROR: Module load completed but symbols could not be loaded for cm11264.sys

Probably caused by : cm11264.sys ( cm11264+2923f )

Loaded symbol image file: cm11264.sys

Image path: \SystemRoot\system32\drivers\cm11264.sys

Image name: cm11264.sys

Browse all global symbols functions data

Timestamp: Wed Nov 28 21:52:13 2012 (50B6CDDD)

cm11264.sys : Driver Reference Table - cm11264.sys

Update your C-Media USB Audio Driver.

ALSO, uninstall USBPcap Sniffer Driver

fffff801`52c73bf8 fffff808`2d1d3e39*** WARNING: Unable to verify timestamp for USBPcap.sys

*** ERROR: Module load completed but symbols could not be loaded for USBPcap.sys

USBPcap+0x3e39

Run the Norton cleanup tool linked below to remove remnants.

Download and run the Norton Removal tool.

Uninstall and Reinstall Norton product using the Norton Remove and Reinstall tool

 

New PC: BSOD DPC_WATCHDOG_VIOLATION Battlefield 1 & Firefox Twitch

FAILURE_ID_HASH_STRING: km:0x133_dpc_nvlddmkm!unknown_function

ffffa280`0d25b618 fffff809`893474c4*** ERROR: Module load completed but symbols could not be loaded for
e2xw10x64.sys

e2xw10x64+0x74c4

Reinstall you NVidia Display and Killer network drivers from the link below.

Support For H170 GAMING M3.

Support For H170 GAMING M3 | Motherboard - The world leader in motherboard design | MSI USA

Update your C-Media USB Audio Driver.

ffffa280`0d25c508 fffff809`899369df*** ERROR: Module load completed but symbols could not be loaded for cm11264.sys

cm11264+0x2069d

fffff809`89730000 fffff809`89b6d000 cm11264 (no symbols)

Loaded symbol image file: cm11264.sys

Image path: \SystemRoot\system32\drivers\cm11264.sys

Image name: cm11264.sys

Browse all global symbols functions data

Timestamp: Wed Nov 28 21:52:13 2012 (50B6CDDD)

C-Media USB Audio Driver:
https://www.sysnative.com/drivers/driver.php?id=cm11264.sys

USB Audio,PCIe audio,USB audio ic,USB sound chip--C-Media Electronics, Inc.

Please update or uninstall, hppdbulkio.sys

Image path: \SystemRoot\system32\drivers\hppdbulkio.sys

Image name: hppdbulkio.sys

Browse all global symbols functions data

Timestamp: Tue Apr 29 12:00:07 2008 (48174607)

 

Hi sparten576,

Welcome to the 10forums and apologies for the delay.

Are you still in need of help?

 

yes i do, thanks. also the bluescreens will not create dumps anymore because my computer flashes the blue screen then restarts.

 

Please check MSI for BIOS updates.

 

i have updated the bios

 

Does the problem keep occuring?

 

I havent left the computer on long enough, but the problem seems to have subsided a lot. Ill leave it on overnight with driver verifier on.

 

i read that if the computer crashes during driver verifer, it will provide a more detailed crash. it was also point to the bad driver.

 

Neither doesn't have to be the case (IME) especially the driver part.

If driver verifier is unable to find any offensive driver but does crash the system then it is most likely a hardware problem.

 

sorry for such a long delay, I havent witnessed a crash until 5 minutes agoAttachment 110137 Same crash, same driver.

 

Hi sparten576,

Unfortunately I'm unable to analyze the last dump due to some issues that are out of my control. I need to wait for Microsoft to handle the problem, until then I have to assume that what is displayed (the same driver) is being blamed.

 

Hi, i recently updated my windows to build 14986 which helped narrow down the issues that im facing. Im now getting different driver failures. Mainly USBXHCI.SYS. I think something is wrong with my USB ports somehow.

 

I doubt it since you're now using a Windows Insider build. The build you're using is a build that has many issues and is only meant for those who understand the risk and don't mind reformatting the HDD to reinstall again when required.

Your drivers are more than likely not optimized for a beta version of Windows which is why you're getting different driver failures.

What troubleshooting steps have you tried since the last post?