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
Yup that sounds right.Yea that's what I did at first and it worked out. I don't really know if it actually updated the driver properly. I had to restart and what not but it was basically an instant update.