NI-PCI 8431

Hello,
I have a problem of writing frames with fixed frequency 200Hz(5mS) using the NI PCI-8431/2 and LABVIEW 2013.
I cannot get frames with constant frequency 200Hz(5mS). The frequency is changed during communication.
Why?
Please open enclosed vi and scope picture from the port output of the NI-PCI-8431.
Thanks.
Solved!
Go to Solution.
Attachments:
Serial write code.jpg ‏133 KB
Serial write front panel.jpg ‏32 KB
IMG-20141202-WA0000.jpg ‏80 KB

For LabVIEW RealTime, you will nee an NI RT controller. These are most common in cRIO or PXI. So you may not be able to use the PCI-8431 anymore. Possibly the PXI version of that card if you use a PXI RT controller.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions

Similar Messages

485 4 wire to 2 wire connection with PCIe 8431

I am trying to connect to a watlow temperature controller with my PCIe 8431. When I wired up the cable I shorted Tx+ to Rx+ (p 4,8) and Tx- to Rx- (P5,9) to connect to the controller. I assume this is converting from 4 wire to 2 wire but, when you look at the "loop back" connections from NI this is exactly what they tell you to do. I ask since I am uncertain and I am not able to establish communication with the controller.
Solved!
Go to Solution.

Have you seen this - http://digital.ni.com/public.nsf/allkb/3EB322DAEAACB19D862571F500021C00

NI-PCI 8431/2 buffering

OK,
I have a 8431/2 that needs to receive data(each message is 5 bytes) coming in at 19200 with 2 IDLE characters between each message. No term chars, no breaks. I also need to process each message real time. What is a good labivew design approach here, other than going to Labview RT.
I have tried using NI-Serial and NI-VISA and data is being overwritten I simply wait for 5 characters to arrive, and process them. The problem is that messages are being lost. I could change the app around to receive a load of input and then process it, but that is not what I am after.

I cannot do my processing in < 2ms for each 5 bytes received. I am certain data is being overwritten. I beleive I need hardware assistance to buffer the data so that I can process it at my rate. Do you know anything about the 8431/2?
Simple example code is not whay I am looking for, been there done that. If I slow down my simulators transmitter, everthing works fine. Unfortunately, the final product that I shall be interfacing with will only have 2 chars idle time between 5 byte packets.
For example, in other programming languages/platforms, I'd have the reciever interrupt when it detects the two idle chars. My ISR would put them in a buffer for my main thread to operate on when it gets to it. Is this possible with the 8431 and Labview? How? Other ideas? Polling is not gonna do it.

Can FieldPoint be configured for use with 4 wire temperature sensors?

I would like to build a fieldpoint-based measurement system that is configured to accept 4 wire type low temperature sensors, pressure sensors, and several 4 wire (100ma) magnetic hall sensors. Each 4 wire temperature and magnetic hall sensor will require a stable current source (20ma -100ma range). We need to be able to synchronously read up to 8 sensors. Under certain circumstances we would like update rates up to 50 Hz (0.02 seconds) on all 8 channels. We currently have FieldPoint products, such as FP-1001 modules (RS-485 Network Interface), FP AI-110 modules (8 channel, 16 bit analog input), FP-RTD-122 modules (8 channel RTD input), FP-RLY-420 modules (SPST Relay), FP-TB-1 (36 screw terminal, Universal Terminal Base), NI-SCC-68 (68 pin Terminal Block with 4SCC expansion slots), PCI-8431 (RS-485 Serial 2 Channel Card), and other FP modules on hand that we would like to use in this experiment design if possible. I would like more information on the NI FP-RTD-124, (4 wire, 8 ch., 16 bit RTD input module) regarding use with platinum RTDs and low level/low temperature signals, and maximum refresh rates. Thanks for your help,
LGF

Hi LGF. FP-RTD-124 info is here: (c)FP-RTD-124 manual.
The range of the -124 on the low end is -200C; we use it to -196C with 100 ohm Platinum sensors with good results.
The update rate, ~ 1S, however, is not going to meet your requirements. Can your temperatures really change that rapidly?
The excitation is fixed at 2mA x 135 mS with a period of 1S. Fine for an RTD, don't know about your Hall sensors.
Your AI-110 module can be configured to read the Hall sensors with external excitation but the maximum update rate is 0.173S.
Hope that helps.
Matt

Robot rs485

Bonjour,
Dans le cadre d'un stage, nous essayons de piloter un bras de robot, qui necessite une liaison RS485 pour communiquer. Ce robot date des années 90, et nous manquons de documentations. Auparavant, il avait été programmé en Turbo Pascal et nous aimerions pouvoir programmer ce robot sous labview.
L'ensemble, se compose d'une armoire et du robot ARIA de marque SWITZERLAND (CASTOR) MR-03.
L'armoire est composé de :
- d'un rack d'alimentation,
- d'un rack d'axes, comportant 6 cartes d'axes, une carte I/O 32 et une carte OPTO 22 :
Différents degrés :
1 : Rotation d’axe X       Caractéristiques : Rotation sur 340°
2 : Translation d’axe X       Caractéristiques : Translation sur 135 mm
3 : Translation d’axe Y       Caractéristiques : Translation sur 200 ou 220 mm
4 : Rotation d’axe Y       Caractéristiques : Rotation sur 190°
5 : Rotation d’axe Z       Caractéristiques : Rotation sur 190°
6 : Rotation autour d’un axe situé sur le plan (X, Y)       Caractéristiques : Rotation sur 2160°
- d'un rack capteurs.
on souhaiterait développer un programme qui permette la commande d'un des axes du bras de robot. Pour cela nous aimerions nous baser sur un exemple qui pourrait déja exister. Malheureusement, nous n'avons pas de connaissances approfondies sur le logiciel labview.
Merci pour vos réponses.
Cordialement M.Popowicz.

