首页 > 代码库 > windbg symbol path
windbg symbol path
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;srv*
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8025465970, Physical Device Object of the stack
Arg3: fffff880009f27f0, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8026efc4a0, The blocked IRP
2: kd> !devstack fffffa8025465970
!DevObj !DrvObj !DevExt ObjectName
fffffa80118602f0 \Driver\ksthunk fffffa8011860440 InfoMask field not found for _OBJECT_HEADER at fffffa80118602c0
fffffa800e4f6840 \Driver\usbscan fffffa800e4f6990 InfoMask field not found for _OBJECT_HEADER at fffffa800e4f6810
> fffffa8025465970 \Driver\usbccgp fffffa8025465ac0 Cannot read info offset from nt!ObpInfoMaskToOffset
!DevNode fffffa800df14010 :
DeviceInst is "USB\VID_04A9&PID_26EF&MI_00\2&2ebd5f7a&0&0000"
ServiceName is "usbscan"
Google search for the HardwareID USB\VID_04A9&PID_26EF&MI_00 shows the device appears to be Canon D400-450:
http://www.google.com/search?q=USB%5CVID_04A9%26PID_26EF%26MI_00&sourceid=ie7&rls=com.microsoft:en-US:IE-SearchBox&ie=&oe
I suspect the driver that may be causing the crash is the vuhub.sys, which is dated Nov 16, 2007.
Can you update the vuhub.sys driver?
If the vuhub.sys is a component of Eltima USB Network Gate for Windows try the following link for an updated driver:
http://wiki.eltima.com/user-guides/usb-to-ethernet/install-wind.html
Hey everyone, I had the same code 10 problem with Teredo Tunnel Pseudo-Interface when I connected my laptop with a public library router. Fortunately I found this solution which really worked it out! (My OS is Vista x64 SP2, but I think XP and Win7 can also follow the same solution)
Solution:
1. Open command prompt with administrator credentials (Find CMD and right-click - Run as Administrator).
2. Enter netsh environment. Type "netsh" and ENTER.
3. "int teredo" and ENTER
4. "set state disabled" and ENTER.
5. Open Device Manager and uninstall "Teredo Tunneling Pseudo-Interface".
6. Open command prompt with administrator credentials once again.
7. netsh + ENTER.
8. "int ipv6" + ENTER
9. "set teredo client" + ENTER
10. Open Device Manager and Scan for new hardware.
11. Select "Show hidden devices" from the View menu. You will now see that it is present without errors with any luck.
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/teredo-tunneling-pseudo-interface-this-device/757db042-c91e-464c-b963-c1f442fdf925
windbg symbol path