Solved BSOD after suspension, error 0x0000007e on Atikmdag.sys

[Compvictor]

Hi, i think it's a driver problem.

 

[Gator]

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=Red]atikmdag.sys[/COLOR]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff880058f2160, fffff88008b77c68, fffff88008b774c0}

Probably caused by : atikmdag.sys ( atikmdag+cd160 )

Followup: MachineOwner
---------

Processing initial command '!analyze -v;r;kv;lmtn;lmtsmn;.bugcheck'
0: kd> !analyze -v;r;kv;lmtn;lmtsmn;.bugcheck
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/COLOR]
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880058f2160, The address that the exception occurred at
Arg3: fffff88008b77c68, Exception Record Address
Arg4: fffff88008b774c0, Context Record Address

*** WARNING: Unable to verify timestamp for VirtuWDDM.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.sys

Your bugcheck is indeed referencing a driver. It is your video card driver. I would uninstall VirtuWDDM.sys and update your videocard drivers. Im not quite sure but it seems like these two drivers may be conflicting with eachother.

Update your Video card, if there is an update available, download that. If you have the most current try to redownload/install it. If that doesn't work, go down to the previous update and test

AMD Radeon

It appears that you have a BIOS update available, that may help

Motherboards - P8B75-M LE - ASUS

Sometimes this bugcheck can occur when you are running low on disk space, ensure this is not the case

Try disabling Memory caching or shadowing in your BIOS. Try updating your BIOS first, if it doesn't work, try disabling this option if its present.

 

[Compvictor]

Thanks, i uninstalled Vitual VMP, reinstalled last video card drivers, updated Bios.
I have plenty disk space available..

The BSOD didn't appeared again...

 

[Gator]

Great, give it a few days to a week and see if it happens again. If it doesn't happen again in that time frame, mark this thread as solved