NI PCIE-8360

NI PCIE-8360 board (PCI Express) works fine in ASUS P5GDC and HP Proliant DL320 server. But when the board are inserted in a ASUS P5LD2-Deluxe (i945) BIOS 0506 or ASUS P5WD2-Premium (i955) BIOS 0606, then the system stops / hang during Power On Self Test (POST). Boths motherboard BIOS are updated to last version. The motherboards runs with an PentiumD processor, but Pentium4 HT, EM64T processor has been tested with same negative result.
Have somebody good experiences using Intel 945 or 955 chipsets.
I have tried allmost everything - even the EEPROM update from ni.com
At the moment my system won´t boot - have somebody some good advices?
Best regards,
Michael Rasmussen

If you have another available PCIe slot (preferably further from PCIe graphic card), try it to see your PC will pass POST.

Similar Messages

Issue with PC not booting when PCIe 8360 attached to controller PXI 8360

I am using a PCIe 8360 in our Windows 7 PC and connecting it to a PXI 8360 controller in a Pickering chassis. When I connect the mxi card to the controller and try starting the PC, the PC will not boot. Has anyone seen this issue and if so, what is the problem/solution?

It sounds like this may be an issue with BIOS compatibility. I have included some more information below. I would recommend upgrading the BIOS to the latest version and seeing if that resolves the issue.
http://pcsupport.about.com/od/fixtheproblem/ht/accessbios.htm
R. Brill
Applications Engineer
National Instruments

Pushing the limits of continuous high-speed DAQ + processing, with PXI-6115 + PXI-8360

Hi all,
I'm trying to do continuous high-speed data acquisition + processing. I currently have:
Chassis: PXI-1042Q
AI card: PXI-6115 (x2)
Link: PXI-8360
PC CPU: Intel Xeon W3503 (dual-core, 2.40 GHz)
RAM: 4 GB
The idea is to continuously grab 8 channels' worth of analog inputs, scan for "events", and if found, log the events to disk.
My client would like to use the maximum sample rate of 10 MHz, but I found that above 5 MHz, DAQmx Read.vi can no longer keep up (e.g. at 6 MHz, it takes 110 ms to read 100 ms' worth of data).
Im thinking of getting beefier components, but I'm not sure where the bottleneck is. Here are some thoughts:
1) The MXI Express link
The PXI-8360 is rated for a sustained throughput of 100 MB/s.
I'm not sure how big the data is. PXI-6115's ADC is 12-bit. Does that mean each datum transferred through the MXI cable is 1.5 bytes? Is the data padded? Or is it 8 bytes per datum, because Dbls are being transferred?
2) The CPU
In Resource Monitor, I notice that the CPU usage is 0% at 60 kHz, 8% at 61 kHz, and 50% at 70 kHz (meaning that one core is maxed out). I'm surprised that it keeps up all the way until 5 MHz though.
What causes this high CPU usage? Is it due to the conversion of the data into 1D array of waveforms?
3) Something else?
Have I missed something completely? Is what I'm describing even possible?
Thanks in advance for any advice!

Hello,
Each sample will take up 2 bytes, 12 bits data + 4 empty bits. so the PXI-PCI 8360 is only able to transfer a maximum of 50S/s in this case.
Also, because the PXI bus is shared among all of the cards, two PXI 6115 cards will be trying to transfer 80MS/s or 160MB/s.
Finally, since the PXI 6115 are DAQ family cards, their specifications aren't really written for continuous data acquisition at the upper end of their sample rate, but I'm interested to know if you can get up to 10MS/s with only one card operating at a time?
-Jim B
Applications Engineer, National Instruments
CLD, CTD

NI PXIe-ExpressCard8360

When I power up my pc with the cable MXI connected between the computer's PCIe-8360 and the PXIe-8360 (with PXI chassis already booted) the PC hangs. I have never used this PC before, so I am wondering about BIOS settings that could be preventing it from working? What other troubleshooting steps can I take?
Thanks

