imjustademo
Member
- Joined
- Apr 29, 2015
- Messages
- 149
- Thread Author
- #1
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {31, fffffa8006fc5d70, fffff880132d3000, fffff8a0053a229c}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+7171 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, 0, fffff8800335b5c8, fffff8800335ae20}
Probably caused by : CMUACWO.sys ( CMUACWO+4f224 )
Followup: MachineOwner
I'm unsure but if there isn't an update available you could try updating your chipset drivers as well as re-installing the device driver again in case it's become corrupted.The drivers for it are located at http://schiit.com/products/modi-2. Could it just be something with their drivers that causes it?