BSOD Crash 1000007e

Hi raider1234 welcome to SF :)
You have the atikmdag.sys error,that is ati graphic card error.
So for first step,
Download the most recent driver for ur ati from AMD Graphics Drivers & Software
Download and install Phyxion.net - Driver Sweeper
1. Uninstall ati driver.
2. Reboot your PC in Safe Mode.
3. Run Driver Sweeper and select ati to clean.
4.Restart in normal mode,install the new ati driver,restart.
5.Update directX
6.Uninstall AVG
7.Download,install MSE Anti-Malware, Virus, Spyware Protection | Microsoft Security Essentials
8.Restart
--------------------
Wait for results and please post back with ANY results.
-------------------

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800028d2055, fffff88002ef4888, fffff88002ef40e0}

Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+2a05a )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: fffff800028d2055, The address that the exception occurred at
Arg3: fffff88002ef4888, Exception Record Address
Arg4: fffff88002ef40e0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiCommitThreadWait+1d5
fffff800`028d2055 488bbb90000000  mov     rdi,qword ptr [rbx+90h]

EXCEPTION_RECORD:  fffff88002ef4888 -- (.exr 0xfffff88002ef4888)
ExceptionAddress: fffff800028d2055 (nt!KiCommitThreadWait+0x00000000000001d5)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002ef40e0 -- (.cxr 0xfffff88002ef40e0)
rax=0000000000000000 rbx=bffffa8003fef2a0 rcx=fffff88002ef4a80
rdx=0000000000187000 rsi=fffffa8003fef360 rdi=fffff880009e8180
rip=fffff800028d2055 rsp=fffff88002ef4ac0 rbp=0000000000000000
 r8=fffffa80021b47c8  r9=0000000000000000 r10=fffffffffffffffe
r11=fffffa800477e010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=fffffa8003fef3a8
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!KiCommitThreadWait+0x1d5:
fffff800`028d2055 488bbb90000000  mov     rdi,qword ptr [rbx+90h] ds:002b:bffffa80`03fef330=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b010e0
 ffffffffffffffff 

FOLLOWUP_IP: 
atikmdag+2a05a
fffff880`048a005a ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff800028d41af to fffff800028d2055

STACK_TEXT:  
fffff880`02ef4ac0 fffff800`028d41af : fffffa80`033d0510 00000003`00000030 00000000`000000fa fffffa80`04596020 : nt!KiCommitThreadWait+0x1d5
fffff880`02ef4b50 fffff880`048a005a : fffffa80`04581b00 fffff880`00000000 fffffa80`04581000 fffff880`04b99500 : nt!KeWaitForSingleObject+0x19f
fffff880`02ef4bf0 fffffa80`04581b00 : fffff880`00000000 fffffa80`04581000 fffff880`04b99500 fffff880`009e8180 : atikmdag+0x2a05a
fffff880`02ef4bf8 fffff880`00000000 : fffffa80`04581000 fffff880`04b99500 fffff880`009e8180 fffffa80`04581000 : 0xfffffa80`04581b00
fffff880`02ef4c00 fffffa80`04581000 : fffff880`04b99500 fffff880`009e8180 fffffa80`04581000 fffffa80`04581000 : 0xfffff880`00000000
fffff880`02ef4c08 fffff880`04b99500 : fffff880`009e8180 fffffa80`04581000 fffffa80`04581000 fffff880`04b99dae : 0xfffffa80`04581000
fffff880`02ef4c10 fffff880`009e8180 : fffffa80`04581000 fffffa80`04581000 fffff880`04b99dae 0000000f`00000048 : atikmdag+0x323500
fffff880`02ef4c18 fffffa80`04581000 : fffffa80`04581000 fffff880`04b99dae 0000000f`00000048 ffffffff`fffc2f70 : 0xfffff880`009e8180
fffff880`02ef4c20 fffffa80`04581000 : fffff880`04b99dae 0000000f`00000048 ffffffff`fffc2f70 000000be`ac19b3d5 : 0xfffffa80`04581000
fffff880`02ef4c28 fffff880`04b99dae : 0000000f`00000048 ffffffff`fffc2f70 000000be`ac19b3d5 000000be`ac233956 : 0xfffffa80`04581000
fffff880`02ef4c30 0000000f`00000048 : ffffffff`fffc2f70 000000be`ac19b3d5 000000be`ac233956 00000001`00000028 : atikmdag+0x323dae
fffff880`02ef4c38 ffffffff`fffc2f70 : 000000be`ac19b3d5 000000be`ac233956 00000001`00000028 fffffa80`04599710 : 0xf`00000048
fffff880`02ef4c40 000000be`ac19b3d5 : 000000be`ac233956 00000001`00000028 fffffa80`04599710 00000000`00000000 : 0xffffffff`fffc2f70
fffff880`02ef4c48 000000be`ac233956 : 00000001`00000028 fffffa80`04599710 00000000`00000000 fffffa80`04581000 : 0xbe`ac19b3d5
fffff880`02ef4c50 00000001`00000028 : fffffa80`04599710 00000000`00000000 fffffa80`04581000 fffffa80`045889a0 : 0xbe`ac233956
fffff880`02ef4c58 fffffa80`04599710 : 00000000`00000000 fffffa80`04581000 fffffa80`045889a0 00000007`00000030 : 0x1`00000028
fffff880`02ef4c60 00000000`00000000 : fffffa80`04581000 fffffa80`045889a0 00000007`00000030 00000000`00000008 : 0xfffffa80`04599710


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  atikmdag+2a05a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a4cf223

STACK_COMMAND:  .cxr 0xfffff88002ef40e0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_atikmdag+2a05a

BUCKET_ID:  X64_0x7E_atikmdag+2a05a

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

raider1234 said:

Thanks panais! I am following your advice. Will update if the system crashes again.

Ok :)
Please post back with ANY results.

raider1234 said:

It worked...

1. Uninstall ati driver.
2. Reboot your PC in Safe Mode.
3. Run Driver Sweeper and select ati to clean.
4.Restart in normal mode,install the new ati driver,restart.
5.Update directX
8.Restart

Followed steps 1 to 5 and the system hasn't crashed since.

Thanks

Your welcome! Thats Good news!!