1073740972
0xC0000354 | Status_Debugger_Inactive | An attempt to do an operation on a debug port failed because the port is in the process of being deleted.
http://www.faultwire.com/solutions-exception_core/Debug-0xC0000354-%2A1718.html
The DebugPort specifies a debug connection to the system kernel (a
system under test) via a serial (rare today), USB or FireWire connection. The connection has been turned off, but a request was made to continue to use it.
Here’s what I did to fix it:
1. I used bcdedit to remove and re-add the /debug command: bcdedit /debug off then bcdedit /debug on
2. I used bcdedit to force the debugger to be active and to listen on the Firewire port: bcdedit /dbgsettings 1394 /start active
3. I used bcdedit to enable boot debugging: bcdedit /bootdebug
4. I rebooted, and voila! I was now able to use WinDBG in local kernel debugging mode.
Get the debugger state
One must boot with /DEBUG in order to do any local kernel debugging work, and as we all know, this disables DVD and high-def support to “ensure a reliable and secure playback environment”. After a couple of days work, I find myself sometimes forgetting if I had booted in debug mode or not, and I don’t want to start WinDBG all the time to check — or maybe you’re in a non-administrative environment and don’t want to use WinDBG. It’s even possible a new class of malware may soon start adding /DEBUG to systems in order to better infiltrate kernel-mode. Here’s two ways to check the state:
1. Navigate to HKLM\System\CurrentControlSet\Config and look at the SystemStartOptions. If you see /DEBUG, the system was booted in debugging mode. However, because it may have been booted in “auto-enable” mode, or in “block enable” mode (in which the user can then enable/disable the debugger at his will), this may not tell you the whole story.
2. Use kdbgctrl, which ships with the Debugging Tools for Windows. kdbgctrl -c will tell you whether or not the kernel debugger is active right now.
What would be really worthwhile, is to see if DVD playback works with /DEBUG on, but kernel debugging disabled with kdbgctrl, and if it stops playing (but debugging works) if kdbgctrl is used to enable it.
529697949
Reinstall MSXML 6.0 parser. Before reinstalling try "regsvr32 msxml6.dll" from command line and check if it fixes. if registering the dll does not fix, go ahead with re-applying MSXML 6.0 parser.