solved cannot install nvidia drivers Results

Sponsored Links:

Hi to all! I installed Windows 7 RC and installed nvidia drivers found on the windows update website. Not long ago Nvidia got up with a new driver version 185.85. I downloaded it and tried to install it. When I try to install this driver the screen flickers once and the installation continues. It takes about a minute to colmplete. After a window is displayed telling me that the driver cannot install. I didnt do anything to win 7 only installed windows update driver and then tried to download and install nvidia driver 185.85. I tried to disable automatic driver installation after I uninstalled the windows update display driver but when I restart the system it einstalls again without any warnings, etc. What can I do to solve this problem?

Hi guys!

I can see that it's a more or less common problem, that some nvidia driver won't install when running Windows 7.

Im currently tryin to solve the following problem on my cousins pc:
He want win 7, but when I tried to install it for him, it goes wrong.

What happens is that the install says that it makes the final configurations, and then it skips right to a black screen with a white blinking underscore. It never gets further than that. When restarting, win 7 install can't get done, because of some error.

I looked it up, and it all seems to have something to do with the default microsoft win 7 drivers for the nvidia graphics-card. The one win 7 installs simply don't work, and the entire win 7 installation cannot complete because of this.

They way to replace the drivers is to restart, press f8 to start in safe mode. When it's done, an error appears claiming that safe mode cannot be used. When this prompt appears, I can press SHIFT+F10 to open a command prompt. There I write compmgmt.msc to start the device manager. And there I can replace the driver with some working ones from nvidia.

My problem now is that I have downloaded alot of versions from nividia for the GeForce 9800 GX2 for win 7 64-bit. I run the setupfile, to extract the drivers to a usbdrive. I then access the usb drive to replace the driver, following the method described above. But windows 7 just keep claiming that no proper driver is located in the folder.

So now I have come down to this:
Either the nvidia driver is not uninstalled properly for manual install, when I just double-clicked the downloaded file, and transferred the content to the usb-drive.
OR I havent found the right driver yet.

Any suggestions?

Hi all.

I am trying to connect my notebook - HP Compaq 6730s to my desktop.
I have ASUS Striker 2 Formula motherboard, nVidia 780i SLI chipset, 2 network adapters, and windows XP Pro SP3, x86 Edition.
On my notebook I haveWindows 7 Ultimate RC 7100 Build.
I couldn't find Win7 drivers for my notebook so I installed VISTA drivers in compatiility mode.
Everything works fine, including the network and internet access.
Right now I am trying to connect 'em using a crossover cable. When I pluged in the cable I was expecting windows to detect my network automatically, in the same way it did when I connected VISTA to XP but it didn't.
I tried to configure the network, I used IP address on my desktop and on my notebook and subnet mask.
Windows 7 popped up a message: "Unidentify network - no internet connection".
I created a new Local Network Connection but again, the same message popped up.
Used ping to test the connection - 100% Loss.
Any ideas?



My post concerns a problem with my video card. Let me explain some of the details of the problem and what I have discovered so far. The problems started somewhere around 25th of October and manifested themselves in the form of windows not starting up, but hanging on the starting windows screen. The computer always hung during the animation where the four colored balls merge into the windows logo during startup.

As I did not have a system restore point or anything similar created I made a clean reinstall of windows 7 on my primary OS drive. Wierdly however, the windows 7 install would not finish, but did hang on the "completing installation" -phase, after the first reboot during the installation process. I tried to repeat the installation process, but the installation did always hang up at the same phase.

After many days (!) of trying to solve the problem I stumbled across a forum and found at least at temporary solution. [1] I went and bought a cheap ATI video card and by substituting it for my 9800 GX2 the installation process completed just fine with no problems whatsoever. Thus, it seems that my video card was responsible for the hang ups.

However, I have still not been able to tackle the root cause, which is the 9800 GX2 in a win 7 environment. Today, I tried to look into the problem by first making a system restore point of my current win 7 setup. After making the necessary preparations I switched in the 9800 GX2 instead of my back-up ATI card which has been functioning as a replacement card for the past month.

