0x00000113 bsod during Nvidia driver update/removal

I am now on the 3rd fresh install of Windows 10 Pro 64bit, today was a new Nvidia driver update which I tried to update ending in bsod during "driver removal" part of the Nvidia setup:

Code:

Microsoft (R) Windows Debugger Version 10.0.10240.9 AMD64Copyright (c) Microsoft Corporation. All rights reserved.     Loading Dump File [C:TempMEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.     ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred srv*c:cache*http://msdl.microsoft.com/download/symbols Symbol search path is: srv*c:cache*http://msdl.microsoft.com/download/symbols Executable search path is:  No .natvis files found at C:Program Files (x86)Windows Kits10Debuggersx64Visualizers. Windows 10 Kernel Version 10240 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10240.16430.amd64fre.th1.150807-2049 Machine Name: Kernel base = 0xfffff802`c061e000 PsLoadedModuleList = 0xfffff802`c0943030 Debug session time: Thu Aug 13 21:40:26.830 2015 (UTC + 2:00) System Uptime: 0 days 0:12:23.544 Loading Kernel Symbols ............................................................... ................................................................ ......................................................... Loading User Symbols   ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************   Use !analyze -v to get detailed debugging information.   BugCheck 113, {1f, ffffe001a1e8ab80, 0, 0}   Probably caused by : dxgkrnl.sys ( dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f )   Followup: MachineOwner ---   5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************   VIDEO_DXGKRNL_FATAL_ERROR (113) The dxgkrnl has detected that a violation has occurred. This resulted in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl is attempting to get enough information into the minidump such that somebody can pinpoint the crash cause. Any other values after parameter 1 must be individually examined according to the subtype. Arguments: Arg1: 000000000000001f, The subtype of the bugcheck: Arg2: ffffe001a1e8ab80 Arg3: 0000000000000000 Arg4: 0000000000000000   Debugging Details: ------     SYSTEM_SKU: To Be Filled By O.E.M.   SYSTEM_VERSION: To Be Filled By O.E.M.   BIOS_DATE: 07/01/2013   BASEBOARD_PRODUCT: Z77 Extreme6   BASEBOARD_VERSION:    BUGCHECK_P1: 1f   BUGCHECK_P2: ffffe001a1e8ab80   BUGCHECK_P3: 0   BUGCHECK_P4: 0   CPU_COUNT: 8   CPU_MHZ: d48   CPU_VENDOR: GenuineIntel   CPU_FAMILY: 6   CPU_MODEL: 3a   CPU_STEPPING: 9   DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT   BUGCHECK_STR: 0x113   PROCESS_NAME: System   CURRENT_IRQL: 0   ANALYSIS_VERSION: 10.0.10240.9 amd64fre   LAST_CONTROL_TRANSFER: from fffff8004aac3c3d to fffff802c076bd00   STACK_TEXT:  ffffd000`2077b828 fffff800`4aac3c3d : 00000000`00000113 00000000`0000001f ffffe001`a1e8ab80 00000000`00000000 : nt!KeBugCheckEx ffffd000`2077b830 fffff800`4b3dc63f : ffffe001`a1e8ab80 ffffe001`a55b8401 ffffe001`a55b8470 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xcd ffffd000`2077b870 fffff800`4e55fe3f : ffffe001`a1f14ba0 ffffd000`2077b9a0 ffffe001`a55b8470 ffffe001`a1ebc840 : dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x8f ffffd000`2077b8a0 fffff800`4e56531b : ffffe001`a1f0b000 ffffffff`00000000 ffffc001`0da52f30 ffffe001`a55b8470 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xa3f ffffd000`2077ba40 fffff800`4e568f5d : ffffe001`a1f0b000 ffffe001`a1f0b000 00000000`00000000 ffffd000`2077bb99 : dxgmms2!VIDMM_WORKER_THREAD::ProcessPendingTerminations+0xa3 ffffd000`2077baf0 fffff802`c0704948 : ffffe001`9e995800 ffffd000`2077bc00 fffff802`c0981100 fffff802`c0770d00 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x9c1 ffffd000`2077bc00 fffff802`c0770de6 : fffff802`c0981180 ffffe001`a1ebc840 fffff802`c09f7740 00000000`00000000 : nt!PspSystemThreadStartup+0x58 ffffd000`2077bc60 00000000`00000000 : ffffd000`2077c000 ffffd000`20776000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16     STACK_COMMAND: kb   FOLLOWUP_IP:  dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f fffff800`4b3dc63f eb03 jmp dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+0x94 (fffff800`4b3dc644)   SYMBOL_STACK_INDEX: 2   SYMBOL_NAME: dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete+8f   FOLLOWUP_NAME: MachineOwner   MODULE_NAME: dxgkrnl   IMAGE_NAME: dxgkrnl.sys   DEBUG_FLR_IMAGE_TIMESTAMP: 55bebfed   BUCKET_ID_FUNC_OFFSET: 8f   FAILURE_BUCKET_ID: 0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete   BUCKET_ID: 0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete   PRIMARY_PROBLEM_CLASS: 0x113_dxgkrnl!ADAPTER_RENDER::NotifyDeferredDestructionComplete   ANALYSIS_ KM   FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!adapter_render::notifydeferreddestructioncomplete   FAILURE_ID_HASH: {5460b617-b6dd-456e-0f7a-45a24c5cf63d}   Followup: MachineOwner ---

Doing a 1st fresh install works fine, but updating (bsod happens the moment the nvidia setup wants to remove the old driver) or removing the driver always ends in this bsod. Hope someone can sort this out whats going on. If I google about this sorted in last months I cant find anything about it, so I guess it's a really rare bug.

Solved it. Got a tip in another forum. The problem seems to be a bug in Windows (10) or Intel drivers or combination of them with Nvidia driver when you have the on-board Intel GPU activated too. I had this because of using QuickSync sometimes.

The bsod is triggered the moment when Nvidia setup removes its own older drivers, and it seems at this point Windows trys to switch to the 2nd on-board GPU (an HD4000), and bam, bluescreen. Maybe it's because HD4000 is DX11 and GTX970 is DX12 and theres a bug in Windows which triggers this. Anyway... the fix is simple:

Deactivate the on-board Intel GPU in bios, check in device manager if GForce is only graphics card installed/active. Do the Nvidia setup and it will run through without bluescreen.

I wont report this to neither MS or Intel, because it's a waste of time and they wont fix it anyway, or even read bug reports.

Thanks for letting us know, that's great information. Glad you got it sorted.