| View previous topic :: View next topic |
| Author |
Message |
lcineyes
Newbie cheater
![]() Reputation: 0
Joined: 19 May 2025
Posts: 14
|
 Posted: Sat Sep 20, 2025 3:29 am Post subject: Does DBVM pass through IOMMU-related memory? |
 |
|
| I booted DBVM from a USB drive, and everything worked normally until I opened a program that uses VT-d, after which the system froze. After enabling TSC protection, I encountered a CLOCK_WATCHDOUT_TIMEOUT blue screen error. I really can’t figure out why. Now I suspect that the IOMMU memory is not properly exposed to the system.
|
|
| Back to top |
|
 |
Dark Byte
Site Admin
 Reputation: 470
Joined: 09 May 2003
Posts: 25785
Location: The netherlands
|
| Posted: Sat Sep 20, 2025 5:40 am Post subject: |
|
|
it's possible. There's only basic nested intel.vt support
what program do you use to i can reproduce ?
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
| Back to top |
|
|
lcineyes
Newbie cheater
![]() Reputation: 0
Joined: 19 May 2025
Posts: 14
|
| Posted: Sun Sep 21, 2025 2:56 am Post subject: |
|
|
Game Valorant
I found that after entering the system, loading DBVM using the driver works fine. However, if I boot into DBVM from a USB drive first and then enter the system, I suspect that some ACPI information is not accurately passed to the operating system, which may cause a blue screen.
|
|
| Back to top |
|
|
Dark Byte
Site Admin
Reputation: 470
Joined: 09 May 2003
Posts: 25785
Location: The netherlands
|
| Posted: Sun Sep 21, 2025 3:58 am Post subject: |
|
|
your vmdisk.img is the same on the usb as the one the driver uses ? (In case you're on an older vmdisk.img)
_________________
Do not ask me about online cheats. I don't know any and wont help finding them.
Like my help? Join me on Patreon so i can keep helping |
|
| Back to top |
|
|
lcineyes
Newbie cheater
![]() Reputation: 0
Joined: 19 May 2025
Posts: 14
|
| Posted: Sun Sep 21, 2025 7:30 pm Post subject: |
|
|
Version 17 is being used in all cases. The error below doesn't appear to be directly related to VT-d, but it consistently triggers a CLOCK_WATCHDOG_TIMEOUT when VT-d is used. This issue is unrelated to how DBVM is loaded.
| Code: |
00 ffffbc80`e8726c88 fffff806`02c26aee : 00000000`00000101 00000000`0000000c 00000000`00000000 ffffbc80`e7feb180 : nt!KeBugCheckEx
01 ffffbc80`e8726c90 fffff806`02a275ed : 00000000`00000000 ffffbc80`e870d180 00000000`00000246 00000000`00004358 : nt!KeAccumulateTicks+0x20271e
02 ffffbc80`e8726cf0 fffff806`02a27b91 : 00000000`00004100 00000000`00002823 ffffbc80`e870d180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
03 ffffbc80`e8726d40 fffff806`02a218e3 : ffffbc80`e870d180 00000000`00000000 fffff806`034319a0 00000000`00000000 : nt!KiUpdateTime+0x4a1
04 ffffbc80`e8726e80 fffff806`02a29fe2 : ffff8e86`cbe5a010 ffff8e86`cbe5a090 ffff8e86`cbe5a000 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
05 ffffbc80`e8726f30 fffff806`02b43a65 : 00000000`a0a63e77 ffffa50e`499332e0 ffffa50e`49933390 00000000`00000000 : nt!HalpTimerClockInterrupt+0xe2
06 ffffbc80`e8726f60 fffff806`02bff5aa : ffff8e86`cbe5a090 ffffa50e`499332e0 0000007f`fffffff8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
07 ffffbc80`e8726fb0 fffff806`02bffdd7 : ffff8e86`cbe5a200 ffffbc80`e8715ed8 ffffa50e`499332e0 ffffbc80`e8715ed8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa (TrapFrame @ ffffbc80`e8726e70)
08 ffff8e86`cbe5a010 fffff806`02a4ac07 : ffffffff`ffffffd1 fffff806`02a2e83a 00000000`00000010 00000000`00040286 : nt!KiInterruptDispatchNoLockNoEtw+0x37 (TrapFrame @ ffff8e86`cbe5a010)
09 ffff8e86`cbe5a1a0 fffff806`02a2e83a : 00000000`00000000 00000000`0045de00 00000040`00000000 0000007f`fffffff8 : nt!KeYieldProcessorEx+0x17
0a ffff8e86`cbe5a1d0 fffff806`02a0ee3f : fffff806`1f3f2606 00000000`00000000 fffff806`00000001 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x2a
0b ffff8e86`cbe5a200 fffff806`02a85cdf : ffffa50e`50000000 00000000`00000000 00000000`00000000 ffffa000`0cd05120 : nt!MiLockPageTableInternal+0x38f
0c ffff8e86`cbe5a270 fffff806`02a8bb30 : 00000000`00000000 ffffa50e`507a0000 00000000`00000000 ffff8241`29439418 : nt!MiLockLowestValidPageTable+0x9f
0d ffff8e86`cbe5a2e0 fffff806`02a8b997 : 00000000`00000000 ffff8e86`cbe5a3f0 ffff8252`87283000 fffff806`02d1f0fe : nt!MiLockPoolCommitPageTable+0xe0
0e ffff8e86`cbe5a360 fffff806`02a8b827 : 00000000`00000000 00000000`00001000 00000000`00000000 00000000`00000000 : nt!MiCommitPoolMemory+0xeb
0f ffff8e86`cbe5a3b0 fffff806`02a8b674 : 00000000`00230000 ffff8e86`cbe5a4a0 ffffbc80`e80a5180 00000000`00000040 : nt!MmAllocatePoolMemory+0xcf
10 ffff8e86`cbe5a470 fffff806`02a8b4c5 : 00000000`00230000 ffff8e86`cbe5a5c8 ffffa50e`507a0000 00000000`00000230 : nt!RtlpHpEnvAllocVA+0xc8
11 ffff8e86`cbe5a4d0 fffff806`02a8ad7f : 00000000`00000003 00000000`00000000 00100410`018302ff ffffa50e`553b9080 : nt!RtlpHpAllocVA+0xf5
12 ffff8e86`cbe5a590 fffff806`02a8ab1e : ffffffff`ffffff00 00000000`00000230 00000000`00000000 00000000`00000230 : nt!RtlpHpSegMgrCommit+0xef
13 ffff8e86`cbe5a660 fffff806`02a89f7b : 00000007`00000010 ffffa50e`50000f40 00000002`00000000 00000000`00000230 : nt!RtlpHpSegPageRangeCommit+0x1ee
14 ffff8e86`cbe5a700 fffff806`02abd196 : 00000000`00230000 00000000`00230000 ffff8e86`cbe5a841 00000000`00000000 : nt!RtlpHpSegAlloc+0xab
15 ffff8e86`cbe5a760 fffff806`02abc86f : ffffbc80`00000002 00000000`00000000 00000000`6b737473 ffffa50e`5382d180 : nt!ExAllocateHeapPool+0x8f6
16 ffff8e86`cbe5a8a0 fffff806`031b418e : 00000000`00000000 00000000`00000080 fffff807`94891f2c 00008603`00000000 : nt!ExpAllocatePoolWithTagFromNode+0x5f
17 ffff8e86`cbe5a8f0 fffff807`94857ea9 : 00000000`00000000 fffff806`02acaa0d ffffa50e`5382d080 ffffa50e`4b166dd0 : nt!ExAllocatePoolWithTag+0x2e
|
|
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
