Windows XP SP3 bsod during installation (Intel SATA drivers)

[lolindir]

Dear all,

I was trying to install windows XP SP3 with the latest Intel SATA drivers (9.6.0.1014) integrated in the installation ISO (done with nlite). During the installation however I 'm getting a bsod (whether I chose an IDE controller for my HD or a SATA controller).

When using a normal IDE controller (ICH6), I'm getting the following error:

BAD_POOL_HEADER

...

***STOP: 0x00000019 (0x00000020, 0xF8471538, 0xF8471B50, 0xCCC35D5B)

*** acpi.sys - Address F8471538 base at F845B000, DateStamp 480252b1
*** acpi.sys - Address F8471B50 base at F845B000, DateStamp 480252b1

When not integrating the Intel drivers, the installation with IDE controller is succeeding, so it has something to do with the integrated drivers from Intel.

Does anyone know what's going wrong? Is this a bug in VB?

Thanks for your help!

[mpack]

I see no evidence for believing any VBox bug is involved. We know the virtual SATA hardware works.

Perhaps you should try asking this on a Microsoft site: be sure to tell them you have created your own non-standard install CD, are getting BSODs during setup, and now are looking for free technical support. I expect they'll be quite amused!

[vbox4me2]

There is a bug of some sorts, I'd had it as well when upgrading from 2.2.4 to 3.1.x, but after removing the whole sata stuff it seems the ide drivers work just as fast with a sata Host as it did before 3.1 with sata drivers. Some VM's keep working(w2k, linux) but most crash(xp,w3k,w8k), maybe you need never ahci drivers but currently with 3.1 there's little difference in HD speed.

[Simple User]

@ lolindir
The drivers you're using are the culprits.
Use the drivers mentioned in the following post:
SATA Drivers AHCI v7.0.0.1020 for ICH8
Just proceed the usual way using nLite, choose Intel(R) 82801 HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M) when prompted.

[ozhoo]

Bump..

Should we always expect that VirtualBox will only work with drivers that are 2 or more major revisions behind Intel's? Is there a bug open for this?

[mpack]

If you have a continuing problem with SATA virtualization in VirtualBox then I suggest you open a new thread and describe your problem thoroughly.

[Sasquatch]

This is not a VB problem or anything else. Intel just ditched the support for this SATA controller in their newer versions. My previous laptop has an ICH7M controller and it just won't work with newer versions of the Matrix Storage Controller, because it's no longer supported. Just check the release notes of the driver!

[yoonux]

I've done a lot of experimenting with Intel's AHCI drivers, v7,v8,v9 on vboxes and real boxes. My advice is not to use them at all during installs of XP. They cause serious memory leaks that screw the installation kernel, even when AHCI isn't selected in the BIOS or vbox setup. Don't slipstream the drivers with nLite (BSOD at "32 mins left") and don't use F6 during startup (BSOD after 15 secs). v7 appears to work with vbox installs, whereas only v9 works on my Gigabyte mobo. Perhaps the memory leaks didn't BSODomize the kernel, but there's no guarantee of a correct install.

After installation you can convert XP to run on an AHCI port. I've not had any trouble doing this. An external enclosure or eSata docking station is very useful, and less than $30. Don't switch to an AHCI port until the drivers are running properly. Doing RAID with XP will require a lot of preparation. On a vbox, why bother doing XP on the SATA bus. Virtual docking stations don't exist yet!

>There is a bug of some sorts,
YES! Its in the Intel drivers, all versions. WHQL = What a Horrible Questionable Load of sh*t. To prove the point try the following test. We know that slipstreaming or F6ing the v9 drivers into an XP install causes a BSOD (see above).
* Do a very clean install of XP-SP2 or SP3. Don't install any drivers. Select ICH6 bus only. No SATA bus.
* Don't install GuestAdditions yet. (Will need to rght-Ctl and recapture the cursor to control it)
* Powerdown and turn on the SATA-AHCI bus. Leave the v9 drivers (the F6 ones) in a shared folder or floppy.
* Powerup and let XP detect the bus and bring up the driver window. Browse the v9 drivers and let XP install then.

Reboot and the v9 drivers work fine. Powerdown and transfer the XP disk over to the SATA bus. Reboot and it all works 100%. n.b. I have used XP-Pro-SP2, and SP3.

Intel drivers are no good for installing XP. QED

[mpack]

On a vbox, why bother doing XP on the SATA bus. Virtual docking stations don't exist yet!

Docking stations are not the only reason to use SATA in the physical world. Performance advantages exist too, and it's alleged that the performance advantage also applies to the virtual version - I say alleged because I've never personally attempted to measure it.

[Sasquatch]

@yoonux,
You must have screwed up something, because I can use any Intel driver between 5.5 and 7.8 of the Matrix Storage Manager and have no memory leaks or anything. I have created all my XP VMs with nLite, slipstreamed the drivers in it, no problems. They all run smooth and the memory consumption stays within it's set limit.

[yoonux]

Sigh! Mr. Sasq is one of those. Last time I bother with this site.

READ MY POST BEFORE REPLYING COMPLETE RUBBISH!

I said v7 works in VirtualBox, but v9 BSODs, when using these drivers during XP installs. If you actaully READ the f*cking release notes for v9 you will see it covers all but the oldest chipsets. I have show you how to use v9 in VBox without getting a BSOD. Intel AHCI drivers cause memory leaks when used with the XP installation kernel.
I suspect Sasq. does not know what a memory leak is!

Good bye permanently

[Sasquatch]

It seems YOU never read MY reply a bit up where I stated CLEARLY that Intel had DROPPED the support for the older controllers. Here's the post itself:

This is not a VB problem or anything else. Intel just ditched the support for this SATA controller in their newer versions. My previous laptop has an ICH7M controller and it just won't work with newer versions of the Matrix Storage Controller, because it's no longer supported. Just check the release notes of the driver!