6153 PCI Dividers

I was wondering what the PCI bus runs at various FSB's
FSB 66 to somewhere under 100:- my guess = 1/2
FSB 100 to somewhere under 133:- my guess = 1/3
FSB 133 and over:- My guess = 1/4
This is my question does this board support the 1/4 divider
It is a 2.1 revision board flashed to the latest Bios
Also could someone tell me the best way to set & confirm these speeds
Thanks in Advance
Ian

6153VA (VIA 693 has 1/4 PCI devider and 1/2 AGP devider for 133MHz), 6153FC (intel 440BX) doesn't have the AGP devider but has the PCI devider.

Similar Messages

MSI!! where is the AGP-PCI Divder

Does anybody know when MSI will fix the AGP-PCI speed in the bios so we can raise the frontbuss without the mobo going bananas.
One thing would be nice is to see the PCI-AGP speed in the bios, so i can see how much the speed is raised when overclocking.
Will they add AGP-PCI dividers like ABIT has done for their socket 754 mobo KV8 MAX 3
MSI K8T NEO FIS2R

I don't think it's going to happen my friends. If you search for some past posts on this issue, you'll see that a PCI/AGP lock is not possible with the K8T800 chipset on any board. Via is known for this kind of thing. If you look at this BIOS revision history for the ABit K8V Max3, there is no mention of any PCI/AGP divider. Anantech did an article in the past about this problem. There is a new ABit board coming out soon based on the K8T880 Pro (or something like that) that may have these dividers, but unfortunately, I really don't think it will not happen on our boards. If you have a link to that article on Anandtech about the Abit dividers, please post it.

Corecenter and benchmarks show FSB as 200?

my stats are below, why does core center show it as 200? i thought it was supposed to be 800 full duplex combining to make 1600, (which would show up as 800) is this normal? is it because the bus is built into the cpu and not mobo?
i have great performance, i benchmarked in 3dmark 2001se with 17406
http://service.futuremark.com/compare?2k1=7550859
there is the link, any help or general knowlege on this would be nice
thanks

Quote
Originally posted by REILLY875
Well then that Board is in the Minority , as Most Boards allow for this feature.....Bummer for the K8T800 ..And regardless, it is a Much Better and Safer Utility to use, Than "Core-Center" .......Sean REILLY875
The fact that this chipset has no AGP/PCI lock is a known issue. When you said that this utility had it, I thought maybe you found something new. The only thing I've seen about a lock so far is a review of an AOpen board where the BIOS adjusted the AGP and PCI dividers to keep them running very close to 66 and 33 MHz respectively.
By the way, messing with clockgen was the first time my computer has locked since I built it in December. I think it was because I was running corecenter at the same time and really messing with all the options in clockgen. I didn't overclock it at all, but I did drop the multiplier down and the fsb down to the point of getting 500 MHz out of it. It crashed hard too. I had to do a warm reboot and got a nasty message from Windows saying it had to recover registry settings. Luckily, everything looks OK so far. The only difference I've noticed is a change in icons next to my Favorites in Internet Explorer.
Clockgen does seem to be a good utility though, I love the fact that it isn't installed at all and just works as an executible. I'll probably try it out when I get up the nerve to void my warranty and overclock. I'm really just hoping for some kind of AGP/PCI lock workaround first.

KT4V PCI/AGP Dividers

Hi,
Can anyone tell me how to change the AGP/PCI divider ratios in the KT4V?

They change automatically with the FSB settings. See stickys above.

Frequency divide by N doesn't work on Counter-Timer PCI-6602

Hello everybody,
I tried to do something basic ( ?) with this Counter-Timer 6602 Board, and it doesn’t work.
So I hope some people with more experience than me could understand what happens here.
1) What I need:
I need to generate 4 synchonised clocks, whose periods will be multiple of 1 ms.
2) What I have:
LabVIEW 7.0 and a PCI-6602 Counter-Timer Board in a DELL PC running under XP pro.
The PCI-6602 Counter-Timer Board has 8 counter timers named CTR 0, CTR 1, ... CTR7.
3) What I have already done, and that worked:
- Generate a 1 kHz “Master Clock” signal from CTR 4, configured by “Continuous Pulse Generator Config.vi” (found in “Data Acquisition, Counters...).
- configure CTR 0 and CTR 1 to work as frequency dividers, by use of “Down Counter or Divider Config.vi”.
- Apply the output signal of CTR 4 (OUT ) to the SOURCE inputs of CTR 0 and CTR 1 by means of physical wiring in the SCB-68 connection box.
When I do this, I get two nice secondary clock signals on my oscilloscope screen, ( with periods = 3 ms, or 5 ms or whatever multiples of 1 ms I choose) from CTR 0 and CTR 1 outputs , very clean and perfectly in phase with the 1 kHz Master Clock.
So far, so good...
But I still need 2 more secondary clocks...
One would say: “No problem, do the same trick with two other counters...” Well, not so simple, it seems...
4) What I tried to do, and that didn’t work:
When I try to do the same frequency division with any of the remaining counters, (CTR2 to CTR7), the program stops and I get an error “ –10020 : Time base not valid “.
I can’t figure out what happens here: I thought any counter could be configured to work as a frequency divider, but it seems not to be so, and I am stuck here.
Has anyone an idea about how to fix this type of problem?
Attached file: hor_div02New.vi
Attachments:
hor_div02New.vi ‏123 KB

