WinXP BSOD 0x0000001a Memory Management

Discussions about using Windows guests in VirtualBox.
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

Hi
ich versuche seit Tagen verzweifelt Win XP in der Virtual Box auf einem Win 7 64 bit Rechner zum laufen zu bekommen...

Hab es jetzt Testweise auch auf meinem Laptop probiert, da funktioniert alles ohne Probleme... Beide Systeme, PC und Laptop, hab ich erst frisch formatiert und alles Installiert (Treiber).
Wenn ich jetzt auf dem PC die VB installiere, die VM erstelle und starte, funktioniert noch alles perfekt. Ich starte von der WIN XP CD und die Installation läuft auch ganz normal an... Bei einem Installationsfortschritt zwischen 20 und 40 Prozent, konmt dann plötzlich der oben genannte BSOD...
Hab schon sämtliche Einstellungen geändert und probiert, leider ohne Erfolg...

Mein System:

amd x6 1090 T
Gforce gtx 460
samsung ssd mit 128 gb

Schon mal vielen vielen Dank für Eure Hilfe im Vorraus
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: WinXP BSOD 0x0000001a Memory Management

Post by mpack »

VBox version?

VM log file?
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

Re: WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

tried every version... now i have installed 4.0.18
Attachments
xp-2014-09-25-13-35-08.log
(69.12 KiB) Downloaded 12 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: WinXP BSOD 0x0000001a Memory Management

Post by mpack »

Krokette wrote:tried every version... now i have installed 4.0.18
Why would you do that? Try 4.3.12, provide a screenshot of the error and a log file from that version.
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

Re: WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

version 4.3.12 dosent start the vm...
Attachments
fehler1.PNG
fehler1.PNG (105.73 KiB) Viewed 5354 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: WinXP BSOD 0x0000001a Memory Management

Post by mpack »

Do a full uninstall of VirtualBox. Make sure it is gone completely. Reboot the host, then reinstall VirtualBox using "Run as administrator".
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

Re: WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

now the bsod and the log from 4.3.12
Attachments
xp-2014-09-25-15-51-25.log
(76.36 KiB) Downloaded 13 times
fehler2.PNG
fehler2.PNG (50.75 KiB) Viewed 5346 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: WinXP BSOD 0x0000001a Memory Management

Post by mpack »

Where did this VM come from, and has it ever previously worked as a VirtualBox VM?

Basically, this looks to me like a driver crash inside the guest, which is something you might see in a Physical to Virtual migration project. Is that what this is? If so you can try booting the guest in safe mode.

p.s. If you like, I'll move this topic to "Windows Guests", since this is no longer a German language discussion.
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

Re: WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

ive downloaded this vm from this site... so i think it should work... on my laptop it works fine...

i cant boot the guest in safe mode because this bsod appears during the installation of xp...

what do you mean with "...you might see in a physical to virtual migration project."

you can move this topic to "windows guests"
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: WinXP BSOD 0x0000001a Memory Management

Post by mpack »

Topic moved to "Windows Guests".

A "physical to virtual migration project" (P2V for short) is when you make an image of the hard drive of a physical PC, and use the image as the hard drive in a virtual PC. It's quite common to do that with old XP PCs, which is why I wondered if it had been done here.

XP is copyrighted software. If this is downloaded from a warez site then I won't be able to help you any further. I suggest that you try to get a legal, licensed copy of an full XP setup CD. Copyright aside, we can only support official distributions because those are the only ones we can be sure about.
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

Re: WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

on the host pc is a original win 7 installed and activated... for the guest i want the old xp because my scanner didnt work on win 7 64 bit... its a original win xp...
i didnt make any images...

i installed win 7 and all drivers and updates, then i installed vb and tried to install win xp... thats all i have done...

btw... on my laptop it works...
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: WinXP BSOD 0x0000001a Memory Management

Post by mpack »

I just noticed that the log you provided is from 4.3.16, and not 4.3.12. I had good reason for not recommending 4.3.16!
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: WinXP BSOD 0x0000001a Memory Management

Post by mpack »

I also notice that the host doesn't provide any DMI information. Is this a home built PC? Running a memory test on the host might rule out problems with the host hardware.
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

Re: WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

yes, its a homebuild pc... build it 2 years ago and had no problems with it... i also made a memtest... without any errors...
Krokette
Posts: 12
Joined: 25. Sep 2014, 11:43

Re: WinXP BSOD 0x0000001a Memory Management

Post by Krokette »

no more ideas...??? :(

edit: same problem with 4.3.12
Post Reply