Bsod
 

I've only seen the PAGE_FAULT_IN_NONPAGED_AREA(dlkmd.sys) once.

I can repeat the BSOD with no issue but it is either: VIDEO_SCHEDULER_INTERNAL_ERROR or VIDEO_TDR_FAILURE(igdkmd64.sys)

I noticed the support tool has logging functions. Is that something we can try?

Thanks for clarifying - I will be sure to get back to you if we need extra logging thanks

I'll see if I can repro this tomorrow.

Thanks,
James

@mausland

Hi,

No luck reproducing so far.

I have a Surface Pro 3 with identical BIOS, OS, graphics driver plus the Surface Pro 3 dock but no BSOD.

Have tried a variety of monitors, docks and adapters but no go so far.

Will see if installing the Enterprise version of Windows 10 makes any difference (I have the Pro version installed).

Just a thought, do you have all the latest Windows Updates installed?

Thanks,
James

Bsod
 

Yes, I have the latest updates.

Not sure what to do next. Do you have the dmp files? Do they tell you anything?

Also, I tried uninstalling the Intel driver from device manager and re-downloaded through WU. Same issue.

Hi,

I've raised this internally for further investigation.

To help me try and reproduce it can you let me know:
- What was your display layout? Both external monitors extending?
- Which ports are the DP and USB monitors connected to? Those on the dock or those on the Surface Pro 3 itself?

I will also try on a slower Core i3 SP3 to see if it is timing related. I note you have the i5 variant (the one I'm using is i7).

Thanks,
James

Display configuration
 

Display configuration:

• Surface in the dock
• Display 1 (surface monitor) disconnected
• Display 2 – display port – primary monitor – connected to dock display port – VGA to display port adapter
• Display 3 – USB port – connected to USB 3 port on back of dock (have tried both USB 2 and 3 ports) – DVI into Displaylink
• Desktop extended across display 2 and 3

@mausland

Hi,

I think what you seeing is the same as has been posted on this Microsoft forum:
http://answers.microsoft.com/en-us/w...b-015507ed0c94

It looks to be an issue with the operating system; I would encourage you add you findings to this thread.

Thanks,
James