The first start-up was successful, with no hanging on the animation during startup. However, at first startup with the 9800 GX2 in the system, windows 7 automatically installed its own WDDM 1.1 graphics drivers as well as a pretty new version of NVIDIA's graphics driver (258.??) for the card by using the auto-update function for drivers. Unfortunately, when restarting the system after these installations the computer did again hang at the animation during startup.

Later I did the same process by not allowing windows to auto-fetch any drivers, after using system restore to undo the driver installations. However, windows would not recognize the type of video card and as a result I could not install the NVIDIA drivers. Clearly, I have no use of this outcome. If we go one step further and let windows install only its own WDDM 1.1 drivers the system won't start again, but hang at the same point during startup.

At all instances when the system has hung up during the animation I have still been able to enter windows via safe mode. Interestingly, by disabling one or both of the cards (9800 GX2 consist of two cards) the system will start in normal mode. However, the system cannot utilize the card(s) that are disabled. In case of only disabling one card, the card that is enabled will not function and the device manager gives me error "code 43" for it.

All these symptoms clearly indicate that there is a problem with my video card and the drivers I try to install. Interestingly, I have managed to install windows 7 using the same hardware that I have now in the fall of 2009. Furthermore, I have managed to install windows XP using the exact same hardware.

Due to these factors, I can only think that the problem is associated with the drivers and the video card. However, I have no idea how I could solve it. So far I have, in addition to the aforementioned, tried to install three different versions of the NVIDIA drivers (260.99, 257.21, 195.62). I still have warranty left on my video card, but since I managed to install win XP using the exact same hardware I highly suspect that my video card is broken. However, I cannot really understand why windows 7 did manage to install in the fall of 2009 successfully, since I used the exact same installation CD.

Any suggestions on how proceed or similar cases are highly appreciated! If you have any questions or details I have not yet provided I am happy to do this.

[1] Win 7 64 bit Black screen of death? - Windows 7 Forums

My system specifications can be found in my profile or below:

Operating System: Windows 7 x64 Professional
Processor: Intel E8400
Motherboard: evga Nforce 750i SLI FTW
OS drive: OCZ SSD Vertex 2 120 GB
Video card: Gainward GeForce 9800 GX2

Secondary video card: Asus ATI EAH4350 Silent

Instinctively, you may believe that it is necessary to install drivers for your components, once you have Windows 8 up and running. This may not be the case, however, and historically has not been. If your device, whether it be a PCI card, a USB device, or even something connected to a serial port, was created and placed onto the retail marketplace before Windows 8 was released to manufacturers, and a Windows 8 driver already appears for that device, you may not need to get a "special driver" for Windows 8.

Despite what most people think, the problem with driver compatibility arises after Microsoft Windows already hits store shelves. Companies begin to design products for the latest version of Windows, and the drivers for those products do not exist already in Windows. The reason for this is actually quite simple: Because Windows 8 was finalized when it was released to manufacturers, only the manufacturers of hardware and software peripherals have responsibility over complete driver development after that date.

To give you an idea of what I am talking about, many people who run JBOD, RAID, or SCSI devices for their hard drives have difficulty installing Windows without pre-loading a driver when performing the installation. In almost every case, this is because the storage controller device did not have driver development performed on it that was submitted to Microsoft leading up to the final release of Windows. Since Microsoft cannot include every single driver for every single device in the universe on their DVDs and images, Windows 8 has a set number of drivers and compatibility drivers once it is released. It is then up to the manufacturer to make a difference.

In the case of drivers reaching Windows Update, not only do they need to be developed, quality assurance (QA) tested, and finalized, but they also need to be digitally signed and submitted to Microsoft for testing. Depending on what company has developed the driver and how it is being integrated into Windows, the digital signature of the driver is usually completed by a trusted root certificate authority, either operated on behalf of Microsoft, or known throughout the world as a trusted root CA. An example of a newer trusted root certificate authority would be Google. An example of an older trusted root CA would be VeriSign, or, as it was previously known when it had a monopoly on Internet domain names, Network Solutions. To solve the solution of having insecure root certificate authorities, but not having enough in the world, policies were implementing to allow small companies to chain off of existing large root certificate authorities. This means a company like GeoTrust, which is a large, world renowned root certificate authority, can also allow smaller companies to chain off of their certificate authority servers. If the smaller company becomes unreliable or technically compromised, at any time, GeoTrust can revoke their own certificates or that of the smaller company. Similarly, because Microsoft has direct control of the root certificate authority trusted certs that ship with Microsoft Windows, they can make immediate changes if a security problem arises.

