none
xbootmgr BSOD on reboot RRS feed

  • Question

  • Hi,

    Just got a BSOD "PAGE_FAULT_IN_NONPAGED_AREA" while rebooting automatically after I launched an xbootmgr -trace boot command.
    The exact command used was:
    xbootmgr -trace boot -traceflags Base+CSWITCH+DRIVERS+POWER -postbootdelay 60

    A few seconds into the reboot, after the animated sequence appeared, the BSOD occurred.
    This happened while using an HP Touchsmart 300 box running Win 7 x64 Home premium edition.
    Here are the details from the minidump analysis:


    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,it must be protected by a Probe. Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: fffffa80164f7020, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002987e1e, If non-zero, the instruction address which referenced the bad memory address.
    Arg4: 0000000000000000, (reserved)

    Debugging Details:
    ------------------
    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abd0e0
    fffffa80164f7020

    FAULTING_IP:
    nt!IopPerfCompleteRequest+3e
    fffff800`02987e1e 488b4328 mov rax,qword ptr [rbx+28h]

    MM_INTERNAL_CODE: 0
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0x50
    PROCESS_NAME: System
    CURRENT_IRQL: 0
    TRAP_FRAME: fffff88003177030 -- (.trap 0xfffff88003177030)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000000c rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002987e1e rsp=fffff880031771c0 rbp=fffffa80164f44b0
    r8=0000000000000000 r9=fffff88006d921a0 r10=0000000000000020
    r11=fffffa80164d3fa4 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!IopPerfCompleteRequest+0x3e:
    fffff800`02987e1e 488b4328 mov rax,qword ptr [rbx+28h] ds:0123:00000000`00000028=????????????????
    Resetting default scope
    LOCK_ADDRESS: fffff80002a89400 -- (!locks fffff80002a89400)
    Resource @ nt!PiEngineLock (0xfffff80002a89400) Available
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
    Lock address : 0xfffff80002a89400
    Thread Count : 0
    Thread address: 0x0000000000000000
    Thread wait : 0x0

    LAST_CONTROL_TRANSFER: from fffff800029061e4 to fffff80002886f00

    STACK_TEXT:
    fffff880`03176ec8 fffff800`029061e4 : 00000000`00000050 fffffa80`164f7020 00000000`00000000 fffff880`03177030 : nt!KeBugCheckEx
    fffff880`03176ed0 fffff800`02884fee : 00000000`00000000 fffffa80`164f6ff8 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x42907
    fffff880`03177030 fffff800`02987e1e : 00000000`0d224f29 fffff800`028901af fffffa80`16109c00 00000000`00000103 : nt!KiPageFault+0x16e
    fffff880`031771c0 fffff880`06d903ed : 00000000`00000103 fffffa80`164f44b0 00000000`00000103 fffffa80`164f6c00 : nt!IopPerfCompleteRequest+0x3e
    fffff880`03177270 fffff880`06d90037 : 00000000`0000005b fffff880`031773f0 fffff880`031773f8 00000000`000007ff : hidusb!HumCallUSB+0x2b9
    fffff880`03177310 fffff880`06d95972 : fffffa80`1642cf00 00000000`00000000 fffffa80`164f5010 fffffa80`1642cf00 : hidusb!HumGetDescriptorRequest+0x143
    fffff880`03177380 fffff880`06d8df70 : fffffa80`0000005b fffffa80`164f4440 fffffa80`164f5440 00000000`00000001 : hidusb!HumGetReportDescriptor+0xa2
    fffff880`031773f0 fffff880`06d83517 : 00000000`00000001 fffffa80`1642cb40 fffffa80`1642cb40 fffffa80`1642cb40 : hidusb!HumInternalIoctl+0x14c
    fffff880`03177460 fffff880`06d79002 : 00000000`00000003 fffffa80`1642ccc0 fffff880`00000001 00000000`000007ff : HIDCLASS!HidpCallDriverSynchronous+0x4b
    fffff880`031774c0 fffff880`06d85cd2 : fffffa80`1642ccc0 00000000`00000001 fffffa80`164f5010 fffffa80`1642ccb0 : HIDCLASS!GetHIDRawReportDescriptor+0x7e
    fffff880`03177530 fffff880`06d865b0 : 00000000`00000000 fffffa80`1641f010 fffffa80`1641f010 fffffa80`1642ccb0 : HIDCLASS!AllocDeviceResources+0xaa
    fffff880`03177560 fffff880`06d83ccd : 00000000`00000008 fffff880`06d80300 fffff880`06d86c10 fffffa80`164dfa60 : HIDCLASS!HidpStartDevice+0x160
    fffff880`031775e0 fffff880`06d8364a : fffff880`06d80300 fffffa80`1642cc90 fffffa80`1642cc90 fffff880`031776a8 : HIDCLASS!HidpFdoPnp+0x20d
    fffff880`03177610 fffff880`06d7590d : fffff880`06d803a8 fffff880`06d7f3c0 fffffa80`1642cc90 fffff800`02977d41 : HIDCLASS!HidpIrpMajorPnp+0x8a
    fffff880`03177680 fffff800`029a4f6a : fffffa80`1642c540 fffffa80`1642c540 fffffa80`1642cb40 00000000`00000400 : HIDCLASS!HidpMajorHandler+0xf5
    fffff880`031776f0 fffff800`02c44bde : fffffa80`164dfa60 fffffa80`164f09a0 fffffa80`1642cb40 fffffa80`160ffa00 : nt!IopPerfCallDriver+0x14a
    fffff880`03177790 fffff800`0297f0ed : fffffa80`160ffa00 fffffa80`164f09a0 fffff800`02984cd0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`031777d0 fffff800`02c4f926 : fffff800`02a891c0 fffffa80`160ff730 fffffa80`164f09a0 fffffa80`160ff8d8 : nt!PnpStartDevice+0x11d
    fffff880`03177890 fffff800`02c4fbc4 : fffffa80`160ff730 fffffa80`16b9002d fffffa80`16b92d90 00000000`00000001 : nt!PnpStartDeviceNode+0x156
    fffff880`03177920 fffff800`02c72ea6 : fffffa80`160ff730 fffffa80`16b92d90 00000000`00000001 00000000`00000000 : nt!PipProcessStartPhase1+0x74
    fffff880`03177950 fffff800`02c73438 : fffff800`02a86d80 00000000`00000000 00000000`00000001 fffff800`02af371c : nt!PipProcessDevNodeTree+0x296
    fffff880`03177bc0 fffff800`02987347 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
    fffff880`03177c10 fffff800`02894161 : fffff800`02987020 fffff800`02b80501 fffffa80`036db000 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
    fffff880`03177cb0 fffff800`02b2a166 : 00000000`00000000 fffffa80`036db040 00000000`00000080 fffffa80`03669b30 : nt!ExpWorkerThread+0x111
    fffff880`03177d40 fffff800`02865486 : fffff880`02f63180 fffffa80`036db040 fffff880`02f6df80 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`03177d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND: kb
    FOLLOWUP_IP:
    hidusb!HumCallUSB+2b9
    fffff880`06d903ed 3bde cmp ebx,esi
    SYMBOL_STACK_INDEX: 4
    SYMBOL_NAME: hidusb!HumCallUSB+2b9
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: hidusb
    IMAGE_NAME: hidusb.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcbfe
    FAILURE_BUCKET_ID: X64_0x50_hidusb!HumCallUSB+2b9
    BUCKET_ID: X64_0x50_hidusb!HumCallUSB+2b9
    Followup: MachineOwner


    Not sure about the cause, if hidusb.sys (USB Miniport Driver for Input Devices) is involved could this be linked to the touch screen which is a USB device (as are mouse and keyboard)? Any help appreciated!
    Wednesday, February 17, 2010 8:59 PM

