Hi,
[.greetings. My first post to Windows windowssh blog.] since updating my main desktop to W10Pro from W8.1Pro I've been experiencing random BSODs. Looking at the Event Viewer, they may be driver related..
The driver DriverWSDScan for device SWDDAFWSDProviderurn:uuid:00000000-0000-1000-8000-2c9efcabdb91/http://schemas.canon.com/Scanner stopped the power transition.
I've updated to the latest Canon W10 Pixma driver but the problem remains. I've also run SFC /Scannow which reports clean.
Attached is the standard BSOD logfile.
DSL-OFFICE-12_08_2015_104443_98.zipDSL-OFFICE-12_08_2015_104443_98.zip
I'd welcome suggestions as to how best further investigate and fix the problem.
Many thanks,
Martin..
You've been experiencing 0x9F BSODs, these are caused by DRIVER_POWER_STATE_FAILURES.Code:DRIVER_POWER_STATE_FAILURE (9f) A driver has failed to complete a power IRP within a specific time. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: ffffe000b83c6060, Physical Device Object of the stack Arg3: ffffd0003a45b990, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffe000c0511010, The blocked IRP
Looking at the blocked IRP it's showing Intel Management Engine Interfacedriver. It's pretty old so check herefor an updated version.Code:6: kd> !irp ffffe000c0511010Irp is active with 3 stacks 2 is current (= 0xffffe000c0511128) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [ 16, 0] 0 0 ffffe000b83c6060 00000000 00000000-00000000 Driverpci Args: 00000000 00000000 00000000 00000002 >[ 16, 2] 0 e1 ffffe000bb0c2e20 00000000 fffff800a150dc98-ffffe000bb283670 Success Error Cancel pending Unable to load image SystemRootsystem32DRIVERSTeeDriverx64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for TeeDriverx64.sys *** ERROR: Module load completed but symbols could not be loaded for TeeDriverx64.sysDriverMEIx64 nt!PopRequestCompletion Args: 00041100 00000001 00000001 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-ffffe000bb283670 Args: 00000000 00000000 00000000 00000000 6: kd> lmvm TeeDriverx64 start end module name fffff801`d75e0000 fffff801`d75fc000 TeeDriverx64 T (no symbols) Loaded symbol image file: TeeDriverx64.sys Image path: SystemRootsystem32DRIVERSTeeDriverx64.sys Image name: TeeDriverx64.sys Timestamp: Thu Sep 05 19:02:18 2013(5228C72A) CheckSum: 0001ACA6 ImageSize: 0001C000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 6: kd> !object ffffe000b83c6060
Many thanks for the suggestion. Yes, I have found updated drivers for the Intel Management Engine Interface and installed them. I will let you know how I get on. Previously, I had fully uninstalled the ATI Radeon HD display driver and Catalyst application and reinstalled them. This gave some improvement but didn't seem to provide a total fix.
I'll report back here and let you know the outcome.
For future reference, do you know of any guide for reading/interpreting the BSOD logs as you have done above?
Once again. Thank you for your helpful response.
Best wishes.
Keep us posted, hopefully you're issues are solved.
You can take a read through this tutorial which will give you an introduction to analysing BSODs. WinDBG - The Basics for Debugging Crash Dumps in Windows 10 - Windows 10 blog
Ok. After much chasing around it looks like the culprit was the Realtek HD Audio Driver. During the Windows Update process the driver is automatically updated to version 10.0.10240.16384 but the driver component under 'sound, video and game controllers' stays at version: 6.0.1.7535 if you try and force and update it will do so but then revert back to the same version. With version 6.0.1.7535 the system hangs when waking from sleep.
The solution I found was to completely uninstall and delete the Realtek driver. Then download and install the latest v R2.79 from their site. Interestingly this installs the same 10.0.10240.16384 version under the 'audio' section but installs a version 6.0.1.7541 under the 'sound, video and game controller' section. With this version wake from sleep works correctly.
It is not clear why the same driver version 10.0.10240.16384 doesn't apply to both 'audio' and 'sound, video and game controller' driver sections. Also on another Gigabyte pc (albeit with a different motherboard) the same discrepancy doesn't prevent the wake from sleep working. That is with the 'standard' W10 updated versions 10.0.10240.16384/6.0.1.7535 for Realtek HD Audio Sleep/Wake works correctly.
In summary I'm pretty confident the 'crash on wake' problem was related to the Realtek HD Audio driver (system has now been working correctly for 48hours). If you're experiencing similar 'crash or black screen on wake' problems you may wish to check the status of these drivers if they apply to your platform.
