So until about a week ago I had downgraded back to 332.60 and had no issues at all. If I have the DisplayLink device disconnected it always works fine. Every single update has caused me to get the driver power state failure BSOD at random times. It is 100% reproducible on my machine, if I have the DisplayLink device plugged in I always get the BSOD on resume from sleep. I'm not really sure.Īs far as I know I have the latest Windows and drivers so it is strange that nobody else is reporting this issue. For more information about how to access your purchased. Enterprise customers with a current vGPU software license (GRID vPC, GRID vApps or Quadro vDWS), can log into the enterprise software download portal by clicking below. Search for previously released Certified or Beta drivers. The error is in the kernel, but somehow the DisplayLink driver is triggering it. Option 2: Automatically find drivers for my NVIDIA products. I just used the commands from the link and according to those commands the DisplayLink driver shows up as the cause (I'm not a windbg expert, so I wasn't sure the commands to use until I found that link). I agree, the crash is different than the link I posted. Ref: 29287 - BSoD at sleep resume after updating to RS5 v1809 w/ Intel HD 4600 I need someone from engineering to look at that. There's no easy culprit visible from the tool as the last calls and the trip are with DirectX.Īs expected, our driver is no in the stack as it's a kernel crash. I've ran the windbg tool and your BSoD code is the same as the website you quoted, but the reason it trips is different.įAILURE_BUCKET_ID: 0x9F_3_dxgkrnl!DpiFdoHandleDevicePower
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |