Help with PCI-E type?

[Flaky]

Or that the chipset driver is there to set pretty names in Device Manager is false too. That, and the way it was presented is what really got my attention here.

I referenced to this particular problem and this particular motherboard. And here this so-called chipset driver does exactly what I said. If in doubt, check for yourself contents of that package
Drivers for other devices, which are either part of chipset, or are connected to chipset are in separate packages.

So before criticizing a long standing and respected member of this site, I would suggest you do your homework first to get your terminology down and facts straight - or you risk looking to be the "flaky" one.

I don't see anything wrong in criticing anyone, as long as the discussion is open, stays on point, and does not escalate. I don't criticize anyone unless I'm more or less certain about something, based either on experience or research. And when someone proves me wrong, I'm happy to learn something new.

I didn't write anything offensive. If anything came up otherwise (as English is not my mother tounge, and I can't really catch all the subtle nuances), please let me know, preferably using PM. Thank you

 

[jboydgolfer]

That damn Z 68 chips it caused issues with a lot of newer video cards. I had issues from both AMD and Nvidia on my z68 extreme 3.

 

[Sasqui]

Went though looking to see if the OP had responded... nothing on TPU since the original post on Sunday.

 

[Bill_Bright]

Went though looking to see if the OP had responded... nothing on TPU since the original post on Sunday.

Good point. And with that being the OPs one and only post on TPU, he or she may not be back.

 

[Fourstaff]

Cleaned. Stay on topic please.

 

[eidairaman1]

Someone forgot to install their chipset driver and the card would not tell the mobo to increase the bandwidth, once the intel chipset driver was installed, it fixed the issue. So it does have alot to do with the bus mastering not increasing the bandwidth.

When working correctly the bus varies speed, it will climb to max supported and then drop down to conserve power.

1 last note i doubt after burner is being used but i recalled an advanced setting caused the bus mastering to not work either, once disabled it worked correctly again

You fail to understand what a driver truly does. I feel sorry for you.

By the way read this here.

https://downloadcenter.intel.com/do...es-Chipset-Based-Desktop-Boards?product=70398

https://www.asus.com/us/supportonly/P8Z68-V/HelpDesk_Download/

If he was using W10 he would be pretty much screwed at this point as intel stopped support and built in Windows drivers provide basic functions just to make it run but provide no enhancements, aka generic driver.

Another thing that can be atrempted id the PCI Express Link power state in power properties/management should be set for High/Max/Best Performance.

He's right about the PCIe bus.

But to assume the chipset is just the PCIe bus is false.

Yes, this goes back to a different discussion we've had about network controllers which work with basic industry standard protocols and drivers. And while network controller drivers may be bundled with chipset drivers, they are not the same either.
Or that the chipset driver is there to set pretty names in Device Manager is false too. That, and the way it was presented is what really got my attention here.

*sighs*

Bill, yes, ethernet is a standard protocol. Ethernet controllers do not share a common driver and I really can't help you if you want to dredge that one up again.

The PCIe bus always will use PCI.sys, supplied by microsoft. That's different than network drivers, which are specific to the chipset in question, bundled or not.

That damn Z 68 chips it caused issues with a lot of newer video cards. I had issues from both AMD and Nvidia on my z68 extreme 3.

Went though looking to see if the OP had responded... nothing on TPU since the original post on Sunday.

Good point. And with that being the OPs one and only post on TPU, he or she may not be back.

Here's another thread, fixed issue with proper sequence of chipset drivers then gpu driver installed.

https://www.techpowerup.com/forums/threads/rx480-uefi-gop-driver.241480/#post-3799967

 

[Flaky]

Here's another thread, fixed issue with proper sequence of chipset drivers then gpu driver installed.

https://www.techpowerup.com/forums/threads/rx480-uefi-gop-driver.241480/#post-3799967

Drivers fixed what?
Did you read the OP's response?

Performing the "put it in another computer test" fixed it.

Reseating && reworking the water-cooling was the key.

 

[eidairaman1]

Drivers fixed what?
Did you read the OP's response?

Please follow the sequence of events correctly.

https://www.techpowerup.com/forums/threads/rx480-uefi-gop-driver.241480/#post-3800170

 

[Flaky]

Well, you asked what drivers the OP has currently installed, and he did respond.
He had a problem with incorrect lane count negotiated, and said "Reseating && reworking the water-cooling was the key". I see no "drivers" here.
I am really confused what you are trying to prove here.

 

[eidairaman1]

Well, you asked what drivers the OP has currently installed, and he did respond.
He had a problem with incorrect lane count negotiated, and said "Reseating && reworking the water-cooling was the key". I see no "drivers" here.
I am really confused what you are trying to prove here.

It was a combination of things as he went with different drivers, he removed and reinstalled them in correct sequence.

Most issues like this result from dust, improper seating, not installing chipset then gpu drivers.

Unless if the card has been physically damaged.

 

[Flaky]

It was a combination of things as he went with different drivers, he removed and reinstalled them in correct sequence.

Most issues like this result from dust, improper seating, not installing chipset then gpu drivers.

Unless if the card has been physically damaged.

So... What are you trying to prove here exactly?

 

[eidairaman1]

So... What are you trying to prove here exactly?

Nvmd you don't get it, figure it out.

Best of luck to you

 

[dorsetknob]

So... What are you trying to prove here exactly?

OP Indicates Problem is Sorted why are you trying to Troll response from some People

Just Drop it Please

 

[Flaky]

My claim in this thread was that drivers have no impact on negotiated PCIe lane count, so installing/reinstalling chipset/gpu drivers does nothing in such problems. eidairaman1 disagrees with that.

Month after the discussion ceased eidairaman1 chimes in, and links to a thread, stating that drivers did help there, even though OP explicitly said what did help. OP there mentioned reseating the card, not drivers. Two different things.

If those drivers are so critical for proper lane count, then finding a platform where drivers solve the problem in a reproducible way should be easy, don't you think?

 

[eidairaman1]

My claim in this thread was that drivers have no impact on negotiated PCIe lane count, so installing/reinstalling chipset/gpu drivers does nothing in such problems. eidairaman1 disagrees with that.

Month after the discussion ceased eidairaman1 chimes in, and links to a thread, stating that drivers did help there, even though OP explicitly said what did help. OP there mentioned reseating the card, not drivers. Two different things.

If those drivers are so critical for proper lane count, then finding a platform where drivers solve the problem in a reproducible way should be easy, don't you think?

He did mention he put the drivers in, in proper sequence even.