How do I identify what is my 'Intel Chipset' , on a Windows 7 Home Premium 64bit system?
This is actually a follow-up question to
The specs for my computer are: HP Pavilion dv7-6b32us Laptop Core i7 2670QM 2.20GHz, 4GB DDR3, 640GB HDD ,Win 7 Prem.
As suggested at the previous Superuser question-and-answer, I tried going to the Intel website via this link. (click to see)
There are 4 downloads being offered by the website, but how do I determine which of these 4 offered downloads is the appropriate one for me to download?
More to the point... how do I identify what is my 'Intel Chipset'?
I did find something called 'Intel Chipset Identification Utility' via
https://downloadcenter.intel.com/download/18498/Intel-Chipset-Identification-Utility
, but, it's stated as being only compatible with 32-bit operating systems. I am on Windows7-home-premium-64bit.
Many thanks for any help that can be offered in helping me identify what is my 'Intel Chipset'.
Status Report#1
Sigh... well, a slight update on the situation, and this corresponds to the preceding thread located here, too.
None of the ideas so far worked, despite spending HOURS trying to get the USB3.0 ports to actually operate at USB3.0 speeds.
I mention this as a warning to others that might be having a similar issue-- solving the problem could potentially eat up a LOT of time.
Status Report#2
Well, I haven't thrown in the towel altogether, but...
Pursuant to the answer provided by @Chris-C in this thread, USB 3.0 ports function as USB 2.0 ports on Windows 7 -- trying to fix via DeviceMgr & downloads from Intel website , I've discovered something terribly distressing.
Specifically, I was told:
NO USB 3.0 support on the Intel 6-series chipset
And, yes. I found out that my system uses a Generation-6 chipset.
Hopefully, people that have this similar issue can be made aware of this limitation by this post.
But... why did Hewlett Packard include USB3.0 ports (I know they're USB3.0 because they have a blue color to their interior) IN THE FIRST PLACE?? Seriously, if you can give me an answer (in a comment), please do!
As far as the underlying concerns go, I'm still not quite giving up. At least not yet.