Persistent BSOD After Intel UHD 630 Driver Install on Windows 10 – Works on Other Partition

[emicmvo]

Hello Sysnative Team,


I’m dealing with a persistent BSOD issue tied to the Intel UHD Graphics 630 driver on one Windows 10 installation. I’d really appreciate your help identifying the root cause.

System Specs:​

• Laptop: HP HP ZBook 15 G5 (dual boot configuration)
• CPU: Intel Core i5-8300H @ 2.30GHz, 4 cores / 8 threads
• GPU: Intel UHD Graphics 630
• RAM: 16GB
• OS: Windows 10 Pro (latest updates)

Problem Summary:​

• When I install the Intel UHD Graphics driver (either via HP Support, Intel site, or Intel Driver Assistant), I immediately get a blue screen (BSOD) either during or right after installation.
• I can only recover by booting into Safe Mode, using DDU to uninstall the driver, and reverting to Microsoft Basic Display Adapter.
• However, after a reboot, Windows Update automatically reinstalls the Intel driver, triggering the BSOD again.

Notable Clues:​

• On a second Windows 10 partition (same laptop), driver version 30.0.101.1340 runs without issue.
• I’ve tried:
  
  • Versions 31.0.101.2130 and 30.0.101.1340
  • Running sfc /scannow, DISM, and chkdsk – no issues found
• Event Viewer shows:
  
  • Event ID 7023 for Intel(R) Content Protection HECI Service and CPHS services failing with unspecified errors.
• Minidumps (analyzed with WinDBG) consistently reference igdkmdn64.sys as the culprit.

Suspicions:​

• Possible conflict with another driver or background service.
• Something in this specific Windows installation is incompatible with the Intel GPU driver.

Available:​

• Logs at following link: Microsoft OneDrive

I’d greatly appreciate help in identifying the conflicting component or steps I can take to fully isolate and resolve the issue.


Thank you for your time and assistance!


Best regards,
Michel

 

[ET_Explorer]

Hi @

emicmvo, welcome to sysnative forums!​

System info > Problem Devices:

Bus controller SM PCI\VEN_8086&DEV_A323&SUBSYS_842A103C&REV_10\3&11583659&0&FC The drivers for this device have not been installed.
Périphérique PCI PCI\VEN_10EC&DEV_525A&SUBSYS_842A103C&REV_01\4&2D95FA0&0&00E0 The drivers for this device have not been installed.
Périphérique PCI PCI\VEN_8086&DEV_A324&SUBSYS_842A103C&REV_10\3&11583659&0&FD The drivers for this device have not been installed.
PCI data acquisition and signal controller PCI\VEN_8086&DEV_A379&SUBSYS_842A103C&REV_10\3&11583659&0&90 The drivers for this device are not installed.

 

[emicmvo]

Hi @

emicmvo, welcome to sysnative forums!​

System info > Problem Devices:

Bus controller SM PCI\VEN_8086&DEV_A323&SUBSYS_842A103C&REV_10\3&11583659&0&FC The drivers for this device have not been installed.
Périphérique PCI PCI\VEN_10EC&DEV_525A&SUBSYS_842A103C&REV_01\4&2D95FA0&0&00E0 The drivers for this device have not been installed.
Périphérique PCI PCI\VEN_8086&DEV_A324&SUBSYS_842A103C&REV_10\3&11583659&0&FD The drivers for this device have not been installed.
PCI data acquisition and signal controller PCI\VEN_8086&DEV_A379&SUBSYS_842A103C&REV_10\3&11583659&0&90 The drivers for this device are not installed.

Hello @ET_Explorer ,

Thank you very much for your answer. Are the above device causing the BSOD? Are these the reasons I am not able to install the Intel GPU Driver?

 

[emicmvo]

Hi @

emicmvo, welcome to sysnative forums!​

System info > Problem Devices:

Bus controller SM PCI\VEN_8086&DEV_A323&SUBSYS_842A103C&REV_10\3&11583659&0&FC The drivers for this device have not been installed.
Périphérique PCI PCI\VEN_10EC&DEV_525A&SUBSYS_842A103C&REV_01\4&2D95FA0&0&00E0 The drivers for this device have not been installed.
Périphérique PCI PCI\VEN_8086&DEV_A324&SUBSYS_842A103C&REV_10\3&11583659&0&FD The drivers for this device have not been installed.
PCI data acquisition and signal controller PCI\VEN_8086&DEV_A379&SUBSYS_842A103C&REV_10\3&11583659&0&90 The drivers for this device are not installed.

Hello @ET_Explorer ,

After installing all above mentioned drivers (ref attached), I tried updating the GPU driver to the intel UHD 630 one but i am still getting the BSOD after installation.

The issue keeps happening.

 

[axe0]

When did the problem start?

What's the dual boot for?

 

[ubuysa]

Looking at several (but not all) of the dumps (which are identical) I think that the problem may lie in the registry. In this stack trace, which you read from the bottom up, we see registry operations in support of the installation taking place (in blue below) immediately before the page fault (in red below) that causes the BSOD..

0xfffff302f0fe5e88 : 0xfffff80046c0e052 : nt!KiPageFault+0x452
0xfffff302f0fe5e90 : 0xffffba88069dd000 :  Trap @ fffff302f0fe5e90
0xfffff302f0fe5f20 : 0x007300730061006c :  !du "lass\{4d36e968-e325-11ce"
0xfffff302f0fe5f28 : 0x00640034007b005c :  !du "\{4d36e968-e325-11ce"
0xfffff302f0fe5f30 : 0x0039006500360033 :  !du "36e968-e325-11ce"
0xfffff302f0fe5f38 : 0x0065002d00380036 :  !du "68-e325-11ce"
0xfffff302f0fe5f40 : 0x002d003500320033 :  !du "325-11ce"
0xfffff302f0fe6048 : 0xfffff80046e2db64 : nt!ObpFreeObject+0x194
0xfffff302f0fe60a8 : 0xfffff80046e2d978 : nt!ObpRemoveObjectRoutine+0x88
0xfffff302f0fe60e8 : 0xfffff80046a334da : nt!KiUnstackDetachProcess+0x17a
0xfffff302f0fe6108 : 0xfffff80046a5ac67 : nt!ObfDereferenceObjectWithTag+0xc7
0xfffff302f0fe6148 : 0xfffff80046e331e7 : nt!ObCloseHandleTableEntry+0x6d7
0xfffff302f0fe6808 : 0xfffff80046ab18f9 : nt!RtlpHpSegMgrCommit+0x1f9
0xfffff302f0fe68d8 : 0xfffff80046ab15b9 : nt!RtlpHpSegPageRangeCommit+0x219
0xfffff302f0fe6978 : 0xfffff80046ab0a58 : nt!RtlpHpSegAlloc+0x118
0xfffff302f0fe69c0 : 0xfffff80046800000 : "nt!VrpRegistryString <PERF> (nt+0x0)"
0xfffff302f0fe69d8 : 0xfffff80046a4c5ea : nt!ExAllocateHeapPool+0xb9a
0xfffff302f0fe6a70 : 0xfffff80047416b08 : nt!ExpTaggedPoolLock
0xfffff302f0fe6b18 : 0xfffff800471b7074 : nt!ExAllocatePoolWithTag+0x64
0xfffff302f0fe6c78 : 0xfffff8005eadc8c0 :  !du "EnableHeciKmdDirect"
0xfffff302f0fe6c88 : 0xffffba880324f010 :  !du "\REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\igfx\Parameters"
0xfffff302f0fe6d08 : 0xfffff8005eac77d0 :  !du "ReturnWithStatus"
0xfffff302f0fe6d18 : 0xffffba880324f010 :  !du "\REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\igfx\Parameters"
0xfffff302f0fe6d98 : 0xfffff8005eac51b0 :  !du "\Registry\machine\System\CurrentControlSet\Services\iAlm\Device0"
0xfffff302f0fe6da8 : 0xfffff8005eac7590 :  !du "\REGISTRY\MACHINE\SOFTWARE\Intel\Display\igfxcui\MediaKeys"
0xfffff302f0fe6db8 : 0xfffff80046800000 : "nt!VrpRegistryString <PERF> (nt+0x0)"

I'm wondering whether there is a corruption in the registry of that Windows 10 installation in the Intel graphics driver area (that's where these registry access are)...?

 

[emicmvo]

When did the problem start?

What's the dual boot for?

The laptop is set up in dual boot with two Windows installations:

• The first is the factory-installed system that came with the HP ZBook 15 G5.
• The second is a system I migrated from another laptop that had a hardware failure.

The problem occurs only on the migrated installation.


After installing the migrated drive into the ZBook, Windows began updating drivers automatically. At one point, I was prompted to authorize a GPU driver update, which I did using the Intel Driver & Support Assistant downloaded from Intel’s official website.


The first blue screen (BSOD) happened immediately after the system attempted to update the GPU driver.

 

