Jump to content
RESET Forums (homeservershow.com)

BSOD random every day


danielsan123
 Share

Recommended Posts

Hi!

 

Since one or two weeks back in time I get a BSOD on my HyperV (Gen8). Regarding to windows debugger it seems to be related to NDIS.SYS. I haven´t attached any new hardware or updated any drivers more than windows updates. Yetserday I tried patch some drivers from HP´s site but I still get the BSOD. I have done some diskcheck (SFC /Scannow) and checkdisk but no issues. No memorytest yet but ILO interface says everything is OK. 

 

Any ideas on how to progress?

 

Best regards Daniel

Link to comment
Share on other sites

Server2012R2

Ethernetcard :

Driver provider Hewlett-Packard Company.

Driver Date: 2014-09-12

Driver Version: 16.8.0.4

 

Under Driver details: 

Provider: Broadcom Corporation

File version: 16.8.0.4

 

I have disabled WMQ on any ethernetcard and in the virtual guests ethernet switch setting.

Link to comment
Share on other sites

I´ve run HUPSum updating all drivers from the patches released 30/3 2015 but still this BSOD occurres. This is my debuggerinfo:

 

 *******************************************************************************

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd001bdd151d0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd001bdd15128, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
 
Debugging Details:
------------------
 
 
TRAP_FRAME:  ffffd001bdd151d0 -- (.trap 0xffffd001bdd151d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe001e61924e0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe001e618eef0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80101ce4699 rsp=ffffd001bdd15360 rbp=ffffd001bdd153f9
 r8=0000000000000000  r9=0000000000000002 r10=ffffe001e447a930
r11=ffffe001e6192010 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
NDIS!ndisNsiGetAllInterfaceInformation+0x25819:
fffff801`01ce4699 cd29            int     29h
Resetting default scope
 
EXCEPTION_RECORD:  ffffd001bdd15128 -- (.exr 0xffffd001bdd15128)
ExceptionAddress: fffff80101ce4699 (NDIS!ndisNsiGetAllInterfaceInformation+0x0000000000025819)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
 
BUGCHECK_STR:  0x139
 
PROCESS_NAME:  WmiPrvSE.exe
 
CURRENT_IRQL:  2
 
ERROR_CODE: (NTSTATUS) 0xc0000409 - En  verskridning av en stackbaserad buffert uppt cktes. Detta kan ge anv ndare som vill v lla skada kontroll  ver programmet.
 
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - En  verskridning av en stackbaserad buffert uppt cktes. Detta kan ge anv ndare som vill v lla skada kontroll  ver programmet.
 
EXCEPTION_PARAMETER1:  0000000000000003
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
LAST_CONTROL_TRANSFER:  from fffff800e5d617e9 to fffff800e5d55ca0
 
STACK_TEXT:  
ffffd001`bdd14ea8 fffff800`e5d617e9 : 00000000`00000139 00000000`00000003 ffffd001`bdd151d0 ffffd001`bdd15128 : nt!KeBugCheckEx
ffffd001`bdd14eb0 fffff800`e5d61b10 : 00000000`00000000 00000000`00000000 ffffe001`e320d630 fffff800`e5cc1f3d : nt!KiBugCheckDispatch+0x69
ffffd001`bdd14ff0 fffff800`e5d60d34 : ffffd001`bdd153c0 ffffffff`00000000 00000000`00000000 ffffd001`bdd15278 : nt!KiFastFailDispatch+0xd0
ffffd001`bdd151d0 fffff801`01ce4699 : 00000000`ffffe001 ffffe001`e35bba20 ffffd001`bdd153d0 00000000`00000002 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd001`bdd15360 fffff801`01ee86cb : ffffd001`bdd15510 ffffd001`bdd15502 00000000`00000000 00000000`00000001 : NDIS!ndisNsiGetAllInterfaceInformation+0x25819
ffffd001`bdd15460 fffff801`02271fc1 : ffffe001`ea9c3cb0 ffffe001`00000070 00000097`313bc6e0 00000000`00000000 : NETIO!NsiEnumerateObjectsAllParametersEx+0x5cb
ffffd001`bdd15650 fffff801`02271bea : 00000000`00000000 ffffe001`ea37e0e0 ffffe001`ea37e010 00000000`00000000 : nsiproxy!NsippEnumerateObjectsAllParameters+0x201
ffffd001`bdd15840 fffff800`e602a77f : 00000000`00000000 ffffe001`ea37e010 ffffe001`ea37e010 00000000`00000001 : nsiproxy!NsippDispatch+0x5a
ffffd001`bdd15880 fffff800`e6029d22 : ffffd001`bdd15a38 0000000d`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0xa4f
ffffd001`bdd15a20 fffff800`e5d614b3 : ffffe001`e6b7e880 fffff6fb`001f0003 00000097`313bc5c8 fffff6bf`00000001 : nt!NtDeviceIoControlFile+0x56
ffffd001`bdd15a90 00007ffb`1eac123a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000097`313bc648 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`1eac123a
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
NETIO!NsiEnumerateObjectsAllParametersEx+5cb
fffff801`01ee86cb 8bd8            mov     ebx,eax
 
SYMBOL_STACK_INDEX:  5
 
SYMBOL_NAME:  NETIO!NsiEnumerateObjectsAllParametersEx+5cb
 
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:  5cb
 
FAILURE_BUCKET_ID:  0x139_3_NETIO!NsiEnumerateObjectsAllParametersEx
 
BUCKET_ID:  0x139_3_NETIO!NsiEnumerateObjectsAllParametersEx
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x139_3_netio!nsienumerateobjectsallparametersex
 
FAILURE_ID_HASH:  {647902b7-14c2-326a-6aea-d9b7b6d3d895}
 
Followup: MachineOwner
---------
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...