System service exception, Irql_not_less_or_equal errors, mini dump report included!!

Hello guys, my computer has recently crashed a few times, and both of them are related to ntoskrnl.exe. 

I am not familiar with computer thing, can anyone help me find out why is this happening? thank you

both reports are posted below:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8018cf32f5b, Address of the instruction which caused the bugcheck
Arg3: ffffd00036f66f00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

FAULTING_IP: 
nt!KiInsertTimerTable+18b
fffff801`8cf32f5b 4d3b7ef8        cmp     r15,qword ptr [r14-8]

CONTEXT:  ffffd00036f66f00 -- (.cxr 0xffffd00036f66f00;r)
rax=000000000002c580 rbx=0000000000000000 rcx=0000000000009896
rdx=00000067b4050b39 rsi=fffff8018d17e1a0 rdi=ffffe0000703d980
rip=fffff8018cf32f5b rsp=ffffd00036f67930 rbp=fffff8018d17e1a8
 r8=ffffe00006d501a0  r9=0000000000000001 r10=fffff8018ce8d000
r11=fffff78000000008 r12=fffff8018d17df80 r13=0000000000000001
r14=0003fffff9014008 r15=00000067b407d0b9
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
nt!KiInsertTimerTable+0x18b:
fffff801`8cf32f5b 4d3b7ef8        cmp     r15,qword ptr [r14-8] ds:002b:0003ffff`f9014000=????????????????
Last set context:
rax=000000000002c580 rbx=0000000000000000 rcx=0000000000009896
rdx=00000067b4050b39 rsi=fffff8018d17e1a0 rdi=ffffe0000703d980
rip=fffff8018cf32f5b rsp=ffffd00036f67930 rbp=fffff8018d17e1a8
 r8=ffffe00006d501a0  r9=0000000000000001 r10=fffff8018ce8d000
r11=fffff78000000008 r12=fffff8018d17df80 r13=0000000000000001
r14=0003fffff9014008 r15=00000067b407d0b9
iopl=0         nv up ei pl nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
nt!KiInsertTimerTable+0x18b:
fffff801`8cf32f5b 4d3b7ef8        cmp     r15,qword ptr [r14-8] ds:002b:0003ffff`f9014000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  Wow-64.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8018cf31426 to fffff8018cf32f5b

STACK_TEXT:  


FOLLOWUP_IP: 
nt!KiInsertTimerTable+18b
fffff801`8cf32f5b 4d3b7ef8        cmp     r15,qword ptr [r14-8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiInsertTimerTable+18b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c

IMAGE_VERSION:  6.3.9600.16452

STACK_COMMAND:  .cxr 0xffffd00036f66f00 ; kb

BUCKET_ID_FUNC_OFFSET:  18b

FAILURE_BUCKET_ID:  0x3B_nt!KiInsertTimerTable

BUCKET_ID:  0x3B_nt!KiInsertTimerTable

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_nt!kiinserttimertable

FAILURE_ID_HASH:  {16079c3e-6f6f-3ef5-f1bd-fe767eb1932a}

Followup: MachineOwner

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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff8021ab2ce76, address which referenced memory

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8021add4150
GetUlongFromAddress: unable to read from fffff8021add4208
 0000000000000008 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiInsertTimerTable+a6
fffff802`1ab2ce76 4c397008        cmp     qword ptr [rax+8],r14

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

PROCESS_NAME:  Agent.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  ffffd0003b2c67a0 -- (.trap 0xffffd0003b2c67a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000009896
rdx=000002d9cd54fe86 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8021ab2ce76 rsp=ffffd0003b2c6930 rbp=fffff8021ad78c28
 r8=ffffe00018d741a0  r9=0000000000000055 r10=fffff8021aa87000
r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KiInsertTimerTable+0xa6:
fffff802`1ab2ce76 4c397008        cmp     qword ptr [rax+8],r14 ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8021abe07e9 to fffff8021abd4ca0

STACK_TEXT:  
ffffd000`3b2c6658 fffff802`1abe07e9 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`3b2c6660 fffff802`1abdf03a : 00000000`00000000 00000000`00000000 00000000`00342b00 ffffd000`3b2c67a0 : nt!KiBugCheckDispatch+0x69
ffffd000`3b2c67a0 fffff802`1ab2ce76 : 00000000`00cefdb0 00000000`7eeba000 ffffe000`13fbc080 ffffd0b9`70b23e46 : nt!KiPageFault+0x23a
ffffd000`3b2c6930 fffff802`1ab2b426 : ffffe000`13fbc080 ffffe000`0ab23750 00000000`00000001 00000000`00000000 : nt!KiInsertTimerTable+0xa6
ffffd000`3b2c6990 fffff802`1aac29a8 : ffffe000`13fbc080 ffffe000`13fbc1c0 00000000`00000055 00000000`00000000 : nt!KiCommitThreadWait+0x1a6
ffffd000`3b2c69f0 fffff802`1ae30472 : ffffe000`0afa0060 ffffd000`00000006 00000000`00000001 00000000`00def700 : nt!KeWaitForSingleObject+0x248
ffffd000`3b2c6a90 fffff802`1abe04b3 : ffffe000`13fbc080 00000000`00000000 ffffd000`3b2c6ad8 ffffe000`0afa0060 : nt!NtWaitForSingleObject+0xb2
ffffd000`3b2c6b00 00000000`77132772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ceecc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77132772


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiInsertTimerTable+a6
fffff802`1ab2ce76 4c397008        cmp     qword ptr [rax+8],r14

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiInsertTimerTable+a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c

IMAGE_VERSION:  6.3.9600.16452

BUCKET_ID_FUNC_OFFSET:  a6

FAILURE_BUCKET_ID:  AV_nt!KiInsertTimerTable

BUCKET_ID:  AV_nt!KiInsertTimerTable

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:av_nt!kiinserttimertable

FAILURE_ID_HASH:  {1949fc55-7efe-b7ab-5126-09ed4666d971}

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


January 21st, 2014 4:00pm
We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.   We prefer at least 2 DMP files to spot trends and confirm the cause.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask
Free Windows Admin Tool Kit Click here and download it now
January 21st, 2014 5:20pm

ok these files are here : https://skydrive.live.com/redir?resid=6CC679D98D5062BB%21831

thank you very much

January 22nd, 2014 1:38am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics