Windows 10: Driver verification failure in acpi.sys while connecting external GPU.

Hi,


"An IRP dispatch handler for a PDO has deleted its device object, but the hardware has not been reported as missing in a bus relations query"


So, been having some system stability issues. Specifically, my laptop an XPS 13 2-in-1 when connected to my external Razer Core 2 with a Geforce 1080


I've enabled driver verifier, and that seems to produce a core dump on connecting, with various usb peripherals attached.


Any advice for diagnosing and fixing my system stability would be greatly appreciated.


Here is the callstack from the minidump



[0x0] nt!KeBugCheckEx
[0x1] nt!VerifierBugCheckIfAppropriate + 0xdf
[0x2] nt!ViErrorFinishReport + 0x117
[0x3] nt!ViErrorReport10 + 0x6f
[0x4] nt!IovpCallDriver2 + 0xe1
[0x5] nt!VfAfterCallDriver + 0x1d4
[0x6] nt!IovCallDriver + 0x286
[0x7] nt!IofCallDriver + 0x154ff3
[0x8] nt!ViFilterDispatchPnp + 0x121
[0x9] nt!IopfCallDriver + 0x56
[0xa] nt!IovCallDriver + 0x275
[0xb] nt!IofCallDriver + 0x154ff3
[0xc] Wdf01000!FxIrp::CallDriver + 0x11
[0xd] Wdf01000!FxPkgFdo:rocessRemoveDeviceOverload + 0x85
[0xe] Wdf01000!FxPkgPnp::_PnpRemoveDevice + 0x124
[0xf] Wdf01000!FxPkgPnp:ispatch + 0xb4
[0x10] Wdf01000!DispatchWorker + 0x9e
[0x11] Wdf01000!FxDevice:ispatch + 0xbc
[0x12] Wdf01000!FxDevice:ispatchWithLock + 0x113
[0x13] nt!IopfCallDriver + 0x56
[0x14] nt!IovCallDriver + 0x275
[0x15] nt!IofCallDriver + 0x154ff3
[0x16] nt!ViFilterDispatchPnp + 0x121
[0x17] nt!IopfCallDriver + 0x56
[0x18] nt!IovCallDriver + 0x275
[0x19] nt!IofCallDriver + 0x154ff3
[0x1a] nt!IopSynchronousCall + 0xf8
[0x1b] nt!IopRemoveDevice + 0x106
[0x1c] nt!PnpRemoveLockedDeviceNode + 0x1ac
[0x1d] nt!PnpDeleteLockedDeviceNode + 0x8b
[0x1e] nt!PnpDeleteLockedDeviceNodes + 0x76
[0x1f] nt!PipRemoveDevicesInRelationList + 0x8d
[0x20] nt!PnpDelayedRemoveWorker + 0x114
[0x21] nt!PnpChainDereferenceComplete + 0xfd
[0x22] nt!PnpIsChainDereferenced + 0xac
[0x23] nt!PnpProcessQueryRemoveAndEject + 0x2a2
[0x24] nt!PnpProcessTargetDeviceEvent + 0xea
[0x25] nt!PnpDeviceEventWorker + 0x2d8
[0x26] nt!ExpWorkerThread + 0x105
[0x27] nt!PspSystemThreadStartup + 0x55
[0x28] nt!KiStartSystemThread + 0x28


and here is bugcheck analysis:


******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_VERIFIER_IOMANAGER_VIOLATION c9The IO manager has caught a misbehaving driver.Arguments:Arg1: 0000000000000221, An IRP dispatch handler for a PDO has deleted its device object, but the hardware has not been reported as missing in a bus relations query.Arg2: fffff80505ca1010, The address in the driver's code where the error was detected.Arg3: ffffe383e9a3ed30, IRP address.Arg4: ffffe383b8975c20, Device object address.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 2 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-CU8L1B9 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 6 Key : Analysis.Memory.CommitPeak.Mb Value: 89 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: c9BUGCHECK_P1: 221BUGCHECK_P2: fffff80505ca1010BUGCHECK_P3: ffffe383e9a3ed30BUGCHECK_P4: ffffe383b8975c20DRIVER_VERIFIER_IO_VIOLATION_TYPE: 221IRP_ADDRESS: ffffe383e9a3ed30DEVICE_OBJECT: ffffe383d159f2b0DRIVER_OBJECT: ffffe383b8933df0IMAGE_NAME: ntkrnlmp.exeMODULE_NAME: ntkrnlmpFAULTING_MODULE: 0000000000000000 BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: fffff684`5e02e8a8 fffff805`0502c6e3 : 00000000`000000c9 00000000`00000221 fffff805`05ca1010 ffffe383`e9a3ed30 : nt!KeBugCheckExfffff684`5e02e8b0 fffff805`05033947 : 00000000`00000000 ffffe383`b8975c20 00000000`00000221 fffff805`0507e8c0 : nt!VerifierBugCheckIfAppropriate+0xdffffff684`5e02e8f0 fffff805`049e5d7f : 00000000`00000221 ffffe383`b8975c20 ffffe383`e9a3ed30 00000000`00000000 : nt!ViErrorFinishReport+0x117fffff684`5e02e950 fffff805`0502bb15 : ffffe383`ecee1df0 ffffe383`ecee1df0 fffff684`5e02ea38 ffffe383`b8975c20 : nt!ViErrorReport10+0x6ffffff684`5e02ea30 fffff805`0502c908 : ffffe383`ecee1df0 00000000`00000000 ffffe383`ecee1ea8 00000000`00000000 : nt!IovpCallDriver2+0xe1fffff684`5e02ea80 fffff805`050210ba : ffffe383`e9a3ed30 ffffe383`b8975c20 ffffe383`e7a18240 fffff805`0502ba0a : nt!VfAfterCallDriver+0x1d4fffff684`5e02eab0 fffff805`0491b8c3 : ffffe383`e9a3ed30 00000000`00000000 ffffe383`d159f2b0 ffffe383`ecee1df0 : nt!IovCallDriver+0x286fffff684`5e02eaf0 fffff805`05040d21 : ffffe383`e9a3ed30 00000000`00000000 ffffe383`d159f2b0 ffffe383`b8975c20 : nt!IofCallDriver+0x154ff3fffff684`5e02eb30 fffff805`0483b76a : ffffe383`d159f400 00000000`00000000 ffffe383`e9a3ed30 ffffe383`d159f2b0 : nt!ViFilterDispatchPnp+0x121fffff684`5e02eb70 fffff805`050210a9 : ffffe383`e9a3ed30 ffffe383`d159f2b0 fffff684`5e02ed01 fffff684`5e02ec20 : nt!IopfCallDriver+0x56fffff684`5e02ebb0 fffff805`0491b8c3 : fffff684`5e02ed40 00000000`00000000 ffffe383`d0c020d0 ffffe383`ecee44f0 : nt!IovCallDriver+0x275fffff684`5e02ebf0 fffff805`05a28475 : fffff684`5e02ed40 ffffe383`d0c020d0 ffffe383`d0c020d0 00000000`00400000 : nt!IofCallDriver+0x154ff3fffff684`5e02ec30 fffff805`05a26e84 : 00000000`00000001 00000000`00000000 ffffe383`d0c02000 fffff684`5e02ed00 : Wdf01000!FxPkgFdo:rocessRemoveDeviceOverload+0x85 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgfdo.cpp @ 1266] fffff684`5e02ec60 fffff805`059a3c54 : ffffe383`d0c020d0 ffffe383`d03a3db0 00000000`00000000 00000000`00000000 : Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x124 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 2539] fffff684`5e02ecd0 fffff805`059aabd3 : ffffe383`e9a3ed30 ffffe383`d1860030 ffffe383`d03a3c60 00000000`00000000 : Wdf01000!FxPkgPnp:ispatch+0xb4 [minkernel\wdf\framework\shared\irphandlers\pnp\fxpkgpnp.cpp @ 765] fffff684`5e02ed40 fffff805`0483b76a : 00000000`00000000 ffffe383`d03a3c60 00000000`00000000 ffffe383`ec4aee98 : Wdf01000!FxDevice:ispatchWithLock+0x113 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1430] fffff684`5e02eda0 fffff805`050210a9 : ffffe383`e9a3ed30 ffffe383`d03a3c60 ffffe383`e7a18330 fffff805`0502ba0a : nt!IopfCallDriver+0x56fffff684`5e02ede0 fffff805`0491b8c3 : ffffe383`e9a3ed30 00000000`00000000 ffffe383`d159f040 ffffe383`ec4aede0 : nt!IovCallDriver+0x275fffff684`5e02ee20 fffff805`05040d21 : ffffe383`e9a3ed30 00000000`00000000 ffffe383`d159f040 ffffe383`b8975c20 : nt!IofCallDriver+0x154ff3fffff684`5e02ee60 fffff805`0483b76a : ffffe383`d159f190 00000000`00000000 ffffe383`e9a3ed30 ffffe383`d159f040 : nt!ViFilterDispatchPnp+0x121fffff684`5e02eea0 fffff805`050210a9 : ffffe383`e9a3ed30 ffffe383`d159f040 ffffe383`e9a3ed30 fffff805`0502cf69 : nt!IopfCallDriver+0x56fffff684`5e02eee0 fffff805`0491b8c3 : ffffe383`d159f040 fffff684`5e02efc0 fffff684`5e02f020 ffffe383`ecedeed0 : nt!IovCallDriver+0x275fffff684`5e02ef20 fffff805`04c76fe4 : fffff684`5e02efc0 ffffe383`d159f040 fffff684`5e02f020 ffffe383`e9a3ed30 : nt!IofCallDriver+0x154ff3fffff684`5e02ef60 fffff805`04ded23a : 00000000`00000002 ffffe383`b8c35380 ffffe383`b8975c20 ffffe383`b8975c20 : nt!IopSynchronousCall+0xf8fffff684`5e02efe0 fffff805`0482df30 : ffff8a86`3a96a4c0 ffffe383`b8c35380 00000000`0000000a 00000000`00000000 : nt!IopRemoveDevice+0x106fffff684`5e02f0a0 fffff805`04decbef : ffffe383`b8c35380 fffff805`0000000a 00000000`00000000 00000000`00050246 : nt!PnpRemoveLockedDeviceNode+0x1acfffff684`5e02f100 fffff805`04dec88a : ffffe383`b8c35380 fffff684`5e02f180 00000000`0000000a 00000000`00000000 : nt!PnpDeleteLockedDeviceNode+0x8bfffff684`5e02f140 fffff805`04dee171 : ffffe383`b8975c20 fffff684`00000002 ffffe383`d0383a10 fffff805`04dee000 : nt!PnpDeleteLockedDeviceNodes+0x76fffff684`5e02f1c0 fffff805`04debfb4 : 00000000`00000000 fffff684`5e02f240 ffffe383`b8975c20 00000000`00000000 : nt!PipRemoveDevicesInRelationList+0x8dfffff684`5e02f210 fffff805`04deb991 : ffffe383`d0383a10 00000000`00000001 ffffe383`d0383a10 00000000`00000000 : nt!PnpDelayedRemoveWorker+0x114fffff684`5e02f250 fffff805`0482da14 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffe383`b8c35380 : nt!PnpChainDereferenceComplete+0xfdfffff684`5e02f280 fffff805`04deb13a : 00000000`00000001 fffff684`5e02f389 00000000`00000005 ffff8a86`00000001 : nt!PnpIsChainDereferenced+0xacfffff684`5e02f300 fffff805`04dc467e : fffff684`5e02f450 ffffe383`b8c35300 fffff684`5e02f400 ffff8a86`00000001 : nt!PnpProcessQueryRemoveAndEject+0x2a2fffff684`5e02f3f0 fffff805`04c92748 : ffff8a86`3a96a4c0 ffff8a86`496c6210 ffff8a86`496c6210 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0xeafffff684`5e02f420 fffff805`047b03b5 : ffffe383`b4aa7500 ffffe383`eb8bc040 ffffe383`b4aa7500 fffff805`04b1d540 : nt!PnpDeviceEventWorker+0x2d8fffff684`5e02f4b0 fffff805`04727cd5 : ffffe383`eb8bc040 00000000`00000080 ffffe383`b4abe080 000024ef`bd9bbfff : nt!ExpWorkerThread+0x105fffff684`5e02f550 fffff805`04885998 : ffffc300`48279180 ffffe383`eb8bc040 fffff805`04727c80 ebebebeb`ebebebeb : nt!PspSystemThreadStartup+0x55fffff684`5e02f5a0 00000000`00000000 : fffff684`5e030000 fffff684`5e029000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28STACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: 0xc9_221_VRF_IMAGE_ntkrnlmp.exeOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {7bbfe70a-cbc4-db9a-84d7-9f69568f931f}Followup: MachineOwner---------

