Custom Query (16363 matches)
Results (1114 - 1116 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #10799 | obsolete | BSOD in host O/S DRIVER_POWER_STATE_FAILURE (9f) FAULTING_MODULE: fffff88008254000 usbhub | ||
| Description |
Primary O/S (outside of virtual box) is Windows 7. Virtual O/S is windows XP, SP3 Similar to ticket #9997 and #9995 HOST O/S log dump is provided below: Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03218000 PsLoadedModuleList = 0xfffff800`0345d670 Debug session time: Thu Feb 9 06:51:15.125 2012 (UTC - 4:00) System Uptime: 0 days 3:15:56.341 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffffa801ecf1060, Physical Device Object of the stack Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack Arg4: fffffa8056f5ba20, The blocked IRP Debugging Details: ------------------ ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: USBHUB!_DEVICE_EXTENSION_PDO *** *** *** ************************************************************************* TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 DRVPOWERSTATE_SUBCODE: 3 IMAGE_NAME: usbhub.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a68e MODULE_NAME: usbhub FAULTING_MODULE: fffff88008254000 usbhub CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: fffff800`00b9c388 fffff800`03302cd2 : 00000000`0000009f 00000000`00000003 fffffa80`1ecf1060 fffff800`00b9c3d8 : nt!KeBugCheckEx fffff800`00b9c390 fffff800`032a05fc : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90 fffff800`00b9c430 fffff800`032a0496 : fffff800`0343ff00 00000000`000b7fc6 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c fffff800`00b9c4a0 fffff800`032a037e : 0000001b`5f5350e0 fffff800`00b9cb18 00000000`000b7fc6 fffff800`0340eb48 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9caf0 fffff800`032a0167 : 00000008`8e0746c1 00000008`000b7fc6 00000008`8e074698 00000000`000000c6 : nt!KiTimerExpiration+0x1be fffff800`00b9cb90 fffff800`0328c96a : fffff800`0340ae80 fffff800`03418cc0 00000000`00000000 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_VBoxUSB_IMAGE_usbhub.sys BUCKET_ID: X64_0x9F_3_VBoxUSB_IMAGE_usbhub.sys Followup: MachineOwner |
|||
| #9702 | obsolete | BSOD manytimes on windows XP SP3 x86 host on version 4.1.4 | ||
| Description |
Hi ! Using Vbox very long time. But BSOD's came with version 4.1.2 and 4.1.4 Don't know what i doing .. just have running at lease 2-3 machines all time in my host system. With some moment have BSOD. One time it was when i try to go full screen mode with FAR manager (Alt + Enter) with windowsXP guest. One time when i try to save my ubuntu_server... Can't reproduce it. Maybe dump say something ? |
|||
| #8152 | fixed | BSOD on HP Elitebook 8440P | ||
| Description |
Host OS will run into BSOD randomly after running VirtualBox for a while. VirtualBox 4.0.2, 4.0.0, 3.2.12, 3.2.8 have the same problem. Only one hardware model HP Elitebook 8440P has such problem. All other models (HP6930P, 4400) have no such problem. HP Elitebook 8440P CPU: Intel Core i5 Host: Windows Vista Enterprise SP2 32bit Guest: SuSE Linux 64bit log will be posted later. |
|||

