yes we could if we had support contract, but we dont
how to narrow the cause of this issue? should I look for something?
thanks
could this help?
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016b4452, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
tcpip! ?? ::FNODOBFM::`string'+5d64
fffff880`016b4452 488b01 mov rax,qword ptr [rcx]
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff80002c7c100 -- (.trap 0xfffff80002c7c100)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800dcdc7a0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff80001805e80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016b4452 rsp=fffff80002c7c290 rbp=0000000000000000
r8=0000000000006888 r9=00000000000000d0 r10=fffff80001614000
r11=000000000000029d r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
tcpip! ?? ::FNODOBFM::`string'+0x5d64:
fffff880`016b4452 488b01 mov rax,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800016902e9 to fffff80001690d40
There is an amazing pack of free network admin tools.
click here to download it