G
Guest
Guest
Archived from groups: alt.comp.periphs.mainboard.msi-microstar (More info?)
I've got an Athlon XP 2000+, with the FSB Clock set to 133 in the BIOS, and
the clock for my DDR400 mem set to AUTO. The PATA HD is connected on the
same channel as my CDRW with a SATA 133 cable. The motherboard came with
Gigabit Ethernet, FireWire and SATA. Th power-supply is 300W. Curiously,
when I set the system up without an OS installed, the MB beeped
continuously, and I put this down to the fact that the hard drive wasn't
formatted. The beeping stopped when I set the CDROM as bootable and put the
Windows XP CDROM in the drive.
I installed Windows XP with no problems. However. When I leave XP running,
it's stable. But within 15 minutes when I start to open folders, close the
wondows warning boxes such as "You Don't have an antivirus running" etc, the
whole system freezes and I have to switch off by holding the button in for 2
secs, rather than giving it a jab. Also, it sometimes resets itself 3 times
in a row.
How can I pinpoint the problem? Surely there must be a log file which says
exactly wht the problem is.
Thanks.
Fellow
I've got an Athlon XP 2000+, with the FSB Clock set to 133 in the BIOS, and
the clock for my DDR400 mem set to AUTO. The PATA HD is connected on the
same channel as my CDRW with a SATA 133 cable. The motherboard came with
Gigabit Ethernet, FireWire and SATA. Th power-supply is 300W. Curiously,
when I set the system up without an OS installed, the MB beeped
continuously, and I put this down to the fact that the hard drive wasn't
formatted. The beeping stopped when I set the CDROM as bootable and put the
Windows XP CDROM in the drive.
I installed Windows XP with no problems. However. When I leave XP running,
it's stable. But within 15 minutes when I start to open folders, close the
wondows warning boxes such as "You Don't have an antivirus running" etc, the
whole system freezes and I have to switch off by holding the button in for 2
secs, rather than giving it a jab. Also, it sometimes resets itself 3 times
in a row.
How can I pinpoint the problem? Surely there must be a log file which says
exactly wht the problem is.
Thanks.
Fellow