[SOLVED] Pc keeps crashing with dedicated GPU, managed to play fortnite best setting with gpu output through igpu hdmi

Oct 8, 2019
3
0
10
I will make a list of the observations because I cannot organize them in a descriptive text
Computer has Nvidia Gtx1060 6gb gigabyte.
Crashes happens only when pc is in gpu output.
When crash occurs, sometimes it reboots again to gpu output and crashing when os is full loaded, else it boots directly to igpu.
pc has 2 hdmi outputs(from gpu and from motherboard) to same monitor to make easier life with this trouble.
Ofcourse pc worked totally fine for i guess 1-2years
month ago the problem occured but left alone at the point i forgot about it
When i decided i wanted to play with igpu cause gpu is trouble,i was hdm1 that was the safe output, and i couldn't believe when it worked totally fine with best setting(no crashes happened).It's impossible to make gpu output through igpu right?This has happened only once
Rightclick on desktop shows nvidia settings, sometimes not (this only in igpu mode).
tried to clean unistall with ddu and then clean install without geforce experience to keep everything minimal.problem still occurs
when crashes occurs, sometimes it reboots itself with no output from gpu (and there i was sure in bios was set priority to pcie gpu)
setting duplicate on video output,made me possible to switch to hdmi2(from the monitor) to play with gpu, but fps were very low with minimal setting and it crashed.During the crash where the game freezed with whole pc, i headed back to hdmi1 and noticed there was windows blue screen and it got some bug report.

screen 1
screen 2
-EventData

BugcheckCode0

BugcheckParameter10x0

BugcheckParameter20x0

BugcheckParameter30x0

BugcheckParameter40x0

SleepInProgress0

PowerButtonTimestamp132137472402597981

BootAppStatus0

Checkpoint0

ConnectedStandbyInProgressfalse

SystemSleepTransitionsToOn0

CsEntryScenarioInstanceId0

BugcheckInfoFromEFIfalse

CheckpointStatus0

CPU: Intel Core i5-6600 (Skylake-S, R0)
3300 MHz (33.00x100.0) @ 800 MHz (8.00x100.0)
Motherboard: ASRock H170M Pro4S
BIOS: P7.20, 11/30/2016
Chipset: Intel H170 (Skylake PCH-H)
Memory: 8192 MBytes @ 1066 MHz, 14-14-14-35
- 4096 MB PC17000 DDR4 SDRAM - Kingston KHX2133C14D4/4G
- 4096 MB PC17000 DDR4 SDRAM - Kingston KHX2133C14D4/4G
Graphics: Intel HD Graphics 530 (Skylake-S GT2) - Integrated Graphics Controller [S0/R0] [ASRock]
Intel HD Graphics 530, 1024 MB
Drive: WDC WD10EZEX-00BN5A0, 976.8 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: Crucial_CT275MX300SSD1, 268.6 GB, Serial ATA 6Gb/s @ 6Gb/s
Drive: HL-DT-ST DVDRAM GH24NSC0, DVD+R DL
Sound: Intel Skylake PCH-H - High Definition Audio Controller
Network: Intel Ethernet Connection I219-V
Network: Atheros AR9287 Wireless Network Adapter
OS: Microsoft Windows 10 Home (x64) Build 18362.388 (1903/May 2019 Update)
The error
XML:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
  <EventID>41</EventID>
  <Version>6</Version>
  <Level>1</Level>
  <Task>63</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8000400000000002</Keywords>
  <TimeCreated SystemTime="2019-09-23T21:22:21.584974100Z" />
  <EventRecordID>3493</EventRecordID>
  <Correlation />
  <Execution ProcessID="4" ThreadID="8" />
  <Channel>System</Channel>
  <Computer>DESKTOP-GOMO62Q</Computer>
  <Security UserID="S-1-5-18" />
  </System>
