P35 Platinum and Vista/ACPI issue

I'm having problems trying to get Vista installed on my P35 Platinum-based system.  I'm getting an error at the beginning of Vista's installation that the BIOS doesn't support ACPI.  Well, that option is turned on in the BIOS, and I've toggled just about every setting under the Power Management section of the BIOS config utility, but nothing makes a difference.  I flashed the latest (1.2) BIOS to the board, no change.   I'm also seeing the computer go to a 'Safe to turn off your computer' screen rather than it just powering off - is this related? 
Any suggestions would be appreciated, thanks.

ACPI has to be enabled before you install XP. If you re-enable it after installing XP, you will get a bluescreen.  If you used an existing Windows Installation, that was set up under different system conditions, it probably didn't have the proper HAL drivers for the new  configuration.
If you re-install XP with ACPI, IOAPIC and MPS Table = 1.4 you shouldn't have any problems.
--> http://support.microsoft.com/?scid=kb%3Ben-us%3B309283&x=12&y=12
Quote
Device Manager does not permit the change from a Non-ACPI HAL to an ACPI HAL. You must use a new install of Windows XP or Windows Server 2003 for this kind of change. Change from an ACPI HAL to a Non-ACPI HAL only for troubleshooting purposes.

Similar Messages

  • MOVED: K9A Platinum and Vista 64 issues

    This topic has been moved to Vista problems.
    https://forum-en.msi.com/index.php?topic=109584.0

    Quote from: Paul B on 20-March-08, 23:05:39
    Hi all,
    Ok so I said I'd report back once all working and here i am (touches wood  )
    So my system is now Phenom less, I'm a bit gutted it's going back for RMA for refund. I have in the mean time replaced it with an x2 5000+ BE.
    So just a recap on my spec
    K9a2 Platinum
    x2 5000+ BE Running stock 2.6Ghz
    8GB OCZ DDR2 800 Platinum
    2 x 3870x2 in crossfire X mode.
    Windows Vista x64 OEM
    This OS now installed no issues no BSOD for secondary clock interrupt. But i did have issues installing it on the Promise raid array. Though it was the old more than 2GB ram thing so did the install with one stick and then Patch vista install the other 6GB but no still got system rebooting after the progress bar 9 times out of 10.
    So i have the HDDs on the standard SB600 sata ports as individual drives, installed x64 all 8GB still installed. Not knowing yet if it was driver related I let vista install all the drivers, the only other driver my system needed were the cat 8.3s and I only installed the graphics driver and CCC not the IDE or north bridge filter as the system is using vistas default drivers.
    I have installed all updates and everything seems rock solid. (touches more wood!!) I have spent the last week relentlessly trying to get this OS installed,  but hey I learnt a few things along the way..
    Paul
    But now it is and I have my 8GB and crossfire X I'm happy and when the good Phenoms arrive I'll get one but I'll read all the reviews on the web first....
    Hi,
    Right then resurecting an oldish thread, I have just purchased a Phenom 9750 and installed with the new 1.4 bios, and all is well. The same Vista x64 install is rock solid and damn quick now.
    Buy the B3 Phenoms with confidence they (AMD) have pulled back some ground and in my case some confidence.
    Paul

  • What is the difference between P35 Platinum and P35 Neo2 FIR?

    What is the difference between P35 Platinum and P35 Neo2 FIR?
    P35 Platinum
    P35 Neo2 FIR
    BIOS is identical?

    The P35 Neo2 is FIR is actually listed as P35 Neo2 FR/FIR. It is what you could call a "modular mainboard".  Even if it has the same PCB as the P35 Platinum mainboard, it doesn't necessarily mean, that it will always come with the same features.
    If you look at the mainboard manual you will find that the ICH9R-Chipset and Firewire are mentioned as optional features. That means you will be able to purchase versions of this mainboard that will only have an ICH9 chipset and therefore won't support RAID or that don't have a firewire interface. 
    The abbreviation F,I and R have the following meaning:
    F...Gigabit LAN
    I... Firewire
    R...RAID
    In case you decide to buy the P35 Neo2 mainboard, pay close attention to the feature list. Even if the board is listed as FIR by a specific dealer, make sure it really comes with firewire and an ICH9R-chipset. If someone decides to sell the board with the full name that appears on the MSI Support Site (FR/FIR) he might be actually trying to sell a P35 Neo2-F trying to get a better price. 

  • P35 Platinum and Realtek hd noise sound

    I experience this hiss and crackle noise in the sound on my system and I dont know what causes this.
    P35 platinum
    q6600 processor
    4GB ram (2 working ram sticks in right mem slots)
    Latest Realtek hd driver installed afaik
    Vista 64bit
    I want to ask, could this be some IRQ issue? If so, feel free to teach me how to manage this, as this is beyond me.

    Ah, apparantly the noise go away if I switch from front end jacks to rear end jacks on my computer cabinet. I'll just see if I can figure this out on my own then.

  • P965 Platinum and Vista x64 RAID config?

    Ok, I have looked all over this forum for Vista x64 issues. Nothing even comes close to my problem. When I load Windows Vista Ultimate x64 Edition onto a clean SATAII drive (single non-RAID drive) I have no problems what-so-ever.
    Now here is when it really gets weird. When I run install on a RAID array (2 SATAII Seagate 160GB drives) I see issues in the install. First thing I see is it corrupts the data on the first drive. This causes a blue screen at restart. When I go into the RAID config (ctrl+I) I see the first drive has errors. The only thing I can do is delete the RAID and start over.
    When I reinstall Win XP Pro X64 I have no problems at all. I have downloaded the latest drivers from the downloads section and I have tried the newer Intel drivers. Non work!
    Computer info:
    CPU: Intel 3.4GHz Pentium D x64
    MB: MSI P965 Platinum
    Storage: 2x Seagate 160GB SATAII
    RAID: Intel ICH7R/ICH8R SATA RAID driver 2006-08-29 (and have tried the newer driver from Intel)
    If you need more just ask!
    Oh yeah, I looked at the specs sheet for the P965. They need to remove the NEC 3550 from the "OK" list since it does not Wright period or READ at install. I went through a big deal with MSI about this and they still have not removed it.

    Well sh**! I borrowed a friends Vista x86 and found it to also have the same issue. Would not even load the "Choose Drive" screen or allow me to even install the RAID drivers.
    Man when a board gets Vista approved is must not take much. I have had compatibility issues with this board since day one. I think maybe it is time to through it away. What a shame since it is only a few months old.

  • P35 Platinum and eSata problem

    I recently bought a WD My Book Premium ES 500GB and when i try to connect it via eSata cable, it doesn't work.My system can't recognize the drive, it doesn't show up in BIOS screen where HDD's are. I tried 2 different eSata cables but nothing.Via USB2 connection it works fine.
    My system Specs are: Intel Core 2 Duo E6600,MSI P35 Platinum Mobo with latest BIOS update 1.1, 2GB RAM DDR2, Asus X1950XT VGA,Tagan 500W PSU.
    I tried both eSata ports at the Back Panel of my motherboard but none worked with My Book.
    Is there a problem with My Book? or is a compatibility issue?

    Make sure you have set the switch or whatever your external drive has, to E-Sata mode.  I'm sure you probably already did that but just sayin! 
    I have a different board AND different external drive but after playing with my setup for a whole day trying to get the esata to work, it finally dawned on me that I had not set the switch from  USB to Esata (no wisecracks please 
    As soon as I did the switch, the Esata started working just fine.
    GL

  • P35 Platinum and WD Hard Disks unrecognised on cold boot

    Hi,
    I am having a problem with my WD drives on my P35 Platinum motherboard. Simply, if I power down my PC neither drive is recognised when I boot up again. Usually I have to open the PC, reseat the SATA cables (this may be a red herring) and then when restarted the drives are recognised again.
    A simple restart from within Windows (warm boot) works every time.
    I would have suspected a cabling connection problem, except that I have tried other cables and also the fact that it is both drives every time, rather than one, other or both randomly.
    I have seen other people having problems with the spin-up time of WD drives and have disabled quick booting in the BIOS, but this has not helped much. I have also verified that the RAID Mode is set to IDE, as I am not using any RAID features.
    The disks themselves are plugged into SATA3 & SATA4, whilst my Pioneer DVD Writer is plugged into SATA5.
    I have the latest BIOS installed but cannot remember the version number off the top of the head, my full hardware spec is in my sig and the 160GB drive is my system disk.
    Does anyone have any other suggestions that I could try?
    Apart from this issue my PC works flawlessly.
    Regards,
    Charles

    Quote
    CoolerMaster 700W REAL POWER PRO MODULAR PSU (RS-700-ASAA-A1)
    I would suggest not to use a CoolerMaster REAL POWER PSU for your P35 Platinum.  There are known compatibility issues with these devices:
    https://forum-en.msi.com/index.php?topic=114534.0
    Quote
    not being able to power on with the Cooler Master Real Power Pro 750w PSU. After I push the power button, it will light up for a second and the fans will spin, but it just doesn't power up. I am able to power it on with some generic 500w PSU and my girlfriend's Silverstone 850w PSU, but it always fails to power up when I plug the Cooler Master PSU in.
    https://forum-en.msi.com/index.php?topic=113573.0
    Quote
    System powers on for a split second, then powers off. System will boot with another power supply, just not this one.
    https://forum-en.msi.com/index.php?topic=113573.0
    Quote
    Just FYI though, it appears (by some comments on Newegg.com) that there is some compatibility issue between my CoolerMaster Real Power Pro 750W and the P35 Neo2-FR motherboard.  The power supply worked fine by itself, and the motherboard ended up working fine with a different power supply (Antec Neopower 650 Blue).
    https://forum-en.msi.com/index.php?topic=115623.msg869170#msg869170
    Quote
    with 700w cooler master psu system wont boot or post, fan start about 3 sec then quit
    no beeps, no leds.
    with others psu's EVEN CHEAP 450W OR 500W system post FINE!!!
    https://forum-en.msi.com/index.php?topic=115623.msg869170#msg869170
    Quote
    We had the same (ground) issues with Real Power Pro 550W, 650W and 750W.
    In fact all of them are based on the same "hardware"
    https://forum-en.msi.com/index.php?topic=115623.msg869135#msg869135
    Quote
    They suspect a ground issue, but also have been reported several 12V rail "abnormal behaviours".
    http://forum.coolermaster.com/viewtopic.php?p=79607
    Quote
    MSI P35 Neo2-FR not compatible with Real Power 750W

  • P35 Platinum and Patriot Memory DDR2 PC6400

    Hello,
    I've tried to adjust RAM Timings, RAM Voltage and RAM frequency manually on my P35 Platinum with BIOS 1.4. I had a reboot loop at CAS 4 so I've tried to put at 1000 MHZ ratio 2:3 after a clear CMOS. It's working.
    Now my Patriot Memory is working at CAS 5 ratio 2:3 2,2V and 1000 MHz.
    Should I carry on my "quest" to CAS 4 or are these settings good enough? I'm quite lost.....What should I have to do?
    Does Patriot Memory owners experienced the same issue? Why can't they be set to CAS 4?
    One more thing: After the Post, the Marvell Bios loads but find no hard disk on adapter 1. With Bios 1.1, there was no problem. Do you have any explanations?
    Thanks

    Hello Spikape,
    please list full system specs and provide more information about the specific model/type of Patriot Memory you are using.
    Quote
    I had a reboot loop at CAS 4
    Can you try to be more specific about this?  Was it an on-->off-->on-->boot cycle or did your system reboot multiple times?

  • P35 Platinum and MSI 8600 GT problem

    I have a problem with the computer locking up. It will do it on certain web sites, clicking around in Media player and other programs. I tried everything I could think of. Finally I Got an 8400 video card locally and everything is fine. My question is, since the 8600 GT gets all of it's power from the PCIE slot could it be a voltage problem? If so, I see no way of increasing the PCIE voltage in the bios for this MB.
    Any ideas before I send this card back?
    Thanks,
    Bill
    Msi P35 Platinum Motherboard
    Core2Duo 6850
    2 gig Corsair XMS2 6400C4D Dominator Memory
    OCZ Stealth X Stream 600 Watt Powersupply

    It locked up with default bios settings and no overclocking. I didn't overclock the video card at all. I tried everything. Since I put in a temporary 8400GTS I have the processor overclocked to 3.3gig and everything is fine. Could the 8400 need less power than the 8600GT and if so is there a way to increase the voltage on the 16X PCIE slot? This is a MSI MB and MSI Video card so I would expect them to work together.

  • P35 Platinum and NX8800GTS

    I have both motherboard and graphic card from MSI (oh yeah ):
    - Graphic card : NX8800GTS T2D640OE
    - Motherboard : P35 Platinum (MS-7345 v1.x)
    And I have question about power connectors on board of graphic card and motherboard. On motherboard there is power connector sweetly called JPWR1, described in manual as "JPWR1 12V power connector is used to provide power to the PCIEX16 graphics card".
    But on graphic card is already power connector. I can plug in specific cable that divides in two normal power connectors to connect to power supply.
    It is safe to plug in all three connectors to power supply? (one to JPWR1 on motherboard, two to graph card through this special cable)
    It is even neccessary to plug in all connectors?

    Quote
    Quote from: madcio on 15-August-07, 04:14:18
    CPU: Intel Core 2 Duo E6850 3.00 GHz LGA 775
    RAM: 4x Kingston 1024 MB DDR2 (2x two in each package - Dual Channel)
    Hard drive: Segate SATA-II 500 Gb
    DVD Drive: DVD R/RW LG LightScribe
    Maybe I will buy another hard drive in future, but nothing more.
    I punched your component list into the eXtreme Power Supply Calculator v2.5.  Only the Pro-Version (not free) shows the amperages on the different rails (+12V, +5V, +3,3V).  The overall wattage if a PSU doesn't really really mean anything without the amperage values.
    Anyways, I selected "High End Desktop Mainboard", "2 SATA drives" in the component list, added three 120mm fans, three USB devices and one additional PCI card. I also set CPU Utilization (TDP) to 100%.
    The result is:
    Quote
    373W
    +12V: 23A
    +5V: 13.4A
    3.3V: 9A
    On the bottom the is footnote to the option called "Electrolytic capacitor aging" that says:
    Quote
    When used heavily or over an extended period of time (1+ years) a power supply will slowly lose some of its initial wattage capacity. We recommend you add 10-20% if you plan to keep your PSU for more than 1 year, or 20-30% for 24/7 usage and 1+ years.
    When I enter 15% the calculation adds up to:
    Quote
    429W
    +12V: 26.5A
    +5V: 15.4A
    3.3V: 10.4A
    Finally, I overclocked your CPU to 4GHz / VCore 1.4V:
    Quote
    481W
    +12V: 30.8A
    +5V: 15.4A
    3.3V: 10.4A
    I don't know how accurate these calculations are.  In any case, they should give you an idea of your systems power consumption.  When I choose PSUs I always make sure I have a headroom of about 30% in the +12V-amperages.  So if I was you I would get a PSU with about 36-40A maximum amperage on the +12V-Rail, depending if I plan to overclock the CPU or not. 
    Many users in this forum will recommend choosing a Single +12V-rail PSU.  One of the reason is you won't have to worry about problems due to inbalanced power loads or wasted power resources.
    If you plan to get a PSU with two +12V-rails, make sure that the maximum amperage on each rail is at least 18-20A.  Maximum combined amperage on +12V should not be less than 36-40A. 

  • P35 Platinum and OCZ FLEX 2 4gb

       Hello !
       My sistem spec are :   core 2 quad 6600 G0
                                      P35 Platinum  1.6 bios
                                      2*2gb OCZ Flex 9200 55515  2.1v
                                      Gigabyte 3870
                                      etc
      I have a big problem overcloking my memorii over 1150 mhz . I need to set manualy  tRD (Read Delay) some call it Transaction booster, some performance level.
      The bios dosn't have this option !!!
      I want to set manualy all this options  :
      tRFC    , tRD  , Write to precharge delay  , Write to read delay (tWTR )  ,  tRRD , tRD_WR , tRTP , tREF . CR
      Some of this setings are not in bios. What bios should i use ?  or what can i do to have acces to manualy configure this ???

    Hello,
    note that the P35 Chipset natively supports only DDR2-667 and DDR2-800 memory modules.  From the point of view of the memory controller, DDR2-1066 is already overclocking. 
    Quote
    I have a big problem overcloking my memorii over 1150 mhz
    One reason for inventing DDR3-RAM was to be able to reach higher frequencies.  So you may have reached the limits here.
    Quote
    I need to set manualy  tRD (Read Delay) some call it Transaction booster, some performance level.
      The bios dosn't have this option !!!
    Have you tried using Memset to be able to tweak additional timings?
    http://www.tweakers.fr/memset.html

  • P35 Platinum and 533mhz ddr2

    Hi
    I have a msi 915g motherboard , p4 3.4 (550) 1x533mhz ddr2 550psu and an 7600gt.
    I want to buy the P35 Platinum .
    Will my 533mhz ddr2 work on the P35 Platinum?
    Thanks

    The 2900 bits the 8800 gts in allot of benchmarks and its value rocks
    I've found
     the 2900 in a Greek eshop for 330 euros and the cheapest 8800 is 280 euros.
    50 euros more is nothing compared to the performance difference between the two vga's
    http://www.plaisio.gr/productlist.aspx?catalog=1&category=26174053&MSCSProfile=DCCDF22EB27065BE78648BEA519355291CFBC9442200057CD056AE3C9ED619317D475D9D692FD098F5DA07BA605E19BA198659AD4EBFC920D75C4DE3C1260C410B349F88874AC27496C30A32AAE0B80D6FDEBFFC7556465F48E17B94FFA8BBF65A9617E126A3F7068BD5A3D2F3BBB657D96426480C2E383960FFDD3E7F72A205

  • MOVED: P35 Platinum and Q9550 OC

    This topic has been moved to Overclockers & Modding Corner.
    https://forum-en.msi.com/index.php?topic=140837.0

    Ah OK took me a while but last night finally looked at OCing the Q9550 with my P35 Platinum.
    Not spent lots of time on it so far but a couple of questions if I may?
    It was not happy having the cpu volts on auto when trying 3.4GHZ so have been gradually increasing the FSB and vcore manually.
    My cpu has a VID of 1.1 volts.
    When I manually increase the voltage in the bios it suggests anything highlighted in red might cause instability, and 1.1875 is the first increment that is highlighted in red.
    1. This seems a little low to me for a warning, is this MSI being cautious as the Q9550 can go higher than that? (temperatures were in the high 50s during prime95)
    At this voltage I have reached 3.3 GHZ so far but will increase as long as its safe to raise the voltage?
    I would like to hit a stable 3.4GHZ as Bernhard reached happily so that my ram is running at the correct speed (800) with the divider set at 1:1. (its about 777 at the moment).
    2. How would I know if any instabilities were due to the vcore being too low or if the NB volts needed tweaking?
    Any pointers would be appreciated as I'm quite inexperienced at this.
    Thanks

  • P35 Platinum and 1066mhz Ram OC

    Hi there I just bought 4 x 1GB DDR2 1066mhz just would like to know how to set it to run at that speed can anybody help me out im looking for the easyiest way
    Specs:
    MSI P35 Platinum bios v1.8
    MSI 8800GT 512mb OC
    Intel Q9300
    4GB 1066mhz Ram DDR2
    Zalman 750watt PSU

    you have to change the FSR: DRAM Ratio.... Your quad has 333mhz of FSB (if you didn't OC), so... you have to choose between 1:1.5 -> to push the mems to DDR 1000mhz (333 x 1.5 = 500mhz) or 1:1.66 to obtain DDR 1100mhz (333 x 1.66 = 550mhz)...
    EDIT: see the especifications of your mems, surely they need 2.1v at least to go at 1000 or 1100mhz

  • MSI K9A Platinum and VIA drivers issue? XP 0x0000007B stop error.

    I get a Windows Stop error when trying to boot into Windows XP with new components. The SATA hard drive (and Windows XP installation) is from the old computer.
    The new computer components are:
    MB: MSI K9A Platinum, chipset: RD580 (North Bridge), SB600 (South Bridge)
    CPU: AMD Athlon 64 x2 5600+, boxed (the cooler and fan came with the CPU).
    Video: MSI Radeon 1950 XTX
    The old (and working) computer setup is:
    OS: XP Professional
    MB: Abit AV8-3rd Eye, chipset: VIA K8T800Pro + VT8237
    CPU: AMD Athlon 64 3500+
    Video: Sapphire Radeon 9800Pro All-in-Wonder, videodriver: atidvag.dll version 6.14.10.6542
    HD: Maxtor 6B200M0 SCSI Disk Device
    BIOS: Phoenix 6.00PG 20.04.2005
    System drivers with "via" in the name: VIAAGP1.SYS, viaide.sys, viasride.sys
    VIA 4in1 (Hyperion) version: 4.55 (that can be found at HKEY_Local_Machine\Software\Via4in1Driver).
    VIA 2.20e SATA/RAID driver was used when installing this computer setup.
    The precise stop error is:
    0x0000007B (0xba4c3528, 0xc0000034, 0x00000000, 0x00000000)
    From many sites I have gathered that the error is related to Windows XP not being able to access a critical system drive. Most probably the SATA hard drive issue.
    The problem probably is the VIA drivers of the old motherboard and/or the SATA driver.
    First I should mention, that MSI K9A Platinum does not have a hard disk SATA driver. If it does, I have been unable to find one. Certainly no such floppy disk included, and no such driver in the MSI's Web page for this motherboard.
    Second important point: I never used RAID. I did use VIA 2.20e SATA/RAID driver disk when installing Windows XP to the old computer.
    Strange that the hard drive model is reported as a "SCSI Disk Device". It's not a SCSI drive however: it's a SATA disk.
    I have tried to uninstal the motherboard chipset drivers (Hyperion v4.55), but there seems to be a bug here: the drivers should be uninstalled using the installation program, and select the uninstall option. However, I do not get the uninstallation option to choose at all! Yes, I'm using the normal installation mode, not the quick installation (although tried that, too). The Hyperion setup program just installs, and asks to reboot the computer. After rebooting and trying again, it still does not offer me an uninstallation choise.
    I know how to install hard drive VIA SATA driver, but I have no idea how to uninstall it. And I'm afraid to do that without certainty that it IS the solution, since I could not access the hard drive any more in the old computer setup (and return to read this forum). Also, I do not have a floppy drive any more. Anyone know if there is an issue with K9A and XP having VIA SATA driver installed?
    When I tried the new computer setup, I first tried the simplest possible hardware combination: there were no CD/DVD-drives, no (parallel)IDE hard drives, and no PCI cards, except the MSI video adapter.
    My BIOS Setup experiments. None of these helped: got the same stop error each time.
    1) I didn't much touch the BIOS setting first. Just tried to boot with the settings BIOS came with.
    2) Next I disabled the integrated audio, LAN and IEE1394 devices and floppy drive and disabled all other choises except the SATA drive as a boot device.
    3) Next I tried with the fail-safe BIOS defaults.
    4) Cleared CMOS.
    5) Changed OnChip SATA type from Native IDE to Legacy IDE. (Only one boot attempt with the setting as Legacy.)
    6) Disabled PCI IDE BusMaster.
    7) Never touched anything in the Cell Menu: so the settings are in minimum.
    A step I have taken after the last attempt: run Windows XP hard drive error-checking tool to every logical drive with the fix option selected, and the system drive also with scan the bad sectors option selected.
    My plans next are:
    1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
    2) to disable USB-devices in the BIOS (desperate),
    3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
    4) to uninstall the Anti-Virus software (Avira Antivir).
    I've read a numerous Web pages so far about the 0x0000007B stop error. Here are some links:
    Quote
    http://www.seagate.com/www/en-us/support/knowledge_base/
    Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
    This Stop message, also known as Stop 0x7B, indicates that Windows XP Professional lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following:
        * Hardware problems
        * Corrupted or incompatible storage drivers
        * File system problems
        * Boot sector viruses
        * Outdated firmware
    During I/O system initialization, this error can occur when:
        * The controller or driver for the startup device (typically the hard disk) failed to initialize the necessary hardware.
        * File system initialization failed because the system did not recognize the data on the boot device.
    Quote
    http://support.microsoft.com/kb/314082
    You receive a Stop 0x0000007B error after you move the Windows XP system disk to another computer
    SYMPTOMS
    After you move the Microsoft Windows XP system (boot) disk to a backup computer, you may receive the following Stop error when you try to start the Windows XP-based backup computer:
    STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
    CAUSE
    This error may occur if the registry entries and the drivers for the mass storage controller hardware in the backup computer are not installed in Windows XP.
    RESOLUTION
    To resolve this error, use the same hardware for the backup computer.
    Heh, heh! Very nice Microsoft, but I plan to update my computer, so I NEED to use different components
    Quote
    http://support.microsoft.com/kb/324103
    Device Driver Issues
    You may receive a "Stop 0x0000007B" error message in the following scenarios:
    •   A device driver that the computer boot controller needs is not configured to start during the startup process.
    •   A device driver that the computer boot controller needs is corrupted.
    •   Information in the Windows XP registry (information related to how the device drivers load during startup) is corrupted.
    Hardware Issues
    You may receive a "Stop 0x0000007B" error message if there is a resource conflict between the boot controller and another controller or between SCSI devices. You may also receive this Stop error message if drive translation is not being performed or if drive translation was changed. To troubleshoot this issue:
    1.   If an IRQ or I/O port address conflict exists between the boot controller and another controller, Windows XP either stops responding (hangs) or displays a "Stop 0x0000007B" error message. If you recently added new hardware, remove the new hardware or reconfigure it so that it does not conflict with the resources of any other installed controllers.
    2.   If you are using a SCSI hard disk, check the SCSI chain for correct termination. Remove any unused SCSI devices or make sure that each SCSI ID is unique.
    3.   Make sure that drive translation is turned on (if it is required) and that it has not been changed. For example, if you recently switched controllers, this issue may occur. For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 314082.
    Quote
    http://support.microsoft.com/kb/316401/
    SYMPTOMS
    When you start your Microsoft Windows XP-based computer after you replace the motherboard on the computer, you may receive a Stop error message that is similar to the following:
    STOP 0x0000007B INACCESSABLE_BOOT_DEVICE
    CAUSE
    This issue may occur if the new motherboard contains an embedded IDE controller that has a different chipset than the original motherboard.
    RESOLUTION
    Method 1: Perform an in-place upgrade of Windows XP [<- That means repair installation of Windows XP]
    •   Do not use a repair or in-place upgrade if you suspect disk problems.
    Method 2: Repartition and format your hard disk and reinstall Windows XP

    Alright I got the situation over.
    Quote from: Roskaposti on 19-May-07, 04:44:59
    My plans next are:
    1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
    2) to disable USB-devices in the BIOS (desperate),
    3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
    4) to uninstall the Anti-Virus software (Avira Antivir).
    I did try all all the above, and none of them helped.
    And by the way: after installing the new Hyperion (VIA chipset drivers), I was finally able to also uninstall. It also uninstalled the IDE SATA (I think) and PATA drivers.
    But what I had to do, was to make a REPAIR installation of Windows XP.
    So, I was wondering now afterwards: this is really, really silly. Why the hell we need to re-install Windows if we move the SYSTEM SATA drive to another computer? We don't have similar problem with parallel IDE drives. Whom should we thank here??
    The issue is to insert the driver files and the information of the ide drivers Windows should use with the next boot. How can it be this difficult?
    What you basically need is..
    - the information about the new chipset's PCIIDE.SYS/[VENDOR_PROVIDED_FILE].SYS and ATAPIIDE.SYS inserted into the values in HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\CriticalDeviceDatabase
    - and the vendor's IDE drivers to the %SYSTEMROOT%/System32/drivers folder.
    Maybe something else, I don't know. But the problem was, Windows didn't know how, or what drivers to use. That can't be so big problem you need to install the whole OS anew!

Maybe you are looking for