Our new Indie Games subforum is now open for business in G&T. Go and check it out, you might land a code for a free game. If you're developing an indie game and want to post about it, follow these directions. If you don't, he'll break your legs! Hahaha! Seriously though.
Our rules have been updated and given their own forum. Go and look at them! They are nice, and there may be new ones that you didn't know about! Hooray for rules! Hooray for The System! Hooray for Conforming!
Okay, I don't know if this needs a new thread or not, but I'm worried. I just got in all the parts for my new PC yesterday (Antec Sonata III case, 3 ghz Core 2 Duo E7500, 4 GB of RAM, an Asus P5QL motherboard, and the aforementioned GeForce GTX 260) and put them together. I had no other OS, so I used a Win7 RC1 (build 7100 if it matters) disc I had for a while and got everything set up.
Installing Windows was a breeze, and setup and all went A-OK. Got connected to my home's wireless network and so on, and things were fine. However, after about 30 minutes of doing little things like getting Firefox downloaded and starting to download some driver updates and in general getting used to Win7's UI, I got a BSOD, with an nvlddmkm.sys error. The PC auto-rebooted, POSTed fine, and proceeded to the Windows loading screen. I got the nvlddmkm.sys error again, and it repeated the cycle. I booted into safe mode, and I could do everything in that. I looked around and began to discover that it seems to be a video card driver thing, so I finished getting the latest drivers and installed them. I rebooted and no longer got the error, but the trouble got worse.
My display locked to 640x480, and nothing could get it out of it. There are what I can only assume are artifacts everywhere (it looks like when you get locked into an 8-bit color display), even during POST and in the BIOS setup. I've cleaned out the old drivers, installed older drivers, the newest drivers again, and anything I can think of. I've reseated the video card, and I'm at a total loss here. I have no idea what could be going on, but I'm very worried.
Edit: Going into Device Manager, the 260 has a warning symbol on it, and going into it produces the following: "Windows has stopped this device because it has reported problems (Code 43)".