Link to home
Start Free TrialLog in
Avatar of edvardr
edvardr

asked on

Problems with firewire - code 10

I have av Asus A7N8X Delux motherbord with build in Firewire ports. I cant how ever get this to work. In device manager in WinXP I get  this error message: "OHCI compliant IEEE host controller, this device cannot start (code 10)"

I have tryed uninstalling the driver, and restarting the computer. XP recognice the hardware, installs the driver, but I still have the same problem.

At http://www.hardwareanalysis.com/content/topic/4557/ I found some sugestinons witch I have tryed, but they did not help - obviesly, or I had not been posting here.

Hardware:
Motherboad: Asys A7N8X Delux
Prosessor: AMD Athlon XP2500
RAM: 1 Gb, TwinMOS PC3200

Software
Windows XP, SP 1

Driverversion FireWire: 5.1.2535.0

Avatar of GUEEN
GUEEN
Flag of United States of America image

Go to Start |  run   and type   regedit

Remove the Upperfilters and Lowerfilters values completely from the
following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11C
E-BFC1-08002BE10318}
Do not forget to save a copy of registry before deleting (file - export from My Computer at top of tree) and reboot XP
Have you tried clearing your BIOS and resetting it.
You would do it with a jumper but on this board, it is important to also remove and replace the Battery.
Pete
Avatar of edvardr
edvardr

ASKER

Cfourkays: Yes, I have tryed clearing the BIOS. That did not help.

shekerra: Tryed yours sugestion, but it did not help. The registry key did how ever not seam to have any thing to do with the firewire.

My key {4D36E965-E325-11CE-BFC1-08002BE10318} had the following keys:
(Standard)             REG_SZ             DVD-/CD-ROM stasjoner
Class                      REG_SZ            CDROM
EnumProkPages32 REG_SZ            MmSys-Cpl,MediaPropPageProvider
Icon                       REG_SZ             -51
Installer32             REG_SZ             storprop.sll,DvdclassInstaler
LowerFilters           REG_Multi_ SZ  drvmcdb OxHelp20 Pfc
NoInstallClass        REG_SZ            1
SilentInstall            REG_SZ            1
TroubleShooter-o   REG_SC            hcp://help/tshout/tsdrive.htm

And then some subkeys, 0000,0001,0002,0004,0005,0006 and Properties

I use a Norwegian version of WinXP, maby thats the reason for the key not to correspond?
Have you had this problem since you installed the system or did this recently happen?

Have you installed the all-in-one driver package?

Dennis
Avatar of edvardr

ASKER

I bought a new motherboard, CPU and some other stuff, but used my old disk with WinXP already installed. Avter assembling the new computer I had to do a reinstall/repair of WinXP to get it to work. I have not tryed a newinstall of XP, due to the work is is reeinsalling all my software.

After the reinstall/repaire of WinXP I have not gotten the FireWire to work.

On my old computer I had a Pinacle DV200 FireWire card that worked. I have uninstalled this card.

I have tryed the all-in-on driver package, but there dont seem to be any FireWire drivers. I have also tryed ASUS home page without any luck.
Hmmm, that explains it. You won't be able to fix this until you do a reinstall, as XP needs to use the new hardware INF file from ASUS. There's not need to try different drivers as it doesn't matter. When you change motherboards that are completely different, XP needs to see the manufacturers installer files and load the drivers in a specific order beginning with the basic motherboard functions and then any onboard peripherals.
Dennis
Avatar of edvardr

ASKER

I have acutaly just  tryed a new install of XP on a small HD I have (2.7Gb). It was just enought space for the installation, but that did not solve the problem.


Did you use the ASUS installer CD? ...and make sure that you loaded all of the drivers from that CD?
Avatar of edvardr

ASKER

Yes, I did. But then again, I cant find any firewire drivers on that CD. I have seen several places at the internett that it is not nessesary with drivers for FireWire.
You won't find any firewire drivers on the CD because the firewire drivers are part of windows.  In XP it should be detected as OHCI Compliant IEEE 1394 Host Controller.  Is there a chance that you are using an Adaptec scsi card for your burner?  Post card\burner details please.
Avatar of edvardr

ASKER

