• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

first timer just fitted his new mobo :-)

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

IrelandMadMan

Member
Joined
Sep 4, 2003
Location
Ireland
How r yas !

Just fitted a new dfi lanparty nf2 and xp2600, but i am getting this message :

A problem has been detected and windows has been shut down to prevent damage to your computer.

If this is the first time you have seen this stop error screen resart your computer ( tried that ) .
If this screen appears again, follow these steps:

Check for viruses on your computer . Remove any newly installed hard drives or hard drive controllers. Check your hard drive to make sure that it is properly configured and terminated. Run CHKDSK/F to check for hard drive corruption,and then restart your computer.

Technical information:
0x0000007b ( 0xf9e49640, 0xc0000034, 0x00000000, 0x00000000


any ideas?
 
Sounds to me like you have Windows XP or 2000 already installed on another board and tried to switch motherboard without doing anything to the OS.

if thats the case, now you'll need to do a repair install of the OS to reset all the settings and drivers. All your programs and data will be left intact but all the drivers with be replaced.

To do this pop in your cd and boot off it, hit enter at the first question, where is says install or go to the recovery console, say you want to install. On the next screen press R and it will do a repair install.
 
I dont have a copy of xp , looks like i will have to buy 1 :-( , its xp pro, so i will need xp pro yeah?

U were right, i did have xp installed on another board :)

thanks for yer help
 
IrelandMadMan said:
I dont have a copy of xp , looks like i will have to buy 1 :-( , its xp pro, so i will need xp pro yeah?

U were right, i did have xp installed on another board :)

thanks for yer help

There is a way to do it without the CD, but it will involve putting the rig back together as it was before you changed it. The problem is that XP has problems reading from the hard drive when you swap chipsets, so you will need to make it reinstall the drivers the next time it boots up, just like it does when you first install it.

So that said, here is what you need to do... put the system back together as it was and boot it up... should boot up no problem.

Here is how I do it... just follow this guide:

The first thing to do is ensure Windows is in a state where it can work on the new system. In the case of 2000 and XP, this just means that it has to be able to access the hard drives.

To do this, replace the Bus Master drivers with standard generic drivers, as seen below.

If you're changing chipset (think in terms of drivers - Drivers for the VIA KT133 work fine with a KT400, but drivers for i815 won't work at all with an AMD760MPX), then you'll want to knock out the AGP drivers too to avoid video problems after the switch. Either uninstall them from the Control Panel, Add/Remove Programs or, in the case of VIA's 4in1, from the driver installation program. If you have neither (ie. SiS, ALi) or just can't be bothered, then observe the illustration below.

The standard PCI to PCI bridge disables everything AGP, but also makes sure that old AGP drivers aren't around to screw your system up.

You should be good to go now, but it's worth it to do some more cleaning up. Remove both USB controllers (don't do this if you have a USB keyboard/mouse, duh) and uninstall your display drivers. Also uninstall any other non-critical drivers from the Add/Remove Programs in the Control Panel, or any other option your driver installer has. They'll need to be reinstalled anyway, since Windows has to reinstall devices if they change INT# lines and they will.

Finished all that rebooting? You're half way there.

Do your build and power it up. Windows will boot up and complain about drivers. Don't install any of them, just cancel every time. It'll do some automatically, these are probably the ones you don't have any drivers for anyway and you're quite happy to let Windows use the internal drivers.

Open a command line (Start>Run>cmd.exe) and take a look below...

With the devmgr_show_nonpresent_devices set to 1, and "Show Hidden Devices" enabled, you can see the trash left from your previous machine. Notice the Crystal devices in my screenshot, these are the Soundfusion drivers that I installed the FortissimoII drivers over. Notice also the BDA deframers and filters and, off the bottom of the window, some Microsoft filters. Don't get rid of the filters, just the actual hardware that used to be in your system (or still is, you're reinstalling all the drivers). Just kill anything that's ghosted and not something you shouldn't kill like the filters and deframers mentioned above. You may be surprised by how much crap you find. Don't touch anything under Non-PnP Drivers, btw.

Next, let's get going. Install your chipset drivers first. Then the display drivers. It sucks to work in 640x480x16, doesn't it? Now go nuts. Install the drivers for everything and we're done. Remember to reboot every time you're prompted. Nothing screws up a driver install worse than the drivers not knowing what they need to know about the system.
We now have a clean system that doesn't even know you've changed the board.

I've done some really drastic changes like this. In one, I just tore the HD out of the machine (An old PPro200 and slapped it in a Duron).


FAQ

What happens if I don't do the IDE drivers step?
One of two things.
1. The system will give INACCESSIBLE_BOOT_DEVICE and won't even boot up.
2. It'll work if you're upgrading between compatible chipsets (ie. i845 to i850 or KT133A to KT333)

What happens if I don't clean up in Device Manager?
You end up with a whole heap of ghost devices. These can cause problems if you install compatible hardware later on. For example, if I didn't clean out those Crystal CX4624 drivers and I then installed a Santa Cruz (CX4630), I'd have hell trying to get Turtle Beach's drivers on there.

What about the other branded drivers in System (Device Manager)?
You'd worry about these in 98, ASD would kick in probably. 2k and XP are smart enough to replace them with the right ones. The old ones are removed during the clean up phase of this procedure.

Do I need to change the PC Type (ie. ACPI Uniproc to Standard PC)?
You can change freely between ACPI types, but not from ACPI to Standard or back again. So you can go from ACPI Uniproc to ACPI Multiproc (even on a uniproc system) and expect no problems.

Can I do something like this to move my HD from an onboard controller to a RAID or PCI controller, or vice versa?
No. The onboard controller has a standard 'location' where standard drivers will always be able to work with it. PCI and RAID controllers have no such standard, you'll just get INACCESSIBLE_BOOT_DEVICE. You may also get this error if your boot drive is on a PCI controller and you change the slot it's in. This can be worked around on systems with APICs by changing the INT# mapping to match the old INT# to the new location. Other systems can't do this.

Lengthy process, but if you do it right, it WILL work, I have done it many times. The main points is to uninstall the IDE controller drivers and all the chipset drivers. Hope that helps.
 
I cant even build my computer up the way it was because my old xp2100 is messed up and my old board doesnt support my new cpu lol ( nothins easy ) its ok, i will get a copy of xp, think its better if i had one, plus it should make things much easier.

Thanks very much for yer help and time :)
 
Well.. you know for the future :) Sorry to hear about the messed up CPU and best of luck to you :)
 
Back