BSOD - with DPC Watchdog violation plus Driver Power State Failure


  1. Posts : 3
    Windows 10 v1511 build 10586.164
       #1

    BSOD - with DPC Watchdog violation plus Driver Power State Failure


    Sigh... a brand new build on new components. Have a dual boot - works brilliantly in Win 7 (no errors) but fails mostly upon boot up in Win 10.

    Crash dump analysis shows 7 dump files with 6 DPC Watchdog violations and 1 one Driver Power State Failure. Using WhoCrashed shows module ntkrnlmp.exe as likely culprit.

    I am at a loss. Machine works great in Win 7 but is all sadness and woe in Win 10.

    The debug file is loaded - and now?

    Your help will be appreciated.
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    Hi askelly35,

    Welcome to the 10forums :)

    The crashes seem to be caused by 2 very old drivers which are from your Ideazon Merc Stealth USB Human Interface Device keyboard.
    My suggestion is to update the drivers or remove the keyboard.
    Driver Reference Table - Alpham164.sys
    Driver Reference Table - Alpham264.sys
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, ffffe0012a2d9060, ffffd000ed79d890, ffffe001295d20d0}
    
    Unable to load image Alpham164.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Alpham164.sys
    *** ERROR: Module load completed but symbols could not be loaded for Alpham164.sys
    Implicit thread is now ffffe001`25114040
    Probably caused by : Alpham164.sys ( Alpham164+6ba1 )
    
    1: kd> lmvm Alpham164
    Browse full module list
    start             end                 module name
    fffff801`6ae70000 fffff801`6ae7cf00   Alpham164 T (no symbols)           
        Loaded symbol image file: Alpham164.sys
        Image path: Alpham164.sys
        Image name: Alpham164.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Jul 23 09:57:03 2007 (46A45F4F)
        CheckSum:         000134FC
        ImageSize:        0000CF00
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Code:
    Description	Ideazon Merc Stealth USB Human Interface Device
    Name	Enhanced (101- or 102-key)
    Layout	00000409
    PNP Device ID	USB\VID_1038&PID_0510&MI_00\7&377C53D&0&0000
    Number of Function Keys	12
    Driver	c:\windows\system32\drivers\hidusb.sys (10.0.10586.0, 37.50 KB (38,400 bytes), 2015-10-30 3:17 AM)
      My Computers


  3. Posts : 3
    Windows 10 v1511 build 10586.164
    Thread Starter
       #3

    Not my beloved keyboard at fault?


    Remove keyboard? But I love my keyboard.... well, maybe I will love it only in Win 7..

    Will give removal a try.

    (and thanks for such a quick response!!)
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4

    The drivers of your keyboard are ~9 years old, outdated drivers may give various of problems, assuming the drivers aren't updated anymore the best suggestion I can give is to not use it in Windows 10.
      My Computers


  5. Posts : 3
    Windows 10 v1511 build 10586.164
    Thread Starter
       #5

    Found some 'younger' drivers


    Well, a little googling and I found keyboard drivers that are Win7 vintage. So far no more BSOD :)

    I'm optimistic that this is the solve I needed.

    Thanks for pointing me in the right direction - would not have got there without you.

    Cheers..
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #6



    EDIT: the drivers needed at least an update, they were dated for Windows Vista.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:42.
Find Us




Windows 10 Forums