Bonjour,
Concernant votre message d'erreur, veuillez consulter cette Knowledge Base pour voir si elle peut vous aider. Il se peut également que cette erreur vienne d'un soucis au niveau de la vitesse.
Si vous souhaiter vous informez sur nos matériel, il existe par exemple cette carte NI PCI-8431/2 qui a de très bonnes capacités. A partir de cette page vous aurez également un accès à tous nos matériels séries sous différents facteurs de forme.
A propos de l'adresse des cartes d'axes, je ne suis pas sûr de comprendre votre besoin. Si chacune serait branchée sur un port série (d'une carte NI PCIe-8430 8 ports par exemple), l'adressage sera facile par LabVIEW car les ports seront listés. Si vous branchez un unique port série sur un dispositif qui communique avec les différents variateurs, dans ce cas l'addressage doit être indiqué dans la documentation de ce dispositif.
Cordialement,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

EUROTHERM 2604

DEAR SIR, I M TRYING TO COMMUNICATE WITH EUROTHERM 2640 CONTROLLER THROUGH NI PCI 8431/8 PORT RS 485 INTERFACE BUT NOT ABLE TO ESTABLISH THE COMMUINACTION . THE PROTOCOL IS MODBUS AND INTERFACE IS EIA RS 485 ( 2 WIRE) ,NULL MODEM CABLE( CROSS CABLE). FOR COMMUNICATING I HAVE SORTED THE TX + AND RX + AND TX- RX- . I HAVE TRIED NI MODBUS LIBRARY FOR COMMUNICATING BUT NOT ABLE TO DO THE SAME. ON SEARCHING THIS FORUM I CAME TO KNOW ABOUT THE OPC CONNECTIVTY IS POSSIBLE. I M TOTALLY CONFUSED DONT KNOW HOW TO PROCEED.

Hi Rahul,The 2604 controller is a vey versatile instrument and you should not have any problems communicating using Serial Modbus or OPC. I am using both on a daily basis to communicate with the controller, the DataSocket Vis together with iTools (iTools OPC server) and our own Serial Modbus vis for Serial Modbus RS232 and EIA485.I have also used the NI Modbus library to communicate a 2604 controller without any problems.Before I assist you any further we need to identify if the problem is in the hardware, (i.e. incorrect wiring) or is in the software,( i.e. incorrect configuration, settings, etc). Therefore can you please give me a detailed diagram of your wiring from the PCI card to the controller including 9 way connector pin numbers and controller comms terminals (i.e. HD, HE, HF.)In addition can you please confirm the following?1) You have a 458 Communcation module plugged in the controller?2) The module appears on the controller comms page?3) You have identical Communication parameters for both the 2604 controller and the PCI card (Baud Rate, Parity, Flow Control)4) You have the same Slave address in the NI Modbus vi as is set on the 2604?RegardsDimitris

The problem of 8431/4 borad on PXI bus

Hello,
when I connect the PXI-8431/4 board to the PXI bus in QNX system, I find that there is only one "PCI Mem Address" record.
But the other boards(e.g. NI PXI-6602,NI PXI-6250) have two "PCI Mem Address".
you can see the following detail trace:
Class          = Unknown (Unknown)
Vendor ID      = 1093h, National Instruments
Device ID      = 70b9h, Unknown Unknown
PCI index      = 0h
Class Codes    = ff0000h
Revision ID    = 0h
Bus number     = 20
Device number = 13
Function num   = 0
Status Reg     = 280h
Command Reg    = 117h
Header type    = 0h Single-function
BIST           = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 10h un-cacheable
PCI Mem Address = f6406000h 32bit length 4096 enabled    //PXI-6250
PCI Mem Address = f6405000h 32bit length 4096 enabled
Max Lat        = 0ns
Min Gnt        = 0ns
PCI Int Pin    = INT A
Interrupt line = 10
CPU Interrupt = ah
Class          = Communication (Other)
Vendor ID      = 1093h, National Instruments
Device ID      = 70deh, Unknown Unknown
PCI index      = 0h
Class Codes    = 078000h
Revision ID    = 0h
Bus number     = 20
Device number = 14
Function num   = 0
Status Reg     = 280h
Command Reg    = 117h
Header type    = 0h Single-function
BIST           = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 10h un-cacheable
PCI Mem Address = f6407000h 32bit length 4096 enabled   //PXI-8431
Subsystem Vendor ID = 1093h
Subsystem ID        = 70deh
Max Lat        = 0ns
Min Gnt        = 0ns
PCI Int Pin    = INT A
Interrupt line = 10
CPU Interrupt = ah
Is there any problem?
Because there is only one Mem Address in QNX system, the interface function acquireBoard() will be returned by Error: bar1 map: invalid argument.
Therefore, it can not be initialled in QNX system.

Maybe it just gets two memory card.

New system, MSI X800XT PCI-E Issues

Hi there!
I just bought a new motherboard, new ram, new cpu and new videocard and was eagerly wanting to set this stuff up.
My system is now as follows:
Motherboard: MSI 925X Neo-54G
CPU: P4 3.40Ghz (1 Mb L2 Cache) (Socket 775)
RAM: 1 GByte DDR2 533
Video Card: MSI RX800 XT-VTD256 (ATI Radeon X800XT PCI-E)
I put everything up and working and installed Windows XP w/ SP2. Installed every driver needed from the motherboard CD, went to ATI's site and downloaded the latest Catalyst Drivers, etc.
After having everything apparently working as it should, I downloaded 3dMark 2005 to see how it went. I had never used the 2005 version before so I wasn't too shocked to see it only got like 3200 points although I was kinda suspicious after seeing some of the tests going at like 1 fps.
I went back to another PC I have at home (a socket 478, P4 3.0Ghz, Asus P4C800 mobo, 1 GByte DDR400 Ram and a GeForce 6800 Ultra). Ran 3dMark 2005 and to my amazement, it got like 4400 points.
Well, double checked everything on the catalyst control panel (nothing really useful there)... then went back to the BIOS setup to investigate what is not working as it should. MSI boards have that nifty Dynamic Overclocking thing and so I turned it on. My BIOS settings are now as following (only listing settings I have doubts on):
DDR2 533 (Dual Channel Mode Enabled)
DRAM Timing Selectable: By SPD
Memory Hole: Disabled
PCI Express Root Port Func: Auto on all 4 ports
PCI-E Compliance Mode: v1.0a
DRAM Data integrity mode: Non-ECC
PCI IDE Busmaster: Enabled (I have a 250GB 8MB SATA HD,fyi)
Init Display First: PCI-E
Maximum Payload Size (PCI-E): 4096
High performance mode: Optimized (Manual is the other option)
Dynamic Overclocking: 5% (0-15% range)
Adjust DDR Frequency: Auto
Auto Detect PCI Clock: Enabled
Spread Spectrum: Disabled
CPU Clock: 200Mhz
CPU Voltage: By CPU default
Memory Voltage: 1.8v
AGP/PCI-E Voltage: 1.5v
Ok, so, can anyone tell me what is wrong (if anything)? I mean, I think this PC should be faster than my other one...
I'm not really interested in overclocking and I am really convinced this hardware should be able to beat my other one easily with default operating status.
Also, I tested this PC's performance with Rome: Total War and it is just as 3dMark had showed, it performs worse than the other pc I mentioned, with the same exact settings.
Any help please?
Regards!

