Latest nVidia Driver not working in Win 7 64Bit redux

I have just installed Win 7 64 bit onto a partition on my machine:

After suggestions from Torrentg and BlackRoseMD1 (many thanks again) on this forum I have upgraded my BIOS to version 1801 and attempted to install the nVidia 195.39 beta driver. Unfortunately the result was the same. The install gets to about 40% then both screens go black. After about 30 secs to a minute the secondary monitor shows a garbled desktop after which it to goes black. After a further minute or so the system reboots and checks the disk for errors - continuing, the screens go black just after the win 7 logo disappears.

So I would appreciate any advice as to how to continue:

Thanks

Ianmck

--------------------------------------------
Revised spec:

• MoBo: ASUS P5N32-e SLi Bios Revision 1801
• Processor: Intel E6750 2.66 MHz
• Video Card: nVidia GeForce 8600GT
• Memory: 2 x 2048 Mb DDR2 PC2-5300 (333Mhz)
• Dual Monitors: 1680 x 1050 and 1280 x 1024
My system is dual boot - running Win XP & Win 7 very successfully.
---------------------------------------------

Try booting to safe mode and then install the driver manually from the device manager,

Right click card, update driver software, browse, let me pick, have disk, browse. Find the .inf. If you want an educated guess on which .inf, let us know the ones available when you extract from the installer. Or .rar them then and attach to a post. I can tell that way.

It does sound like something is hardware damaged, though. Most likely card or this wouldn't be necessary at all.

You could definitely try.

Hi

After a very busy week I've found the time to try your solutions and unfortunately they don't fix the problem.

I disconnected my 2nd monitor, extracted the .inf file from the latest Beta driver and installed it manually with the device manager in safe mode.

This time when I restarted I actually got to the desktop - for all of 5 seconds - then the screen went black again.

The only other information I can provide is this: when the machine was bought 2 years ago it came with Vista 32 bit pre-installed. I stopped using Vista because I could never get the 2nd monitor to work properly. I always thought that it was the Vista driver problem that everyone seemed to experience at the time, especially since I had no problem with XP. But perhaps it is a hardware fault.

So my next step will be to swop in a different graphics card and see what happens then because I agree, it shouldn't be this problematic.

Again many thanks for your help: TorrentQ and Dwarf

Regards

Ianmck

Swapping to a different card is a great idea. It will at least eliminate 1 more possibility. Cause it sure is sounding like a hardware issue to me.

ianmck said:

Hi

After a very busy week I've found the time to try your solutions and unfortunately they don't fix the problem.

I disconnected my 2nd monitor, extracted the .inf file from the latest Beta driver and installed it manually with the device manager in safe mode.

This time when I restarted I actually got to the desktop - for all of 5 seconds - then the screen went black again.

The only other information I can provide is this: when the machine was bought 2 years ago it came with Vista 32 bit pre-installed. I stopped using Vista because I could never get the 2nd monitor to work properly. I always thought that it was the Vista driver problem that everyone seemed to experience at the time, especially since I had no problem with XP. But perhaps it is a hardware fault.

So my next step will be to swop in a different graphics card and see what happens then because I agree, it shouldn't be this problematic.

Again many thanks for your help: TorrentQ and Dwarf

Regards

Ianmck

I'm guessing it's a problem with MB and Win7? Why? It probably has to do with the chipset of the MB and win7, Don't ask why but I'm leaning towards it being some driver conflict. The only other possibility is a DX10 issue as WinXP doesn't have DX10... Though it worked in Windows Vista? Try it in a Vista machine, if that works then I'm going to lean even more towards a driver conflict. Or even maybe how Win7 is handling the resources.