Motherboad: Asys A7N8X Delux
Prosessor: AMD Athlon XP2500
RAM: 1 Gb, TwinMOS PC3200
Graffic Card: Asus V9520/TD
Raid controller - add on card: Promise FastTrak 100 TX2/TX4
Raid controller - onboard: Silicon Images SiI 3112 SATA (dont us this on)
NIC - Onborad : 3Com 3C920B
NIC - Onboard : Nivdia NForse MCP
Sound - Onboard : NIVIDA NForce
CD/DVD player: IDE, dont know the brand
DC/DVD buner: IDE, Sony DVD RW DRU-510A

No Adaptec Card.
Also what is your board revision and have you flashed to the latest BIOS.  This may be a direct problem with theis mobo - and for that case I would call ASUS to get a replacement mobo.
Try taking every card that you do not need for basic windows startup - out of your system Disable onboard stuff (sound and nic from device manager).  Keep just the basics.  Then go into safe mode to device manager and uninstall the raid controllers.  Next boot up normal and let windows reinstall - any Compliant IEEE 1394 Host Controller now?
Avatar of edvardr

ASKER

Motherborad rev 2.0
Bios 1005, the latest - downloaded yesterday.

I'll try your sugestions, but when you say reinstall - you only mean the drivers not windows?
Not Windows!  
BTW is that Rev 2.00 with 1003 BIOS?
Avatar of edvardr

ASKER

No Rev 2.00 with 1005 BIOS, dated 05/14/2003
OOh I see 1005 - sorry about that - I do not see why that won't work - if you disable\uninstall everything else.  Even go as far as to disable com ports, paralell ports, etc then uninstall the drivers from safe mode - then boot back into windows and the IEEE 1394 Host Controller should be detected.
The issue is to get the IEEE 1394 Host Controller noted by windows - so this may be an IRQ\resource problem and I will bet ASUS is aware of it.
Avatar of edvardr

ASKER

I have now tryed to do as sugestec. In safe mode I disabled most of the other devices, and then removed the IEEE 1394 Host controller. After that I rebooted and from BIOS I disabled every onbord card possible except the IEEE1394 and the NIC that I use for my ADSL.  I also disabled all the COM and Paralell prots.

After rebooting to Windows. The system finds the new hardware, and seems to install it correctly, but it still wount work.

I'll try disableing the NIC also...

What slot is the Promise FastTrak 100 TX2/TX4 on?
Avatar of edvardr

ASKER

Disabling the last NIC did not help

The Promise FastTrak 100 TX2/TX4 is on the top one, the one closest to the AGP port. I did not try to remove the card, just disabled it in devicemanagere.
Try moving the  Promise FastTrak to slot 3 and do not disable.
Avatar of edvardr

ASKER

I'll try that, but what diference should that make? I have just installed my Pinacle DV200 FireWire Card, by chance in slot 3, And Windows recogniced the IEEE1394 ports, and installed the drivers correctly. That card is working just as it should. I'm leaning against a hardware problem with the MotherBoard. But I'll try moving the FastTrak to be sure.
ASKER CERTIFIED SOLUTION
Avatar of GUEEN
GUEEN
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Are you saying that you are trying to use both the on-board firewire, as well as the Pinnacle DV200?

If that's the issue, you're going to have a resource conflict between the two. One will be disabled in windows.
Avatar of edvardr

ASKER

dew_associates: Yes and no. The problem started without the Pinnacle DV200 borad installed. I just tryed that after trying lot of things. Installing the Pinnacle board did not help me in getting the on-board card running, but I got FireWire.
Well to make the on-board firewire work, you'll need to pull the Pinnacle card. Get it working and then try and add back the Pinnacle.

I suspect that this system has too many hardware items to sort out via IRQ and DMA issues.

It would be easier and more effective to remove the extras, disconnect all the externals, USB, Firewire, printers etc, reinstall XP and then add the items back one at a time.
edvardr are you confused now?  
Avatar of edvardr

ASKER

Confused? Not if I ignore dew_associates, he/she has obviusly not read everything we have tryed.

I have a larger disk at work that I can try reinstalling WinXP on. It will give me more room for trying, so I'll give it another try this afternoon.
shekerra, if you have a comment to make, make in the CS area please. Yours is inconsistent with the tenets of this site.
edvardr, I have read through everything that has been posted thus far, and at the moment, in spite of all of the comments, your system still does not function. Your motherboard model happens to be one of the better releases from ASUS that includes SATA and Firewire on board, and it would appear that they update their site frequently with new information on a regular basis when problems surface.

