Hello
I've just installed a new Motherboard (TUSL2-C) to replace my old (P3V133) one and I've got some problems. I Experience, while in games, Graphical Artifacts (similar to errors you get when overclocking your vid card), Cashes (to desktop or lockups) and alot of errors (runtime errors for the most part). I also have IE crashes and explorer crashes.
My config is :
PIII 733 Mhz CPU
TUSL2-C S370 (815EP chipset) (BIOS 1012)
384 MB PC133 SDRAM
MSI MX400 PRO32S (MS-8817) GeForce 2
The rest of the hardware seems irrelevant.
CPU and Vidcard Are in no way overclocked
Tried setting Vcore to 3.3, 3.4 (default) and 3.6 w/o change
AGP set to 2x in bios, that seemed to help.
Software :
Windows 2000 Pro SP3 With all updates (IE6 SP1) (Re-installed after changin mobo)
The Chipset drivers for my board
DirectX 8.1
41.09 Detonator Drivers
I also found that my videocard was making alot of heat.
Any advice is greatly appreciated, thanks!!
P.S. I did not experience this problem On the P3V133, But Did on the TUSL2-C AND on a CUSL2 (i got the CUSL2 one b4 and figured the board was defective, so returned it and got the TUSL2-C)
I've just installed a new Motherboard (TUSL2-C) to replace my old (P3V133) one and I've got some problems. I Experience, while in games, Graphical Artifacts (similar to errors you get when overclocking your vid card), Cashes (to desktop or lockups) and alot of errors (runtime errors for the most part). I also have IE crashes and explorer crashes.
My config is :
PIII 733 Mhz CPU
TUSL2-C S370 (815EP chipset) (BIOS 1012)
384 MB PC133 SDRAM
MSI MX400 PRO32S (MS-8817) GeForce 2
The rest of the hardware seems irrelevant.
CPU and Vidcard Are in no way overclocked
Tried setting Vcore to 3.3, 3.4 (default) and 3.6 w/o change
AGP set to 2x in bios, that seemed to help.
Software :
Windows 2000 Pro SP3 With all updates (IE6 SP1) (Re-installed after changin mobo)
The Chipset drivers for my board
DirectX 8.1
41.09 Detonator Drivers
I also found that my videocard was making alot of heat.
Any advice is greatly appreciated, thanks!!
P.S. I did not experience this problem On the P3V133, But Did on the TUSL2-C AND on a CUSL2 (i got the CUSL2 one b4 and figured the board was defective, so returned it and got the TUSL2-C)