Update the display driver to the latest. Drivers - Download NVIDIA Drivers
When done, Stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .
__________________________________________
Code:
BugCheck 109, {a3a039d89b9ba5ee, b3b7465eee19e2d0, fffff880009be640, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
Code:
...........
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc000001d, fffff8800f133e38, fffff8800395b238, fffff8800395aa90}
Probably caused by : nvlddmkm.sys ( nvlddmkm+d1e38 )
Followup: MachineOwner
---------
4: 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8800f133e38, The address that the exception occurred at
Arg3: fffff8800395b238, Exception Record Address
Arg4: fffff8800395aa90, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
nvlddmkm+d1e38
fffff880`0f133e38 80b99c00000000 cmp byte ptr [rcx+9Ch],0
EXCEPTION_RECORD: fffff8800395b238 -- (.exr 0xfffff8800395b238)
ExceptionAddress: fffff8800f133e38 (nvlddmkm+0x00000000000d1e38)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff8800395aa90 -- (.cxr 0xfffff8800395aa90;r)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80083c11b0
rdx=00000000000001f4 rsi=fffffa800a50b9f0 rdi=fffffa8008390000
rip=fffff8800f133e38 rsp=fffff8800395b470 rbp=fffff8800395b579
r8=0000000000000001 r9=0000000000000000 r10=0000000000000008
r11=fffffa800a50bb00 r12=0000000000000000 r13=fffffa80071e6010
r14=fffffa80098caaf8 r15=fffffa800988c000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd1e38:
fffff880`0f133e38 80b99c00000000 cmp byte ptr [rcx+9Ch],0 ds:002b:fffffa80`083c124c=01
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80083c11b0
rdx=00000000000001f4 rsi=fffffa800a50b9f0 rdi=fffffa8008390000
rip=fffff8800f133e38 rsp=fffff8800395b470 rbp=fffff8800395b579
r8=0000000000000001 r9=0000000000000000 r10=0000000000000008
r11=fffffa800a50bb00 r12=0000000000000000 r13=fffffa80071e6010
r14=fffffa80098caaf8 r15=fffffa800988c000
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nvlddmkm+0xd1e38:
fffff880`0f133e38 80b99c00000000 cmp byte ptr [rcx+9Ch],0 ds:002b:fffffa80`083c124c=01
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800f133e38
FAILED_INSTRUCTION_ADDRESS:
nvlddmkm+d1e38
fffff880`0f133e38 80b99c00000000 cmp byte ptr [rcx+9Ch],0
STACK_TEXT:
fffff880`0395b470 00000000`00000000 : fffffa80`08390000 fffffa80`0a50b9f0 00000000`00000000 fffff880`0395b579 : nvlddmkm+0xd1e38
FOLLOWUP_IP:
nvlddmkm+d1e38
fffff880`0f133e38 80b99c00000000 cmp byte ptr [rcx+9Ch],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+d1e38
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5280da75
STACK_COMMAND: .cxr 0xfffff8800395aa90 ; kb
FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_nvlddmkm+d1e38
BUCKET_ID: X64_0x7E_BAD_IP_nvlddmkm+d1e38
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_bad_ip_nvlddmkm+d1e38
FAILURE_ID_HASH: {460b9b13-edd2-18bd-d851-1fd92bf44eb9}
Followup: MachineOwner
---------
4: kd> lmvm nvlddmkm
start end module name
fffff880`0f062000 fffff880`0fca3000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Mon Nov 11 18:54:05 2013 (5280DA75)
CheckSum: 00C10283
ImageSize: 00C41000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Quote