Broadcom AC Wireless Adapter Freeze

[knightofeffect]

I just bought a brand new asus ac3200 router so of course I need a new wireless adapter card for my desktop.

I settled on the TP-Link 1750AC adapter to plug in one of my space pcie slots on my ASRock Z87M Extreme 4 mobo. I choose the pcie slot 4 as the only other valid option (slot 3) would have it butting up to the fans on my 970gtx.

I started up the computer, noticed the lights on the new card came on and windows started fine. I downloaded and installed the newest drivers for the card from TP-link... and the computer immediately froze. Literally the second the driver installs. My computer build has been extremely stable, and I have actually never seen a hard freeze in Windows 10, not a crash or anything, just a locked freeze.

Upon restart, the computer would again freeze the moment before the login screen would come up, on rare occasion actually making it to the splash. This makes sense as that is the first moment networking is initialized. Roughly 50% of the time, the computer would bluescreen with a DPA_WATCHDOG_ERROR after 10 or so seconds and reboot, the other times it would just stay frozen (or my patience would run out).

I can simply boot into safe mode and uninstall the driver (which is completely "successfully" installed as far as the device manager is concerned and is correctly identifying the card) and the computer returns to normal operation.

I have now tried 4 different broadcom wlan drivers for windows 10 x64 and they all have the exact same result.

Are all the wlan broadcom drivers still really this crap? Surely there can't just not be windows 10 drivers for wlan adapters still.

What should I do? Try the other pcie slot? Assume the card is DOA? Perform some sort of ritualistic dance?

Does anyone have a similar set-up confirmed working?

 

[knightofeffect]

Well I just discovered my mobo has a new bios that specifically lists the following three things in its description:
1.Add NVMe support.
2.Update Network module.
3.Improve PCIE compatibility.

Here's hoping =)

 

[knightofeffect]

Well I updated my bios and all MB drivers, installed the wlan driver in safemode, moved the card to the other pcie slot, all amounts to nothing. Exact same behavior.

Anyone have any ideas? Is the card just bad?

 

[Ch-Fahad]

I Juss Finally found a solution for BSOD on windows 10 is that .. Just install windows 10 new version 1511 and then install ASUS PCE-AC68 Utility 2.1.1.5 after installing the driver I just go to Device manager and update the drivers to version broadcom_wlan_7.35.308.0 .. now there is no single one issue is remaining .. you can find broadcom_wlan_7.35.308.0 from a single search of google.... Thanks..

 

[knightofeffect]

I followed those steps and unfortunately experienced the same behavior. Immediately upon installing either the Asus Utility 2.1.1.5 or the broadcom_wlan_7.35.308.0 driver the computer freezes and continues to freeze every startup until uninstalling.

 

[Colif]

download and run http://www.resplendence.com/whocrashed
it will look at error logs and give us some insight into the cause of problem, though it seems pretty obvious what that is.

copy/paste results in here.

Try downloading a program like Driver Booster and see what drivers you missed. Its likely to be Intel drivers or USB. Lots of times motherboard makers haven't got latest drivers for some parts of motherboard.

 

[knightofeffect]

Thanks for the suggestions! I really thought we had it licked there for a second.

The driver booster software detected several drivers that needed to be updated including the broadcom wlan driver. I installed all the necessary drivers leaving the broadcom for last. Everything installed fine, I rebooted and everything remained fine. I disconnected my external wlan adapter and went into the network and sharing center to connect using the new internal AC adapter... then everything froze, and once again, began freezing on every reboot.

Unfortunately, the who crashed application isn't going to do anything as the computer freezes so hard no dump is written. Wouldn't that point to a hardware fault within the new wlan adapter? I really wish I understood what condition resulted it in not freezing for ~5min after the initial driver booster installation.

One more interesting tidbit, my Logitech G900 driver started having issue in the middle of all this. Occasionally it just doesn't work when I restart windows and I have to use my old Logitech G510 to update the G900 driver then it works fine. The more interesting part of this is that when I'm running windows 10 in safe mode to uninstall the wlan driver the G900 mouse has not worked in the last 5+ renditions. IE it seems now that whenever the wlan adapter driver is installed, it kills the mouse driver.

 

[Colif]

has the WiFi card that causes the freeze ever worked? I know its new but it is looking to be the cause.

I should have got you to the ritualistic dance, you never know, it might have worked

pcie and USB are connected in some way. They may share irq's


As for that error you always get:

I would be looking at any usb devices on your machine and the BIOS version info.
particularly if you use a USB wireless thumb device.

Bugs in the BIOS cause the USB devices not to work correctly, you plug a USB device in, the plug and play detect it and starts to install a driver, the driver installs fails, the Plug and play detect that you don't have a driver and tries to install the driver again. OVER AND OVER.
at some point the system thinks the CPU core is hung and shuts down the machine with a bugcheck.

http://www.tomsguide.com/answers/id-2780847/dpc-watchdog-violation-bsod-error-windows.html

You have latest drivers and newest bios. Are there any other USB devices attached that could be interfering?

Have a look in event viewer/custom views/administrative events and see if anything is showing around time you freeze. Windows still knows it crashed even if it doesn't show an error

 

[knightofeffect]

No it has never worked. I actually completely forgot about the watchdog error as I have not seen that error in some time now. Really only the original configuration (IE old bios, and other PCIe slot) gave me that error.

Under typical operation I about have the number of USB devices you can hook to this computer maxed out, but have had no problem with any USB device hooked up to the computer. The exception would be these very recent issues with my G900 mouse that seems to be linked in some way to the attempted installation of the wlan adapter.

I just underwent several install attempts with no USB devices hooked up, literally none, but still received the same results.

I then decided to go back and try the original PCIe slot on my MB, which is really the one I think it should be in to begin with as the other one is recommended for SLI. Upon initial boot (again with no USB devices connected) it started fine and recognized the wlan adapter. I cautiously connected my keyboard and mouse and logged and started looking at network properties, where the wlan adapter was listed, but it was not finding any networks so it really wasn't working (I'm surrounded by a wifi maelstrom). I looked at the resources of the device and noted that the IRQ was 0x0000000 (how ever many all 0's) which I thought was odd. I decided to restart, cause why not, and then it went back to auto-freezing right as windows boots.

I did yet another reinstall attempt of the driver from driver booster with the original PCIe slot and this time it gave me a bluescreen "CRITICAL_PROCESS_FAILED" error before hard-freezing at a 0% core dump. (something that the other PCIe slot never gave).

So to make a long story short, I try a whole bunch of different things and get ever-so-slightly different behavior, but the same end result.

On to the events... I actually had looked at the events before which led me to believe that the driver was never actually successfully installing as it would end with "more installation required" and "driver NULL installed", so once I attempted to install the driver in safe mode, just to see if I could trick it, and it actually completed the driver installation, but still wouldn't successfully boot into normal windows.

So I have a ton of error administrative events tied to the attempted wlan installations... In general a failed installation shows the following for the events related directly to the wlan adapter:

Information 5/28/2016 12:35:19 PM Kernel-PnP 430 None
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 5/28/2016 12:35:19 PM
Event ID: 430
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: KOE-FINIX
Description:
Device PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6ae6995&0&00E4 requires further installation.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>430</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T17:35:19.866457600Z" />
<EventRecordID>1523</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="120" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6ae6995&0&00E4</Data>
</EventData>
</Event>

Information 5/28/2016 12:35:27 PM UserPnp 20001 (7005)
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 5/28/2016 12:35:27 PM
Event ID: 20001
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: KOE-FINIX
Description:
Driver Management concluded the process to install driver NULL Driver for Device Instance ID PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4 with the following status: 0x0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T17:35:27.914597400Z" />
<EventRecordID>19428</EventRecordID>
<Correlation />
<Execution ProcessID="2780" ThreadID="2804" />
<Channel>System</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>NULL Driver</DriverName>
<DriverVersion>0</DriverVersion>
<DriverProvider>
</DriverProvider>
<DeviceInstanceID>PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4</DeviceInstanceID>
<SetupClass>{00000000-0000-0000-0000-000000000000}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>false</UpgradeDevice>
<IsDriverOEM>false</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>
</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>


However, on the rare occurrence, I can get this:

Information 5/28/2016 11:58:04 AM Kernel-PnP 430 None
Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 5/28/2016 11:58:04 AM
Event ID: 430
Task Category: None
Level: Information
Keywords:
User: SYSTEM
Computer: KOE-FINIX
Description:
Device PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6ae6995&0&00E4 requires further installation.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>430</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T16:58:04.439469100Z" />
<EventRecordID>1510</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="244" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6ae6995&0&00E4</Data>
</EventData>
</Event>

Information 5/28/2016 11:58:07 AM UserPnp 20003 (7005)
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 5/28/2016 11:58:07 AM
Event ID: 20003
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: KOE-FINIX
Description:
Driver Management has concluded the process to add Service BCMWL63A for Device Instance ID PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4 with the following status: 0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20003</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T16:58:07.617288300Z" />
<EventRecordID>18760</EventRecordID>
<Correlation />
<Execution ProcessID="3108" ThreadID="3128" />
<Channel>System</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<AddServiceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<ServiceName>BCMWL63A</ServiceName>
<DriverFileName>\SystemRoot\system32\DRIVERS\bcmwl63a.sys</DriverFileName>
<DeviceInstanceID>PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4</DeviceInstanceID>
<PrimaryService>true</PrimaryService>
<UpdateService>true</UpdateService>
<AddServiceStatus>0</AddServiceStatus>
</AddServiceID>
</UserData>
</Event>

Information 5/28/2016 11:58:07 AM UserPnp 20003 (7005)
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 5/28/2016 11:58:07 AM
Event ID: 20003
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: KOE-FINIX
Description:
Driver Management has concluded the process to add Service vwifibus for Device Instance ID PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4 with the following status: 0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20003</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T16:58:07.620042200Z" />
<EventRecordID>18761</EventRecordID>
<Correlation />
<Execution ProcessID="3108" ThreadID="3128" />
<Channel>System</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<AddServiceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<ServiceName>vwifibus</ServiceName>
<DriverFileName>\SystemRoot\system32\DRIVERS\vwifibus.sys</DriverFileName>
<DeviceInstanceID>PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4</DeviceInstanceID>
<PrimaryService>false</PrimaryService>
<UpdateService>true</UpdateService>
<AddServiceStatus>0</AddServiceStatus>
</AddServiceID>
</UserData>
</Event>

Information 5/28/2016 11:58:07 AM UserPnp 20001 (7005)
Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 5/28/2016 11:58:07 AM
Event ID: 20001
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: KOE-FINIX
Description:
Driver Management concluded the process to install driver bcmwdi.inf_amd64_87f53495b3e17982\bcmwdi.inf for Device Instance ID PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4 with the following status: 0x0.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T16:58:07.807884500Z" />
<EventRecordID>18762</EventRecordID>
<Correlation />
<Execution ProcessID="3108" ThreadID="3128" />
<Channel>System</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>bcmwdi.inf_amd64_87f53495b3e17982\bcmwdi.inf</DriverName>
<DriverVersion>7.35.295.2</DriverVersion>
<DriverProvider>Broadcom</DriverProvider>
<DeviceInstanceID>PCI\VEN_14E4&DEV_43A0&SUBSYS_061914E4&REV_03\4&6AE6995&0&00E4</DeviceInstanceID>
<SetupClass>{4D36E972-E325-11CE-BFC1-08002BE10318}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>true</UpgradeDevice>
<IsDriverOEM>true</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>Broadcom 802.11ac Network Adapter</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>


Now for the juicy administrative event details that are completely beyond me =)

