Jake Emms
Member
- Joined
- Mar 26, 2016
- Location
- United Kingdom
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8000286643e, ffffd00025893a38, ffffd00025893240}
Probably caused by : atikmdag.sys ( atikmdag+c5243e )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {b500190637, ffffd00025ed83c8, ffffd00025ed7bd0, fffff800f411ee0c}
Probably caused by : memory_corruption
Followup: memory_corruption
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {b500190637, ffffd00025ed83c8, ffffd00025ed7bd0, fffff800f411ee0c}
Probably caused by : memory_corruption
Followup: memory_corruption
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D5, {ffffcf81a4e9cfa0, 0, fffff8006ecc01db, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+bb1db )
Followup: MachineOwner
RefCause
The Driver Verifier Special Pool option has caught the driver accessing memory which was earlier freed.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, 0, ffffd0004018a0a0, 0}
Probably caused by : win32k.sys ( win32k!DirectComposition::CApplicationChannel::EmitUpdateCommands+42 )
Followup: MachineOwner
Cause
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.