karolik,
I'm just adding a followup in English. As Marc L. mentioned, the particular vi named "Down Counter or Divider Config" isn't compatible with the 6602. While the 6602 does have the ability to generate 4 synchronized clocks, a different syntax is needed. Here's how I'd do it:
Traditional NI-DAQ
1. Configure a continuous pulsetrain on CTR 4. Route its output to, say, RTSI 4. Don't start it yet.
2. Configure CTR 0,1,2,3 for continuous pulsetrains using RTSI 4 as their "timebase source." Start them.
3. Start the CTR 4 pulsetrain.
4. Now CTR's 0-3 should generate separate clocks with synchronized phasing.
DAQmx
1. Configure a continuous pulsetrain on CTR 4. Don't start it yet.
2. Configure CTR 0,1,2,3 for continuous pulsetrains using "Ticks" for units. Use a DAQmx property node (probably Channel property node, but am not 100% sure and don't have a LV PC handy to check) to specify that the "ctr4 internal output" should be used as the timebase. Start them.
3. Start the CTR 4 pulsetrain.
4. Now CTR's 0-3 should generate separate clocks with synchronized phasing.
-Kevin P.

MS-6545 pro 5 Dividers

I've got a MS-6545 pro 5 mobo and I don't seem to be able to change the pci (and agp) divider. That seems to me as a bit strange as I do have multiple other options which help to OC the system. I'm using the award bios version 6.00 PG.
Is it just not possible to change the dividers (which makes OC-ing near-impossible) or does it change automaticly at specified FSB speeds? If so, does anyone know what those speeds are?
As a last resort, could I perhaps flash to another bios (like AMI) which might be able to change the dividers?
Anyone? assaf? ?(

Sorry when this is a double post, I didn't see the original post showing up after an hour or so, so I post it again.
Thnx for that info, too bad I get an error I can't explain.
At first, I set the FSB to 133MHz and increased the Vcore to 1,52V. Trying to reboot I got (a bit expected) repeated long beeps, I was fairly sure that meant the memory got an error. It's pc800 Samsung rimm specified up to 411MHz, so 133*4=533MHz was obviously too much.
// Sorry when this is a double post, but I don't see the original post showing up so I post it again//
Then I set the RDRAM Bus Frequency to 300MHz (that would make it 133*3=399MHz, which should be ok for the memory.
Now the strange thing happened, I got a cmos checksum error, loading defaults. When I pressed F1 to continue booting I could normally enter windows using pc600 rimm because the RDRAM setting worked, but the FSB setting didn't. I thought this was strange because it said it had loaded defaults, which it didn't. After rebooting and entering the bios I found that despite the checksum error and loading defaults the FSB was still set to 133MHz and all other options were still as i set them.
But when booting it's all changed except the RDRAM bus frequency??????????
I'm baffled ?(

KT266 PRO2 RU, can it lock AGP/PCI??

There is some way to lock the AGP/PCI bus in this mobo?
Greetings.

nope it just uses dividers like all via boards

Enable SCSI on MS-6153

Hi,
I have a 6310 VIA motherboard with W6153VMS V5.1 Bios,
And the following SCSI cards
PCI Adaptec AVA2904 AIC7856T
PCI Compaq 53C825
What must I do to enable the SCSI cards on my system.
I can install an OS (XP) but if the system is rebooted the bootes failes.
Thanks

Please read the first sentence as
I have a 6153 VIA motherboard with W6153VMS V5.1 Bios,

Kt3 Ultra dividers

Does the KT3 Ultra have 1/5 dividers? I have read on some sites that there are none and on another site they said that the 1/5 dividers kick in at 158mhz fsb. I just want to know if this is true or not.

Quote
Originally posted by spitzaf
so are you saying that the KT3 Ultra DOES support 1/5 dividers? thats something i am really looking into as well. i'm planning a 333 FSB system with some PC2700 and am worried about the dividers. also, are the dividers different for the AGP or PCI slots?
Yes, again. All PCI slots at 152Mhz FSB enjoy 1/5 dividers, for AGP that will be 1/2.5 . That mean only one set of divider for all PCI slots at a time. You can't set 1/4 for PCI-1, and 1/5 for PCI-2.

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.

6153 PCI Dividers

Similar Messages

Maybe you are looking for