Quote
Originally posted by thegrommit
I'm not familiar with Intel motherboards, but posting your DirectX results might help someone who is work out whether you have all the right drivers installed:
Ok, here goes:
System Information
Time of this report: 10/3/2004, 15:48:43
Machine name: PC2
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_rtm.040803-2158)
Language: English (Regional Setting: Portuguese)
System Manufacturer: INTELR
System Model: AWRDACPI
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Pentium(R) 4 CPU 3.40GHz (2 CPUs)
Memory: 1024MB RAM
Page File: 138MB used, 2323MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
DxDiag Notes
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
DirectX Debug Levels
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: RADEON X800 XT
Manufacturer: ATI Technologies Inc.
Chip type: RADEON X800 XT (0x5D57)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_5D57&SUBSYS_03121002&REV_00
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (85Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6476 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 8/25/2004 13:29:04, 209408 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: ati2mtag.sys
Mini VDD Date: 8/25/2004 13:28:46, 787456 bytes
Device Identifier: {D7B71EE2-1E17-11CF-FE6A-1823A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x5D57
SubSys ID: 0x03121002
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
Sound Devices
Description: SB Audigy Audio [D000]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0004&SUBSYS_00531102&REV_03
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: e10kx2k.sys
Driver Version: 5.12.0001.0136 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 11/5/2001 13:02:30, 1758336 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 4000, 191999
Static/Strm HW Mix Bufs: 32, 31
Static/Strm HW 3D Bufs: 32, 31
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Sound Capture Devices
Description: SB Audigy Audio [D000]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: e10kx2k.sys
Driver Version: 5.12.0001.0136 (English)
Driver Attributes: Final Retail
Date and Size: 11/5/2001 13:02:30, 1758336 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
DirectMusic
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: Enabled
Ports: SB Audigy DirectMusic Synthesizer [D000], Hardware (Kernel Mode), Output, DLS, Internal, Default Port
SB Audigy Audio [D000], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Synth A [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Sw Synth [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy Synth B [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy MIDI Port [D000] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, External
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB Audigy MIDI Port [D000] [Emulated], Hardware (Not Kernel Mode), Input, No DLS, External
Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal
Registry: OK
Test Result: Not run
DirectPlay Service Providers
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: Not run
Registry: OK
DirectPlay Adapters
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: Local Area Connection - IPv4 -
DirectPlay Voice Codecs
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
DirectPlay Lobbyable Apps
Disk & DVD/CD-ROM Drives
Drive: C:
Free Space: 190.3 GB
Total Space: 239.4 GB
File System: NTFS
Model: Maxtor 7Y250M0
Drive: E:
Free Space: 42.0 GB
Total Space: 117.8 GB
File System: FAT32
Model: IC35L120AVV207-0
Drive: F:
Free Space: 28.9 GB
Total Space: 76.3 GB
File System: NTFS
Model: ST380011A
Drive: D:
Model: CREATIVE DVD-ROM DVD6240E
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Portuguese), 8/4/2004 06:59:54, 49536 bytes
Drive: G:
Model: AXV CD/DVD-ROM SCSI CdRom Device
Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Portuguese), 8/4/2004 06:59:54, 49536 bytes
System Devices
Name: Intel(R) 82801FB/FBM Ultra ATA Storage Controllers - 266F
Device ID: PCI\VEN_8086&DEV_266F&SUBSYS_70531462&REV_03\3&2411E6FE&0&F9
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:52, 3328 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Portuguese), 8/3/2004 22:59:42, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Name: Intel(R) 82801FB/FBM SMBus Controller - 266A
Device ID: PCI\VEN_8086&DEV_266A&SUBSYS_70531462&REV_03\3&2411E6FE&0&FB
Driver: n/a
Name: PCI Device
Device ID: PCI\VEN_8086&DEV_2668&SUBSYS_26688086&REV_03\3&2411E6FE&0&D8
Driver: n/a
Name: Intel(R) 82801FB/FBM PCI Express Root Port - 2660
Device ID: PCI\VEN_8086&DEV_2660&SUBSYS_00000000&REV_03\3&2411E6FE&0&E0
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C
Device ID: PCI\VEN_8086&DEV_265C&SUBSYS_70531462&REV_03\3&2411E6FE&0&EF
Driver: C:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 26624 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Driver: C:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/4/2004 08:56:44, 7168 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 265B
Device ID: PCI\VEN_8086&DEV_265B&SUBSYS_70531462&REV_03\3&2411E6FE&0&EB
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 265A
Device ID: PCI\VEN_8086&DEV_265A&SUBSYS_70531462&REV_03\3&2411E6FE&0&EA
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 2659
Device ID: PCI\VEN_8086&DEV_2659&SUBSYS_70531462&REV_03\3&2411E6FE&0&E9
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
Device ID: PCI\VEN_8086&DEV_2658&SUBSYS_70531462&REV_03\3&2411E6FE&0&E8
Driver: C:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: C:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: C:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (English), 8/4/2004 00:56:48, 74240 bytes
Driver: C:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: Intel(R) 82801FB Ultra ATA Storage Controllers - 2652
Device ID: PCI\VEN_8086&DEV_2652&SUBSYS_70531462&REV_03\3&2411E6FE&0&FA
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:52, 3328 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Portuguese), 8/3/2004 22:59:42, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Name: Intel(R) 82801FB LPC Interface Controller - 2640
Device ID: PCI\VEN_8086&DEV_2640&SUBSYS_00000000&REV_03\3&2411E6FE&0&F8
Driver: C:\WINDOWS\system32\DRIVERS\isapnp.sys, 5.01.2600.0000 (English), 8/17/2001 13:58:02, 35840 bytes
Name: Intel(R) 925X PCI Express Root Port - 2585
Device ID: PCI\VEN_8086&DEV_2585&SUBSYS_00000000&REV_04\3&2411E6FE&0&08
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: Intel(R) 925X Memory Controller Hub - 2584
Device ID: PCI\VEN_8086&DEV_2584&SUBSYS_00000000&REV_04\3&2411E6FE&0&00
Driver: n/a
Name: Intel(R) 82801 PCI Bridge - 244E
Device ID: PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_D3\3&2411E6FE&0&F0
Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 5.01.2600.2180 (English), 8/3/2004 23:07:48, 68224 bytes
Name: Intel(R) PRO/100 VE Network Connection
Device ID: PCI\VEN_8086&DEV_1064&SUBSYS_053C1462&REV_03\4&10355354&0&40F0
Driver: C:\WINDOWS\system32\DRIVERS\e100b325.sys, 7.01.0012.0000 (Portuguese), 2/10/2004 07:49:14, 154112 bytes
Driver: C:\WINDOWS\system32\Prounstl.exe, 7.00.0006.0000 (English), 11/21/2003 07:26:42, 118784 bytes
Driver: C:\WINDOWS\system32\e100b325.din, 6/26/2002 22:53:38, 5110 bytes
Driver: C:\WINDOWS\system32\IntelNic.dll, 2.05.0001.0000 (English), 7/27/2003 22:55:40, 24064 bytes
Driver: C:\WINDOWS\system32\e100bmsg.dll, 2/18/2004 09:40:00, 12288 bytes
Name: Broadcom NetXtreme Gigabit Ethernet
Device ID: PCI\VEN_14E4&DEV_1677&SUBSYS_053C1462&REV_01\4&F39E1D8&0&00E0
Driver: n/a
Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_1106&DEV_3164&SUBSYS_31641106&REV_06\4&10355354&0&20F0
Driver: C:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Portuguese), 8/3/2004 22:59:42, 25088 bytes
Driver: C:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Driver: C:\WINDOWS\system32\DRIVERS\pciide.sys, 5.01.2600.0000 (English), 8/17/2001 13:51:52, 3328 bytes
Name: Creative Game Port
Device ID: PCI\VEN_1102&DEV_7003&SUBSYS_00401102&REV_03\4&10355354&0&01F0
Driver: C:\WINDOWS\system32\drivers\gameenum.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:22, 10624 bytes
Name: OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1102&DEV_4001&SUBSYS_00101102&REV_00\4&10355354&0&02F0
Driver: C:\WINDOWS\system32\DRIVERS\ohci1394.sys, 5.01.2600.2180 (English), 8/4/2004 07:10:10, 61056 bytes
Driver: C:\WINDOWS\system32\DRIVERS\1394bus.sys, 5.01.2600.2180 (English), 8/4/2004 07:10:08, 53248 bytes
Driver: C:\WINDOWS\system32\DRIVERS\nic1394.sys, 5.01.2600.2180 (English), 8/4/2004 09:05:44, 61824 bytes
Driver: C:\WINDOWS\system32\DRIVERS\arp1394.sys, 5.01.2600.2180 (English), 8/4/2004 09:05:44, 60800 bytes
Driver: C:\WINDOWS\system32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/17/2001 14:46:40, 6400 bytes
Name: Creative SB Audigy
Device ID: PCI\VEN_1102&DEV_0004&SUBSYS_00531102&REV_03\4&10355354&0&00F0
Driver: C:\WINDOWS\system32\ksuser.dll, 5.03.2600.2180 (Portuguese), 8/4/2004 00:56:44, 4096 bytes
Driver: C:\WINDOWS\system32\ksproxy.ax, 5.03.2600.2180 (Portuguese), 8/4/2004 00:56:58, 130048 bytes
Driver: C:\WINDOWS\system32\drivers\ks.sys, 5.03.2600.2180 (Portuguese), 8/3/2004 23:15:22, 140928 bytes
Driver: C:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:00, 60288 bytes
Driver: C:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.2180 (English), 8/3/2004 23:15:50, 145792 bytes
Driver: C:\WINDOWS\system32\drivers\stream.sys, 5.03.2600.2180 (Portuguese), 8/3/2004 23:08:04, 48640 bytes
Driver: C:\WINDOWS\system32\wdmaud.drv, 5.01.2600.2180 (English), 8/4/2004 00:56:58, 23552 bytes
Driver: C:\WINDOWS\system32\drivers\e10kx2k.sys, 5.12.0001.0136 (English), 11/5/2001 13:02:30, 1758336 bytes
Driver: C:\WINDOWS\system32\drivers\ctoss2k.sys, 5.12.0001.0131 (English), 9/11/2001 13:10:14, 186944 bytes
Driver: C:\WINDOWS\system32\ctdlang.dat, 9/11/2001 13:36:02, 161900 bytes
Driver: C:\WINDOWS\system32\ctstatic.dat, 9/11/2001 13:27:44, 144493 bytes
Driver: C:\WINDOWS\system32\ctdaught.dat, 9/11/2001 13:24:48, 44055 bytes
Driver: C:\WINDOWS\system32\default.ecw, 9/23/1999 00:18:50, 2259067 bytes
Driver: C:\WINDOWS\system32\sfman32.dll, 5.12.0001.0130 (English), 8/17/2001 15:35:44, 36864 bytes
Driver: C:\WINDOWS\system32\a3d.dll, 80.00.0000.0003 (English), 9/11/2001 13:05:52, 49152 bytes
Driver: C:\WINDOWS\system32\ctbas2w.dat, 9/11/2001 13:35:58, 111123 bytes
Driver: C:\WINDOWS\system32\SBAudigy.ico, 8/17/2001 13:42:28, 7406 bytes
Driver: C:\WINDOWS\system32\AUDIGYICON.bmp, 8/17/2001 13:42:08, 1912 bytes
Name: RADEON X800 XT Secondary
Device ID: PCI\VEN_1002&DEV_5D77&SUBSYS_03131002&REV_00\4&2B4A1FD5&0&0108
Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6476 (Portuguese), 8/25/2004 13:28:46, 787456 bytes
Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6476 (English), 8/25/2004 13:29:04, 209408 bytes
Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0252 (English), 8/25/2004 13:10:20, 237568 bytes
Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2494 (English), 8/25/2004 13:27:08, 65536 bytes
Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0257 (English), 8/25/2004 13:25:56, 2239328 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0001.0029 (English), 8/25/2004 13:15:16, 476928 bytes
Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0005 (English), 8/25/2004 13:26:32, 81920 bytes
Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4100 (English), 8/25/2004 13:12:10, 17408 bytes
Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/9/2001 11:01:04, 24064 bytes
Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4105 (English), 8/25/2004 13:26:56, 389120 bytes
Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4105 (English), 8/25/2004 13:27:00, 86016 bytes
Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2491 (English), 8/25/2004 13:27:18, 126976 bytes
Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0010 (English), 8/25/2004 13:27:12, 102400 bytes
Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2494 (English), 8/25/2004 13:27:04, 30720 bytes
Driver: C:\WINDOWS\system32\ATIDEMGR.dll, 1.00.1698.24059 (Portuguese), 8/25/2004 14:22:08, 151552 bytes
Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.4582 (English), 8/25/2004 13:48:12, 6508544 bytes
Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4003 (English), 8/25/2004 14:40:02, 294912 bytes
Name: RADEON X800 XT
Device ID: PCI\VEN_1002&DEV_5D57&SUBSYS_03121002&REV_00\4&2B4A1FD5&0&0008
Driver: C:\WINDOWS\system32\DRIVERS\ati2mtag.sys, 6.14.0010.6476 (Portuguese), 8/25/2004 13:28:46, 787456 bytes
Driver: C:\WINDOWS\system32\ati2dvag.dll, 6.14.0010.6476 (English), 8/25/2004 13:29:04, 209408 bytes
Driver: C:\WINDOWS\system32\ati2cqag.dll, 6.14.0010.0252 (English), 8/25/2004 13:10:20, 237568 bytes
Driver: C:\WINDOWS\system32\Ati2mdxx.exe, 6.14.0010.2494 (English), 8/25/2004 13:27:08, 65536 bytes
Driver: C:\WINDOWS\system32\ati3duag.dll, 6.14.0010.0257 (English), 8/25/2004 13:25:56, 2239328 bytes
Driver: C:\WINDOWS\system32\ativvaxx.dll, 6.14.0001.0029 (English), 8/25/2004 13:15:16, 476928 bytes
Driver: C:\WINDOWS\system32\ATIDDC.DLL, 6.14.0010.0005 (English), 8/25/2004 13:26:32, 81920 bytes
Driver: C:\WINDOWS\system32\atitvo32.dll, 6.14.0010.4100 (English), 8/25/2004 13:12:10, 17408 bytes
Driver: C:\WINDOWS\system32\ativcoxx.dll, 6.13.0010.0005 (English), 11/9/2001 11:01:04, 24064 bytes
Driver: C:\WINDOWS\system32\ati2evxx.exe, 6.14.0010.4105 (English), 8/25/2004 13:26:56, 389120 bytes
Driver: C:\WINDOWS\system32\ati2evxx.dll, 6.14.0010.4105 (English), 8/25/2004 13:27:00, 86016 bytes
Driver: C:\WINDOWS\system32\atipdlxx.dll, 6.14.0010.2491 (English), 8/25/2004 13:27:18, 126976 bytes
Driver: C:\WINDOWS\system32\Oemdspif.dll, 6.14.0001.0010 (English), 8/25/2004 13:27:12, 102400 bytes
Driver: C:\WINDOWS\system32\ati2edxx.dll, 6.14.0010.2494 (English), 8/25/2004 13:27:04, 30720 bytes
Driver: C:\WINDOWS\system32\ATIDEMGR.dll, 1.00.1698.24059 (Portuguese), 8/25/2004 14:22:08, 151552 bytes
Driver: C:\WINDOWS\system32\atioglxx.dll, 6.14.0010.4582 (English), 8/25/2004 13:48:12, 6508544 bytes
Driver: C:\WINDOWS\system32\atiiiexx.dll, 6.14.0010.4003 (English), 8/25/2004 14:40:02, 294912 bytes
Name: SOJU SCSI Controller
Device ID: PCI\SOJU341\0000
Driver: n/a
Hope anyone can help me out

