I just finished my first home build last week. Everything went amazingly well--no issues on powerup and the computer has been running fine up until this weekend when I installed my wireless network card (I believe that's when the trouble started). Now when I turn the computer on I get a "PCI Vendor and Device ID Do Not Match!" error. The computer will still boot up just fine but I don't like seeing the error message and am afraid that something behind the scense may not be working that I haven't identified yet.
Any ideas on what may have caused this error or how to troubleshoot it would be GREATLY appreciated!!!!
Thanks for the help . I already did a google search and wasn't able to find anything that helped. I was hoping to get some more specific help on the forum (i.e. common causes of the problem, best ways to debug, etc). Any help would be greatly appreciated. This is my first build and would appreciate any help at all. Thanks!
Thanks for the help . I already did a google search and wasn't able to find anything that helped. I was hoping to get some more specific help on the forum (i.e. common causes of the problem, best ways to debug, etc). Any help would be greatly appreciated. This is my first build and would appreciate any help at all. Thanks!
Running everything at stock speeds, no overclocking.
Anything else I'm missing?
I'll make a WAG...
Netgear may have re-badged another mfg's wifi card. Then in an attempt to make it more 'theirs', they hacked the driver to add themselves as the mfg of the driver.
To check this... Open up a command prompt, do a ipconfig /all. Should show you the mac address of the device. The first three octets (I think, been a year or three since I hacked mac addresses) refer to the manufacturer. A little googling will show you something about all of the above...
Then check the device in your device manager. What your MAC address shows should match what your driver's provider details show.
If my WAG is wrong, then oh well... Two choices. Does the WIFI card work? Yes? Keep it and live with the error msg. No toss it.
A third choice... Error msg is so obnoxious to you, go with choice two above.
If my WAG is right then it MIGHT be possible to hack the .inf.... Or to get the correct driver from the real manufacturer.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.