Do you have PXI platform services installed? http://joule.ni.com/nidu/cds/view/p/id/4186/lang/en
www.movimed.com - Custom Imaging Solutions

NI ExpressCard-8360 - Adaptor card to low-profile PCIe slot

Hello,
we share PXI chassis in our office between desktop PCs by using of NI Express Card 8360 + Delock PCI Express card to Express Card 34 mm
+
BUT our Dell Desktop PCs have low-profile PCI Express slots. So Delock card doesn't fit properly and its front plate has to be twisted to be able to plug in.
Also it's impossible to screw it so loosing of connection and crashes are noted sometimes.
So my question is: Is there some LOW-PROFILE Adapter in the market?
I mean upper of these two...

Oh and while I was at NewEgg I intend to try
StarTech ECBRACKET2 Stabilizer Adapter
http://www.newegg.com/Product/Product.aspx?Item=N82E16839158051
Its a bit of plastic that clips on the bracket to stop the express card being wobbled / bumped in the adaptor. (I have lost the connection in my laptop before because I bumped the cable.)
Nick

Suitable Laptop for NI ExpressCard 8360

Hello,
I'm looking for an Industrial Laptop, which supports NI ExpressCard 8360 with NI PXI Chassis(8 & 18 slots). we have tried with couple of laptops(HP ProBook & Dell XPS), which has the follwing issues:
1. Booting (This could be fixed by changing the booting order)
2. Digitizer module freezes (when the number of samples are above 60000)
3. Unable to detect all the available PXI modules
Please suggest me a right model.
Thanks in advance...
Solved!
Go to Solution.

Hi,
We don’t have a listed of supported laptops but we do have some resources that can help you.
Tips to Help You Successfully Use NI MXI-Express Controllers
MXI-Express Setup and Compatibility Guide
To address your issues:
1. Booting (This could be fixed by changing the booting order)
What is the problem you have with booting? Will the laptop not boot when your NI ExpressCard 8360 is connected? There is some information regarding this on page 1-3 of the MXI-Express x1 Series User Manual.
“The BIOS of some host machines may not support the extension of the PCI-Express fabric or PCI bus. Since this is the primary function of MXI-Express x1 products, those systems may not boot or function correctly. To address this issue, certain MXI-Express x1 products have additional functionality intended to hide all PCI or PCI-Express resources that are connected to the host machine, and allow NI MXI-Express BIOS Compatibility Software to handle the enumeration process of these resources instead of the BIOS.
In the cases where this software is required, there may be a dip switch on the board that needs to be toggled as instructed by the documentation for the software. The functional block diagrams in this chapter illustrate the locations and availability of the dip switch package. Only the first dip switch in the package is used for this purpose. The other switches serve no function and should be left in their default position.”
After knowing this, I would install NI MXI-Express BIOS Compatibility Software found here.
2. Digitizer module freezes (when the number of samples are above 60000)
Do you have any other systems to try the same card in?
3. Unable to detect all the available PXI modules.
A low maximum limit on the bus number range set by the BIOS, which limits the amount of hardware that can be attached to the system could have something to do with this. Try this: Determining the Number and Range of PCI/PCI Express Root Bus Devices
Hope this helps.
Lewis Gear CLD
Check out my LabVIEW UAV

Pxi 8360 power led flashes red

I have a PXI 8360 MXI Express board mounted in a PXI 1050 chassis. I am seeing the power LED occasionally flash red and I lose communication with the computer. The power LED will return to solid green status after a few minutes but I am not able to do much with NI DAQ to test the system since it has failed self test. The suspicion here is the power supply may be bad but how do we check that.
The system with the computer has worked well over the past several years and we are concerned about possible damage from a power fluctuation that happened here around Christmas time.