PCI DIO 32HS (6533) Suddenly giving "The device is not responding to the first IRQ level" error, and no longer functioning.

Greetings NI folks,
I'm an oceanographer, and have an sidescan sonar data aquasition computer running Windows XP SP2, and NiDAQ 7.0 (Legacy). For several years, this machine has worked flawlessly, but today, I booted it up to test the system for an upcoming job, and I got some strange errors in our sonar program. I tranced the problem to our NI-6533 PCI-DIO-32HS card. I launched NI Automation Explorer to test that the card was responsive, and when I click the "test panel", I get an error: "The device is not responding to the first IRQ level." Continue (yes/no). If I click yes, I can test the digital i/o's, but nothing happens, and all the tests fail (nonresponsive). I tried moving the card to another PCI slot, tried forcing it to have a specific IRQ that was unused by anything else, and finally tried moving it to another computer that had never been used with the DIO card. I'm still getting the error, and the card is nonresponsive. I'm at the limit of my abilities, and would like to know if there's anything else I can do, or should we send the card back to NI for repair/diagnosis.
Thanks.

Duplicate Post
Best Regards
Hani R.
Applications Engineer
National Instruments

Z97 GAMING 9 AC - PCIE and the wi-fi module no longer detecting

Hi,
I 'm Overclocking enthusiast and recently decided to take to my hometown in Brazil using a platform products from MSI, to make disclosure of benchmark tests in social networks and in gaming blogs.
So i purchased a new system including the MSI Z97 GAMING 9 AC motherboard and MSI Gaming N770 TF 4GD5/OC GeForce GTX 770 4GB graphics card. After building the system I initially had problems with the graphics card not being detected and the wi-fi module (that hard to fit in the mobo) don't even appear in device manager. I already tried to dismount and remount the module on the motherboard with extreme care, no success. After some research I updated the bios to 1.5 and used the onboard graphics card to install windows 8.1, drivers etc. After windows, drivers etc were installed the graphics card and the wi-fi module still would not detect.
I have tried another graphics card in this system and it does not seem to work either. In bios it just always says that the PCIE slots are 'empty'.
So I have tried the following:
1. Cleared CMOS.
2. Updated BIOS.
3. Updated Chipset, drivers etc.
4. Tested the Graphics Card in other computers.
5. Used a different graphics card in this system.
6. Tried PCIE 2.0, 3.0 and auto.
7. Completely reformated and started from scratch.
So after many attempts I am disappointed with MSI and need some solution to my problem, since I saw that several customers who have purchased from MSI are the same product with exactly the same problem which possibly conclude that MSI has a duty to resolve these cases.
Full Specs:
•   EVGA SuperNOVA 1300G2 ATX12V/EPS12V 1300W 80Plus Gold Power Supply 120-G2-1300-XR
•   Corsair Cooling Hydro Series H100i Liquid CPU Cooler - Extreme Performance CPU Cooling and Built-In
•   Intel Core i7 4790 LGA1150 CPU 3.6Ghz
•   Corsair Vengeance Pro 16GB 2x8GB DDR3
•   2 x Kingston 120GB SSD 6Gbs
•   Microsoft Windows 8.1 Pro 64bit OEM
•   MSI Z97 Gaming 9 AC Motherboard
•   MSI Gaming N770 TF 4GD5/OC GeForce GTX 770 4GB 256-Bit GDDR5 PCI Express 3.0 HDCP Ready SLI Support Video Card

