Monitor Drvier BSOD RRS feed

  • 问题

  • I wrote a monitor filter drivers, I call the black screen PoRequestPowerIrp to set the monitor, but the blue screen, DUMP file analysis as follows, bother everybody to help:

    The Kernel-Mode Driver Framework was notified that Windows detected an error
    in a framework-based driver. In general, the dump file will yield additional
    information about the driver that caused this bug check.
    Arg1: 0000000d, A power irp was received for the device but the irp was not
    requested by the device (the power policy owner). Possibly there
    are multiple power policy owners. Only one driver in the stack can
    be the power policy owner. A KMDF driver can change power policy
    ownership by calling the DDI WdfDeviceInitSetPowerPolicyOwnership.
    Arg2: 88e4e9f8, Device object pointer.
    Arg3: 89fefe28, Power Irp.
    Arg4: 89f75008, Reserved.

    Debugging Details:

    BUGCHECK_STR:  0x10D_d



    PROCESS_NAME:  System


    LAST_CONTROL_TRANSFER:  from 8d04bf9e to 840eff20

    807c7b6c 8d04bf9e 0000010d 0000000d 88e4e9f8 nt!KeBugCheckEx+0x1e
    807c7b88 8d05ef72 89f75008 0000000d 88e4e9f8 Wdf01000!FxVerifierBugCheck+0x24
    807c7ba4 8d05efce 89f75008 807c7bd0 8d052e02 Wdf01000!FxPkgFdo::DispatchDeviceSetPower+0x6e
    807c7bb0 8d052e02 88e4ed30 807c7bd8 89fefe28 Wdf01000!FxPkgFdo::_DispatchSetPower+0x23
    807c7bd0 8d02fa3f 89fefe28 807c7bf8 8d02fc63 Wdf01000!FxPkgPnp::Dispatch+0x207
    807c7bdc 8d02fc63 88e4e9f8 89fefe28 88e4e9f8 Wdf01000!FxDevice::Dispatch+0x7f
    807c7bf8 84026e6d 88e4e9f8 89fefe28 00000000 Wdf01000!FxDevice::DispatchWithLock+0x7b
    807c7c50 8421af5e 00000000 aa90f2a8 00000000 nt!PopIrpWorker+0x351
    807c7c90 840c2219 84026b1c 00000000 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    8d04bf9e cc              int     3


    SYMBOL_NAME:  Wdf01000!FxVerifierBugCheck+24

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Wdf01000

    IMAGE_NAME:  Wdf01000.sys


    FAILURE_BUCKET_ID:  0x10D_d_Wdf01000!FxVerifierBugCheck+24

    BUCKET_ID:  0x10D_d_Wdf01000!FxVerifierBugCheck+24

    Followup: MachineOwner

    1: kd> lmvm Wdf01000
    start    end        module name
    8d00b000 8d07c000   Wdf01000   (pdb symbols)          c:\symbol\Wdf01000.pdb\A9E46808F4F748178D3071AA9EE76FB71\Wdf01000.pdb
        Loaded symbol image file: Wdf01000.sys
        Mapped memory image file: c:\symbol\Wdf01000.sys\4A5BBF2871000\Wdf01000.sys
        Image path: \SystemRoot\system32\drivers\Wdf01000.sys
        Image name: Wdf01000.sys
        Timestamp:        Tue Jul 14 07:11:36 2009 (4A5BBF28)
        CheckSum:         000717B7
        ImageSize:        00071000
        File version:     1.9.7600.16385
        Product version:  1.9.7600.16385
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     wdf01000.sys
        OriginalFilename: wdf01000.sys
        ProductVersion:   1.9.7600.16385
        FileVersion:      1.9.7600.16385 (win7_rtm.090713-1255)
        FileDescription:  Kernel Mode Driver Framework Runtime
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    I know the blue screen because of the lower driver doesn't support this IRP processing From the DUMP,but  I don't know why?

    2015年9月2日 3:42