Error 5/28/2016 12:36:08 PM DistributedCOM 10016 None
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 5/28/2016 12:36:08 PM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: KOE-FINIX\knightofeffect
Computer: KOE-FINIX
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user KOE-FINIX\knightofeffect SID (S-1-5-21-3049512764-3745822111-1548185579-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.Cortana_1.6.1.52_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-1861897761-1695161497-2927542615-642690995-327840285-2659745135-2630312742). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T17:36:08.342102900Z" />
<EventRecordID>19431</EventRecordID>
<Correlation />
<Execution ProcessID="924" ThreadID="4536" />
<Channel>System</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-21-3049512764-3745822111-1548185579-1001" />
</System>
<EventData>
<Data Name="param1">machine-default</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{C2F03A33-21F5-47FA-B4BB-156362A2F239}</Data>
<Data Name="param5">{316CDED5-E4AE-4B15-9113-7055D84DCC97}</Data>
<Data Name="param6">KOE-FINIX</Data>
<Data Name="param7">knightofeffect</Data>
<Data Name="param8">S-1-5-21-3049512764-3745822111-1548185579-1001</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
<Data Name="param10">Microsoft.Windows.Cortana_1.6.1.52_neutral_neutral_cw5n1h2txyewy</Data>
<Data Name="param11">S-1-15-2-1861897761-1695161497-2927542615-642690995-327840285-2659745135-2630312742</Data>
</EventData>
</Event>

Warning 5/28/2016 12:36:10 PM Kernel-EventTracing 4 Logging
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 5/28/2016 12:36:10 PM
Event ID: 4
Task Category: Logging
Level: Warning
Keywords: Session
User: SYSTEM
Computer: KOE-FINIX
Description:
The maximum file size for session "ReadyBoot" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl". The maximum files size is currently set to 20971520 bytes.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1</Task>
<Opcode>10</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2016-05-28T17:36:10.217193500Z" />
<EventRecordID>758</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="172" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">ReadyBoot</Data>
<Data Name="FileName">C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">276824064</Data>
<Data Name="MaxFileSize">20971520</Data>
</EventData>
</Event>

Error 5/28/2016 12:36:10 PM Kernel-EventTracing 3 Session
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 5/28/2016 12:36:10 PM
Event ID: 3
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: KOE-FINIX
Description:
Session "ReadyBoot" stopped due to the following error: 0xC0000188
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>3</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>14</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2016-05-28T17:36:10.217195000Z" />
<EventRecordID>759</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="172" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">ReadyBoot</Data>
<Data Name="FileName">C:\WINDOWS\Prefetch\ReadyBoot\ReadyBoot.etl</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">276824064</Data>
<Data Name="FailureReason">0</Data>
</EventData>
</Event>

Warning 5/28/2016 12:36:27 PM Kernel-EventTracing 4 Logging
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 5/28/2016 12:36:27 PM
Event ID: 4
Task Category: Logging
Level: Warning
Keywords: Session
User: SYSTEM
Computer: KOE-FINIX
Description:
The maximum file size for session "Circular Kernel Context Logger" has been reached. As a result, events might be lost (not logged) to file "C:\WINDOWS\system32\WDI\LogFiles\BootCKCL.etl". The maximum files size is currently set to 104857600 bytes.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>4</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1</Task>
<Opcode>10</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2016-05-28T17:36:27.112264100Z" />
<EventRecordID>760</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="216" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">Circular Kernel Context Logger</Data>
<Data Name="FileName">C:\WINDOWS\system32\WDI\LogFiles\BootCKCL.etl</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">41943168</Data>
<Data Name="MaxFileSize">104857600</Data>
</EventData>
</Event>

Error 5/28/2016 12:36:27 PM Kernel-EventTracing 3 Session
Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 5/28/2016 12:36:27 PM
Event ID: 3
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: KOE-FINIX
Description:
Session "Circular Kernel Context Logger" stopped due to the following error: 0xC0000188
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>3</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>14</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2016-05-28T17:36:27.112265900Z" />
<EventRecordID>761</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="216" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">Circular Kernel Context Logger</Data>
<Data Name="FileName">C:\WINDOWS\system32\WDI\LogFiles\BootCKCL.etl</Data>
<Data Name="ErrorCode">3221225864</Data>
<Data Name="LoggingMode">41943168</Data>
<Data Name="FailureReason">0</Data>
</EventData>
</Event>

Error 5/28/2016 12:36:52 PM WLAN-AutoConfig 10000 None
Log Name: System
Source: Microsoft-Windows-WLAN-AutoConfig
Date: 5/28/2016 12:36:52 PM
Event ID: 10000
Task Category: None
Level: Error
Keywords: (536870912)
User: SYSTEM
Computer: KOE-FINIX
Description:
WLAN Extensibility Module has failed to start.

Module Path: C:\WINDOWS\system32\Rtlihvs.dll
Error Code: 126

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WLAN-AutoConfig" Guid="{9580D7DD-0379-4658-9870-D5BE7D52D6DE}" />
<EventID>10000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000020000000</Keywords>
<TimeCreated SystemTime="2016-05-28T17:36:52.387019400Z" />
<EventRecordID>19433</EventRecordID>
<Correlation />
<Execution ProcessID="416" ThreadID="2816" />
<Channel>System</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="ExtensibleModulePath">C:\WINDOWS\system32\Rtlihvs.dll</Data>
<Data Name="ErrorCode">126</Data>
</EventData>
</Event>

Error 5/28/2016 12:38:54 PM DistributedCOM 10010 None
Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 5/28/2016 12:38:54 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: KOE-FINIX
Description:
The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2016-05-28T17:38:54.199994700Z" />
<EventRecordID>19434</EventRecordID>
<Correlation />
<Execution ProcessID="924" ThreadID="1164" />
<Channel>System</Channel>
<Computer>KOE-FINIX</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">{784E29F4-5EBE-4279-9948-1E8FE941646D}</Data>
</EventData>
</Event>