- <EventData>
  <Data Name="BugcheckCode">0</Data>
  <Data Name="BugcheckParameter1">0x0</Data>
  <Data Name="BugcheckParameter2">0x0</Data>
  <Data Name="BugcheckParameter3">0x0</Data>
  <Data Name="BugcheckParameter4">0x0</Data>
  <Data Name="SleepInProgress">0</Data>
  <Data Name="PowerButtonTimestamp">132137472402597981</Data>
  <Data Name="BootAppStatus">0</Data>
  <Data Name="Checkpoint">0</Data>
  <Data Name="ConnectedStandbyInProgress">false</Data>
  <Data Name="SystemSleepTransitionsToOn">0</Data>
  <Data Name="CsEntryScenarioInstanceId">0</Data>
  <Data Name="BugcheckInfoFromEFI">false</Data>
  <Data Name="CheckpointStatus">0</Data>
  </EventData>
  </Event>
 
Solution
ok so right click on hd graphics and uninstall it. Then click on gtx 1060 and see if it says enable device. If so click on that. Let me know what the small box says if it isn't listed. You may have to uninstall it and reinstall it.
This is an error report from the computer shutting down incorrectly. Either by power loss, using power switch to shutdown etc. Go to device manager and see what is listed under your display adapters. Let me know what is says. Also are there any yellow triangles in the device manager listings?
 
under device manager, after cold boot it detects both gpus, while after the crash it only detects igpu. I've managed to find the memory dump that should be very detailed about the crash, i hope you can see it better than me, thanks for trying.
Code:
Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff807`13400000 PsLoadedModuleList = 0xfffff807`13848210
Debug session time: Thu Oct 10 22:03:21.416 2019 (UTC + 2:00)
System Uptime: 0 days 0:13:07.083
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
1: 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: 0000000000000019, The subtype of the bugcheck:
Arg2: 0000000000000002
Arg3: 00000000000010de
Arg4: 0000000000001c03

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  To Be Filled By O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  P7.20

BIOS_DATE:  11/30/2016

BASEBOARD_MANUFACTURER:  ASRock

BASEBOARD_PRODUCT:  H170M Pro4S

BASEBOARD_VERSION:                      

DUMP_TYPE:  1

BUGCHECK_P1: 19

BUGCHECK_P2: 2

BUGCHECK_P3: 10de

BUGCHECK_P4: 1c03

CPU_COUNT: 4

CPU_MHZ: cf0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: C6'00000000 (cache) C6'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x113

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-GOMO62Q

ANALYSIS_SESSION_TIME:  10-10-2019 22:10:30.0026

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8071af841a0 to fffff807135c1220

