Dear all,

since one month I'm experiencing a strange behavior from my DELL XPS 12 9Q33, Mid 2013 with Windows 8.1 Pro. When the notebook is left unattended for more than 5 minutes, it freezes with the BSOD with two different causes: KERNEL_SECURITY_CHECK_EXCEPTION and IRQL_NOT_LESS_OR_EQUAL. I already activated the Verifier Utility and debugged the results of the memory dump, obtaining following reason:

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: ffffcf80c94c2fb8, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff800b76aa534, address which referenced memory

 

Debugging Details:

------------------

 

 

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80157965138

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

 ffffcf80c94c2fb8

 

CURRENT_IRQL:  2

 

FAULTING_IP:

ndis!ndisNsiGetInterfaceInformation+5f5

fffff800`b76aa534 498b8e98050000  mov     rcx,qword ptr [r14+598h]

 

CUSTOMER_CRASH_COUNT:  1

 

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

 

BUGCHECK_STR:  AV

 

PROCESS_NAME:  svchost.exe

 

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

 

TRAP_FRAME:  ffffd001775b82c0 -- (.trap 0xffffd001775b82c0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000

rip=fffff800b76aa534 rsp=ffffd001775b8450 rbp=0000000000000002

 r8=0000000000000007  r9=fffff800b87dd054 r10=0000000000000000

r11=ffffd001775b87f0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei ng nz na pe nc

ndis!ndisNsiGetInterfaceInformation+0x5f5:

fffff800`b76aa534 498b8e98050000  mov     rcx,qword ptr [r14+598h] ds:00000000`00000598=????????????????

Resetting default scope

 

LAST_CONTROL_TRANSFER:  from fffff8015775e7e9 to fffff80157752ca0

 

STACK_TEXT: 

ffffd001`775b8178 fffff801`5775e7e9 : 00000000`0000000a ffffcf80`c94c2fb8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

ffffd001`775b8180 fffff801`5775d03a : 00000000`00000000 00000000`00000002 ffffd001`775b3000 ffffd001`775b9000 : nt!KiBugCheckDispatch+0x69

ffffd001`775b82c0 fffff800`b76aa534 : 00000000`00000002 ffffe000`e5677200 00000000`00000000 ffffe000`e56771a0 : nt!KiPageFault+0x23a

ffffd001`775b8450 fffff800`b6f84572 : ffffd001`775b85c0 ffffe000`e8d98d02 ffffe000`e8d98d00 00000000`00000000 : ndis!ndisNsiGetInterfaceInformation+0x5f5

ffffd001`775b8500 fffff800`b87d6a25 : 00000000`00000050 00000000`00000050 ffffe000`e42c2de0 00000000`00000000 : NETIO!NsiGetParameterEx+0x222

ffffd001`775b8660 fffff800`b87d6be3 : 00000000`00000000 ffffe000`e86900e0 ffffe000`e8690010 ffffe000`e768e9f0 : nsiproxy!NsippGetParameter+0x195

ffffd001`775b87f0 fffff801`57c7b911 : ffffe000`e8690010 00000000`00000002 00000000`00000000 fffff801`578a5701 : nsiproxy!NsippDispatch+0x53

ffffd001`775b8830 fffff801`57a2777f : 00000000`00000000 ffffd001`775b8b80 ffffe000`e8690010 ffffe000`e768e950 : nt!IovCallDriver+0x3cd

ffffd001`775b8880 fffff801`57a26d22 : ffffd001`775b8a38 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa4f

ffffd001`775b8a20 fffff801`5775e4b3 : ffffe000`e61fd080 00000000`001f0003 0000009c`1f6ff658 00000000`00000001 : nt!NtDeviceIoControlFile+0x56

ffffd001`775b8a90 00007fff`88a9123a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

0000009c`1f6ff6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`88a9123a

 

 

STACK_COMMAND:  kb

 

FOLLOWUP_IP:

NETIO!NsiGetParameterEx+222

fffff800`b6f84572 8bd8            mov     ebx,eax

 

SYMBOL_STACK_INDEX:  4

 

SYMBOL_NAME:  NETIO!NsiGetParameterEx+222

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: NETIO

 

IMAGE_NAME:  NETIO.SYS

 

DEBUG_FLR_IMAGE_TIMESTAMP:  546029c5

 

IMAGE_VERSION:  6.3.9600.17485

 

BUCKET_ID_FUNC_OFFSET:  222

 

FAILURE_BUCKET_ID:  AV_VRF_NETIO!NsiGetParameterEx

 

BUCKET_ID:  AV_VRF_NETIO!NsiGetParameterEx

 

ANALYSIS_SOURCE:  KM

 

FAILURE_ID_HASH_STRING:  km:av_vrf_netio!nsigetparameterex

 

FAILURE_ID_HASH:  {f5408a12-c1db-c14f-1bc7-98a11ba14432}

 

Followup: MachineOwner

---------

 

Thanks in advance

Dr. Paolo Casoto

PC

 We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

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

Hi,

According to your Debug result, it seems like caused by ndis (Network Driver Interface Specification), it would be better to reinstall the NIC driver for test.

On the other hand, it would be better to follow ZigZag's suggestion to upload the dump file here. 

Hello, I have similiar issue as author of this topic - as long as I am doing something on my laptop (Dell Vostro 3450) it is absolutely fine. Several minutes after my last action system crashes.  

Here are my dumps of latest incidents. Can anyone help me? Thank you. 

http://1drv.ms/1Nq9rDd

http://1drv.ms/1Nq9DT0

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)