verifier dmp file

could somebody analysis this BSOD dmp file. thxs




Windows Forum Admin
Staff member
Premium Supporter
Microsoft MVP
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck C9, {216, fffff880070b47e4, fffff980c3a76ab0, 0}

Probably caused by : ks.sys ( ks!CKsDevice::DispatchPnp+0 )

Followup: MachineOwner
please look in the start menu for command prompt, right click on it, choose properties and then run as admin. Type:
sfc /scannow
Press enter and await results.
The above dump points to ks.sys which relates to Kernel CSA Library so I just want to see what state your os is in.
Driver verifier has also caught a driver but I'll be damned if I can find it lol.. I'll consult with a friend and post back shortly. In the meantime:

asahxp64.sys Wed Mar 23 07:36:12 2011: ASMedia 106x SATA Host Controller Driver please update:

asmthub3.sys Wed Sep 14 08:36:19 2011:
asmtxhci.sys Wed Sep 14 08:36:09 2011: Asmedia USB3 drivers Later version found on motherboard support page:

athrx.sys Tue Feb 22 20:17:31 2011: Atheros network adapter driver

mv91cons.sys Tue Aug 09 03:25:00 2011: Marvell 91xx Confige Device Driver for 6G SATA Controller. Your actual Marvel SATA controller is the Marvell 88SE9128. The latest drivers for which can be found on this page here:

nvlddmkm.sys Wed Oct 23 07:21:50 2013: Nvidia gpu drivers. Please remove using this app as it will also remove anything left behind by previous drivers:

Please re-install latest driver release:

Run the Intel driver utility:

Please post any further dump files after updating the above. I'll now check with a buddy re the above.

All the drivers are up to date and I've setup verifier as requested, will report back when the next bsod happens.

All this might be to do with an external audio DAC, with its drivers.

Last edited:


Extraordinary Member
Microsoft MVP
If Driver Verifier has not yet BSOD'd your system, it likely did not find any violations in 3rd party drivers.

Let it run another 12 hours, then turn off - bring up Admin CMD screen and type

verifier /reset

Then re-boot.

Regards. . .


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.