The issue is with nvidia Optimus. But I am not able to suggest the best action here.
Plus, you monitor the temps. See if it increases with time from what is stated in the screenshot.
I will ask for others opinion in this thread.
____________________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {10, 2, 1, fffff80002e8af1f}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+e498c )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002e8af1f, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b9100
GetUlongFromAddress: unable to read from fffff800030b91c0
0000000000000010 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`02e8af1f 488717 xchg rdx,qword ptr [rdi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: TuneUpUtilitie
TAG_NOT_DEFINED_c000000f: FFFFF800047ABFB0
TRAP_FRAME: fffff800047ab420 -- (.trap 0xfffff800047ab420)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff800047ab690 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e8af1f rsp=fffff800047ab5b0 rbp=fffffa800733f000
r8=fffff800047ab690 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeAcquireInStackQueuedSpinLock+0x5f:
fffff800`02e8af1f 488717 xchg rdx,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e81169 to fffff80002e81bc0
STACK_TEXT:
fffff800`047ab2d8 fffff800`02e81169 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`047ab2e0 fffff800`02e7fde0 : fffff800`047ab558 00000000`00000004 fffff800`047ab560 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`047ab420 fffff800`02e8af1f : fffffa80`0977ad90 00000000`00000030 fffff880`0f444f2d 00000000`000007ff : nt!KiPageFault+0x260
fffff800`047ab5b0 fffff880`0f35b98c : fffffa80`0733f000 00000000`00000000 fffffa80`0733f000 00000000`c1d00061 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff800`047ab600 fffffa80`0733f000 : 00000000`00000000 fffffa80`0733f000 00000000`c1d00061 00000000`0000000d : nvlddmkm+0xe498c
fffff800`047ab608 00000000`00000000 : fffffa80`0733f000 00000000`c1d00061 00000000`0000000d fffff880`0f349c5d : 0xfffffa80`0733f000
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+e498c
fffff880`0f35b98c ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm+e498c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52676afe
FAILURE_BUCKET_ID: X64_0xA_nvlddmkm+e498c
BUCKET_ID: X64_0xA_nvlddmkm+e498c
Followup: MachineOwner
---------
0: kd> lmvm nvlddmkm
start end module name
fffff880`0f277000 fffff880`0feae000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Wed Oct 23 11:51:50 2013 (52676AFE)
CheckSum: 00C0CF0F
ImageSize: 00C37000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8006bbfa10, fffff80000b9c3d8, fffffa8008751010}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006bbfa10, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8008751010, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DEVICE_OBJECT: fffffa8007115040
DRIVER_OBJECT: fffffa8007119060
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52676afe
MODULE_NAME: nvlddmkm
FAULTING_MODULE: fffff8800f2ab000 nvlddmkm
IRP_ADDRESS: fffffa8008751010
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0
STACK_TEXT:
fffff800`00b9c388 fffff800`02f4d8d2 : 00000000`0000009f 00000000`00000003 fffffa80`06bbfa10 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02ee885c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02ee86f6 : fffffa80`07944c58 fffffa80`07944c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02ee85de : 00000049`0c134471 fffff800`00b9cb18 00000000`001eafe6 fffff800`0305cf48 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02ee83c7 : 00000011`14e6f9c4 00000011`001eafe6 00000011`14e6f9f5 00000000`000000e6 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02ed58ca : fffff800`03058e80 fffff800`03066cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x9F_3_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C4, {f6, ac, fffffa8008346060, fffff8800f37cbbd}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+9abbd )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000000ac, Handle value being referenced.
Arg3: fffffa8008346060, Address of the current process.
Arg4: fffff8800f37cbbd, Address inside the driver that is performing the incorrect reference.
Debugging Details:
------------------
BUGCHECK_STR: 0xc4_f6
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: rundll32.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff8000351b4ec to fffff8000308ebc0
STACK_TEXT:
fffff880`09708888 fffff800`0351b4ec : 00000000`000000c4 00000000`000000f6 00000000`000000ac fffffa80`08346060 : nt!KeBugCheckEx
fffff880`09708890 fffff800`03530bf4 : 00000000`000000ac fffffa80`08346060 00000000`00000004 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`097088d0 fffff800`032e8890 : fffff800`03384780 fffff880`09708b20 fffff880`09708d00 fffff880`09708eb0 : nt!VfCheckUserHandle+0x1b4
fffff880`097089b0 fffff800`0335e6b5 : fffff8a0`027c9800 fffff8a0`00000001 fffffa80`044173b0 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x2027e
fffff880`09708a80 fffff800`0308de53 : fffffa80`08346b50 fffff880`09708e38 00000000`00000002 00000000`00000000 : nt!NtQueryValueKey+0x115
fffff880`09708c10 fffff800`0308a410 : fffff800`0351fd96 fffff880`0f37cbbd fffff880`09708eb0 fffff880`09708ea8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`09708e18 fffff800`0351fd96 : fffff880`0f37cbbd fffff880`09708eb0 fffff880`09708ea8 fffff800`0308a410 : nt!KiServiceLinkage
fffff880`09708e20 fffff880`0f37cbbd : fffff880`097098ca fffff880`09708ef0 fffff880`097098b8 fffffa80`03ff7f98 : nt!VfZwQueryValueKey+0x76
fffff880`09708e70 fffff880`097098ca : fffff880`09708ef0 fffff880`097098b8 fffffa80`03ff7f98 00000000`00000000 : nvlddmkm+0x9abbd
fffff880`09708e78 fffff880`09708ef0 : fffff880`097098b8 fffffa80`03ff7f98 00000000`00000000 fffff880`09708ea0 : 0xfffff880`097098ca
fffff880`09708e80 fffff880`097098b8 : fffffa80`03ff7f98 00000000`00000000 fffff880`09708ea0 fffff980`00000000 : 0xfffff880`09708ef0
fffff880`09708e88 fffffa80`03ff7f98 : 00000000`00000000 fffff880`09708ea0 fffff980`00000000 00000000`000000ac : 0xfffff880`097098b8
fffff880`09708e90 00000000`00000000 : fffff880`09708ea0 fffff980`00000000 00000000`000000ac fffffa80`00280026 : 0xfffffa80`03ff7f98
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+9abbd
fffff880`0f37cbbd 3d340000c0 cmp eax,0C0000034h
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: nvlddmkm+9abbd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52676afe
FAILURE_BUCKET_ID: X64_0xc4_f6_nvlddmkm+9abbd
BUCKET_ID: X64_0xc4_f6_nvlddmkm+9abbd
Followup: MachineOwner
---------
2: kd> lmvm nvlddmkm
start end module name
fffff880`0f2e2000 fffff880`0ff19000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Wed Oct 23 11:51:50 2013 (52676AFE)
CheckSum: 00C0CF0F
ImageSize: 00C37000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4