sailfishos / virtualbox

8 stars 35 forks source link

VBoxUSB.sys crashing on pc #12

Open d0n13 opened 2 years ago

d0n13 commented 2 years ago

Is this the place to report issues on a VBoxUSB.sys problem? The driver is crashing my Windows machine when transferring files to a USB device.

SYSTEM_PTE_MISUSE


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff806`5c000000 PsLoadedModuleList = 0xfffff806`5cc2a2b0
Debug session time: Thu Jun  9 11:57:02.622 2022 (UTC + 1:00)
System Uptime: 0 days 0:11:07.326
Loading Kernel Symbols
...............................................................
............................Page 7d731c not present in the dump file. Type ".hh dbgerr004" for details
....................................
................................................................
..............................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000037`8f4b2018).  Type ".hh dbgerr001" for details
Loading unloaded module list
....................
For analysis of this file, run !analyze -v
14: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_PTE_MISUSE (da)
A driver has corrupted system PTEs.
Set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes
to a DWORD 3 value and reboot.  If the same bugcheck occurs again the stack trace will
identify the offending driver.
Arguments:
Arg1: 0000000000000200, Type of error.
Arg2: ffffbe80c0280000
Arg3: 0000000000000000
Arg4: 0000000000000000

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

Page 2919cf not present in the dump file. Type ".hh dbgerr004" for details
Page 2919cf not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BTG-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    Key  : Analysis.System
    Value: CreateObject

BUGCHECK_CODE:  da

BUGCHECK_P1: 200

BUGCHECK_P2: ffffbe80c0280000

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  usbipd.exe

STACK_TEXT:  
ffff9b09`ae98f4c8 fffff806`5c54ee81 : 00000000`000000da 00000000`00000200 ffffbe80`c0280000 00000000`00000000 : nt!KeBugCheckEx
ffff9b09`ae98f4d0 fffff806`5c4378ec : 00000000`00000000 fffff806`5cc4ed80 fffff806`5cc4ed80 00000000`00000000 : nt!MiCheckPteReserve+0x55
ffff9b09`ae98f520 fffff806`5c2643e4 : ffffae89`13dfc390 00000000`00000000 ffffae89`42e62680 ffffae89`13dfc3b8 : nt!MiReservePtes+0x1d3cec
ffff9b09`ae98f5f0 fffff806`bd422d09 : ffffae89`13dfc3b8 ffffae89`00000000 00000000`00000002 ffffae89`42e62680 : nt!MmMapLockedPagesSpecifyCache+0xd4
ffff9b09`ae98f650 fffff806`bd421366 : ffffae89`440ede30 ffffae89`3b344050 00000000`00000098 ffffae89`47586870 : VBoxUSB+0x2d09
ffff9b09`ae98f6d0 fffff806`5c24e565 : ffffae89`3b344050 00000000`00000002 00000000`00000000 00000000`00000700 : VBoxUSB+0x1366
ffff9b09`ae98f700 fffff806`5c60da18 : ffffae89`3b344050 00000000`00000000 ffffae89`3b344050 00000000`00000000 : nt!IofCallDriver+0x55
ffff9b09`ae98f740 fffff806`5c60e9f7 : 00000000`00000000 ffff9b09`ae98fa80 00000000`00040005 ffff9b09`ae98fa80 : nt!IopSynchronousServiceTail+0x1a8
ffff9b09`ae98f7e0 fffff806`5c60dd76 : 00000000`00000000 00000000`00000000 00000000`00000000 00000189`317ad660 : nt!IopXxxControlFile+0xc67
ffff9b09`ae98f920 fffff806`5c4096b5 : ffffae89`3ac68080 ffff9b09`ae98fa80 00000037`914beb38 ffffae89`435bd1c0 : nt!NtDeviceIoControlFile+0x56
ffff9b09`ae98f990 00007ffb`ccc4ce24 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000037`914be358 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`ccc4ce24

SYMBOL_NAME:  VBoxUSB+2d09

MODULE_NAME: VBoxUSB

IMAGE_NAME:  VBoxUSB.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  2d09

FAILURE_BUCKET_ID:  0xDA_VBoxUSB!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {82481b05-1d94-979d-554d-84d1270c9edb}

Followup:     MachineOwner
---------
d0n13 commented 2 years ago

If I'm posting this in the wrong place can you let me know where I might be able to go after the original source? I'm looking for the maintainers of the VBoxUSB driver.

Thanks Donie