STACK_TEXT:
ffff8988`ae51f2d8 fffff807`1af841a0 : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
ffff8988`ae51f2e0 fffff807`1aea42e7 : ffffa78a`9c3bd117 ffffa78a`9c3bd180 ffffa78a`9c3bd180 ffffa78a`9c3bd117 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8988`ae51f320 fffff807`1ad7c139 : ffff8988`ae51f400 ffffa78a`9c3bd117 ffffa78a`9c3bd030 00000000`00000000 : dxgkrnl!DpiFdoHandleSurpriseRemoval+0x167
ffff8988`ae51f360 fffff807`1ad3bcaa : ffffa78a`9c3bd030 ffffa78a`a3077010 ffffa78a`a3077010 fffff807`1335e848 : dxgkrnl!DpiFdoDispatchPnp+0xb9
ffff8988`ae51f410 fffff807`1dc4993d : ffffa78a`9c402000 00000000`00000000 ffffa78a`9c402000 00000000`3880a847 : dxgkrnl!DpiDispatchPnp+0xea
ffff8988`ae51f530 fffff807`1dc49312 : 00000000`c0000002 00000000`00000017 fffff807`1dc4982a 00000000`00000000 : nvlddmkm+0xd993d
ffff8988`ae51f5f0 fffff807`13431f39 : ffffa78a`9c3bd030 ffff8988`ae51f6c0 ffff8988`ae51f720 00000000`69706e04 : nvlddmkm+0xd9312
ffff8988`ae51f620 fffff807`13a3e024 : ffff8988`ae51f6c0 ffffa78a`9c3bd030 ffff8988`ae51f720 ffffa78a`a3077010 : nt!IofCallDriver+0x59
ffff8988`ae51f660 fffff807`13b2b8ba : 00000000`00000017 ffffa78a`96e639a0 ffffa78a`96e63060 ffffa78a`96e639a0 : nt!IopSynchronousCall+0xf8
ffff8988`ae51f6e0 fffff807`13b2b479 : ffffdf0a`21db6d00 00000000`00000000 00000000`00000308 00000000`00000000 : nt!IopRemoveDevice+0x106
ffff8988`ae51f7a0 fffff807`13b2b23b : ffffa78a`96e639a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PnpSurpriseRemoveLockedDeviceNode+0xb5
ffff8988`ae51f800 fffff807`13b2af0a : ffffa78a`96e639a0 ffff8988`ae51f880 00000000`00000000 fffff807`13b2accf : nt!PnpDeleteLockedDeviceNode+0x57
ffff8988`ae51f840 fffff807`13b29707 : ffffa78a`96e63060 00000002`00000002 00000000`00000002 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x76
ffff8988`ae51f8c0 fffff807`13afc8fa : ffff8988`ae51fa10 ffffa78a`96e63900 ffff8988`ae51fa00 ffffdf0a`00000002 : nt!PnpProcessQueryRemoveAndEject+0x1ef
ffff8988`ae51f9b0 fffff807`13a7e318 : ffffdf0a`21db6d00 ffffdf0a`1a938530 ffffdf0a`1a938530 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0xea
ffff8988`ae51f9e0 fffff807`134bd465 : ffffa78a`9644dca0 ffffa78a`a2173040 ffffa78a`9644dca0 ffffa78a`9644dca0 : nt!PnpDeviceEventWorker+0x2d8
ffff8988`ae51fa70 fffff807`1352a725 : ffffa78a`a2173040 00000000`00000080 ffffa78a`96464040 000024ef`bd9bbfff : nt!ExpWorkerThread+0x105
ffff8988`ae51fb10 fffff807`135c886a : ffff9700`09ec4180 ffffa78a`a2173040 fffff807`1352a6d0 ff63abd3`ff61abd2 : nt!PspSystemThreadStartup+0x55
ffff8988`ae51fb60 00000000`00000000 : ffff8988`ae520000 ffff8988`ae519000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC:  908bd99156fe2267556f870535759e7a3a14cf32

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  3fa464eebacef5e6bbe69bac540d1961f6e1b205

THREAD_SHA1_HASH_MOD:  b30020c8c31a398779d41ae3683d0994236f0f52

FOLLOWUP_IP:
dxgkrnl!DpiFdoHandleSurpriseRemoval+167
fffff807`1aea42e7 483bf7          cmp     rsi,rdi

FAULT_INSTR_CODE:  75f73b48

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgkrnl!DpiFdoHandleSurpriseRemoval+167

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  167

FAILURE_BUCKET_ID:  0x113_dxgkrnl!DpiFdoHandleSurpriseRemoval

BUCKET_ID:  0x113_dxgkrnl!DpiFdoHandleSurpriseRemoval

PRIMARY_PROBLEM_CLASS:  0x113_dxgkrnl!DpiFdoHandleSurpriseRemoval

TARGET_TIME:  2019-10-10T20:03:21.000Z

OSBUILD:  18362

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  4aa8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x113_dxgkrnl!dpifdohandlesurpriseremoval

FAILURE_ID_HASH:  {bea10195-35f6-424b-5ad3-3c856cd9ec71}

Followup:     MachineOwner
---------
looking around internet, seems like it's a problem of driver conflicts, but i've no clue of what to do, cause i've already tried to fresh install things the clean way
 
and I've just found out that while it seems it's not detected, in device manager gtx1060 is seen as hidden device, and it says it's not connetted
 

TRENDING THREADS