I have the exact same problem with my gaming 9 AC only the PCIe slot for gfx card worked initially. MSI support sent me a new WiFi adapter, it also didnt work. When I installed it, the PCIe slot would not identify my graphics card anymore. MSI support then advised me to return the board to the reseller, where it is now - they are checking it for defects before they do anything.
Ill keep you updated how they proceed from here. If there are any more problems I will just ask my reseller to downgrade me to a gaming 7, I can add a pcie wifi card on my own, and avoid the hassle.

Z97 GAMING 9 AC - PCIE no longer detecting

Hi,
So I recently purchased a new system including the MSI Z97 GAMING 9 AC motherboard and MSI R9 280X GAMING G3 graphics card. After building the system I initially had problems with the graphics card not being detected. After some research I updated the bios to 1.4 and used the onboard graphics card to install windows 8.1, drivers etc. After windows, drivers etc were installed the graphics card still would not detect until I went into the bios and changed the PCIE to 2.0 (instead of auto). This then used the 280x instead of onboard and allowed me to install the graphics card drivers. I switched the PCIE to 3.0 after it was working.
Initially everything was working but the next morning I had the same issue again: only the onboard graphics card was being used. I switched back to PCIE 2.0 and it worked again. Until the next morning: the 280x is no longer being detected at all in any PCIE slots or in PCIE auto, 2.0 or 3.0. I have ruled out a graphics card issue as the 280x works in other pcs. I have tried another graphics card in this system and it does not seem to work either. In bios it just always says that the PCIE slots are 'empty'.
So I have tried the following:
1. Cleared CMOS.
2. Updated BIOS.
3. Updated Chipset, drivers etc.
4. Tested the Graphics Card in other computers.
5. Used a different graphics card in this system.
6. Tried PCIE 2.0, 3.0 and auto.
7. Completely reformated and started from scratch.
Any suggestions as to why the PCIE slots seem to have stopped detecting?
Full Specs:
Corsair AX860i ATX Power Supply,80 PLUSPlatinum Full Modular
Corsair Cooling Hydro Series H100i Liquid CPU Cooler - Extreme Performance CPU Cooling and Built-In
Intel Core i7 4770K LGA1150 CPU 3.5Ghz 8Mb Cache Haswell
Corsair 16GB (2x8GB) DDR3 CMY16GX3M2A1600C9R 1600MHz Dimm, Unbuffered, 9-9-9-24, Vengeance Pro Red H
Samsung 250GB SSD 840 EVO SATA III 6Gbs 2.5 7mm 540MB/s/520MB/s
Microsoft Windows 8.1 Pro 64bit OEM
MSI Z97 Gaming 9 AC Motherboard
MSI Radeon R9 280X Gaming 3GB