Disabling functions in the BIOS, uninstalling or attempting to remove drivers does nothing to remove entries from the HAL layer that is created during the installation process, nor does it change the INF files in such areas as *\Windows; *\Windows\inf; *\Windows\system32 etc.

There is a specific order that XP and drivers must be installed, and firewire, USB2, SATA etc are no different. Indeed, basic Firewire drivers are included with the basic XP installation, however this doesn't mean that those drivers are appropriate for your motherboard. In order for drivers to load properly, they must load in a specific order beginning with the motherboards chipset drivers, bus drivers and then peripheral drivers.

Follow on with a new install on that extra hard drive, but physically remove hardware items that are not needed, and remove all external items.
Avatar of edvardr

ASKER

Do you meen that I should disable On-Board functions until WinXP is finish with the installation? And then enable then on by on in a specific order so that XP can recognice them?

No, to the contrary.

When doing a fresh installation:

1. Make sure your BIOS is current, but only flash (update) the BIOS if doing so resolves an issue that effects your installation.

2. Set your BIOS to it's default or performance settings, whichever is recommended by the motherboard manufacturer. Usually, this is the default.

3. Make sure that you set your power management settings correctly. If you have an option to set either APM (advanced power management) or ACPI (Advanced Configuration and Power Interface), then set it too ACPI.

4. Make certain that Plug and Play is disabled.

5. Do not attach any external peripherals such as USB, firewire, printers etc.

6. Make sure that the hard disk is of the size consistent with that which can be recognized by the BIOS. If the BIOS has a disk size limitation, then you will need figure out whether a BIOS update will fix it, or whether you need to use a smaller drive.

7. Partition the drive, make the partition active, and format it if necessary.

8. Install XP.

9. Add the drivers from the motherboard manufacturer. If the installer does not install them in order automatically, then begin with the motherboard chipset drivers, and then proceed through video, sound etc if you are using the onboard video and sound. Next, add all the peripheral drivers. XP does not have a USB 2.0 device driver, hence if your motherboard is USB 2.0 compliant, you will need the 2.0 driver from the manufacturer. Now load all remaining drivers.

Note: If you plan on using Serial ATA, the Silicon Image driver MUST BE INSTALLED at the beginning of the XP install by touching F6 and adding the driver.

Note: Firewire drivers are loaded immediately after the USB device drivers.

Avatar of edvardr

ASKER

No luck with this try eighter.

My the shop where I bought the motherboard are going to check if there is anything wrong with it, and if there is, send me anotherone. The problem with that is that I then will be without my computer for some time - witch I hate.

My problem is not solved but I'll treat this as a hardware problem. Thanks for all the sugestions for diferent solutions to my problem. Since it probalbly is a hardware problem none of you is to blame for not comming up with the right solution. I'm going to give my point to shekerra, Its my opinion that your sugestions gave me most on the way to treating this as a hardware problem.

Thanks!
Thanx edvardr :)
Reference
*******************************************************************
Comment from shekerra
Date: 07/26/2003 03:41PM PDT
 Comment  

Go to Start |  run   and type   regedit

Remove the Upperfilters and Lowerfilters values completely from the
following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11C
E-BFC1-08002BE10318}
********************************************************************

I was having the exact same problem. You suggestion worked perfectly. Thank you!!
 
edvardr did you solve the problem as i just purchased an Asus A7N8X-E Deluxe and have the same problem got the latest drivers form Asus but no go
Avatar of edvardr

ASKER

No, I never found a solution. I have a addon FireWire card I use instad.

If you find any solution it would be nice if you post it here.

After Hounding Asus they said the motherboard may be faulty and to have it replaced so i will let you if it solves the problem

Cheers Ray
Hello all.

I'm actually having this same problem, only with an Intel mobo and CPU.  I've never used my Firewire, but was curious about it.  I can remember a few times when it didn't have the code 10 error.  Strange that it would appear out of nowhere.  I have XP Pro SP1.  I tried the reg hack that shekerra suggested, and this lead me to my CD-ROM drives.  Also, I have tried flashing my BIOS, but the installer keeps saying it's unsuccessful.
Ok i got my new motherboard and guess what all was fixed and now firewire just works as to what  BlindWolf8 has said thats what happened to me int errors so would not supprise me if it is faulty too.
Looks like all firewire ports intergrated on mobos are having this problem?  This has to be a problem with XP if its happened on multiple systems...it's just plain freaky!  :-P