Community
cancel
Showing results for 
Search instead for 
Did you mean: 
AHaut
Novice
1,122 Views

Win10 + I219-V + Intel ME + VLANs = BSOD

Yesterday I got an update for the Intel ME component for my MSI Z270 motherboard, and after I restarted the computer, it blue screened on me. I had to end up resetting the Windows install to be able to get access to the computer again, even while I had to download and reinstall all my apps (luckily I have all my files on a different drive).

I started my troubleshooting session. Downloaded all latest drivers for my setup, installed all but the Intel ME drivers, since it was the last thing I did before it broke it all. Ran the Windows update, reconfigured my VLANs, restarted a few times at drivers requests, with no issues. All was fine. Installed the ME drivers, restarted, BSOD. So yeah, I was on the right path.

Reset Windows one more time, installed Intel ME drivers first. Restarted the computer after each driver was getting installed, to find out which one was the ME driver getting upset with. All drivers installed, all was still fine, I felt confused. Ran Windows update, all still fine. Went configure my very first VLAN, BSOD. So I had a big hint.

I downloaded WinDBG and ran it against the memory.dmp files generated during the last BSODs and at all times the error was a memory corruption on the NDIS stack. Not much past that as by default Windows only dumps 200Mb of memory, and I had not changed to collect a full dump and force another crash (full dump sucks when you have 64Gb RAM).

The Intel ME driver 11.6.0.1036 caused this trouble, whereas with driver 11.6.0.1026 VLANs were working just fine. The only reason why I posted this report under Wired networks is because this is the component that is failing, not the ME - but I might either cross-post or have a mod move this thread there.

I am trying to get the previous ME driver 11.6.0.1026 with MSI to roll back and see if the VLAN will still work - I might have them take a look at this topic too. One end user reporting issues might not cause much attention, but a VAR reporting could take a very different route.

So if you happen to use a few advanced features and things got broken on you, hope this can help.

Other related drivers and product version:

Intel PROSet Version 22.0.18.0, with Windows driver version 12.15.23.9

Windows 10 Pro x64, Version 1067 Build 14393.

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 14393.953.amd64fre.rs1_release_inmarket.170303-1614

SYSTEM_MANUFACTURER: MSI

SYSTEM_PRODUCT_NAME: MS-7A69

SYSTEM_SKU: Default string

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1.10

BIOS_DATE: 02/03/2017

BASEBOARD_MANUFACTURER: MSI

BASEBOARD_PRODUCT: Z270M MORTAR (MS-7A69)

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 1

BUGCHECK_P1: 7

BUGCHECK_P2: d699

BUGCHECK_P3: b96acc4c

BUGCHECK_P4: ffffda87ad768208

POOL_ADDRESS: ffffda87ad768208

FREED_POOL_TAG: Filt

BUGCHECK_STR: 0xc2_7_Filt

CPU_COUNT: 4

CPU_MHZ: bb8

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 48'00000000 (cache) 48'00000000 (init)

DEFAULT_BUCKET_ID: CODE_CORRUPTION

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: HQUEST

ANALYSIS_SESSION_TIME: 03-19-2017 17:22:22.0774

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER: from fffff803f9060cf3 to fffff803f8f657c0

STACK_TEXT:

 

ffff8e80`5c558da8 fffff803`f9060cf3 : 00000000`000000c2 00000000`00000007 00000000`0000d699 00000000`b96acc4c : nt!KeBugCheckEx

 

ffff8e80`5c558db0 fffff80b`f261fbb5 : ffffda87`ad768208 00000000`0000009c ffff8e80`5c558f40 00000000`0000006a : nt!ExFreePool+0x1d3

 

ffff8e80`5c558e90 fffff80b`f24d8182 : ffff8e80`5c559240 ffff8e80`5c558f49 ffff8e80`5c558fd0 ffffda87`a8421260 : ndis!NdisFreeMemory+0x15

 

ffff8e80`5c558ec0 fffff80b`f24d2dc2 : ffffda87`99ce1a20 fffff80b`f262766f 00000000`00000000 ffffda87`98fb1c10 : iansw60e+0x8182

 

ffff8e80`5c558fb0 fffff80b`f262750d : ffffda87`98fb1c10 ffff8e80`5c559130 ffff8e80`5c559240 ffff8e80`5c559410 : iansw60e+0x2dc2

 

ffff8e80`5c559000 fffff80b`f26270c4 : 00000000`00000002 ffffda87`ad9481a0 ffffda87`ad9481a0 ffffda87`ad9481a0 : ndis!ndisInvokeStatus+0x39

 

ffff8e80`5c559030 fffff80b`f2626ab8 : ffffda87`ad9481a0 00000000`0000000c ffffda87`ad9481a0 00000000`00000000 : ndis!ndisIndicateStatusInternal+0x464

 

ffff8e80`5c559210 fffff80b`f26ba175 : ffffda87`ad9481a0 ffffda87`ad9481a0 00000000`00000000 ffffda87`a23fcc00 : ndis!ndisIndicateInitialStateToBinding+0x304

 

ffff8e80`5c559500 fffff80b`f26b3f29 : ffffb101`5d1c5d70 ffffb101`6816a278 ffffb101`6dd50740 ffffb101`6816a278 : ndis!ndisBindNdis6Protocol+0x541

 

ffff8e80`5c5597a0 fffff80b`f26b5c2d : ffffda87`ad9481a0 00000000`000013d0 00000000`000013e8 00000000`00000002 : ndis!ndisBindProtocol+0x55

 

ffff8e80`5c559880 fffff80b`f26b588c : ffff8e80`5c559ad0 ffffda87`ad9495f8 ffffda87`ad949630 ffff8e80`5c559ad0 : ndis!Ndis::BindEngine::Iterate+0x34d

 

ffff8e80`5c559a80 fffff80b`f26b567a : ffffda87`ad086800 ffffb101`6816a2b8 ffffda87`ad193dc0 00000000`00000000 : ndis!Ndis::BindEngine::UpdateBindings+0x44

 

ffff8e80`5c559ab0 fffff803`f8e7c6f9 : ffffda87`ad086800 ffffda87`ad949630 ffffda87`00000000 fffff803`00000000 : ndis!Ndis::BindEngine::UpdateBindingsWorkItem+0x3a

 

ffff8e80`5c559b00 fffff803`f8ecd2d5 : ffff8e80`57017180 00000000`00000080 ffffda87`98477040 ffffda87`ad086800 : nt!ExpWorkerThread+0xe9

 

ffff8e80`5c559b90 fffff803`f8f6ac86 : ffff8e80`57017180 ffffda87`ad086800 fffff803`f8ecd294 00310100`0d010900 : nt!PspSystemThreadStartup+0x41

 

ffff8e80`5c559be0 00000000`00000000 : ffff8e80`5c55a000 ffff8e80`5c553000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

0 Kudos
0 Replies
Reply