maximus iv extreme-z unknown device

Discussion in 'Asus' started by erbutra, Aug 16, 2011.

  1. erbutra

    erbutra Guest

    i have istall total drivers and working

    but if see on:
    universal serial bus controller
    ----
    generic usb hub
    generic usb hub
    generic usb hub
    generic usb hub
    intel 6 series/c200 series chipset family usb enhanced host controller
    1c26
    intel 6 series/c200 series chipset family usb enhanced host controller
    1c2d
    renesas electronics usb 3.0 host controller
    renesas electronics usb 3.0 host controller
    renesas electronics usb 3.0 hub
    renesas electronics usb 3.0 hub
    renesas electronics usb 3.0 root hub
    renesas electronics usb 3.0 root hub
    unknown device (my problem)
    usb composite device
    usb composite device
    usb composite device
    usb composite device
    usb root hub
    usb root hub

    i have disconnect total usb device but "unknow deveci" appear egual

    **************

    i have install Intel Management Engine Interface

    reinstall operating system with ps2 device and disconnect total usb
    device

    i find another people with my problem

    http://www.overclock.net/intel-motherboards/1089309-asus-maximus-iv-extreme-z-unknown.html

    i have installa latest drivers for bluetooth device

    on another mb this problem not appear but not install original bluetooth
    device

    I think the fault lies with the bluetooth adapter asus.

    I can not do this test because to remove it, remove motherboard

    thanks
     
    erbutra, Aug 16, 2011
    #1
    1. Advertisements

  2. erbutra

    Fierce Guppy Guest

    Which version of the Intel Chipset Software Installation Utility did you
    install?
    It should be using version 9.2.0.1030 ( http://tinyurl.com/3dr6xln )

    Tony.
     
    Fierce Guppy, Aug 17, 2011
    #2
    1. Advertisements

  3. erbutra

    Fierce Guppy Guest

    Which version of the Intel Chipset Software Installation Utility did you
    install?
    It should be version 9.2.0.1030 ( http://tinyurl.com/3dr6xln )

    Tony.
     
    Fierce Guppy, Aug 17, 2011
    #3
  4. erbutra

    Paul Guest

    You don't say what operating system you're using.

    If it is Win2K or WinXP, have a look in setupapi.log . I do
    not know what the equivalent of that is in Windows 7 (but
    you could try C:\Windows\inf\setupapi.dev.log and see what is
    in it).

    For example, I have a driver missing in Win2K, and the log entry looks like this.
    This is from C:\WINDOWS\setupapi.log in Win2K.

    *******
    [2011/04/01 11:06:37 1168.2]
    Munged cmdline: rundll32.exe newdev.dll,DevInstall ACPI\PNP0C32\4 <---- hardware ID is here
    EXE name: C:\WINDOWS\system32\rundll32.exe
    Set selected driver.
    Device install function: DIF_SELECTBESTCOMPATDRV.
    Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible drivers for this device.
    Completed default installer, error: Error 0xe0000228: There are no compatible drivers for this device.
    [2011/05/07 09:11:21 272.3 Driver Install]
    Munged cmdline: C:\WINDOWS\system32\services.exe
    EXE name: C:\WINDOWS\system32\services.exe
    Device install function: DIF_SELECTBESTCOMPATDRV.
    Selecting best compatible driver caused error: Error 0xe0000228: There are no compatible drivers for this device.
    Completed default installer, error: Error 0xe0000228: There are no compatible drivers for this device.
    *******

    Based on that, I would search on

    ACPI\PNP0C32\4

    and I haven't managed to trace down the issue (P5E Deluxe). I think
    that item, magically appears after some other driver is installed.
    I can't find a matching item in WinXP running on the same motherboard.

    Asus uses some "ACPI objects", to control overclocking from Windows
    or do other things. Regular hardware devices use VEN/DEV or VID/PID
    for identification, but it is also possible for the BIOS to pass
    devices to the OS, in which case the identification scheme is different.

    Paul
     
    Paul, Aug 17, 2011
    #4
  5. erbutra

    erbutra Guest

    [Device Install Log]
    OS Version = 6.1.7601
    Service Pack = 1.0
    Suite = 0x0100
    ProductType = 1
    Architecture = amd64

    [BeginLog]

    [Boot Session: 2011/08/18 15:10:08.610]
    ump: Creating Install Process: DrvInst.exe 15:10:26.692
    ndv: Retrieving device info...
    ndv: Setting device parameters...
    ndv: Searching just Driver Store...
    dvi: {Build Driver List} 15:10:26.723
    dvi: Searching for hardware ID(s):
    dvi: usb\unknown
    dvi: Searching for compatible ID(s):
    dvi: usb\unknown
    cpy: Policy is set to make all digital signatures equal.
    dvi: Enumerating INFs from path list 'C:\Windows\INF'
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'
    ([strings.0409])
    dvi: Created Driver Node:
    dvi: HardwareID - USB\UNKNOWN
    dvi: InfName -
    C:\Windows\System32\DriverStore\FileRepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf
    dvi: DevDesc - Unknown Device
    dvi: DrvDesc - Unknown Device
    dvi: Provider - Microsoft
    dvi: Mfg - (Standard USB Host Controller)
    dvi: ModelsSec - Generic.Section.NTamd64
    dvi: InstallSec - BADDEVICE.Dev
    dvi: ActualSec - BADDEVICE.Dev.NT
    dvi: Rank - 0x00ff0000
    dvi: Signer - Microsoft Windows
    dvi: Signer Score - INBOX
    dvi: DrvDate - 06/21/2006
    dvi: Version - 6.1.7601.17586
    inf: Searched 1 potential matches in published INF directory
    inf: Searched 36 INFs in directory: 'C:\Windows\INF'
    dvi: {Build Driver List - exit(0x00000000)} 15:10:26.832
    ndv: Selecting best match from just Driver Store...
    dvi: {DIF_SELECTBESTCOMPATDRV} 15:10:26.832
    dvi: No class installer for 'Universal Serial Bus controllers'
    dvi: No CoInstallers found
    dvi: Default installer: Enter 15:10:26.832
    dvi: {Select Best Driver}
    dvi: Selected driver installs from section
    [BADDEVICE.Dev] in
    'c:\windows\system32\driverstore\filerepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'.
    dvi: Class GUID of device changed to:
    {36fc9e60-c465-11cf-8056-444553540000}.
    dvi: Set selected driver complete.
    dvi: Selected:
    dvi: Description - [Unknown Device]
    dvi: InfFile -
    [c:\windows\system32\driverstore\filerepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf]
    dvi: Section - [BADDEVICE.Dev]
    dvi: Signer - [Microsoft Windows]
    dvi: Rank - [0x00ff0000]
    dvi: {Select Best Driver - exit(0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 15:10:26.832
    inf: Opened INF: 'C:\Windows\INF\usb.inf' ([strings.0409])
    inf: Saved PNF: 'C:\Windows\INF\usb.PNF' (Language = 0409)
    ndv: INF specified BasicDriverOk for this device, skipping Windows
    Update search.
    inf: {SetupCopyOEMInf: C:\Windows\INF\usb.inf} 15:10:26.848
    inf: Driver Store location:
    C:\Windows\System32\DriverStore\FileRepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf
    inf: Published Inf Path: C:\Windows\INF\usb.inf
    inf: {SetupCopyOEMInf exit (0x00000050)} 15:10:26.848
    dvi: Searching for hardware ID(s):
    dvi: usb\unknown
    dvi: Searching for compatible ID(s):
    dvi: usb\unknown
    inf: Opened PNF:
    'C:\Windows\System32\DriverStore\FileRepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'
    ([strings.0409])
    dvi: Selected driver installs from section [BADDEVICE.Dev] in
    'c:\windows\system32\driverstore\filerepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'.
    dvi: Class GUID of device changed to:
    {36fc9e60-c465-11cf-8056-444553540000}.
    dvi: Set selected driver complete.
    ndv: Driver selected, now performing install...
    ndv: {Core Device Install} 15:10:26.848
    inf: Opened PNF: 'C:\Windows\INF\usb.inf' ([strings.0409])
    inf: Opened PNF: 'C:\Windows\INF\usb.inf' ([strings.0409])
    dvi: {DIF_ALLOW_INSTALL} 15:10:26.863
    dvi: No class installer for 'Unknown Device'
    dvi: No CoInstallers found
    dvi: Default installer: Enter 15:10:26.863
    dvi: Default installer: Exit
    dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 15:10:26.863
    ndv: Installing files...
    dvi: {DIF_INSTALLDEVICEFILES} 15:10:26.863
    dvi: No class installer for 'Unknown Device'
    dvi: Default installer: Enter 15:10:26.863
    dvi: {Install FILES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'
    ([strings.0409])
    inf: {Install Inf Section [BADDEVICE.Dev.NT]}
    inf: CopyFiles=BADDEVICE.CopyFiles
    (usb.inf line 93)
    ! inf: Empty Section! [BADDEVICE.CopyFiles]
    inf: {Install Inf Section [BADDEVICE.Dev.NT]
    exit (0x00000000)}
    dvi: Processing co-installer registration
    section [BADDEVICE.Dev.NT.CoInstallers].
    inf: {Install Inf Section
    [BADDEVICE.Dev.NT.CoInstallers]}
    inf: {Install Inf Section
    [BADDEVICE.Dev.NT.CoInstallers] exit (0x00000000)}
    dvi: Co-installers registered.
    dvi: {Install INTERFACES}
    dvi: Installing section
    [BADDEVICE.Dev.NT.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: {Install FILES exit (0x00000000)}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 15:10:26.863
    ndv: Pruning file queue...
    dvi: {_SCAN_FILE_QUEUE}
    flq: ScanQ flags=620
    flq: SPQ_SCAN_PRUNE_COPY_QUEUE
    flq: SPQ_SCAN_FILE_COMPARISON
    flq: SPQ_SCAN_ACTIVATE_DRP
    flq: ScanQ number of copy nodes=0
    flq: ScanQ action=200 DoPruning=32
    flq: ScanQ end Validity flags=620 CopyNodes=0
    dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
    ndv: Committing file queue...
    flq: {_commit_file_queue}
    flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
    flq: CommitQ early exit: No nodes are queued
    flq: {_commit_file_queue exit OK}
    ndv: Registering CoInstallers...
    dvi: {DIF_REGISTER_COINSTALLERS} 15:10:26.879
    dvi: No class installer for 'Unknown Device'
    dvi: Default installer: Enter 15:10:26.879
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'
    ([strings.0409])
    inf: {Install Inf Section
    [BADDEVICE.Dev.NT.CoInstallers]}
    inf: {Install Inf Section
    [BADDEVICE.Dev.NT.CoInstallers] exit (0x00000000)}
    dvi: Co-installers registered.
    dvi: Default installer: Exit
    dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)}
    15:10:26.879
    ndv: Installing interfaces...
    dvi: {DIF_INSTALLINTERFACES} 15:10:26.879
    dvi: No class installer for 'Unknown Device'
    dvi: No CoInstallers found
    dvi: Default installer: Enter 15:10:26.879
    dvi: {Install INTERFACES}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'
    ([strings.0409])
    dvi: Installing section
    [BADDEVICE.Dev.NT.Interfaces]
    dvi: {Install INTERFACES exit 00000000}
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 15:10:26.879
    ndv: Installing device...
    dvi: {DIF_INSTALLDEVICE} 15:10:26.879
    dvi: No class installer for 'Unknown Device'
    dvi: Default installer: Enter 15:10:26.879
    dvi: {Install DEVICE}
    inf: Opened PNF:
    'c:\windows\system32\driverstore\filerepository\usb.inf_amd64_neutral_153b489118ee37b8\usb.inf'
    ([strings.0409])
    dvi: Processing Registry/Property directives...
    inf: {Install Inf Section [BADDEVICE.Dev.NT]}
    inf: AddReg=BADDEVICE.AddReg (usb.inf
    line 92)
    inf: {Install Inf Section [BADDEVICE.Dev.NT]
    exit (0x00000000)}
    inf: {Install Inf Section
    [BADDEVICE.Dev.NT.Hw]}
    inf: Empty section
    inf: {Install Inf Section [BADDEVICE.Dev.NT.Hw]
    exit (0x00000000)}
    dvi: {Writing Device Properties}
    dvi: Provider name=Microsoft
    dvi: DriverDate 06/21/2006
    dvi: DriverVersion=6.1.7601.17586
    dvi: Class name=USB
    dvi: Manufacturer=(Standard USB Host
    Controller)
    dvi: Matching DeviceID=usb\unknown
    dvi: Strong
    Name=usb.inf:Generic.Section.NTamd64:BADDEVICE.Dev:6.1.7601.17586:usb\unknown
    dvi: {Writing Device Properties - Complete}
    inf: {Install Inf Section
    [BADDEVICE.Dev.NT.Services]}
    inf: AddService=,0x00000002 (usb.inf line
    100)
    ! dvi: Add Service: NULL Controlling
    service.
    inf: {Install Inf Section
    [BADDEVICE.Dev.NT.Services] exit(0x00000000)}
    dvi: Updated reflected section names for:
    usb.inf
    dvi: {Install DEVICE exit (0x00000000)}
    dvi: Writing common driver property settings.
    dvi: DriverDescription=Unknown Device
    dvi: DeviceDisplayName=Unknown Device
    dvi: Install Device: Restarting device. 15:10:26.895
    dvi: Install Device: Restarting device completed.
    15:10:26.926
    dvi: Default installer: Exit
    dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 15:10:26.926
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 15:10:26.926
    dvi: No class installer for 'Unknown Device'
    dvi: Default installer: Enter 15:10:26.926
    dvi: Default installer: Exit
    dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)}
    15:10:26.926
    ndv: Device install status=0x00000000
    ndv: Performing device install final cleanup...
    ! ndv: Queueing up error report since device has a PnP
    problem...
    ndv: {Core Device Install - exit(0x00000000)} 15:10:26.926
    ump: Server install process exited with code 0x00000000
    15:10:26.926
    <<< Section end 2011/08/18 15:10:26.926
    <<< [Exit status: SUCCESS]
     
    erbutra, Aug 18, 2011
    #5
  6. erbutra

    Paul Guest

    So just working on that amount of information. What Device has a VID of 0000
    and a PID of 0000. That is immediately suspicious! That sounds like a reserved
    value.

    You'll notice here, the table doesn't start at 0000. There is no Vendor with
    a VID value of 0000.

    http://www.linux-usb.org/usb.ids

    If you need to remove the Bluetooth module, it mounts on a 2x6 pin header,
    and should be removable. I can see a picture of it, but the picture is tiny
    and I can't see if there is a mounting screw attached to it or not.

    Paul
     
    Paul, Aug 18, 2011
    #6
  7. erbutra

    erbutra Guest

    the problem:
    usb bluetooth not remove, for remove i have disasseble motherboard

    if it was an easy thing I had already raised
     
    erbutra, Aug 19, 2011
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.