Changes between Initial Version and Version 1 of Ticket #19154, comment 7
- Timestamp:
- Dec 23, 2019 2:24:03 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #19154, comment 7
initial v1 1 1 Thanks for reporting this bug (I've upgraded VB 6.0.14 to 6.1 lately and about the same time increased RAM in machine so I've had suspicion about new RAM). 2 2 3 Host: Windows 7 SP1 x64, nVidia GPU, earlier installed VB 6.0.14 without this problem.3 Host: Windows 7 SP1 x64, nVidia GPU, earlier was installed VB 6.0.14 without this problem. 4 4 5 Now VB 6.1 installed - if in VM settings graphics controller is VMSVGA with 3D enabled, I'm getting during guest machine restart (Mint 18.3 Cinnamon; KDE neon 5.17.4) this error: 6 "VirtualBoxVM.exe - Application Error. The instruction at 0x........ referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program." 5 Now with VB 6.1 - if in VM settings: as graphics controller is '''VMSVGA''' with '''3D enabled''', I'm getting during guest machine restart (Mint 18.3 Cinnamon x64; KDE neon 5.17.4 x64) this error:[[BR]] 6 "VirtualBoxVM.exe - Application Error. [[BR]] 7 The instruction at 0xda1dd31c referenced memory at 0x00000000. The memory could not be read. Click on OK to terminate the program." 7 8 8 If I uncheck 3D option then VM are restarting without "VirtualBoxVM.exe" crash. 9 If I uncheck 3D option then VM is restarting fine, without "VirtualBoxVM.exe" crash. 10 11 fragment of Vbox.log: 12 13 {{{ 14 00:06:34.676485 !!! rtR3WinUnhandledXcptFilter caught an exception on thread 000000000000222c!!! 15 00:06:34.676488 16 00:06:34.676488 ExceptionCode=0xc0000005 ExceptionFlags=0x00000000 ExceptionAddress=000007feda1dd31c 17 00:06:34.676494 ExceptionInformation[0]=0000000000000000 18 00:06:34.676495 ExceptionInformation[1]=0000000000000000 19 }}}