When dealing with driver signing, this all becomes quite convoluted, and potentially confusing for end users. What is important to know is that driver signing is not much different than digitally signing a document using a certificate authority, or providing a SSL (Secure Socket Layer) encryption digital signature for a website domain name. In the case of drivers, the digital signing will assure one certain thing: the driver has not been altered or modified since it was published. This prevents hackers from taking over a web server that is providing drivers and distributing malware-infected drivers.

How does the process of publishing drivers take place once Windows is published? Well, Microsoft itself works with thousands of companies to get drivers placed into Windows for peripheral devices before and after the release of Windows. But, ultimately, if you were to invent a product or service, it would become your responsibility to keep it up to date. Similarly, the manufacturer of hardware or software that requires drivers to operate in Windows needs to make sure that those drivers are secure and will not damage the operating system. In the past, one of the leading causes of system crashes was known as DLL (dynamic link library) hell and the problem of drivers not being adequately tested. Drivers run in the hardware abstraction layer of the kernel and control how Windows communicates with the hardware. Microsoft has created a framework for ensuring that all drivers conform to both quality and security standards whereas:

The drivers will not significantly slow down the operating system or eat up an enormous amount of system resources.

The drivers will not compromise system security.

The drivers will function appropriately, and will be well-defined as to what their function is for what hardware.

To get to the level where we are at today, where unsigned drivers at not permitted to even run in Windows, Microsoft implemented an enormous security overhaul effort with the release of Windows Vista and onward. For that, they should be credited, as well as for including so many functional drivers for old hardware.

But wait, I have a device, and it doesn't work because I don't have the driver

If you have a device that predates Windows 8, and there is no driver for it, apparently anywhere, not even from the manufacturer, this usually means that the manufacturer did not want to spend the time or money to have the driver developed by programmers, quality tested, digitally signed, and/or submitted to Microsoft. There are reasons for this. The development of new drivers could have been considered by the company that you bought your product from as costing too much money. Or, the very same company may want their customers to buy only newer technology. And it is remotely possible that the company simply couldn't make their device work with a newer version of Windows, although this reason is highly suspect.

If you have been following the development of Windows 8, then you have seen the release of many public tests prior to the finalized copy of Windows 8 reaching manufacturers. Even the RTM version, which will not differ at all from the version that hits store shelves, has been sent to manufacturers to make sure that all of their products work on release day. The developer preview, and even the consumer preview, were designed to make it easier for Microsoft not only to track down bugs, but for developers to learn how to write code for Windows 8, including code for drivers. With months, and even years given to companies to get their act together before Windows hits store shelves, it becomes hard to blame Microsoft for a piece of hardware not to have driver compatibility.

For example, the Windows RTM version that was released last month has the near latest drivers from NVIDIA and AMD for graphics cards. It works with almost all of Canon's printers and scanners. Owners of nearly any device from Intel, Logitech, or Samsung need not worry, as the latest drivers are already there. It is no longer necessary, at the time of this post, to download and install any chipset compatibility drivers from Intel. It is evidenced that they have been working directly with Microsoft since around 2009-2010 so that they would not have to release the "Intel INF Update" utility again.

So there you have it, ladies and gentlemen... Windows 8 has a lot of driver compatibility, but there will continue to be drivers that you don't need. This is at least true until Windows 8 gets older. As new products are released that the developers of Windows could have never imagined, it becomes necessary to make sure that you have the latest hardware and software updates.

Before looking for newer drivers, always check Windows Update.
Access Device Manager by hitting the Windows Key + R and type: devmgmt.msc
Or search for Device Manager
For your device, right-click and go to properties and look at the date.

If the hardware or software you are examining had drivers published by Microsoft in Windows 8, you will rarely need to worry about the driver publication date.

However, if the driver you have has been published within the latest 3-6 months, you are usually good to go with this device. The only exception is almost always graphics cards and network adapters.

Look to the manufacturer to see what they are doing about making sure your purchase is compatible with Windows 8. See if they are willing to spend some time (and thus money) to even speak to their customers about driver compatibility.

