GT60 2OC-024 and Windows7 Drivers

Hi
i got the new GT60 with the win8 preinstalled and i installed Win7 on it and i downloaded the drivers from the MSI web site and the utilities from MSI web site,
but the SCM don't show the bluetooth for disable /enable ,i tried the SCM from Win8 on Win7 and it has not Wireless nor bluetooth,and i tried to update the last nvidia driver from the website "Beta" after i uninstalled mine ,but it says that it's not compatible HW so get back to the old one i have from MSI web site but it says the same now
the Model :GT60 2OC-024
CPU:Intel 4900
GPU:Nvidia GeForce GTX 770M
Chipset:Intel HM87 Chipset
LAN:Killer DoubleShot
Wireless LAN:Killer DoubleShot
i tried to use the Driver Genius Pro to update the driver  but it didn't download the drivers
any help

Quote from: Tamer on 03-September-13, 13:55:43
i contacted the MSI support and they said that i need to update the EC,i did update the EC by the link they give my using WinFlasher not the DOS flasher and nothing changed, so i talked to them again and then they told me to flash the Bios ,and they give me a shortcut to disable the bluetooth "Fn+F9" so i asked them to the complete list of shortcuts so i don't need to flash the bios and my problem is solved,but they give me instructions in win8 to disable the wireless :( even if i told them it's win7  .
so if any one has a complete list of shortcuts that do the action of the SCM ,please give it to me.
i'll try to flash the bios by the forum tool with the bios they give me
Well, to be perfectly honest, the problem with the soft keys is actually in the electronic controller. We've seen it and proven this out a number of times, unfortunately MSI Engineers still believe the problem does not exist, and that it should work fine in both Windows 7 and Windows 8.
All I can say is to call in and continue doing what they ask. Eventually they will run out of things to do and just keep commenting that the shortcuts above the keyboard are controlled by the electronic controller, and perhaps the firmware isn't working properly in Windows 7.
The unfortunate aspect of this, is even if you flashed the Win 7 EC firmware (DO NOT DO THIS), other functions will not work properly.

