Windows 10: VIDEO DXGKRNL FATAL ERROR trying to install Creator Fall update

I removed the NI IEE488 drivers, the Minitool Partition Wizard, and Windriver. I then retried the upgrade. which failed again with the reboot loop after a failure (which I think was another DXGKRNL_FATAL_ERROR). I'm now copying the install partition for diagnosis and will try a clean install of the fall update from the CD. This stinks of a fundamental problem with the AMD drivers and new Directx code.

Dave

 

Please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums

And post any new Panther log files.

 

Well that was strange - I deleted all partitions on the first drive and did a trial clean install which seemed to work just fine and then restored my previous install on top of that to collect some information I wanted.

I then deleted all partitions from the first drive again and re-ran the clean install (booted from install CD). If failed almost immediately after showing the desktop for the first time on the final boot with VIDEO_DXGKRNL_FATAL_ERROR and then rebooted, and repeated the same error and rebooted etc...

I tried again and got the same problem!!! Don't understand why it worked one time, but failed on subsequent attempts *Sad

I managed to boot up into Safe mode showing Build 16299.rs3_release.170928-1534 and have run DM Log collector.

Here's the data ...

DESKTOP-VPJ2KOS-14_12_2017_164012_91.zip

Dave

 

Further update I booted to safe mode again and uninstalled the ATI (AMD) 8.970.100.9001 level driver that was installed by W10 Fall Update installation, and set Windows to not auto update drivers.

I then rebooted and was able to get a good login screen and desktop at 1024*768 with the MS Basic Display Adapter. Not long after the ATI FireGL V7600 driver level was automatically installed (Huh!???). and I got a 1920*1200 desktop.... So far so good, but on reboot, you can guess what happened: VIDEO_DXGKRNL_FATAL_ERROR!! at the point where the login screen would be displayed.

Looks like the AMD driver level 8.970.100.9001 is SNAFUed.

Dave

 

There was 1 BSOD mini dump.
The bugcheck was 113.
Debugging did not display a definitive driver.

The VIDEO_DXGKRNL_FATAL_ERROR bug check has a value of 0x00000113. This indicates that the Microsoft DirectX graphics kernel subsystem has detected a violation


Run FurMark -
Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
Aim for testing 1 hour and abort testing as needed for freezing, display artifacts, and temperature.
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Performance Maintenance Tutorials





Code: 14/12/2017 16:24 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 113 P2: 20 P3: ffffce0647904010 P4: ffff P5: 0 P6: 10_0_16299 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\Windows\Minidump\121417-12125-01.dmp \\?\C:\Windows\TEMP\WER-59125-0.sysdata.xml \\?\C:\Windows\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1102.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_113_6ffbf2bded74f7baf0b2a119edc027a168e6b7ae_00000000_cab_02791112 Analysis symbol: Rechecking for solution: 0 Report ID: fddfc0f3-d629-4701-87b9-eb9d99060468 Report Status: 4 Hashed bucket:[/quote]

 

Read my post more carefully this is a reboot loop. I can't run Furmark. This is a SNAFUed video driver.

I've just bought an Nvidia Quadro K4000 video card which should arrive in a day or two. In the meantime I've restored the system from the backup.

I don't expect to put any more work into this using the current video card.

Dave

 

See what happens if you boot without the malfunctioning video card.

 

I don't have another video card right now so can't boot w/o it (this mobo doesn't have Intel embedded graphics). Pretty certain failure is in driver, not card as works fine on Creators Edition and also similar problems reported on AMD forums with this driver level and Fall Update.

 

The quadro are good cards. This is a link for the older drivers: Older AMD drivers: Previous

 

I already tried uninstalling the "new" driver and installing the driver level I was using with Creator Edition. That failed identically, so my suspicion is that some change in Directx at this level is no compatible with these "legacy" drivers. To be slightly fair to AMD, the V7600 is now ten years old.

Anyway I've got an NVidia Quadro K4000 on the way and hope this will fix all.

Dave

 

By way of an update on this. the nVidia K4000 card arrived. I removed the graphics drivers using DDU http://www.guru3d.com/files-details/...-download.html and installed the new card.

The update to level 1709 went fine, so this was a problem with the Windows supplied AMD driver for the V7600.

HtH
Dave

 

That's great news.
If you have any problems please post a new zip for review:
log collector v2-beta06.zip