Hi Xavier,
The red flashing light is on the PXI 8360. I have not seen any flashing lights on the chassis.
The modules present in the system are
PXI 8360 MXI Express
PXI 4071 7 1/2 digit flex DMM
PXI 4110 Programmable DC power supply
PXI 4110
PXI 4110
PXI 8252 1394 Host Adapter
TB 2627 multiplexer terminal block
PXI 6289 M series multifunction DAQ
SCXI 1306
SCXI 1303
SCXI 1303
SCXI 1300
So far all testing has been done with all modules installed. Another person has tried reseating all modules to see if that would fix the problem but it does not.
The system will work fine for a few hours and then the blinking LED will begin and somewhere near that time the communications fail with the computer. The light will blink for a few minutes and then will return to solid green. Once the error has occurred it seems that the only way to re establish proper operation is to shut down the whole system, PXI chassis and computer, and restart. I saw one time where the power LED on the 8360 went from flashing red to solid green when the computer was turned off.
The computer is a Dell Precision 690 with PCIe 8361.
I will be opening up the chassis hopefully in the next day or two to check fuses and voltages where I can.
Bill

NI PCIe-8362

We installed an NI PCIe-8362 into a Super c2sbc-q motherboard in the X4 pcie slot. The MXI4 8362 connected to two NI PXI-8360. The machine booted correctly for several days. After that we found the PC would not boot (hangs in BIOS). We removed the 8362 and the machine still doesn't boot but hangs in the BIOS. The same symptoms occurred after moving the 8362 to another Super c2sbc-q motherboard. The motherboard/8362 combination seems to ruin the motherboard.
We had the same symptoms over a year ago but then the symptoms occured when we installed the 8362 into the video x16 PXIe slot. That "ruined" the motherboard but we determined by using a new Super C2sbc-q and installing the 8362 in the PCIe X4 slot the machine booted and all PXI I/O boards booted worked correctly. In fact several machines in that configuration have been in constant use for over a year. That configuration : Super c2sbc-q and xPCIe 8362 in the X4 slot works for machines configured over a year ago, but is failing with recently purchased boards of the same type.
Do you have any experience or insight into how we could be ruining motherboards with the NI PCIe 8362/Super c2sbc-q motherboard combination? Again this combination works well based on hardware from over a year ago. We can't understand why now we are seeing those symptoms - the motherboard becomes useless.

Hi brokebelt,
Is the PCIe slot on the motherboard intended to be used with a graphics or video card? The user manual for the PCIe-8362 states on page 3-2 that "The BIOS or motherboard may not support the NI PCIe-8361/8362 in a slot
intended for a graphics card." I believe this is probably what was happening when you mentioned trying to use this card in a video x16 slot of a different motherboard. If this card worked on an older version of the motherboard you are trying to use, it is possible that there has been a revision to either the motherboard or BIOS that makes it so it doesn't support anything other than a graphics card in that slot.
I would recommend checking the user manual for the motherboard or check with the manufacturer to see if this slot is intended for a graphics card or not. Hopefully this is helpful! I'm going to attach a link to the PCIe-8362 user manual below.
MXI-Express x1 Series User Manual
http://forums.ni.com/t5/forums/replypage/board-id/270/message-id/12053
Josh B
Applications Engineer
National Instruments

Pxi 1033 with expresscard 8360

Hello,
I have a PXI 1033 Chassis with ExpressCard 8360. I connect it to laptop using ExpressCard.
I want to connect it to PC desktop. Would you please tell me how can I connect. What kind of board i need to connect ExpressCard to PC desktop.
Best regards

There are 2 options for using your PXI 1033 with a desktop. You can buy an NI PCIe-8361 to go in your desktop, then switch the cable between your desktop (with the NI PCIe-8361) and your laptop (with the ExpressCard-8360). Or you can buy an ExpressCard adapter for your computer.
If you go the adapter route, you need to get one that plugs into a PCIe slot. ExpressCard supports 2 interfaces: PCIe and USB. On a "real" ExpressCard slot, both interfaces are available on the connector. Some adapters plug into USB and only provide the USB interface, which works fine for ExpressCards that use the USB interface. Some adapters plug into a PCIe slot and have a cable that plugs into a USB header on the motherboard, so it can support both interfaces (PCIe and USB).
The ExpressCard-8360 uses PCIe, so any adapter that connects via USB simply won't work. Also note that the card retention isn't very good, and the slot won't support hot-plug like a native ExpressCard port.
- Robert