Similar Messages

  • MSI GT60 2OC - Is my GPU Dead?

    Hello,
    I bought MSI GT60 2OC few days ago and it seems that there is something wrong with the main GPU. I've noticed poor performance in game and when I try to update nvidia drivers I got a message that the hardware cannot be found. When I try to acces the nvidia control panel I got a message the user do not use a monitor connected to NVIDIA graphic card. What should I do? I bought it in Poland few days ago (I'm in UK now and it would be expensive to send it back to the store). I live in Coventry and I found following address on the MSI website:
    United Kingdom
    D&J HENRY LTD,
    Address: Unit 3B Quinn Close, Seven Stars Industrial Estate,Coventry CV3 4LH
    Tel:(024) 76886800
    Fax:(024) 76886801
    Can I just take it there to get it fixed? It's just few miles from my place.
    Or maybe I need to install something/update windows 8?
    I'm using original OS and all drivers from the cd that I got with the laptop (used one touch instalation).
    Regards
    Greg

    Quote from: darkhawk on 08-September-13, 09:06:00
    Try those drivers.
    Most likely the problem is either the computer isn't switching to the NVidia card when the game is launched, or the GPU/CPU are overheating and throttling back. This could be caused by bad thermal compound or it being installed incorrectly (which isn't unheard of).
    I manage to install it but still can't access the nvidia panel and can't even get through borderlands 2 menu.
    Tomorrow I will call msi support and hopefully they will be able to get it fixed. Anyone already tried this UK warranty repair service based in Coventry?

  • GT60 2OC-030UK DPC Watchdog Violation

    Hi all. I bought a GT60 2OC laptop about two weeks ago for my studies and gaming at University and it has been nothing but a nightmare. At first it would bluescreen randomly but I managed to track the error down to the Killer drivers that were preinstalled. Slightly annoying that a laptop could be sold not in working condition but I updated them and all seemed to be well.
    Then the dreaded bluescreen struck again, while listening to music. It said DPC Watchdog Violation which from a bit of googling appears to be related to SSDs not being compatible with Windows 8. I'm sure this is not the case as surely nobody would sell a laptop with parts that aren't compatible, but I would like to know if there is a fix for this issue as it's happened within two weeks of me buying the laptop and I really want everything to be working before university.
    I'm also very disappointed with the laptop in general, my old PC had 3 BSOD's in it's 4 years of use, this laptop has had 4 BSOD's in two weeks. Any help would be greatly appreciated as I spent quite a lot of money on this and it's very upsetting that it doesn't work.

    Quote from: darkhawk on 29-August-13, 21:45:45
    Also....
    [can't post external links]
    Knowing that, were you trying to do anything at the time when the BSoD happened? Like plug headphones in or something to that effect?
    It might even be better to get the information from the system log to see what the exact error code was regarding the DPC Watchdog Violation. There might also be a driver associated with it that is causing the problem.
    I was listening to music like I usually do and it was halfway through a track. The music just stopped and when I turned to look at the screen it looked exactly like the image in the link you posted. I hadn't tried to do anything when the BSOD happened, it just sort of happened randomly. It's not done it again yet but the next time it does I will snap a picture on my phone if it will help.

  • GT60 2OC Quick Launch Sensor Problem

    Hello, my MSI GT60 2OC notebook is having a problem, the Keyboard LED Backlight Switch Quick Launch Sensor is not responding to any key presses and the button is not even lighting up when pressed, so I can't turn off the backlight with the keyboard. Is it possible that the function was left out from the EC firmware? Could it be fixed?
    I'm running Windows 7 Ultimate x64 with all the drivers installed, including the latest version of the SCM and KLM utilities.

    Quote from: nitten on 02-September-13, 12:40:55
    Slightly off-topic and Im sorry for that.
    darkhawk, you mean to say that installing win 7 on this laptop is not supported and therefore not recommended? I have all sorts of problems with win 8 (see my recent thread) and combined with really hating the UI of win 8 (like  ) made me consider actually buying a win 7 version just to get rid of win 8? But that would be a bad idea?
    It's not supported so far as we've been told. While drivers are made available, and in most cases everything works fine for the user (in so far as they know), some things just do not work. The above case is the perfect example where some things just do not work.
    While the moderators here do have contacts with MSI that we can talk to, there is only so much that we can do to push certain issues. This issue is one of them. We have been told a few details, most of which I outlined above (MSI Engineers believe the EC firmware is working perfectly fine, and all functions of the laptop should work in both Win 7 and Win 8, this goes for both the GT60/GT70 0NX's and 2OX's that came with Windows 8 preinstalled and using the Win8 EC), along with that we should NOT recommend installing the Win7 EC firmware.
    This is why I HIGHLY suggest contacting MSI if you are installing Windows 7 on one of these laptops and cannot get the touch buttons functioning properly. I agree that this SHOULD be supported in Windows 7, because like you, some users prefer Windows 7.
    (Let me just state that I'm not sure how much of that information I should divulge, and hopefully no one cares that I do)
    NOW, I am personally using a GT70 0NE with Windows 8 installed. I don't care for Windows 8, personally. Some aspects are faster, booting is better, and the general responsiveness of the OS is faster.
    BUT, the desktop UI is absolutely horrid and reminds me of the days back in Windows 3.1 or earlier. The Metro UI is a complete waste in so far as a laptop or desktop are concerned, especially when it has no touch interface.
    I personally use Start8 as my start button replacement. I have set the OS up to act essentially the same as Windows 7 and never get the Metro UI.
    In this state, Windows 8 is very usable, it just isn't as 'pretty' as Windows 7 was. In fact, Windows 8 is downright bland compared to Windows 7 in that regard.
    That's my personal experiences. Keep in mind that my GT70 0NE was one that came with Windows 7 pre-installed, so I won't have any issues AT ALL with the touch buttons no matter what OS is installed on the laptop.

  • MSI GT60 2OC Wifi Problems?

    After getting my new GT60 2OC, i updated the system through windows update and manually downloaded the most up to date drivers for the killer wireless 1202 n and the nvidia 770m graphics card. However after installing the wifi driver for the laptop, i started having random disconnects and after finding out that it's not a problem with the router/ISP, i installed the wifi driver again using the disk that came with the laptop. Now, the wifi works only after installing, and if i reboot, the driver would become unrecognized by windows. Any help please?
    Edit: Also the cd drive is EXTREMELY loud (as loud as the fan boost) is this normal?
    Edit 2: Managed to get my wifi working again. The solution was to uninstall the wifi driver in device manager after installing the killer suite, then scan for hardware changes, and apply a copy of only the wifi driver. Everything is working fine now, i'll post again if i need any more help. I think the problem was that the bluetooth drivers were somehow disabling/conflicting with the wifi driver during the installation. (Wifi works before the bluetooth driver installs, but once the installation is done, the wifi driver stops working instantly or after restarting the computer)

    Quote from: ZetiX on 29-October-13, 02:11:20
    I have the TSST corp CDDVDW SN-208DB for my cd drive, I haven't tried any other CD Disks besides the one driver/utility disk that came with the laptop so it might be a problem with the disk. I'll see if its the problem with the disk if i can find a CD disk somewhere in the house. Also the wifi connection problem is back once again, Internet would randomly drop but i can still connect to the internet using my phone that's connected to the same wifi.
    Edit: After testing with a different CD Disk, i can confirm that the problem lies with the CD Drive and not the disk.
    Edit: Also i have the newest version of the driver which i downloaded from the Killer Gaming website:http://www.killergaming.com/support/driverdownloadsupport
    My Wifi/Lan card is the KillerE2200.
    For the DVD drive issue, most likely an RMA is the only way to fix it.
    For the WIFI/LAN, your LAN is a E2200, but it is NOT the WIFI. This can be different for some notebooks, and I'm not certain what the config is for the GT60 20C. You might have a Killer Networks 1202 WIFI card, or maybe some Intel card, I'm not entirely sure. You'll need to look into it and figure it out yourself as far as which card you have. From there, we can then try to look into the problem more. But without knowing the proper WIFI card, it's going to be difficult.

  • GT60 2OC key swap

    Hi
    I've seen several people asking for two keys to be swapped. I wonder if you could do something like this:
    Fn key acts like Windows key
    Windows key acts like application/context menu key (which is otherwise missing from this keyboard)
    The second backslash key (the one present on 105-key keyboards but missing from 104-key ones; usually it's between the left shift and the Z key, on this notebook it's to the right of the space bar) acts like the Fn key
    The normal backslash key (the one above the enter key) acts normally when pressed alone and acts like the second backslash key when pressed together with Fn.
    I understand this seems a bit weird but it's actually the closest I can get to a 'standard' layout on this keyboard while still having all the keys.
    The notebook is a GT60 2OC, versions:
    BIOS: E16F4IMS.506
    EC: 16F4EMS1 Ver5.05
    Let me know if it's possible and i'll send a donation immediately.
    Thanks

    Hello,
    can you draw it with arrows for better clarify of wanted changes?
    [ie: what changes to what, in other words to show me what to become into what with arrows]
    use this photo:

  • SoundBlaster 5.1 VX and Windows7 Bass redirection

    Hi,
    i have a SoundBlaster 5. VX and an analog 5. surround system. My OS is Windows 7 final.
    I can't get my subwoofer to work. I set my speakers to 5., tested them and every speaker including the subwoofer works. But when i try to play music in windows media player or any other program i get no bass (already tried the driver that comes with windows and also the driver on the creative page).
    I got it to work in (and only in) winamp by installing a plugin. But i do not hope that i have to find and install a plugin for every program that playes media files such as kmplayer, vlcplayer, dvbviewer, and so on.
    There HAS to be a way to tell windows in general, that i HAVE a subwoofer, and that it should be used. I googled about the bass redirection and found many other people who have the same problem. There were some solutions, i tried everyone (different drivers, different settings, ...) and nothing worked.
    Is there a way to get Windows itself to redirect the bass to the subwoofer? After searching and trying now for 5 hours i really don't know what to do any more. I hope there is a way to fix this ... just don't want to buy another soundcard just because of that!
    Thanks for your help in advance!

    Re: SoundBlaster 5. VX and Windows7 Bass redirection? "go to control panel and sound and then to speakers, and to configure and do not check or should I say uncheck full size speakers"
    did this. what it changed: i don't hear anything on the center speaker now too, only left and right are working.
    in control panel - sound - speakers - properties - i see:
    tab general, levels, sound blaster, advanced
    but i dont see "tone" anywhere on any of these tabs (i can in/decrease the levels of all of the 6 speakers, but it only has an effect on "left" and "right").
    in the "sound blaster" tab i also disabled the sound blaster enhancements, and in settings there i ticked off every option, restarted the sound application (i tried several), ticked them on - and nothing changes.
    many thanks for your quick reply!

  • Unlocked Bios MSI GT60 2OC

    hi,
    Can I have unlocked bios for MSI GT60 2OC 15,6 ??
    Can i Overclock my laptot with this bios ??
    Thx and give me the adress for donation !
    #INTER

    hello,
    what is your current bios version?
    look in bios setup system information
    Quote
    Can i Overclock my laptot with this bios ??
    don't know about this, assume it as no. [what options will be there and how will works don't depend of me]

  • I need help with GT60 2oc recovery windows 8

    hi i have MSI G Series GT60 2OC-022US
    Intel Core i7-4700MQ Processor (3.2 - 3.4 GHz, 6M Cache)
    8 GB DDR3 RAM
    1 TB 5400 rpm Hard Drive
    15.6-Inch Screen
    Windows 8
    i want to do factory recovery reset i try it by clicking on F3 the go to troubleshoot>advance>factory recovery
    after it a window come up and search for  the recovery it says can't find it
    i went to check if there is a recovery partition  i found it about 14gb hiding
    so what do i do here?

    Did you make the backup DVD's that it says you should make?
    If you're having issues with the factory recovery, I would try using the backup DVD's.

  • MSI GT60 2OC unlocked latest bios

    Hi Svet please unlock/unhide all hidden options in bios version E16F4IMS.50Y non RAID SKU for my MSI GT60 2OC. Thx!
    Donation sent !
    Confirmation number: 5YG65632P8646554D.

    received it, will work on and send back to you when its done after 3-4 hours
    EDIT: It's now done, check PM

  • HP 15-R074TU Audio and Video drivers

    Hello,
    Recently 2 weeks back I have bought  HP 15-R074TU laptop free dos. I have installed windows7 64 bit.  And other required softwares, I have problems with audio which is very low.  Video display is not proper, movies are not comfortable to watch without any reason get stucks. I have installed HP recommended video and audio driver but still having problems.
    Requesting you to recommend the audio and video drivers for HP 15-R074TU model, which will be very helpful for me
    This question was solved.
    View Solution.

    Hi:
    See if the graphics driver directly from Intel works for you...
    https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24245
    Try the audio driver directly from Realtek.  Accept the agreement.  DL and install the second driver on the list.
    http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownT...

  • GT60 2OC - Windows Experience Index scores - Question!

    I had a MSI GT70 0NC before this one and now I'm a bit confused with the Windows Experience Index on the graphics and HDD scores, on the GT70 the graphics score was 7.3 and 7.3 (Nvidia GT 670m) and on the MSI GT60 2OC I get 7.2 and 7.2 (Nvidia GT 770m), is this score good? I mean that I get lower score on a new/better graphics board? 
    The other question is about the 2 Msata drives in raid 0, the score on the old one was 7.9 (with a Samsung 840 Pro 256GB SSD) and now with the 2 Msata in raid 0 I get 7.8, is this score good? What is better: the 2 Msata or the single Samsung SSD? ... 

    I've contacted MSI UK sales department and was advised to try with customer support ( [email protected] ) and now I'm waiting for an answer... meanwhile I had some time to test and install the Samsung 840 PRO (removed the 750GB HDD) and made some tests on all drives, this is what I got using CrystalDisk Mark and Samsung Magician:
    The 2nd picture is made with RAPID mode activated (it was looking a but too boosted on CrystalDisk Mark) 
    Now the laptop feels again fast and "furious"  the bad part is that I don't have any other space to keep my files at the moment, just the 120GB from the 2 mSata and what is left from the SSD... I hope I can get an SATA board so I can use the SSD as Primary and the HDD as secondary/data drive.

  • MSI GT60 2OC mSATA Ports

    Hello, does the MSI GT60 2OC have mSATA ports for SSDs or for two SATA HDDs only?

    It depends on which model I believe.
    Some of the GT60's can come with the SuperRaid card, which should have support for up to 3 mSATA SSD's. If it did not come with the SuperRaid card, then it should have support for 2 x 2.5" HDD's.
    The easiest way to find this out is to remove the bottom panel (about 12 screws I believe) and just look at the 2 disk drive bays. One should have a disk, and the other will either have the SuperRaid card/PCB, or it will have a SATA connector.

  • Sever issue with Xorg and Nvidia Drivers

    I run a 2.6.20 kernel with Xorg and Nvidia drivers all from arch rep on a Asus NV6200. Everything works fine, except one thing. When I exit X, the monitor shuts down imediatly. It wont start up at all, not even by manual startup. I cant understand what happens. The configuration is correct, is done with the correct settings for my video-card and monitor taken directly from the documentation. I cant use my X server at all since several days ... I checked the logs and there are no EE's. Anyway ... here is the log. Help anyone can help, I cant use X at all.
    X Window System Version 7.2.0
    Release Date: 22 January 2007
    X Protocol Version 11, Revision 0, Release 7.2
    Build Operating System: UNKNOWN
    Current Operating System: Linux solarflare 2.6.20-ARCH #1 SMP PREEMPT Fri Mar 16 20:22:11 CET 2007 i686
    Build Date: 27 February 2007
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 21 03:26:45 2007
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Simple Layout"
    (**) |-->Screen "Screen 1" (0)
    (**) | |-->Monitor "AOC 7F+"
    (**) | |-->Device "NVIDIA 6200"
    (**) |-->Input Device "Mouse1"
    (**) |-->Input Device "Keyboard1"
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/100dpi").
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/75dpi").
    (**) FontPath set to:
    /usr/share/fonts/misc
    (==) RgbPath set to "/usr/share/X11/rgb"
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    (II) No APM support in BIOS or kernel
    (II) Loader magic: 0x81c34a0
    (II) Module ABI versions:
    X.Org ANSI C Emulation: 0.3
    X.Org Video Driver: 1.1
    X.Org XInput driver : 0.7
    X.Org Server Extension : 0.3
    X.Org Font Renderer : 0.5
    (II) Loader running on linux
    (II) LoadModule: "pcidata"
    (II) Loading /usr/lib/xorg/modules//libpcidata.so
    (II) Module pcidata: vendor="X.Org Foundation"
    compiled for 7.2.0, module version = 1.0.0
    ABI class: X.Org Video Driver, version 1.1
    (--) using VT number 7
    (II) PCI: PCI scan (all values are in hex)
    (II) PCI: 00:00:0: chip 1106,3099 card 1106,3099 rev 00 class 06,00,00 hdr 00
    (II) PCI: 00:01:0: chip 1106,b099 card 0000,0000 rev 00 class 06,04,00 hdr 01
    (II) PCI: 00:0a:0: chip 1317,0985 card 1113,1216 rev 11 class 02,00,00 hdr 00
    (II) PCI: 00:10:0: chip 1106,3038 card 1019,0996 rev 80 class 0c,03,00 hdr 80
    (II) PCI: 00:10:1: chip 1106,3038 card 1019,0996 rev 80 class 0c,03,00 hdr 80
    (II) PCI: 00:10:2: chip 1106,3038 card 1019,0996 rev 80 class 0c,03,00 hdr 80
    (II) PCI: 00:10:3: chip 1106,3104 card 1019,0996 rev 82 class 0c,03,20 hdr 00
    (II) PCI: 00:11:0: chip 1106,3177 card 1019,0996 rev 00 class 06,01,00 hdr 80
    (II) PCI: 00:11:1: chip 1106,0571 card 1019,0996 rev 06 class 01,01,8a hdr 00
    (II) PCI: 00:11:5: chip 1106,3059 card 1019,0996 rev 50 class 04,01,00 hdr 00
    (II) PCI: 01:00:0: chip 10de,0221 card 1043,820c rev a1 class 03,00,00 hdr 00
    (II) PCI: End of PCI scan
    (II) Host-to-PCI bridge:
    (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
    (II) Bus 0 I/O range:
    [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) Bus 0 non-prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (II) Bus 0 prefetchable memory range:
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set)
    (II) Bus 1 non-prefetchable memory range:
    [0] -1 0 0xe8000000 - 0xeaffffff (0x3000000) MX[b]
    (II) Bus 1 prefetchable memory range:
    [0] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b]
    (II) PCI-to-ISA bridge:
    (II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
    (--) PCI:*(1:0:0) nVidia Corporation NV44A [GeForce 6200] rev 161, Mem @ 0xe8000000/24, 0xd0000000/28, 0xe9000000/24
    (II) Addressable bus resource ranges are
    [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[b]
    [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) OS-reported resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) PCI Memory resource overlap reduced 0xe0000000 from 0xe7ffffff to 0xdfffffff
    (II) Active PCI resource ranges:
    [0] -1 0 0xeb021000 - 0xeb0210ff (0x100) MX[b]
    [1] -1 0 0xeb020000 - 0xeb0203ff (0x400) MX[b]
    [2] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [3] -1 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b](B)
    [4] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [5] -1 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b](B)
    [6] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
    [7] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [8] -1 0 0x0000dc00 - 0x0000dc1f (0x20) IX[b]
    [9] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[b]
    [10] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[b]
    [11] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
    (II) Active PCI resource ranges after removing overlaps:
    [0] -1 0 0xeb021000 - 0xeb0210ff (0x100) MX[b]
    [1] -1 0 0xeb020000 - 0xeb0203ff (0x400) MX[b]
    [2] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [3] -1 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b](B)
    [4] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [5] -1 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b](B)
    [6] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
    [7] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [8] -1 0 0x0000dc00 - 0x0000dc1f (0x20) IX[b]
    [9] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[b]
    [10] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[b]
    [11] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
    (II) OS-reported resource ranges after removing overlaps with PCI:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    (II) All system resource ranges:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xeb021000 - 0xeb0210ff (0x100) MX[b]
    [5] -1 0 0xeb020000 - 0xeb0203ff (0x400) MX[b]
    [6] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [7] -1 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b](B)
    [8] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [9] -1 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b](B)
    [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [12] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
    [13] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [14] -1 0 0x0000dc00 - 0x0000dc1f (0x20) IX[b]
    [15] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[b]
    [16] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[b]
    [17] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
    compiled for 7.2.0, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
    compiled for 7.2.0, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
    compiled for 7.2.0, module version = 2.1.0
    Module class: X.Org Font Renderer
    ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font FreeType
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.9755
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 0.1
    (II) Loading extension GLX
    (II) LoadModule: "nvidia"
    (II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
    (II) Module nvidia: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.9755
    Module class: X.Org Video Driver
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 0.6
    (II) LoadModule: "kbd"
    (II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
    (II) Module kbd: vendor="X.Org Foundation"
    compiled for 7.1.1, module version = 1.1.0
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 0.6
    (II) NVIDIA dlloader X Driver 1.0-9755 Mon Feb 26 23:23:13 PST 2007
    (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    (II) Primary Device is: PCI 01:00:0
    (--) Assigning device section with no busID to primary device
    (--) Chipset NVIDIA GPU found
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 7.2.0, module version = 1.0.0
    ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "wfb"
    (II) LoadModule: "wfb"
    (II) Loading /usr/lib/xorg/modules//libwfb.so
    (II) Module wfb: vendor="NVIDIA Corporation"
    compiled for 7.1.99.2, module version = 1.0.0
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Loading /usr/lib/xorg/modules//libramdac.so
    (II) Module ramdac: vendor="X.Org Foundation"
    compiled for 7.2.0, module version = 0.1.0
    ABI class: X.Org Video Driver, version 1.1
    (II) resource ranges after xf86ClaimFixedResources() call:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xeb021000 - 0xeb0210ff (0x100) MX[b]
    [5] -1 0 0xeb020000 - 0xeb0203ff (0x400) MX[b]
    [6] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [7] -1 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b](B)
    [8] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [9] -1 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b](B)
    [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [12] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
    [13] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [14] -1 0 0x0000dc00 - 0x0000dc1f (0x20) IX[b]
    [15] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[b]
    [16] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[b]
    [17] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
    (II) resource ranges after probing:
    [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [4] -1 0 0xeb021000 - 0xeb0210ff (0x100) MX[b]
    [5] -1 0 0xeb020000 - 0xeb0203ff (0x400) MX[b]
    [6] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [7] -1 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b](B)
    [8] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [9] -1 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b](B)
    [10] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
    [11] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
    [12] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
    [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [15] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
    [16] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [17] -1 0 0x0000dc00 - 0x0000dc1f (0x20) IX[b]
    [18] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[b]
    [19] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[b]
    [20] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
    [21] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
    [22] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    (==) NVIDIA(0): RGB weight 888
    (==) NVIDIA(0): Default visual is TrueColor
    (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    (**) NVIDIA(0): Enabling RENDER acceleration
    (II) NVIDIA(0): NVIDIA GPU GeForce 6200 at PCI:1:0:0 (GPU-0)
    (--) NVIDIA(0): Memory: 131072 kBytes
    (--) NVIDIA(0): VideoBIOS: 05.44.a2.03.00
    (II) NVIDIA(0): Detected AGP rate: 4X
    (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    (--) NVIDIA(0): Connected display device(s) on GeForce 6200 at PCI:1:0:0:
    (--) NVIDIA(0): AOC Spectrum7F (CRT-0)
    (--) NVIDIA(0): AOC Spectrum7F (CRT-0): 400.0 MHz maximum pixel clock
    (II) NVIDIA(0): Assigned Display Device: CRT-0
    (II) NVIDIA(0): Validated modes:
    (II) NVIDIA(0): "1024x768"
    (II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
    (--) NVIDIA(0): DPI set to (81, 81); computed from "UseEdidDpi" X config
    (--) NVIDIA(0): option
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC? No, I don't.
    (II) resource ranges after preInit:
    [0] 0 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b]
    [1] 0 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b]
    [2] 0 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b]
    [3] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
    [4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
    [5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
    [6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
    [7] -1 0 0xeb021000 - 0xeb0210ff (0x100) MX[b]
    [8] -1 0 0xeb020000 - 0xeb0203ff (0x400) MX[b]
    [9] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[b]O
    [10] -1 0 0xe9000000 - 0xe9ffffff (0x1000000) MX[b](B)
    [11] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
    [12] -1 0 0xe8000000 - 0xe8ffffff (0x1000000) MX[b](B)
    [13] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
    [14] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
    [15] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
    [16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
    [17] -1 0 0x00000000 - 0x000000ff (0x100) IX[b]
    [18] -1 0 0x0000e400 - 0x0000e4ff (0x100) IX[b]
    [19] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[b]
    [20] -1 0 0x0000dc00 - 0x0000dc1f (0x20) IX[b]
    [21] -1 0 0x0000d800 - 0x0000d81f (0x20) IX[b]
    [22] -1 0 0x0000d400 - 0x0000d41f (0x20) IX[b]
    [23] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[b]
    [24] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
    [25] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
    (II) NVIDIA(0): Setting mode "1024x768"
    (II) Loading extension NV-GLX
    (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
    (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
    (==) NVIDIA(0): Backing store disabled
    (==) NVIDIA(0): Silken mouse enabled
    (II) Loading extension NV-CONTROL
    (==) RandR enabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension XAccessControlExtension
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    (II) Initializing extension GLX
    (**) Option "Protocol" "Auto"
    (**) Mouse1: Device: "/dev/input/mice"
    (**) Mouse1: Protocol: "Auto"
    (**) Option "CorePointer"
    (**) Mouse1: Core Pointer
    (**) Option "Device" "/dev/input/mice"
    (==) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
    (**) Option "ZAxisMapping" "4 5 6 7"
    (**) Mouse1: ZAxisMapping: buttons 4, 5, 6 and 7
    (**) Mouse1: Buttons: 11
    (**) Option "CoreKeyboard"
    (**) Keyboard1: Core Keyboard
    (**) Option "Protocol" "standard"
    (**) Keyboard1: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard1: XkbRules: "xorg"
    (**) Option "XkbModel" "pc104"
    (**) Keyboard1: XkbModel: "pc104"
    (**) Option "XkbLayout" "us"
    (**) Keyboard1: XkbLayout: "us"
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard1: CustomKeycodes disabled
    (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
    (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
    (--) Mouse1: PnP-detected protocol: "ExplorerPS/2"
    (II) Mouse1: ps2EnableDataReporting: succeeded
    FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing.

    No ... the problem is in the kernel that comes precompiled.
    I did this test.
    The first time I installed the kernel I unloaded nvidiafb since I dont like it.
    When I install nvidiafb back something strange happends. Nvidia module fails to load.
    The modprobe sais it cannot find the device nvidia.ko ... but it is there!
    So my best guess is, there is something with the kernel. Any ideas?
    Problem resolved, installed older driver
    Last edited by Nefer-Ra (2007-03-22 02:59:25)

  • 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