[Bug]: Virtual-Display-Driver causes system blue screen crash

[N0exp]

Which OS?

Win10 Pro

Which release?

22H2

Driver Version

Virtual.Display.Driver-v24.12.24-setup-x64

Device Specifications

GPU：NVIDIA A16-2Q
CPU: Intel Xeon E312xx(Sandy Bridge)

Describe the bug

After disabling the NVIDIA graphics driver in the system device manager, re-enabling the NVIDIA graphics driver will trigger a system blue screen. Without installing Virtual.Display.Driver-v24.12.24-setup-x64 and adding a monitor, this operation will not be abnormal. Checking the dump file information may be related to the LUID used by Virtual.Display.Driver

Steps to reproduce

System blue screen dump file ： 032725-16640-01.dmp

Expected behavior

No response

Log File

<vdd_settings>

1


Best GPU (Auto)



<g_refresh_rate>60</g_refresh_rate>
<g_refresh_rate>90</g_refresh_rate>
<g_refresh_rate>120</g_refresh_rate>
<g_refresh_rate>144</g_refresh_rate>
<g_refresh_rate>165</g_refresh_rate>
<g_refresh_rate>244</g_refresh_rate>



800
600
<refresh_rate>30</refresh_rate>


1366
768
<refresh_rate>30</refresh_rate>


1920
1080
<refresh_rate>30</refresh_rate>


2560
1440
<refresh_rate>30</refresh_rate>


3840
2160
<refresh_rate>30</refresh_rate>

</resolutions>
<options>
	<CustomEdid>false</CustomEdid> <!-- Custom Edid should be named "user_edid.bin"! This does not support emulating resolutions!-->
	<PreventSpoof>false</PreventSpoof> <!--Enable this to prevent manufacturer spoofing when using custom edid. Please only do so if you need to!-->
	<EdidCeaOverride>false</EdidCeaOverride> <!--Enable this to override or add hard coded cea-extension block to custom Edid support allowing you to enable HDR-->
	<HardwareCursor>true</HardwareCursor>
	<SDR10bit>false</SDR10bit>
	<HDRPlus>false</HDRPlus> <!-- If you have SDR10 bit enabled, HDRPlus wont work - there’s a conflict because the display system cannot simultaneously handle both high dynamic range 12-bit and standard dynamic range 10-bit settings. -->
	<logging>false</logging>
    <!-- DEBUG LOGGING FOR EXPERTS ONLY!-->
    <debuglogging>false</debuglogging> 
    <!-- DEBUG LOGS CAN GENERATE 1000+ LINES-->
	<!-- Warning: Leaving logging on too long can lead to excessive filesize. Especially DebugLogging, which should only be used for short periods to log errors. -->
	<!-- Logging: Useful to troubleshoot and determine which GPUs are being used, and if displays are working as intended.-->
	<!-- Debug Logging: Logs local system information with every driver function/event/process. Useful for GitHub Help Tickets.-->
</options>

</vdd_settings>

Contact Details

1007950413@qq.com