Windows 10 kernal failure

[techneutral]

Thanks James, that link appears to only point to the support tool to gather information. However I was able to find the cleaning tool from a different link. Unfortunately I still had the same results. I ran the data collection from the support utility again. I am unable to run the utility with the DisplayLink 4k plug and play adapter plugged in because my computer blue screens and gives the page fault error shortly after plugging the device in. Anyway here is an updated copy of the logs.

[JamesH]

Hi,

Thanks for this info.

Just to make sure I have got this right, please check if these steps are correct:

1. You had Windows 8.1 Professional installed
2. You upgraded to Windows 10 (with the Dell D3100 dock attached)
3. During the upgrade the DisplayLink driver was updated to 7.9 M0
4. After the Windows 10 upgrade completed, the screen went black (with just the mouse cursor appearing) and then you got the BSOD
5. The only way to not get the BSOD is to keep the Dell D3100 unplugged

Thanks,
James

[techneutral]

Hey James, I wanted to provide an update, all of the above information appears to be correct except for bullet point 5. It appears that eventually windows gives up on installing the video drivers for the display link adapter. When it does not attempt to install the video portion it will let me have the device plugged in, and it will pass keyboard, mouse, and network.

So it appears that it is just the video portion of the device that is causing the issues.

[ChrisGonzo]

Hi,
I have the same issue on a E7450 with Intel 5500 Graphics card.
I made an Win10 update from the DELL Win7 factory image withouit having DisplayLink installed on the system.
During DisplayLink installation i connected the DisplayLink Adapter on request of the 7.9 driver software and got the BSOD "Page_Fault_in_Nonpaged_area (dlkmd.sys)". After a restart the monitor connected with the DisplayLink Adapter stays black, Windows does not find the monitor even when the DisplayLink Adapter is connected with a green light.
Here is my support file:

[techneutral]

Hey James, is there any update on this? I am still unable to use my DisplayLink adapter to output video.

[Garfunko]

I am having the same issue. I was able to get the screen to work finally for a second when I used the RC version 7.9 RC, but then the screen flickered and BSOD was reborn.

[JamesH]

Hi,

Can you try installing DisplayLink v7.9 M2 software?

Thanks,
James

[techneutral]

Hey James, I tried v 7.9 m2 and I continue to receive the BSOD. Before installing the software I uninstalled the previous version of the software, rebooted, installed the new version of the software. I received the same error on the blue screen (page fault in Non paged area)

I have included Several windows logs below that look like they may be relevant. There was one that looked like it may be something that I can change that may have an impact which was allowing for interactive services. I am going to try reinstalling the software again and report back with results once I have changed settings for interactive services. In the meantime here is a large dump of some windows logs that may be relevant.

Here are 2 Windows application Log entries that look like they may be particularly relevant. These entries only occur prior to the bluescreen after the install of the Display Link Software. These services look like they may be the native video and audio drivers for the laptop but the Display link software crashes them every time.

First Entry - Video

The description for Event ID 0 from source igfxCUIService2.0.0.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Service started/resumed

Second Entry - Audio

The description for Event ID 0 from source RtkI2SAudioService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

RtkI2SAudioService
InitSensorAPI = FALSE


Here are the System Logs that may be relevant

Next Entry

Display driver igfx stopped responding and has successfully recovered.

Next Entry

The description for Event ID 267 from source Win32k cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:


The specified resource type cannot be found in the image file

Next Entry

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{05D1D5D8-18D1-4B83-85ED-A0F99D53C885}
and APPID
{AD65A69D-3831-40D7-9629-9B0B50A93843}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The DisplayLinkManager service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly.

Next Entry

The access history in hive \??\C:\WINDOWS\system32\config\elam was cleared updating 2 keys and creating 2 modified pages.

Here is the entry in the application log that shows the BSOD

Fault bucket LKD_0x141_Tdr:6_IMAGE_igdkmd64.sys, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: cb18be7c-98f8-44fb-8ebf-52e744a6af9d

Problem signature:
P1: 141
P2: ffffe001405094c0
P3: fffff800c3366550
P4: 0
P5: 2bc
P6: 10_0_10240
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
C:\Windows\LiveKernelReports\WATCHDOG\WD-20150902-1007-02.dmp
C:\Users\bmfuller\AppData\Local\Temp\WER-358359-0.sysdata.xml
C:\Users\bmfuller\AppData\Local\Temp\WER969A.tmp.W ERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive \Kernel_141_298675f88f3fed8ce3645d7f9d93bd82673e9c _00000000_cab_20cfd6f5

Analysis symbol:
Rechecking for solution: 0
Report Id: 4574fc7a-5184-11e5-8298-acd1b8c0abf2
Report Status: 0
Hashed bucket: