Bugcheck 0x7E with igdkmd64.sys

[Tripredacus]

Windows 7 Pro SP1 x64 image bugchecks on first boot after imaging.

Master Image

With the master image, deploying to an Asus Z97 chipset board with an i5 CPU, Windows will bugcheck on first boot with a 0x7E pointing at igdkmd64.sys. No Memory.DMP is created. This indicates that the driver currently in the image for video device VEN_8086&DEV_0402 is incorrect. Before jumping to that conclusion (because I have already done so) I wanted to take a look at what is actually happening with the OS.

%windir%\setupact.log has this info:

 

2015-06-26 05:03:25, Error                 CBS    Failed to call external evaluate applicability on package: Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11, Update: 2685813-1_neutral_LDR [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]2015-06-26 05:03:25, Info                  CBS    Failed to evaluate external applicability for package update: 2685813-297_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]2015-06-26 05:03:25, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11, Update: 2685813-297_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]2015-06-26 05:03:25, Info                  CBS    Failed to evaluate external applicability for package update: 2685813-445_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED]2015-06-26 05:03:25, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11, Update: 2685813-445_neutral_PACKAGE [HRESULT = 0x80070bc9 - ERROR_FAIL_REBOOT_REQUIRED][06/26/2015 05:03.25.352] WudfUpdate: Update process returned -2145124329.[06/26/2015 05:03.25.383] WudfUpdate: SetFakeSystemRestorePoint: Problem finalizing nested restore point - (1058)[06/26/2015 05:03.25.399] WudfUpdate: update returned error 0x80240017 - status(80240017) <no error text>.[06/26/2015 05:03.25.430] WudfUpdate: For additional information please look at the log files %windir%\windowsupdate.log and %windir%\Logs\CBS\CBS.log[06/26/2015 05:03.25.446] WudfUpdate: Cleaning up update.[06/26/2015 05:03.25.461] WudfUpdate: Error updating UMDF - status(80240017) <no error text>.  Aborting installation.

To note that most Intel 6 series and newer Asus boards have a device detected as ACPI\PNP0A0A, which is some ACPI/ASUS/AMD device. What the device does exactly, I do not know. The driver for this requires the UMDF v1.11 x64 update to be in the image. Failing to add that package and having just the driver causes an entirely different bugcheck and logs stating something like "pending primitives." The reason for mentioning this is because the KB2685813 in the logs is a UMDF update.

Some errors exist in %windir%\WindowsUpdate.log.

 

2015-06-26	05:03:18:987	 940	664	PT	WARNING: Cached cookie has expired or new PID is available2015-06-26	05:03:19:939	 940	664	Agent	WARNING: Failed to evaluate Installed rule, updateId = {C735DBB1-06B4-49F2-815F-97976B4B86A4}.102, hr = 8004100A2015-06-26	05:03:20:001	 940	664	Agent	WARNING: Failed to evaluate Installed rule, updateId = {6A8FE277-1048-48B1-803B-4580C15BBDF1}.100, hr = 8004100A2015-06-26	05:03:20:360	 940	664	Handler	FATAL: UH: 0x80070bc9: EvaluateApplicability failed in CCbs::EvaluateApplicability2015-06-26	05:03:20:360	 940	664	Agent	WARNING: Failed to evaluate Installed rule, updateId = {4D6711E4-CF8A-4F91-857E-487159ABE994}.501, hr = 80070BC92015-06-26	05:03:20:454	 940	664	Handler	FATAL: UH: 0x80070bc9: EvaluateApplicability failed in CCbs::EvaluateApplicability2015-06-26	05:03:20:454	 940	664	Agent	WARNING: Failed to evaluate Installable rule, updateId = {4D6711E4-CF8A-4F91-857E-487159ABE994}.501, hr = 80070BC92015-06-26	05:03:20:563	 940	664	Handler	FATAL: UH: 0x80070bc9: EvaluateApplicability failed in CCbs::EvaluateApplicability

%windir%\Panther\setuperr.log

 

2015-06-26 05:02:17, Error                 SYSPRP SPPNP: Error 0x25 (CONFIGRET) occurred while determining the buffer size needed to hold the list of devices that are using service iusb3xhc.2015-06-26 05:02:17, Error                 SYSPRP SPPNP: Error 0x424 occurred while opening a handle to the service iusb3xhc.[gle=0x00000424]

Here is a different error relating to the Intel USB 3.0 Driver. These errors are not in the setupact.log.

Image 2

I previously mentioned something about not jumping to conclusions. Image 2 was created because I did just that, figuring that the Intel Video driver (mentioned in the bugcheck) was the cause. Image 2 is the Master image with all Intel video drivers removed.

EDIT: I made an error and never actually had deployed Image 2 yet.

Link to Memory.dmp here:

https://onedrive.live.com/redir?resid=DF9CED75545B2B97!221&authkey=!AKRMa8G2HsY3zns&ithint=file%2cDMP

With both of these images, the OS will boot fine if I put a non-Intel video card in the system. To note I only put Intel video drivers in Win7 images.

Edited June 26, 2015 by Tripredacus