Videocards - NVIDIA GeForce Drivers Section In this section you can discuss everything GeForce driver related. GeForce ForceWare and GeForce Exerience drivers are for NVIDIA Quadro and all GeForce based videocards.

May be you can help me to shed some light on my mysterious problem.
Since a while my computer does not recognize my GTX 770 anymore on a regular basis during boot. After several restarts it is recognized as a GTX 660 both in the Device Manager and Nvidia control panel, but then runs stable, and it seems without any lack of performance. In the NVidia it also displays the correct graphics clock rate, etc. only it writes GTX 660 instead of GTX 770.

When did that occur?
Not 100% sure. Either when I installed a razor Nostromo or during some update by the Nvidia Experience software. Of course I am not sure if this is related in any way.

What did I do so far.
1.
Uninstalled the razor Nostromo.
Uninstalled the display driver. Used driver Fusion (safe mode)
Installed the driver 320.49 again. this time only the driver and PhysX
did not help
2.
Same procedure..unistall. driver fusion (safe mode)
Installed the driver 327.23. Only the driver and PhysX
did not help
3.
updated graphics card bios
did not help
4.
Reinstalled win 8
Installed driver 327.23. Only the driver and PhysX
did not help

Also may be note worthy.
In case the Nvidia card is not recognized but a generic VGA I see the whole boot sequenze coming up. Otherwise the screen stays black and I arrive at the Win 8 login screen directly.

Only way to be sure is physically checking the board, this information can be manipulated by BIOS.

Palit GeForce GTX 770 JETSTRE@M (2048MB GDDR5) has a much longer PCB compared to Palit GeForce GTX 660 (2048MB GDDR5), no way that anyone can fake that and mount that 3-fan JetStre@m cooler on Palit GTX 660 PCB with ease.

Maybe one lost Palit GTX 660 soul is haunting your graphic card. Time for egsorcizm... Just joking...

I've seen so much weird things about PC hardware in my career but never something like that, that can't happen without some manual edit of graphic card BIOS or without manual editing of NVidia drivers cfg files.

Like 3dPlayer mentioned before show us some proof for that, I'm geting suspicious...

Ok guys. Let's please not debate if I have a GTX770 or not...one more time It was recognized as GTX770 before and was running stable since may or so. Now I have the hickup during start recognizing it most of the time as generic VGA. Once it is running it is shown as GTX 660.
Any idea how I can solve this?

I say RMA that card to save your nerves, if that card is acting weird after flashing to latest BIOS probably the BIOS chip is faulty. Do a revert to latest BIOS from Palit.biz and send that card to RMA.

Hm...k I will try to get it installed into another computer.
Bios of GTX 770 is updated
Bios of the motherboard is updated. After that win8 run into a problem and I had to restore the whole thing.
Still the same....

After bios update and win8 reinstall it was starting up now without problems but still the GTX 660 was shown.

-Changed power settings to High performance
-Installed Unigine Heaven benchmark to test performance.
-Got message that MSVCP100.dll is missing. So I installed the Microsoft Visual C++ 2010 Redistributable Package (x64).
-Run the benchmark despite the GTX 660 naming, the result was comparable to other GTX 770 setups which I found online.

In the meanwhile windows asked for a system update to be installed and oh wonder the computer started up and recognized my card again as GTX 770. Strangely at the moment that happened my intel 3000 onboard graphics adapter dissapeard from the device manager....

Not this again...
Anyways, why windows always has issues when the BIOS has Intel CPU graphic enable...

PS:It is not onboard, it is onCPU.

Right, CPU
Before the Bios was set to use PCI 16 slot as preferred one. When I installed the Gtx 770 into my existing win 8 system there was no problem whatsoever... And all of a sudden big time failure. Next time they should give a warning: we will update your nicely running system, please expect your computer running unstable afterward.