PXI-4070 with PXIe-1062Q+NIe-8360+Labtop Why? Max not found instrument.

Dear all
my condition
PXI-4070 with PXIe-1062Q+NIe-8360+Labtop
Window XP SP3
NI-DMM 3.1
Why? Max not found instrument.
found PCI Device "PXI10:15::INSTR
see picture
How to fix this problem?
Best Regard,
Sermsak.
Attachments:
PXI-4070.jpg ‏42 KB

Hello,
Is it possible to take another picture of MAX? That one is very pixilated and I can't quite make out the configuration/error. Does the chassis show up? Every now and then MXI compatibility software is needed for certain BIOS versions so this may be the cause. Did the system work ever before?
Thanks,
Eric E.

Lenovo t420 ExpressCard 8360 troubleshooting help needed

Hi all,
I need help with getting MAX to recognize my 1033 chassis and the associated cards. When I powered it up last time MAX recognized the DMM and the Freq Source but hung badly (hard reset of PC) when trying to use NI-Scope. Now I can't even get the chassis to show up in MAX. Please help me
I have a NI ExpressCard 8360, a Lenovo T420, and a 1033 chassis w/ 5122,4070, and 5404 in slots 3,4, and 2. I'm running LV 2012 f5
Description: The two green lights on the 1033 are lit. The chassis was turned on for one minute before turning on the PC. MAX was started. The only things showing up in Devices are the simulated devices if configured. No 1033...
My software configuration is LV 2012 Service Pack 1 V12.0.1f5 (32 bit)
When I look at Device Manager in Windows unders System I see "PCI bus" but nothing like PCI bridge to bridge. Not sure if I should or not...
Any pointers would be helpful.
Thanks,
JD360

Hi JD360,
As long as the Express card is working properly and you do not have MXI Compatibility Software installed, there should be a PCI-PCI Bridge in device manager. Sometimes this has a yellow bang next to it if it has not been recognized properly, but it should be there. Can you verify you don't have the compatibility software and double check the device manager to see if there is a PCI-PCI bridge?
Some more general quick questions to help troubleshoot:
1) What OS do you have?
2) What DAQmx version do you have?
3) In Windows Services, is PXI Platform Services started and running?
4) In Windows Services, is NI Device Loader started and running?
I hope this helps,
Eric E.

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

Poor PXI IO performance on Latitude E6410 with ExpressCard 8360

Hello,
I have a Dell Latitude E6410 with a Core-i5 M520 which is giving me very poor io performance when using an ExpressCard 8360 card to connect to a PXI Rack.
The sustained IO rate that I can get appears to be about 1/3 of that that I can get using the same ExpressCard on a Dell Latitude E6400 (with a Core2Duo processor).
I am using the A05 bios (latest at time of writing) on the E6410.
Wade.

I am running Windows XP (32 bit) sp3 in both cases.
The E6410 has 4GByte of memory fitted.
The E6400 has 2GByte of memory fitted.
I have also use the same ExpressCard 8360 via a PXIe to ExpressCard Adaptor in a Desktop machine with similar performance figures to the E6400 - i.e. much better than the E6410.
The Desktop Machine is an HP Compaq D7900 with 4GByte of memory, Core2Duo E8500 also running Windows XP sp3 (32 bit).
Also, on the Desktop, I am running NI PXI Platform Services 2.3.2 and NI-Visa runtime version 4.3.
On the E6410, I am running NI PXI Platform Services 2.5.2 and NI-Visa runtime version 4.6.
I no longer have access to the E6400 so I am not sure what sofware versions were installed. However, they are unlikely to be new than the versions installed on the E6410.
Wade.

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.

NI PCIE-8360

Similar Messages

Maybe you are looking for