:)

 

“Missing ASUS ACPI Driver windows 10

There is a step by step guide on what to do here
http://www.tomshardware.co.uk/faq/id-1959382/missing-asus-acpi-driver-windows-back.html It refers to Windows 8, but the remedy has worked for many other people.

If you don't feel like trying that yourself, then all that I can suggest is that you ask you local computer store to help, or find a friend who understands windows computers, show them this thread and ask them to help you with the process of installing the
hotkey utility.

 

My External GPU Challenge

• 
  
  I really have a tough conundrum today;
  I’m trying to connect an external GPU to my laptop…
  What I have:
  
  • Computer - Sony Vaio e series laptop (EA37FH), with a dedicated internal GPU ATI mobility HD 5670
  • External card unit – SAWAKE EXP GDC Beast Laptop External Independent Video Card Dock
  • Discrete GPU card – Powercolor HD 7990
  • Extra PSU – Thermaltake Tough power 650W
  [ALL OF MY GEAR IS BEING DETAILED WITH SPECS AND PICTURES RESPECTIVELY]
  Shutterfly
  
  https://www.facebook.com/avi.assaya...04860&type=3" target="_blank" rel="nofollow">
  
  What I’m trying to do:
  
  
  1. physically connect the e-gpu to my system via the express card port. The card is lighting up, the psu is working just fine (go)
  2. making my OS (windows 7 x64) recognize the new card in “device manager” (go)
  3. play games and running 3d mark benchmarks with the use of the e-gpu (no go)
  
  My problems and symptoms:
  
  
  1. I am unable to install the driver set of my external gpu on this laptop: It just “runs” a super-fast iteration of the installation without doing any real installations of the software. Also, Its’s not even synching between the software and the new hardware. (no go)
  2. I tried to uninstall the mobility dedicated internal gpu with DDU and completely disabling and uninstalling it from the device manager. I also made sure windows will not automatically install the drivers for the mobility gpu (no go)
  3. So basically. There “is no way” to install the dedicated new drivers for the hd7990, even if I completely disable the inboard gpu (no go)
  4. I heard of a way of doing it with a special bios hack with a 25$ software that I just didn’t seem to be able to find – and trust me that I am quite good at searching. (no go)
  
  
  My question:
  
  
  1. Can any of you tech-savvy engineers/super-geeks/crazy technicians help me figure this out?
  2. If and how can I disable the internal GPU with a magic bios hack or anything else?
  3. Can you please help me with tutorials, experience-based advices, useful links to software and manuals?
  4. If any of you people did it before, and struggled like I am – please dig me out of this pit hole of a mess I am in right now.
  Praise Cthulhu
  

 

Eeepc 1215N ACPI Driver

I did exactly as proposed (all the way down step 2)... I still get the message about the missing Asus ACPI Driver in win10.