• GeForce GTS 450 showing up as 0DC1 instead of GF106
    7 replies, posted
I got a free GTS450 1GB card from my step-dad for my birthday, since he works at nvidia. So I loaded it into my case, and did side-by-side screenshots of GPU-z to compare it to the GTS450 he got me earlier. There are subtle differences, but the main problem is getting drivers to install. I got this screen: [IMG]http://img684.imageshack.us/img684/5978/ypfha.jpg[/IMG] The problem is, the drivers are looking for my GF106, but finding it to be 0DC1, and won't install: [IMG]http://img542.imageshack.us/img542/1955/newgf106.jpg[/IMG] I've looked into the BIOS with NiBiTor (nvidia BIOS editor) and haven't found any values I can change to correct the problem, and I've tried flashing the BIOS from my older GTS450, and the flash was successful, but the GPU ID remains at the problematic 0DC1. Should I just hand it back to my stepdad, and see what he can do back at the lab? Here is my BIOS for the card: [b][url=https://dl.dropbox.com/u/13181909/GF106.rom]Here[/url][/b] in case you want to take a look at it yourselves.
Are you sure it's anything to do with the BIOS? You're technically supposed to remove the drivers before you install a new graphics card, even if its the same one. Have you tried fully removing the previous drivers first?
[QUOTE=djjkxbox360;36134423]Are you sure it's anything to do with the BIOS? You're technically supposed to remove the drivers before you install a new graphics card, even if its the same one. Have you tried fully removing the previous drivers first?[/QUOTE] I emailed my stepdad, and here's what he said: [QUOTE]Hey James, Yep, I think that I know what is going on. That GPU was so new at the time (like one of the first proto-types) that it didn’t have the correct fuses blown in it when it was first made at TSMC. Blowing the fuses is what “Hard Codes” the type of device it is. When we are in development we get what are called “INIT” parts meaning initial parts which means that none of the fuses are blown because we don’t know what fuses need to be blown until software tells us what needs to be read and where. Until that time, all of the drivers we use in development do not read the chip information for configuration, that is left up to us. I’ll go an talk to some of my guys and see if they can give me a driver for this card that is not production and therefore does not care if the fuses are blown or not. If that doesn’t work we just may swap it out for another video card that does. Sorry about the hassle though, we’ll get ‘er fixed up all sweet-like, OK? SRC[/QUOTE]
Yea he totally gave you a dev card.
You can usually force Windows to install a driver by installing the driver through the device manager and pointing to the Nvidia driver folder. It'll tell you the usual "driver may not be compatible with hardware", but it works most of the time.
[QUOTE=bohb;36192478]You can usually force Windows to install a driver by installing the driver through the device manager and pointing to the Nvidia driver folder. It'll tell you the usual "driver may not be compatible with hardware", but it works most of the time.[/QUOTE] That's exactly what I did, and it worked. I just haven't tried using the card for any CUDA encodes or games yet, but I'll probably end up keeping it as long as they work fine without any further troubles.
Just make sure you never sell/give the card to anyone else so they don't bitch how the card doesn't work :v:
[QUOTE=bohb;36267617]Just make sure you never sell/give the card to anyone else so they don't bitch how the card doesn't work :v:[/QUOTE] Yeah, I'm going to keep the messed-up card, and give away the good one to my friend in-need.
Sorry, you need to Log In to post a reply to this thread.