Virtual Box craches after Debian installation


I want to create a developing IDE by using Debian, virtualized under Virtual Box. Suddenly, the new Debian Virtual Machine crashed right after the first start up (no other program installed or other configurations!) and show a strange error message. I have all possible details:

  • Win 10 PRO as host, updated;
  • The guest is Debian 10.2.0, latest version;
  • The Virtual Box version is 6.1.0, absolutely the latest
  • I see the error message which I attached
  • I have also seen the complete log, with the following result

enter image description here

2d10.22b4: KiUserExceptionDispatcher: 0xc0000005 (0000000000000000, 0000000000000000) @ 00007ffc2f817613 (flags=0x0)
  rax=000000000761c990 rbx=0000000007447860 rcx=0000000000000000 rdx=00000000012feaf8
  rsi=0000000000000148 rdi=0000000007630110 r8 =0000000000000001 r9 =0000000007447868
  r10=0000000000000000 r11=0000000000000246 r12=0000000007447860 r13=0000000000000000
  r14=00000000012fee18 r15=00000000025e9830  P1=0000000000000028  P2=0000000001ffd460
  rip=00007ffc2f817613 rsp=00000000012feac0 rbp=0000000000000148    ctxflags=0010005f
  cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b    eflags=00010282   mxcrx=00001fa0
   P3=0000000000000000  P4=00007ffc80052d68  P5=00007ffc80052d40  P6=00007ffc8178083d
  dr0=0000000000000000 dr1=0000000000000000 dr2=0000000000000000 dr3=0000000000000000
  dr6=0000000000000000 dr7=0000000000000000 vcr=0000000000000000 dcr=0000000000000000
  lbt=0000000000000000 lbf=0000000000000000 lxt=0000000000000000 lxf=0000000000000000
2d10.22b4: supR3HardenedIsApiSetDll: ApiSetQueryApiSetPresence(ext-ms-win-kernel32-errorhandling-l1-1-0.dll) -> 0x0, fPresent=1
2d10.22b4: supR3HardenedMonitor_LdrLoadDll: pName=ext-ms-win-kernel32-errorhandling-l1-1-0.dll (rcNtResolve=0x0) *pfFlags=0x0 pwszSearchPath=0000000000000001:<flags> [calling]
2d10.22b4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffc7f7f0000 'ext-ms-win-kernel32-errorhandling-l1-1-0.dll'
4ba4.7f8: supR3HardNtChildWaitFor[2]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 426933 ms, the end);
1e60.209c: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 427371 ms, the end);
asked on Stack Overflow Jan 8, 2020 by Archimede • edited Jan 13, 2020 by halfer

0 Answers

Nobody has answered this question yet.

User contributions licensed under CC BY-SA 3.0