Could be very much a graphics card problem.
Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\YUSRA\Downloads\debug -LORELEI-HP-Sun_03_01_2015_155135_28\022615-23680-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`03466000 PsLoadedModuleList = 0xfffff800`036a9890
Debug session time: Fri Feb 27 06:57:10.736 2015 (UTC + 6:00)
System Uptime: 0 days 0:59:21.171
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88011117deb, fffff880069c5228, fffff880069c4a80}
Probably caused by : atikmdag.sys ( atikmdag+c4deb )
Followup: MachineOwner
---------
3: 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: fffff88011117deb, The address that the exception occurred at
Arg3: fffff880069c5228, Exception Record Address
Arg4: fffff880069c4a80, 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:
atikmdag+c4deb
fffff880`11117deb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]
EXCEPTION_RECORD: fffff880069c5228 -- (.exr 0xfffff880069c5228)
ExceptionAddress: fffff88011117deb (atikmdag+0x00000000000c4deb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 00000000000006a8
Attempt to read from address 00000000000006a8
CONTEXT: fffff880069c4a80 -- (.cxr 0xfffff880069c4a80;r)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000240000 rdi=0000000000000002
rip=fffff88011117deb rsp=fffff880069c5460 rbp=fffffa8006c1c8a0
r8=0000000000000002 r9=000000f414450000 r10=0000000000000000
r11=fffff880069c5690 r12=fffffa8006c15880 r13=fffffa80051d08c0
r14=fffffa8007cbb740 r15=fffff88011053000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc4deb:
fffff880`11117deb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000240000 rdi=0000000000000002
rip=fffff88011117deb rsp=fffff880069c5460 rbp=fffffa8006c1c8a0
r8=0000000000000002 r9=000000f414450000 r10=0000000000000000
r11=fffff880069c5690 r12=fffffa8006c15880 r13=fffffa80051d08c0
r14=fffffa8007cbb740 r15=fffff88011053000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
atikmdag+0xc4deb:
fffff880`11117deb 488b83a8060000 mov rax,qword ptr [rbx+6A8h] ds:002b:00000000`000006a8=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
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: 00000000000006a8
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003713100
GetUlongFromAddress: unable to read from fffff800037131c0
00000000000006a8 Nonpaged pool
FOLLOWUP_IP:
atikmdag+c4deb
fffff880`11117deb 488b83a8060000 mov rax,qword ptr [rbx+6A8h]
BUGCHECK_STR: 0x7E
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000010 to fffff88011117deb
STACK_TEXT:
fffff880`069c5460 00000000`00000010 : 00000000`00000246 fffff880`069c5488 00000000`00000018 fffffa80`07cbb740 : atikmdag+0xc4deb
fffff880`069c5468 00000000`00000246 : fffff880`069c5488 00000000`00000018 fffffa80`07cbb740 fffff880`11176b48 : 0x10
fffff880`069c5470 fffff880`069c5488 : 00000000`00000018 fffffa80`07cbb740 fffff880`11176b48 00000000`00000000 : 0x246
fffff880`069c5478 00000000`00000018 : fffffa80`07cbb740 fffff880`11176b48 00000000`00000000 00000000`00000000 : 0xfffff880`069c5488
fffff880`069c5480 fffffa80`07cbb740 : fffff880`11176b48 00000000`00000000 00000000`00000000 00000000`00000000 : 0x18
fffff880`069c5488 fffff880`11176b48 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`07cbb740
fffff880`069c5490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x123b48
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+c4deb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 531fc36e
STACK_COMMAND: .cxr 0xfffff880069c4a80 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmdag+c4deb
BUCKET_ID: X64_0x7E_atikmdag+c4deb
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_atikmdag+c4deb
FAILURE_ID_HASH: {8ab0e090-39cf-8fdd-73c3-69b7e6ad36a6}
Followup: MachineOwner
---------
3: kd> lmvm atikmdag
start end module name
fffff880`11053000 fffff880`11df5000 atikmdag T (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Timestamp: Wed Mar 12 08:16:14 2014 (531FC36E)
CheckSum: 00D4BCDD
ImageSize: 00DA2000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Check for updates on the ATI driver. If that does not help, use on board graphics if you have it.
Also go through this thread: