nforce 2 + ATI = DEAD machine help please
i am getitng this EXACT error with my new rig. Abit NF7 with nforce 2 chipset. Once any ati driver is loaded (8500LE radeon) I logon and the logon box goes away and comes back again and again, eventually i get in but no exe's will run whatsoever.
i am getitng this EXACT error with my new rig. Abit NF7 with nforce 2 chipset.
http://www.videocard-forum.com/ati/windows_2000_server_and_radeon_153571.html
Once any ati driver is loaded (8500LE radeon) I logon and the logon box goes away and comes back again and again, eventually i get in but no exe's will run whatsoever. I am imaging between dirver tests so far cat 3.2, 3.7, 3.10 all doing it. It's enraging me.
Windows 2000 server with SP4 DX 9b, newest nforce drivers from a 2 weeks ago. 1 hard drive one burner, 512 ram @333, barton 2500+ @ 333, nothing else in the machine.
bios settings all set to safe and or default, no overclockage anywhere.
http://www.videocard-forum.com/ati/windows_2000_server_and_radeon_153571.html
Once any ati driver is loaded (8500LE radeon) I logon and the logon box goes away and comes back again and again, eventually i get in but no exe's will run whatsoever. I am imaging between dirver tests so far cat 3.2, 3.7, 3.10 all doing it. It's enraging me.
Windows 2000 server with SP4 DX 9b, newest nforce drivers from a 2 weeks ago. 1 hard drive one burner, 512 ram @333, barton 2500+ @ 333, nothing else in the machine.
bios settings all set to safe and or default, no overclockage anywhere.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
Fixed. It is ATI drivers coupled with another thing. I will splain. There was a system tweak to "enable large system cache" i first saw it in xsetup. It makes a pro workstation use the large system cache that server uses. Well since I installed server, it is enabled by default (its not a tweak for server it is default)
With this setting it caused this problem. When I launched xsetup and disabled it (making my server have a small pro type system cache it fixed.
With this setting it caused this problem. When I launched xsetup and disabled it (making my server have a small pro type system cache it fixed.