Was this issue ever solved as im seeing the same issue.
When I first booted the machine all was well however when I came to reboot my machine for the first time it no longer sees I have a GPU and so switched to the Intel onboard 4600.
At first I assumed the GPU had come lose or some BIOS setting needed changing. BIOS is set to use PEG (PCI-E Graphics card device) so i reseated the card and rebooted. This didn't work.
I reset the BIOS CMOS and that fixed the issue, my machine booted using the graphics card again however as soon I rebooted windows again it lost the card switching back to the onboard.
According to the BIOS the PCI-E slot is empty. I swapped the card out for an older ATI 7870 but had the same problem. PCI-E slot is empty unless I clear the CMOS (I made no changes in the BIOS).
At this point it sounds like some kind of software issue I have updated my BIOS to the latest version (1.5) but that hasn't fixed the issue. Whenever I shutdown or restart it will lose sight of my card unless I clear the CMOS or power down at the wall.
SPEC:
Intel 4790k
Nvidia 970 GTX
MSI Z97i Gaming AC mini-itx
8GB 1866mhz Kingston
Corsair 600w PSU

Dv6265us connexant PCI sound card + windows 7 = Not working

So I'm here becuase I can't find a driver on my own. I've scoured the internet for hours, finding very little to help with my issue. So here goes...
I have an HP Pavilion dv6000 (Dv6265us), and ever since I installed window 7, Windows cannot figure out what drivers to install for the PCI sound card. The best I've found so far says this:
"Windows found driver software for your device but encountered an error while attempting to install it"
"Microsoft UAA Bus Driver for High Definition Audio"
"If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Now here's the funky part...everywhere I've found information on my laptop, it says I have a Conexant PCI sound card. If I'm wrong I would love for someone to tell me; better yet, a link to a download to actually be able to use the PCI sound card. Right now the card is under other devices and is listed as "PCI Device".
Now the Link I've provided from the conexant site will tell you this under PC Audio Support - Windows® 7,
"Conexant develops audio solutions that are used in a wide range of products including personal computers. We provide customized audio drivers to our customers, which include major computer manufacturers globally. At the request of these manufacturers, Conexant does not provide end-user support or drivers for PC audio products. If you have an issue with the audio configuration in Windows 7, please contact the manufacturer of your computer.
I tried calling HP support, but they wouldn't even answer my yes or no question... "Do you have audio drivers for my laptop that will allow me to hear sound?" Instead of saying yes or no, I was told that I needed to pay fifty to one-hundred dollars;....fifty dollars for a one time fee of telephone service, or one-hundred for the year. I even went as far as asking..."if you can't fix my problem, do I get a refund?" I was told no...so here I am. I've had problems before with hp...but this is rediculous, and whats worse is from the way things look, Connexant was told NOT to support their own product, or provide drivers for windows 7 by their customer(HP). I realize everyone is hurting for money, but **bleep**, this is a new low...

To answer your question, there are no windows 7 drivers for that model notebook. The notebook was designed for Windows 2000, Windows xp and windows vista.
This is one of the issues with upgrading the OS on a computer before checking the specs of the hardware.
I do understand the frustration but it would be more beneficial to revert back to the original OS that the notebook came with. That is what the HP support desk will have you do to prove functionality of the notebook should you have paid for the Diagnostic Support.
Although I am an HP employee, I am speaking for myself and not for HP. Clicking the "Kudos star" to the left is a great way to say thanks!
When your problem has been solved, accept the solution by clicking the "Accept as Solution" button to help other members in the future!

PCIE 3.0 test with MSI Z68A-GD80 G3 :)

