none
Device Path Exerciser测试发生蓝屏 RRS feed

  • 常规讨论

  •  
      测试环境:
       2003 service sp2   DTM1.4 
       测试设备: 公司开发的 3G上网Modem
       测试客户端:  windows7 RC
       出现蓝屏的用例: Device Path Exerciser
     
      蓝屏信息:
      KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 8daf7918, The address that the exception occurred at
    Arg3: 8c553af8, Trap Frame
    Arg4: 00000000

     调用栈:
    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be
    wrong.
    8c553664 828aa07c 0000008e c0000005 8daf7918 nt!KeBugCheckEx+0x1e
    8c553a88 82853fe6 8c553aa4 00000000 8c553af8
    nt!IoGetRelatedDeviceObject+0x2aa6
    8c553bac 82c2fba9 84b74bac 8c553bd0 8284cad1 nt!Kei386EoiHelper+0x1de
    8c553bb8 8284cad1 862a4988 84ba74e0 8c553c60 hal!KfLowerIrql+0x61
    8c553bd0 829f964e 8c553c60 00000000 862a4988 nt!IofCallDriver+0x64
    8c553c04 8283a3c8 862a4988 8c553c24 86ca3ce8 nt!FsRtlOplockBreakH+0x3f5
    8c553c70 829fc47b 8c553c7c 00000000 8c553d18 nt!PoRegisterSystemState+0x185
    8c553c80 82ad7f6d 8c553cd4 93598320 000001a0
    nt!RtlCopyLuidAndAttributesArray+0x75
    8c553d18 828533fa 000001a0 0055fb50 019aaef0
    nt!NtSetVolumeInformationFile+0xde
    8c553d34 76e28244 badb0d00 0055fb30 00000000 nt!ZwYieldExecution+0xb5a
    8c553d38 badb0d00 0055fb30 00000000 00000000 0x76e28244
    8c553d3c 0055fb30 00000000 00000000 00000000 0xbadb0d00
    8c553d40 00000000 00000000 00000000 00000000 0x55fb30

    指向我们的code地方:
      PNP 分发函数处理中的
     stackDeviceObject = deviceExtension->TopOfStackDeviceObject;
     
      难点: 既然指出我们自己的驱动代码问题有问题,但是调用栈中没有调用我们的驱动?
               不知道如何处理和分析?


    goodgold
    2009年7月29日 10:12