Could My PCI-E Slot Be Bad?

[PohTayToez]

I have a Foxconn NF4UK8AA-8EKRS Socket 939 NVIDIA nForce4 Ultra ATX AMD Motherboard and a while ago it started resetting itself every now and then, and then finally it wouldn't display video at all. I took out my PCI-E card and put in a PCI graphics card and it has worked fine ever since. I RMA'd my PCI-E card, thinking that it had went bad (I assumed the restarts were it over heating), but I just got it back, put it in, and still nothing. I'll be getting another PCI-E card for another build in a few days, and I could use that to test it out and make sure, but it seems to me that the PCI-E slot or something controlling the PCI-E has went bad... something that I have never heard of happening. Anyway, I'd really hate to RMA my mother board... I don't have a decent computer to fall back on, but it seems as if I may have to.

 

[The_Other_One]

What type of PCI-Express card do you have? I'm almost certain it would require more power than an older PCI card... It could be a failing PSU...

 

[PohTayToez]

GeForce 7300, which I am sure uses more power, but that's what I thought it would be at first, so I unplugged everything except for the motherboard and GPU, and it still wouldn't display anything.

EDIT:
Also, I haven't experienced a single shutdown when using the PCI Card... and it's not that old. It's a GeForce 5500 256MB, and I've burned CDs and watched movies at the same time, which should use a considerable amount of power, but no problems. And the shutdowns I had with the PCI-E seemed to be random... sure, sometimes when I was watching a movie it would happen, but it also happened when I was just browsing the internet... that's why I think it's my motherboard.

 

[Kornowski]

I don't know if you've seen my post about restarting but it sounds very similiar.

Turn off the automatic restart feature so the nest time it does it you'll get a BSOD displaying the file that is causing the problem.

Right Click 'My Computer' > Properties > Advanced >

I can't remember where it is from there but it's around there

Anyway, it's probably an outdated display driver.