[emicmvo]

Looking at several (but not all) of the dumps (which are identical) I think that the problem may lie in the registry. In this stack trace, which you read from the bottom up, we see registry operations in support of the installation taking place (in blue below) immediately before the page fault (in red below) that causes the BSOD..

0xfffff302f0fe5e88 : 0xfffff80046c0e052 : nt!KiPageFault+0x452
0xfffff302f0fe5e90 : 0xffffba88069dd000 :  Trap @ fffff302f0fe5e90
0xfffff302f0fe5f20 : 0x007300730061006c :  !du "lass\{4d36e968-e325-11ce"
0xfffff302f0fe5f28 : 0x00640034007b005c :  !du "\{4d36e968-e325-11ce"
0xfffff302f0fe5f30 : 0x0039006500360033 :  !du "36e968-e325-11ce"
0xfffff302f0fe5f38 : 0x0065002d00380036 :  !du "68-e325-11ce"
0xfffff302f0fe5f40 : 0x002d003500320033 :  !du "325-11ce"
0xfffff302f0fe6048 : 0xfffff80046e2db64 : nt!ObpFreeObject+0x194
0xfffff302f0fe60a8 : 0xfffff80046e2d978 : nt!ObpRemoveObjectRoutine+0x88
0xfffff302f0fe60e8 : 0xfffff80046a334da : nt!KiUnstackDetachProcess+0x17a
0xfffff302f0fe6108 : 0xfffff80046a5ac67 : nt!ObfDereferenceObjectWithTag+0xc7
0xfffff302f0fe6148 : 0xfffff80046e331e7 : nt!ObCloseHandleTableEntry+0x6d7
0xfffff302f0fe6808 : 0xfffff80046ab18f9 : nt!RtlpHpSegMgrCommit+0x1f9
0xfffff302f0fe68d8 : 0xfffff80046ab15b9 : nt!RtlpHpSegPageRangeCommit+0x219
0xfffff302f0fe6978 : 0xfffff80046ab0a58 : nt!RtlpHpSegAlloc+0x118
0xfffff302f0fe69c0 : 0xfffff80046800000 : "nt!VrpRegistryString <PERF> (nt+0x0)"
0xfffff302f0fe69d8 : 0xfffff80046a4c5ea : nt!ExAllocateHeapPool+0xb9a
0xfffff302f0fe6a70 : 0xfffff80047416b08 : nt!ExpTaggedPoolLock
0xfffff302f0fe6b18 : 0xfffff800471b7074 : nt!ExAllocatePoolWithTag+0x64
0xfffff302f0fe6c78 : 0xfffff8005eadc8c0 :  !du "EnableHeciKmdDirect"
0xfffff302f0fe6c88 : 0xffffba880324f010 :  !du "\REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\igfx\Parameters"
0xfffff302f0fe6d08 : 0xfffff8005eac77d0 :  !du "ReturnWithStatus"
0xfffff302f0fe6d18 : 0xffffba880324f010 :  !du "\REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\igfx\Parameters"
0xfffff302f0fe6d98 : 0xfffff8005eac51b0 :  !du "\Registry\machine\System\CurrentControlSet\Services\iAlm\Device0"
0xfffff302f0fe6da8 : 0xfffff8005eac7590 :  !du "\REGISTRY\MACHINE\SOFTWARE\Intel\Display\igfxcui\MediaKeys"
0xfffff302f0fe6db8 : 0xfffff80046800000 : "nt!VrpRegistryString <PERF> (nt+0x0)"

I'm wondering whether there is a corruption in the registry of that Windows 10 installation in the Intel graphics driver area (that's where these registry access are)...?

I also suspected similar issue, how can i troubleshoot and confirm/correct this?

 

[emicmvo]

I also suspected similar issue, how can i troubleshoot and confirm/correct this?

Note that when i get to the BSOD stage, I usually recover by booting into Safe Mode, using DDU (Display Driver Uninstaller) to uninstall the Intel driver, and reverting to Microsoft Basic Display Adapter.

I believe DDU normally resets the registry and all faulty information there????

 

[ubuysa]

• The second is a system I migrated from another laptop that had a hardware failure.

The problem occurs only on the migrated installation.

That may well be the problem. It's never wise to move (migrate) a Windows installation from one system to another. Many of the drivers on the old system will be wrong (chipset drivers for example). In addition Windows configures itself at install time for the hardware platform it's being installed on to. If you migrate that installation to another hardware platform the installation configurations, many of which will be registry based, will no longer be valid and may well cause issues.