g-a-m-e
04-15-06, 09:18 AM
It's not the 'dreaded nforce3 bug' since this motherboard has a SIS chipset (or something)
We've tried reinstalling chipset drivers, reinstalling nforce driver but it doesnt seem to do the trick.
Anyone else had this problem, or know what to do to fix it ?
We are now goint to delete the nforce driver again (properly with driver cleaner this time instead of windows crap de-installation), then re-install the motherboards AGP driver again, and then reinstalling the newest nforce driver again, but i have a feeling that won't do the trick...
So any other suggestions are more then welcome ...
We've tried reinstalling chipset drivers, reinstalling nforce driver but it doesnt seem to do the trick.
Anyone else had this problem, or know what to do to fix it ?
We are now goint to delete the nforce driver again (properly with driver cleaner this time instead of windows crap de-installation), then re-install the motherboards AGP driver again, and then reinstalling the newest nforce driver again, but i have a feeling that won't do the trick...
So any other suggestions are more then welcome ...