Thanks for reading.

This problem has plagued my windows 7 installation for a very long time.... i wrote a post on these (and many other forums) before giving up on the issue a few months back and switching to a linux operating system. That's fine, i would keep using linux but i am receiving a new graphics card as a gift and i would like to try to play some pc games on my new card, and as you all know serious gaming on linux is pretty tough/near impossible.

HERE is the link to the post i made a few months back about the same problem. I'll quote it here since it's relevant:

All right so i'm usually pretty good at figuring out any problems with my pc but this ones out of my league, plus i think theres a wide range of things that it could be.

I have a somewhat old hp media center 7580n (pos, bout 3 years old) upgraded it to windows 7.

This problem appeared when i started using this computer to play video games again (only game is WoW though), but at the same time I set up winamp to play my music out of my speakers so that i could use my usb headset for speaking over ventrilo (makes sense). I started getting BSOD's with what seems to be random error messages. These messages go from "IRQL_MORE_OR_LESS_NOT_EQUAL" and "MEMORY_MANAGEMENT" to "BAD_POOL_HEADER" and many more (sometimes there isn't even an error message). These bluescreens almost always happen (i say almost always because it has happened at other times) when i'm running WoW, it seems as if there's a higher chance of it happening if I'm alt-tabbing out of full screen, but I just had it happen when i was running windows mode in a really small window (less strain on the GPU).

My first guess was that it was driver related, so I went ahead and booted into safe mode, and started reinstalling/updating as many drivers as I could think of (of course the first i did was my piece of **** nvidia card driver), but that apparently has had no effect.

My next guess was that it was my RAM sticks, i move around my desktop a decent bit (didn't move it anytime around the time this problem started though) so i thought that maybe my ram sockets had warped a bit or something from all the travel. And maybe a faulty address in memory or something could explain this, so i ran memtest and it came back with no errors. So i switched the RAM sockets of my ram sticks (there's 4 sockets so i took the 2 sticks and put them in the other sockets) all had no effect. I also tried to alternate the sticks (as in run with 1 stick only) but i only ran like that for a day (had no errors) but I got fed up with running on a gig of ram and put the other one back in.