The Z68A-GD80 G3 is MSI’s first motherboard with PCIE 3.0 connectivity. Currently there are no PCIE 3 devices available yet but later on we can test its performance by using a PCIE SSD. Aside from this, the board has also a new UEFI Bios named “Click Bios II” which for me is way better than the previous version.
Before we take a closer look on the board, let’s check out the package first.
Box design is a bit the same as the GD80 B3 version before. Once you open it up, all main features of the said board are enumerated
Extreme Power Design, Military Class II Components (SFC, Hi-C Caps, Multi Bios), 3 PCIEx16 Slots, Super Charger and OC Genie II
For the bundled accessories, you have the same old story – Manual, Software Disc, four SATA cables, two Molex to SATA power connectors & SLI Bridge. Then for some extras - PCI USB 3.0 two ports bracket, guide headers for faster and easy connectivity and lastly voltage check points.
Next, the “Mainboard”. By physically looking at it and by comparing it side by side against the Z68A-GD80 B3 motherboard. You won’t find any difference except for the PCIE X16 locks. It has also the same black and blue color theme, two vrm heatsinks connected by a flat heatpipe and V-Check points.
Moving closer to the board you have 8 Power Pins to power up the processor, 2 PCI slots, 2 PCIE x1 slots for devices such as TV Tuners or Audio Cards. 2 PCIE Gen3 & 1 PCIE Gen2 x16 Slots. With one VC connected at the top most slot, speed will be @ x16. If both top and middle are used, it will be @ x8/x8. Lastly, by using the 3rd PCIEx16 Gen2 slot. You have x8/x8/x4. It would also disable certain onboard devices such as eSATA Port, Sata 7, one onboard front USB 3.0, two PCI Slots and firewire. So if possible avoid using the last VC slot.
At the top most PCIE x1 area. You will find a 6-pin power connector. This will provide more juice/power for multi-GPU setups.
Next, at the bottom part of the board. You have the Easy Buttons (Power and Reset) and the popular one button “OC Genie”. The red colored USB header is for the Super Charger while the blue is a regular USB 3.0. For the SATA Connectors you have a total of 7. 4 regular SATA 3GB/s, 2 SATA 6GB/s controlled by Intel chipset and another SATA 6GB/s by Marvell.
Wrapping things up, we have now the IO terminal ports. Starting from the left we have combo PS2 port and SPDIF Optical Out. Clear CMOS Button, e-SATA port running under Marvell, 2 USB 2.0 and Firewire ports controlled by Via. Moving across, 2 Gigabit Lan by Realtek 8111E, 2 USB 2.0 and 2 USB 3.0 run under NEC D720200 controller. Next, we have DVI and HDMI output connections and 6 analog audio ports by Realtek ALC892.
Once you are into the bios, you will find the new and improved Click Bios. Nice and professional looking, faster navigation and easier to use.
To test the performance of the new PCIE Gen3 technology, we will be using this Photofast PCIE SSD device http://www.photofast.tw/comboproducts.asp?pid=1.
We will be connecting the PCIE SSD device on the GD80’s Gen3 and Gen2 slots and compare the results using the disk benchmark software ATTO. I ran the benchmark 9 times for the two set of tests.
System Configuration as follows:
Processor: Intel Core i7 2600K at default stock speed
Memory: Kingston HyperX Genesis Grey 2x2GB DDR3 2133MHz
SSD: OCZ Vertex 2
Motherboard: MSI Z68A-GD80 G3
Softwares: CPU-Z 1.58, Windows 7 Ultimate 64 Bit with SP1, Latest Atto Software 1.47 I think.
First test, Photofast running on Gen2 (third VC slot). One screenshot from the 9 tests made
Second, using the Gen 3 connectivity. One screenshot from the 9 tests made
Below is the summary of all the tests done on the board with the Photofast SSD PCIE.
That’s probably it. More forum posts to come 

Quote
I have a eSata hdd Seagate Freeagent Xtreme 1,5tb which cannot be recognized by win7
Did you have your previous board's BIOS set to AHCI or IDE ? You need to set this BIOS the same.
Firstly only insert one RAM module in the slot closest to the CPU. Remove the rest. Then do full CMOS clear >>Clear CMOS Guide<< also remove the MB battery.
What BIOS do you currently have ? The initial BIOS releases were plagued by CPU throttling which have been fixed in the cyrrent beta BIOS releases.

PCI-e wireless card causes lock ups Z87 MPower MAX

I've already asked this question once, but was part of an epic essay that I've decided to break down into smaller more manageable chunks (as unsurprisingly that one got no replies).
I've got an ASUS PCE-A66 wireless ac pci-e card. Had absolutely no issues with it in my old Z77 board, but I seem to be having a lot of issues with it in my new Z87 MPower MAX. System was locking up like mad when I was trying to install the drivers at first. Had to rip out the WiFi/Bluetooth/WiDi module to get the drivers installed but the system randomly hangs on boot up? Don't get the issues with the card unplugged and don't always get it with it plugged in, but there seems to be some form of conflict with it that I can't resolve. Has anyone else had any such issues with any PCI-e add in cards on this motherboard?
Specs are:
i7 4770k
MSI MPower MAX using .128 bios (will try the .131 later)
2x4GB Corsair Dominator Platinum 2400
Coolermaster Silent Pro Hybrid 1050w
EVGA NVidia GTX 780 SC ACX
Windows 8 Pro 64bit

Yes, old system was Win8 Pro 64 bit too and the drivers are Windows 8 certified. As I say though, I had no issues with it on the old build? Even got a replacement sent out by Amazon in case the card itself was damaged Did initially try to do a warm update of the hardware into the same OS installation but didn't play well so did a full re-install in the end. Tried standard and UEFI installs (just in case) and after a problem with my OCZ Vector 2 not being recognised I bought a new Samsung 840 Pro so was a virgin SSD installed on to as well.
I'll raise it directly with MSI but just wanted to know if anyone else had experienced anything similar with any wireless cards in this mobo.
Cheers for the reply though

PCI 2.1 SLot on K7T Turbo Limited Edition?

I'm about to get a Firewire Card but I'm not sure whether my MB : K7T Turbo Limited Edition (MS-6330 v3.X) has a PCI 2.1 slot. I haven't found it in manual either. Can anybody help?
Thanks
minurec

Welcome!
My Turbo2 manual doesn't specify either, but specs on MSI site for mine shows 32 bit PCI 2.2, usually backward compatible. Your MB is just one very short edition back, and I bet your slots are probably the same and 2.1 compatible. MSI shows yours as 32 bit, but w/o the #version. To my memory the 2.1 standard predates our MBs by a couple of years or more. I think you're safe to go.

NI-PCI 8431

Similar Messages

Maybe you are looking for