Forum Replies Created
-
Posts
-
The installer checks for {Visual Studio directory}VCvcprojects. If it does not exist, you are missing the Visual C++ component and VisualDDK won’t work.
Please attach the DDKDebugger-dbg.log file from VisualDDK directory. It would probably contain the reason for hanging.
Not 100% sure, but I think I’ve stumbled upon some article from Microsoft explaining that the loader debugging is only possible using COM1. I would suggest googling around to see if anyone managed to set up other protocol for the bootloader (e.g. FireWire).
Maybe, it’s related to the way child processes are created. Try making a batch file that starts KD using “start” command and tell VMMON to use it (the “custom:” radio button).
This bug was caused by a recent output format change in latest versions of WinDbg.
Fixed in VisualDDK 1.5.6How did you integrate VirtualKD into VirtualBox? Could you have accidentally left VBoxDD0.dll from an older VirtualBox version? (e.g. just replaced VBoxDD.dll after updating VirtualBox, but did not update VBoxDD0.dll)?
Try reinstalling VirtualBox and reintegrating VirtualKD with it (since VisualDDK 1.5.6 it can be done by running VirtualKDSetup.exe). This will ensure that all files have correct versions.Thanks for the minidump. I think, I’ve found the problem. Please check this version: http://wincdemu.sysprogs.org/temp/BazisVirtualCDBus.sys
Hi, could you please attach a minidump here? The minidumps are located in C:windowsminidump. By analyzing the minidump I will be able to understand and fix the cause of the BSOD!
Second entry appears if you have selected “create a new entry” in the installation program.
To uninstall it, revert your VM to the pre-VirtualKD snapshot, or use bcdedit.exe to remove the entry manually.That’s strange. Normally, this error happens in one of 3 cases:
1. You’re trying to load a 32-bit driver on a 64-bit machine, or vice versa.
2. Your driver misses a signature (this shouldn’t matter if you have connected to the VM using WinDBG/VisualDDK). Anyway, you can make a free testsigning certificate (more info http://msdn.microsoft.com/en-us/library/windows/hardware/ff546236%28v=vs.85%29.aspx), but you’ll al need to enable testsigning mode (bcdedit /set testsigning on).
3. You have copied the driver file from an EFS-encrypted location (the ‘encrypted’ checkbox in file properties). Then, the SYS file in the DRIVERS directory will also be encrypted and the kernel won’t load it. This is very easy to check by right-clicking at the driver file, selecting properties and ensuring that encryption is off.