And my last guess was that something was overheating. So i downloaded CPUID hardware monitor and started paying attention to the temperatures of various components. My CPU was up to 70 -75 degrees celsius, and my GPU was up to about the same numbers during times of high stress (aka playing wow on lowest settings possible hell yeah nvidia 7300 le). The CPU temps seemed rather high so I opened it up and took an old toothbrush to the fan and the heatsink underneath it and got it what seemed like my problem. The dust in there was pretty much compacted into a fat solid layer of **** knows what. I got out all that i could, and went ahead and dusted the rest of my computer including my nvidia card (which didn't have that much dust on it). I was almost sure that was the problem. Started running again and i noticed my CPU core temperatures went from 70-75 down to 30-40 ish, and my GPU went down about an average of 10-5 degrees celsius. But apparently that's not it, since i'm still getting bluescreens. I never bothered putting the full case back on the comp i just run it case open to keep it cooler.

So now i give up and come here. I can include some of my dump files (I have about 10 or so in the folder). I have no idea how to analyze those so i didn't even try. Does anyone have ANY idea? I'm starting to get extremely frustrated. Here are my specs, i haven't bought anything new this is all stock:

CPU: AMD Athlon 64 X2 4400+
Motherboard: ASUS A8M2N-LA (HP Name- Nodus-GL8E)
Socket AM2: Micro ATX GeForce 6150 LE
RAM: 2 GB Hynix PC2-4200 (2 X 1 GB)
Storage: Seagate 320 GB 7200RPM Serial ATA
Graphics: Asus Geforce 7300LE 128 MB PCIe
Audio: Realtek ALC 888 High Definition 8 channel compatible
PSU: Bestec 300Watt Single fan
Networking: Wired 10/100 Base T

And yes, i have tried looking at other problems similar to this one but i had no luck there.

Quick edit: Here is a screenie of BlueScreenView I have now reinstalled a nice fresh installation of windows. 100% clean. I have set up some of my applications. just a few minutes ago i got a bluescreen that seemed all too familiar. I was doing nothing intensive, in fact i was listening to music through winamp and writing on an index card when i look up and see a BSOD.

I think the fact that i had no problems running my linux os means that the problem CANNOT be hardware related (can someone confirm?). I think it MUST be a driver. I have only installed a single driver since i re-installed windows 7, the nvidia 258.96 driver for my terrible 7300 LE graphics card, which will soon be upgraded to a 9800 GTX, hence the need to use windows again.

This is an extremely frustating problem.... i have spent so many countless hours trying to resolve it only to find no solution. i would really like to try to game with this card a bit, but if i simply can't find a solution i'm probably going to try to downgrade to windows xp, and then if that doesn't solve it, switch back to ubuntu and try to play my games through wine.

Last time i posted on these forums i got 0 replies (as you can see) so i'd really really appreciate ANY advice or ideas. I plan on disabling the nvidia driver and switching back to the one that came with windows 7 and seeing if the problem is solved, but even if that solves my problem, it may ruin my gaming ambitions, right?

Thanks for reading.

I have attached the 1 dump i have (so far....). Attached Files (28.0 KB, 63 views) Share Share this post on Digg Technorati Twitter
Reply With Quote .postbitlegacy .postfoot .textcontrols a.post_info_button, .postbit .postfoot .textcontrols a.post_info_button { background: url(/images/post_infobox.png) no-repeat transparent left; padding-left: 20px; } .postbitlegacy .postfoot .textcontrols a.post_info_button:hover, .postbit .postfoot .textcontrols a.post_info_button:hover { background: url(/images/post_infobox-hover.png) no-repeat transparent left;   JavaScript must be enabled 07-30-2010 #2 TorrentG Premier Member Enjoys Windows 7 Forums  
Join Date May 2010 Posts 3,913 Re: Confusing BSODs Hey man. Consider your problems over.

Code: WlanGZG WlanGZG.sys Wed Jul 04 22:58:34 2007 Update your USB network driver for your specific device, from Zyxel's website. Let me know if you need further help. Enjoy:

ZyXEL - Country Selector

I installed the Pre-release Driver for my NVIDIA 7600 GT video card, and restarted my computer. It said it had successfully installed, but i cannot seem to be able to display the native resolution of 1440 x 990 for my 19 inch widescreen monitor and on Device manager I get the following message -

This device cannot find enough free resources that it can use. (Code 12)
If you want to use this device, you will need to disable one of the other devices on this system.

Could someone please help me to find a way how to solve this issue.

These are my computer and OS specs,

Windows 7 RC build 7100 (dual booted with) Windows XP proffesional
2gb RAM
256 Mb Nvidia 7600Gt graphics card
Intel pentium D ( i cant remember which model i have, but it is 2.8 GHZ)


These games are running on HP pavilion dv6409wm laptop.
Current list, will update as I install

Age of Conan - works
Battlefield 2 (with expansions) - works
Battlefield 2142 - works
Fable TLC - after several hours of working on getting this game to run I finally did get it working. It was all in my video drivers. if anyone else has trouble running this goto Code: post #10. Message me if ya need any help.
HalfLife - works Compatibility XP
Halflife 2 (with Xpacs)- works
Spore - Never worked for me on vista, barely works on Win7, massively lags (really slow) crashes every few min.
X3 - works when downloaded with steam, but cannot install with disks ( havnt found a solve yet)
Unreal Tournament 2004 (best game ever) - works with few crashes, maybe nvidia related. had same problem on vista.
Starcraft (with Broodwar) - surprisingly the easiest to install and play =-P
WarPath - had a few issues works with compatiblity
World of Warcraft - works great

Well, this is another one of those problems that can be hard to find the cause, let's see if the Lounge can help.

Sometimes when I reboot the PC in question (Start>Turn Off Computer>Restart), it reboots OK, I can see BIOS POST (or in my case an Asus logo), I see Windows load indicator, but instead of Welcome Screen (or Desktop) next is a "scattered display". The screen is a mess of coloured dots, BUT mouse cursor is working (and PC has not hanged). So when I move the cursor around this mess of dots I can find the link in left corner of Welcome Screen to reboot the machine or turn it off.

There is a second version of this; after POST or Windows load indicator a completely black screen. This one is a hang, since Caps Lock on keyboard isn't working, Num Lock light goes out after some shifts. If I wait for some time and at last press the reboot button on PC case, I, after reboot get the Windows "black screen" with options for Safe Mode, Last known good, Normal Mode etc.

In both above cases, and sometimes even when loading OK, during the Windows load indicator screen there is a short "flicker", I don't know how to describe this since English isn't my native language, but most of the time the lower part of the screen (load indicator) gets sliced and jumps, then goes back to looking normal.

After I built this PC 3 months ago I did a test installation and ran it one week. Mostly to test different tools and drivers that came with the new hardware, to know what I later wanted to install. During that period I used the Nvidia driver from vendor on CD, Forceware 84.21 WHQL from March this year. When thinking about it, I can't recall that I did see this behaviour then. At final install I, however, chose the later 91.47.

On this PC there has been very few programs installed. On the other hand I saw case 1 from above on the second day after install during update installation. I don't use MU/WU, in this case patches was/is installed from HD. After installation of 913580 (number 31 of 46 updates that day!) and following reboot, the screen looked like case 1. After some reboot to Safe Mode etc. etc. (this is 3 months ago, can't remember everything) it looked OK in Normal Mode. I thought this was a one time glitch at the time, especially since it was a massive update install and at this point 3-5 reboots following each other.

I cannot see any pattern; some hours before a reboot today, I installed an old non-security patch, 920872, for audio related files. The forced reboot went OK, but a later reboot didn't (case 2). This is an old patch, and there hasn't been any issues related to it in this context. Some have had other problems with it, but not related to this.

What could cause this? Can it be related to graphic drivers? Today I was actually preparing the PC for some new software (WMP11, etc.), but instead have to decide if I'm going to uninstall Forceware 91.47 and go back to 84.21, or even hope it works better with the latest 93.71. But then again, every driver has some non-solved issues. Then also decide if to use some driver cleaner software, or if it's OK to follow Nvidia's advice and just uninstall ... sigh.

Nothing found in Event Viewer.

Any help & comments is appreciated.

Hello all,

I've been having some trouble with error code 109 on my PC. I have a dump file but I'm a noob at this and I don't know how to upload it. The specs are below:
ASUS P8Z68-V LX motherboard
Intel® Core™ i5-2500K Processor (4x 3.30GHz/6MB L3 Cache)
8 GB [4 GB X2] DDR3-1600 corsair ram
NVIDIA GeForce GTX 560 Ti - 2GB - Single Card
120 GB ADATA S510 SSD (for boot)
1 TB HARD DRIVE -- 32M Cache, 7200 RPM, 6.0Gb/s - Dual 1TB Drives (1TB Capacity) - RAID 1 Data Security
Microsoft Windows 7 Home Premium
Realtek Sound card
I literally got this computer up and running two days ago. Everything was running fine until I tried putting games on it. First I started blue-screening during games, then eventually during web browsing, watching movies or idling. I then did a system restore back to before I installed any games and there were no blue screens. I tried installing a different game and the computer blue screened again with the 109 error code.

I've read that this problem could be due to faulty memory, so I ran Windows Memory Diagnostic with no errors. I am hesitant to run memtest because I really doubt it is a memory issue, since I bought this computer from ibuypower and they test these sorts of things before shipping it out.

My first guess is that this is a registry problem or a compatibility issue with Win 7 64-bit and these games (Bioshock 2 and Fallout 3) but I'm not certain. I've also read about issues with Realtek audio drivers and DirectX. I've seen others have problems with their HDD in RAID. I've just run a registry cleaner and hope this will solve some problems, but it is too early to tell yet.

Does anyone have any ideas? Also, how do I upload a .dmp file so it is readable (I currently cannot read it)?

Hello! Just joined the community and I thank everyone in advance for any help with this matter.

First let me give a little background of where I am today that might help diagnose this issue.

Brand new computer, upon installing Windows 7 could not boot into windows due to missing file errors. The HDD I am trying to install onto is a SSD, I will provide system specs at the end of the post. Anyway I unplugged my secondary SATA hard drive and then I was able to install Windows 7 and boot into windows.

Now after all my drivers have been installed I am recieving error messages when logging into Windows. I ran SFC.exe and the log output gave me hundreds of lines saying Cannot repair member file. Here is an example:

2012-09-27 20:28:38, Info CSI 00000116 [SR] Cannot repair member file [l:24{12}]"fpcmbase.sys" of avmx64c.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-09-27 20:28:38, Info CSI 00000118 [SR] Cannot repair member file [l:24{12}]"fpcmbase.sys" of avmx64c.inf, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate", TypeName neutral, PublicKey neutral in the store, hash mismatch
2012-09-27 20:32:26, Info CSI 0000138d [SR] Cannot repair member file [l:14{7}]"wet.dll" of Microsoft-Windows-MigrationWizardApplication, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

Anyone have any ideas on how to solve this problem? I have tried re-formatting again only to have the same issue. Maybe it has something to do with me trying to install onto the SSD drive? I have not yet tried installing windows onto just the SATA HDD I have and disconnecting my SSD.

System Specs:
Intel Core i7 3930k Processor
32GB [4GB x8] DDR3-1600 G.Skill Ripjaws X
NVIDIA GeForce GTX 670 - 2GB - EVGA Superclocked - Core: 1046MHz
240 GB Corsair Force Series GT SSD
2TB Hard Drive 7200rpm

Thank you!!!

Here is a list of Network Connection Fixes I have read about.

(Ignore the html coed)

1. Click "Start" and type "Fix Net" and press enter to let windows try to diagnose and repair problems.
2. Verify network drivers are up to date for your adapter... (upgrading may
use old Vista drivers that are not compatible with 7) Click Start and type
"Device Manager" and look for any driver errors.. usually a yellow triangle.
3. Click Start and type and enter "ev" and it will run the Event Viewer. Look
under Custom at the Administrative logs. Problems with initializing drivers are
logged here at startup.
4.Click Start and type "perfmon /report" and press enter... it takes 60 seconds
to gather a comprehensive diagnostic report and then it presents resolutions.
5. Disable NORTON and all AV programs and Firewalls. Norton 360 is NOT
compatible with Win 7.
6. Reset the router and test
7. Bypass the router, connect directly to modem and test - not exactly a fix but narrows the problem.
8. Go into your device manager. (Control Panel --> Device Manager) and open up the
drop down list under Network Adapters. Find your network controller(s), right
click it (them) and uninstall. After uninstall is complete, click any other
device in your Network Adapters and choose "Scan for Hardware Changes". Windows
should automatically detect and reinstall your network controllers.
9. Go to Task Manager /services /services
and Disabled the "Function Discovery Resource Publication" service
Note: Windows 7's new "HomeGroup" connectivity requires this service.
10. Remove the Bonjour service if you have Apple/iTunes
- Click Start and enter and run this command: "C:Program FilesBonjourmDNSResponder.exe" -remove
- Navigate to the following folder in Windows Explorer. "C:Program FilesBonjour"
and Rename the mdnsNSP.dll file in that folder to mdnsNSP.old
- Restart your computer and DElETE the "Program FilesBonjour" folder

11. Fix for NVIDIA USB Enhanced Host Controller Interface (EHCI) chipset BUG

12. Cannot get IP address

13. Unidentified Network
Go to the NIC properties and uncheck these things:
-Internet Protocol Version 6 (TCP/IPv6)
-Link Layer Topology Discovery Mapper I/O Driver
-Link Layer Topology Discovery Responder
14.Make sure that all wires are connected (for example, make sure your modem is
connected to a working phone jack or cable connection, either directly or
through a router).
15.If you're trying to connect to another computer, make sure that computer is on
and that you have enabled file and printer sharing on your network. For more
information, see Networking home computers running different versions of
16.If your computer has a wireless network adapter, Windows will automatically
detect wireless networks that are nearby. To see a list of wireless networks
that Windows has detected, click the Start button , and type "Conn" then click
Connect to netwok. If Windows does not detect a network that you think is in
range of your computer, open Help and Support and search for "Troubleshoot
problems finding wireless networks."
17. Still not working? Did you do a clean/custom install?
Upgrading frequently fails for too many reasons to list.
18. If these steps don't solve the problem, look for a specific problem in the following list.