All replies

  • Some additional information:Apparently it's the "DRIVERS " traceflag which triggers the BSOD.
    The following commands work without problems:
    >xbootmgr -trace boot -traceflags Base+CSWITCH 
    or
    >xbootmgr -trace boot -traceflags Base+CSWITCH+POWER

    (Note that the xperf command works OK with the DRIVERS kernel flag)
    • Proposed as answer by Andre.Ziegler Thursday, December 2, 2010 4:33 PM
    Thursday, February 18, 2010 2:09 PM
  • Is this a known bug at MS? Does it often happens when using the DRIVERS flag?

    André
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, February 18, 2010 11:50 PM
  • André, not sure if this is a known bug at MS. It happens systematically for me when using xbootmgr with the DRIVERS flag.
    If you have access to a Win 7 64bit box, could you please try to run the same command (xbootmgr -trace boot -traceflags Base+CSWITCH+DRIVERS) on your machine and report the result.
     Here is an analysis from a BSOD from xbootmgr with the DRIVERS flag, this time the bugcheck is 0x7E and the call stack is cleaner; hidusb is again identified:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002983e38, The address that the exception occurred at
    Arg3: fffff88003185018, Exception Record Address
    Arg4: fffff88003184870, Context Record Address

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L

    FAULTING_IP:
    nt!IopPerfCompleteRequest+58
    fffff800`02983e38 488b4cc270      mov     rcx,qword ptr [rdx+rax*8+70h]

    EXCEPTION_RECORD:  fffff88003185018 -- (.exr 0xfffff88003185018)
    ExceptionAddress: fffff80002983e38 (nt!IopPerfCompleteRequest+0x0000000000000058)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT:  fffff88003184870 -- (.cxr 0xfffff88003184870)
    rax=0000000000000000 rbx=fffffa80164d13f8 rcx=0000000000000000
    rdx=001a001900180017 rsi=0000000000000100 rdi=fffffa80164d1010
    rip=fffff80002983e38 rsp=fffff88003185250 rbp=fffffa80036ef510
     r8=0000000000000000  r9=fffff880015f31a0 r10=0000000000000020
    r11=fffffa80164f72c0 r12=0000000000000005 r13=fffff880015f31a0
    r14=0000000000000001 r15=0000000000000000
    iopl=0         nv up ei ng nz ac pe cy
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00210293
    nt!IopPerfCompleteRequest+0x58:
    fffff800`02983e38 488b4cc270      mov     rcx,qword ptr [rdx+rax*8+70h] ds:002b:001a0019`00180087=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ERROR_CODE: (NTSTATUS) 0xc0000005 - L
    EXCEPTION_PARAMETER1:  0000000000000000
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ab90e0
     ffffffffffffffff

    FOLLOWUP_IP:
    hidusb!HumCallUSB+2b9
    fffff880`015f13ed 3bde            cmp     ebx,esi

    BUGCHECK_STR:  0x7E

    LOCK_ADDRESS:  fffff80002a85400 -- (!locks fffff80002a85400)

    Resource @ nt!PiEngineLock (0xfffff80002a85400)    Available

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
        Lock address  : 0xfffff80002a85400
        Thread Count  : 0
        Thread address: 0x0000000000000000
        Thread wait   : 0x0

    LAST_CONTROL_TRANSFER:  from fffff880015f13ed to fffff80002983e38

    STACK_TEXT:
    fffff880`03185250 fffff880`015f13ed : 00000000`00000000 fffffa80`036ef510 00000000`00000103 fffffa80`164d1010 : nt!IopPerfCompleteRequest+0x58
    fffff880`03185300 fffff880`015f1037 : 00000000`00000012 fffff880`03185468 fffffa80`16583f08 00000000`000007ff : hidusb!HumCallUSB+0x2b9
    fffff880`031853a0 fffff880`015f0365 : 00000000`00000000 fffff880`015f31a0 fffffa80`16583f00 fffffa80`000253a2 : hidusb!HumGetDescriptorRequest+0x143
    fffff880`03185410 fffff880`015eebf8 : 00000000`00000000 fffffa80`00000012 fffffa80`16583b40 fffffa80`16583f00 : hidusb!HumGetDeviceDescriptor+0x79
    fffff880`03185460 fffff880`015f6565 : fffffa80`036fda90 00000000`00000000 00000000`00000000 fffffa80`036fd6f0 : hidusb!HumInitDevice+0x20
    fffff880`03185490 fffff880`00ff5517 : fffffa80`16583b40 00000000`00000001 fffffa80`1640a880 fffffa80`036fd6f0 : hidusb!HumPnP+0x229
    fffff880`03185500 fffff880`00ff858f : fffffa80`036fdad8 00000000`00000001 fffffa80`1640a880 fffffa80`16583cb0 : HIDCLASS!HidpCallDriverSynchronous+0x4b
    fffff880`03185560 fffff880`00ff5ccd : 00000000`00000008 fffff880`00ff2300 fffff880`00ff8c10 fffffa80`036fd6f0 : HIDCLASS!HidpStartDevice+0x13f
    fffff880`031855e0 fffff880`00ff564a : fffff880`00ff2300 fffffa80`16583c90 fffffa80`16583c90 fffff880`031856a8 : HIDCLASS!HidpFdoPnp+0x20d
    fffff880`03185610 fffff880`00fe790d : fffff880`00ff23a8 fffff880`00ff13c0 fffffa80`16583c90 fffff800`02973d41 : HIDCLASS!HidpIrpMajorPnp+0x8a
    fffff880`03185680 fffff800`029a0f6a : fffffa80`164f9680 fffffa80`164f9680 fffffa80`16583b40 00000000`00000400 : HIDCLASS!HidpMajorHandler+0xf5
    fffff880`031856f0 fffff800`02c40bde : fffffa80`036fd6f0 fffffa80`036ef110 fffffa80`16583b40 fffffa80`1610aa00 : nt!IopPerfCallDriver+0x14a
    fffff880`03185790 fffff800`0297b0ed : fffffa80`1610aa00 fffffa80`036ef110 fffff800`02980cd0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`031857d0 fffff800`02c4b926 : fffff800`02a851c0 fffffa80`164e5aa0 fffffa80`036ef110 fffffa80`164e5c48 : nt!PnpStartDevice+0x11d
    fffff880`03185890 fffff800`02c4bbc4 : fffffa80`164e5aa0 fffffa80`16ba002d fffffa80`16ba58a0 00000000`00000001 : nt!PnpStartDeviceNode+0x156
    fffff880`03185920 fffff800`02c6eea6 : fffffa80`164e5aa0 fffffa80`16ba58a0 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
    fffff880`03185950 fffff800`02c6f438 : fffffa80`164c74f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296
    fffff880`03185bc0 fffff800`02983347 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000084 : nt!PiProcessReenumeration+0x98
    fffff880`03185c10 fffff800`02890161 : fffff800`02983020 fffff800`02983001 fffffa80`036db600 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
    fffff880`03185cb0 fffff800`02b26166 : 0001b1d8`0004cf79 fffffa80`036db680 00000000`00000080 fffffa80`03669b30 : nt!ExpWorkerThread+0x111
    fffff880`03185d40 fffff800`02861486 : fffff880`02f63180 fffffa80`036db680 fffff880`02f6df80 0004d8f0`00016fc0 : nt!PspSystemThreadStartup+0x5a
    fffff880`03185d80 00000000`00000000 : fffff880`03186000 fffff880`03180000 fffff880`03184da0 00000000`00000000 : nt!KxStartSystemThread+0x16


    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  hidusb!HumCallUSB+2b9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: hidusb
    IMAGE_NAME:  hidusb.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcbfe
    STACK_COMMAND:  .cxr 0xfffff88003184870 ; kb
    FAILURE_BUCKET_ID:  X64_0x7E_hidusb!HumCallUSB+2b9
    BUCKET_ID:  X64_0x7E_hidusb!HumCallUSB+2b9
    Followup: MachineOwner

    Friday, February 19, 2010 9:59 AM
  • Notice that tracing shutdown or hibernation with xbootmgr using the DRIVERS flag works OK.
    Friday, February 19, 2010 2:40 PM
  • Hi, I'm using Vista/7 x86 and didn't get the BSOD. But I also made a guide to get the traces and posted it also here in the social forums and 1 person said he got a BSOD but the user never answered.

    André

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, February 19, 2010 4:06 PM
  • Hi André,

    Is that the guide you mention?
    Friday, February 19, 2010 4:49 PM
  • Yes, that's the guide.

    André

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, February 20, 2010 6:01 PM
  • Some more information from the kernel dump of the second BSOD described above:

    1: kd> !thread
    THREAD fffffa80036db680  Cid 0004.0044  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 1
    IRP List:
        fffffa80164d1010: (0006,03e8) Flags: 00060000  Mdl: 00000000
    Not impersonating
    DeviceMap                 fffff8a000008ed0
    Owning Process            fffffa8003669b30       Image:         System
    Attached Process          N/A            Image:         N/A
    Wait Start TickCount      1121           Ticks: 0
    Context Switch Count      270            
    UserTime                  00:00:00.000
    KernelTime                00:00:00.015
    Win32 Start Address nt!ExpWorkerThread (0xfffff80002890050)
    Stack Init fffff88003185db0 Current fffff88003184da0
    Base fffff88003186000 Limit fffff88003180000 Call 0
    Priority 13 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    fffff880`03184048 fffff800`02bf1824 : 00000000`0000007e ffffffff`c0000005 fffff800`02983e38 fffff880`03185018 : nt!KeBugCheckEx
    fffff880`03184050 fffff800`02bad435 : fffff880`03184550 fffff800`02b5bb28 fffff880`03184130 fffff880`00000001 : nt!PspUnhandledExceptionInSystemThread+0x24
    fffff880`03184090 fffff800`028b14dc : fffff880`03184570 fffff880`03184518 fffff880`03184534 fffff880`03184562 : nt! ?? ::NNGAKEGL::`string'+0x222d
    fffff880`031840c0 fffff800`028a8bed : fffff800`029e3f30 fffff880`03185d40 00000000`00000000 fffff800`02811000 : nt!_C_specific_handler+0x8c
    fffff880`03184130 fffff800`028b0250 : fffff800`029e3f30 fffff880`031841a8 fffff880`03185018 fffff800`02811000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`03184160 fffff800`028bd1b5 : fffff880`03185018 fffff880`03184870 fffff880`00000000 fffffa80`164d1010 : nt!RtlDispatchException+0x410
    fffff880`03184840 fffff800`02882542 : fffff880`03185018 fffffa80`164d13f8 fffff880`031850c0 00000000`00000100 : nt!KiDispatchException+0x135
    fffff880`03184ee0 fffff800`02880e4a : fffffa80`03723c80 fffff800`02869395 00000000`0020b377 fffffa80`04862000 : nt!KiExceptionDispatch+0xc2
    fffff880`031850c0 fffff800`02983e38 : 00000000`00000000 fffff800`029a0fbc fffffa80`1610e040 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a (TrapFrame @ fffff880`031850c0)
    fffff880`03185250 fffff880`015f13ed : 00000000`00000000 fffffa80`036ef510 00000000`00000103 fffffa80`164d1010 : nt!IopPerfCompleteRequest+0x58
    fffff880`03185300 fffff880`015f1037 : 00000000`00000012 fffff880`03185468 fffffa80`16583f08 00000000`000007ff : hidusb!HumCallUSB+0x2b9
    fffff880`031853a0 fffff880`015f0365 : 00000000`00000000 fffff880`015f31a0 fffffa80`16583f00 fffffa80`000253a2 : hidusb!HumGetDescriptorRequest+0x143
    fffff880`03185410 fffff880`015eebf8 : 00000000`00000000 fffffa80`00000012 fffffa80`16583b40 fffffa80`16583f00 : hidusb!HumGetDeviceDescriptor+0x79
    fffff880`03185460 fffff880`015f6565 : fffffa80`036fda90 00000000`00000000 00000000`00000000 fffffa80`036fd6f0 : hidusb!HumInitDevice+0x20
    fffff880`03185490 fffff880`00ff5517 : fffffa80`16583b40 00000000`00000001 fffffa80`1640a880 fffffa80`036fd6f0 : hidusb!HumPnP+0x229
    fffff880`03185500 fffff880`00ff858f : fffffa80`036fdad8 00000000`00000001 fffffa80`1640a880 fffffa80`16583cb0 : HIDCLASS!HidpCallDriverSynchronous+0x4b
    fffff880`03185560 fffff880`00ff5ccd : 00000000`00000008 fffff880`00ff2300 fffff880`00ff8c10 fffffa80`036fd6f0 : HIDCLASS!HidpStartDevice+0x13f
    fffff880`031855e0 fffff880`00ff564a : fffff880`00ff2300 fffffa80`16583c90 fffffa80`16583c90 fffff880`031856a8 : HIDCLASS!HidpFdoPnp+0x20d
    fffff880`03185610 fffff880`00fe790d : fffff880`00ff23a8 fffff880`00ff13c0 fffffa80`16583c90 fffff800`02973d41 : HIDCLASS!HidpIrpMajorPnp+0x8a
    fffff880`03185680 fffff800`029a0f6a : fffffa80`164f9680 fffffa80`164f9680 fffffa80`16583b40 00000000`00000400 : HIDCLASS!HidpMajorHandler+0xf5
    fffff880`031856f0 fffff800`02c40bde : fffffa80`036fd6f0 fffffa80`036ef110 fffffa80`16583b40 fffffa80`1610aa00 : nt!IopPerfCallDriver+0x14a
    fffff880`03185790 fffff800`0297b0ed : fffffa80`1610aa00 fffffa80`036ef110 fffff800`02980cd0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
    fffff880`031857d0 fffff800`02c4b926 : fffff800`02a851c0 fffffa80`164e5aa0 fffffa80`036ef110 fffffa80`164e5c48 : nt!PnpStartDevice+0x11d
    fffff880`03185890 fffff800`02c4bbc4 : fffffa80`164e5aa0 fffffa80`16ba002d fffffa80`16ba58a0 00000000`00000001 : nt!PnpStartDeviceNode+0x156
    fffff880`03185920 fffff800`02c6eea6 : fffffa80`164e5aa0 fffffa80`16ba58a0 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
    fffff880`03185950 fffff800`02c6f438 : fffffa80`164c74f0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296
    fffff880`03185bc0 fffff800`02983347 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000084 : nt!PiProcessReenumeration+0x98
    fffff880`03185c10 fffff800`02890161 : fffff800`02983020 fffff800`02983001 fffffa80`036db600 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
    fffff880`03185cb0 fffff800`02b26166 : 0001b1d8`0004cf79 fffffa80`036db680 00000000`00000080 fffffa80`03669b30 : nt!ExpWorkerThread+0x111
    fffff880`03185d40 fffff800`02861486 : fffff880`02f63180 fffffa80`036db680 fffff880`02f6df80 0004d8f0`00016fc0 : nt!PspSystemThreadStartup+0x5a
    fffff880`03185d80 00000000`00000000 : fffff880`03186000 fffff880`03180000 fffff880`03184da0 00000000`00000000 : nt!KxStartSystemThread+0x16

    1: kd> !irp fffffa80164d1010
    Irp is active with 11 stacks 12 is current (= 0xfffffa80164d13f8)
     No Mdl: No System Buffer: Thread fffffa80036db680:  Irp is completed. 
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000   

                Args: 00000000 00000000 00000000 00000000
     [  f, 0]   0 e0 fffffa801610aa00 00000000 fffff880015f1110-fffff88003185360 Success Error Cancel
               \Driver\usbccgp     hidusb!HumCallUsbComplete
                Args: 00000000 00000000 00000000 00000000

     The usbccgp driver (USB composite device driver) identified in the IRP information is used by the NextWindow touch screen, I wonder if this helps someone to narrow down the source of the BSOD?
    Sunday, February 21, 2010 5:39 PM
  • Hi,

    can you please contact MS and tell them about the bug?

    http://support.microsoft.com/default.aspx/gp/contactbug

    André
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Sunday, February 21, 2010 6:12 PM
  • OK André, but I was under the impression that this forum was monitored by some Microsoft people (like Michael Milirud, MSFT, Owner)..
    Sunday, February 21, 2010 6:26 PM
  • I didn't see a MS employee here in this WPT forums since I joined this forums.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Sunday, February 21, 2010 7:30 PM
  • André, nearly: you joined on December 15, Michael 's last post in WPT forum was on Dec 18 :-)
    Sunday, February 21, 2010 8:03 PM
  • so, no MS employee is here. Maybe you can try to contact the performance team with the help of their blog.
    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Sunday, February 21, 2010 8:28 PM
  • I have noticed that the BSOD also happens when I impose a safe mode reboot from xbootmgr (via msconfig).
    Tuesday, February 23, 2010 6:59 AM
  • Another element to add to the case:

    If I first launch verifier.exe with about any parameters (like force IRQL checking on beep.sys only), then the same command (xbootmgr -trace boot -traceflags base+cswitch+drivers+power ) does not trigger a BSOD on reboot anymore. However the resulting trace is incomplete and a message warns that kernel logger could not be found in active logger list (this last message may not be relevant).
    Again the same xbootmgr command without the DRIVERS option works as it should.

    Still no clear idea about the source of the BSOD triggered by the DRIVERS option when verifier action is removed.

    (MS and NextWindow have been informed and referred to this thread)
    Tuesday, March 2, 2010 9:50 PM
  • The same BSOD occurs on a clean system right  after windows re-install from HP re-install partition.
    Friday, March 5, 2010 9:47 AM
  • I found another HP user who experienced the same BSOD when launching the  xbootmgr -trace boot -traceflags drivers   command:
    See this post (in Russian) http://forum.oszone.net/post-1328646.html#post1328646 or this one: http://www.thevista.ru/forums.php?m=posts&p=188803#188803
    Since his system seems to be an HP Pavilion DV5T laptop, with no touch screen, this would rule out the NextWindow Touchscreen as a source for the BSOD.

    (Another identical BSOD here: http://www.raymond.cc/blog/archives/2010/03/04/analyze-windows-7-performance-with-microsoft-windows-performance-toolkit/#comment-469279 , but the poster did not give much detail on his set-up)
    Sunday, March 7, 2010 4:25 PM
  • I can confirm this behaviour with a Windows 7 Ultimate 64.

    No HP and no touchscreen atached.

    Tuesday, March 30, 2010 3:21 PM
  • Hi Mic1968F,

    Thanks for reporting. Could you please give more information on your setup? Is the bugcheck code also 0x7E?

    Saturday, April 3, 2010 7:32 PM
  • I get a 'PAGE_FAULT_IN_NONPAGED_AREA (50)' with hidusb.sys as well.  I'm on an Imac 9 with win 7 enterprise 64 bit.  At first I tried

    REG ADD "HKLM\System\CurrentControlSet\Control\Session Manager\Memory Management" -v DisablePagingExecutive -d 0x1 -t REG_DWORD -f

    since you need that for stackwalking in 64 bit win7.  Instead of a bluescreen, I just got a black screen after the windows logo.

    I ended up just disabling the hidusb driver (sc config hidusb start= disabled).  The mouse and keyboard were disabled after a reboot, but I could still control the computer over remote desktop.  I sucessfully got a driver trace, then turned the hidusb driver back on (sc config hidusb start= demand).

     

    • Proposed as answer by trindflo Thursday, July 27, 2017 9:32 PM
    Thursday, November 11, 2010 9:31 PM
  • Had similar issues with 32-bit WES7 on a special custom motherboard (Advantech) with an AMI BIOS.

    JS2010's solution worked for me.

    In order to get the machine out of the trap state I found I needed to boot from CD, rename hidusb.sys temporarily, boot and allow the trace to complete, then finally replace hidusb.sys.

    Thursday, July 27, 2017 9:32 PM