F5F Stay Refreshed Hardware Desktop Oracle VB in XP 64 causando BSOD IRQL_NOT_LESS_OR_EQUAL

Oracle VB in XP 64 causando BSOD IRQL_NOT_LESS_OR_EQUAL

Oracle VB in XP 64 causando BSOD IRQL_NOT_LESS_OR_EQUAL

_
_TheSpirit
Member
Find
116
05-22-2019, 01:36 AM
#1
It was a stable XP-Pro-64 operating on Oracle VM VirtualBox. It has been working well for several years and was just a few days ago. The main system runs Windows 10 with a Ryzen 9 3900X processor. I was using a Windows Sandbox when attempting to launch VB Win XP64. This is the first time I've run a sandbox in the background, possibly related to that. I have the original XP64 installation media available if required. Can I attempt to restore the system somehow? The error message reads: *** STOP: 0x0000000A (0x00000000000000AC,0x000000000000000C,0x0000000000000000,0xFFFFF80001055A59) Thanks!
Reply
Reply
_
_TheSpirit
05-22-2019, 01:36 AM #1

It was a stable XP-Pro-64 operating on Oracle VM VirtualBox. It has been working well for several years and was just a few days ago. The main system runs Windows 10 with a Ryzen 9 3900X processor. I was using a Windows Sandbox when attempting to launch VB Win XP64. This is the first time I've run a sandbox in the background, possibly related to that. I have the original XP64 installation media available if required. Can I attempt to restore the system somehow? The error message reads: *** STOP: 0x0000000A (0x00000000000000AC,0x000000000000000C,0x0000000000000000,0xFFFFF80001055A59) Thanks!

Reply
Reply
L
LittleEgg
Junior Member
Find
6
05-22-2019, 10:10 AM
#2
Consider turning off or removing the sandbox. If that fails, provide the memory dump from your VM at C:\Windows\MEMORY.DMP. If it's missing, verify if any files exist in C:\Windows\Minidump.
Reply
Reply
L
LittleEgg
05-22-2019, 10:10 AM #2

Consider turning off or removing the sandbox. If that fails, provide the memory dump from your VM at C:\Windows\MEMORY.DMP. If it's missing, verify if any files exist in C:\Windows\Minidump.

Reply
Reply
S
ScoooobyDoo
Junior Member
Find
29
05-22-2019, 02:07 PM
#3
I didn’t find any dump files on the Win 10 system. I opened the VDI using PowerISO, which took some time but succeeded. After extraction, I removed the Windows 10 Sandbox, and both VirtualBox and my Win XP 64 functioned properly. I was using Visual Basic 6.1.16, and it now runs on Visual Basic 6.1.32—possibly updated.
Reply
Reply
S
ScoooobyDoo
05-22-2019, 02:07 PM #3

I didn’t find any dump files on the Win 10 system. I opened the VDI using PowerISO, which took some time but succeeded. After extraction, I removed the Windows 10 Sandbox, and both VirtualBox and my Win XP 64 functioned properly. I was using Visual Basic 6.1.16, and it now runs on Visual Basic 6.1.32—possibly updated.

Reply
Reply