First occured when Windows installed.
Windows would boot up and right before login screen came up the monitor would black out into a "hibernate" sort-of mode. Same thing occured with other monitors and a seperate harddrive with linux installed on it.

Note: The reason im posting here is because Id like to make this my linux box but I wouldnt want to waste money on a modem when the monitor blacks out. So I would like to solve this problem now.

Ive updated my BIOS recently. Any ideas of changing some BIOS config around that would help? Heres my hardware info:

Computer:
Operating System - Microsoft Windows XP Home Edition
OS Service Pack - Service Pack 1
Internet Explorer - 6.0.2800.1106 (IE 6.0 SP1)
DirectX - 4.09.00.0902 (DirectX 9.0b)

Motherboard:
CPU Type - AMD Athlon XP, 2133 MHz (16 x 133) 2600+
Motherboard Name - FIC AM35 (3 PCI, 1 AGP, 2 DIMM, Audio, Video)
Motherboard Chipset - VIA VT8375 ProSavageDDR KM266
System Memory - 224 MB (PC2100 D SDRAM)
BIOS Type - Award (08/01/03)
Communication Port - Communications Port (COM1)
Communication Port - ECP Printer Port (LPT1)

Display:
Video Adapter - S3 Graphics ProSavageDDR (32 MB)
3D Accelerator - S3 SuperSavageDDR
Monitor - Dell E770p [17" CRT] (832DX07IH45C)

Multimedia:
Audio Adapter - Creative EMU10K1 SB Live! Audio Processor

Storage:
IDE Controller - VIA Bus Master IDE Controller
Floppy Drive - Floppy disk drive
Disk Drive - SAMSUNG SV0602H (60 GB, 5400 RPM, Ultra-ATA/100)
Optical Drive - LITE-ON COMBO LTC-48161H (DVD:16x, CD:48x/24x/48x DVD-ROM/CD-RW)
SMART Hard Disks Status - OK

Partitions:
C: (NTFS) - 52824 MB (37460 MB free)
D: (FAT32) - 4435 MB (776 MB free)

Input:
Keyboard - Compaq PS2 Keyboard (2K - 3)
Mouse - PS/2 Compatible Mouse

Network:
Network Adapter - Realtek RTL8139 Family PCI Fast Ethernet NIC
Network Adapter - WAN (PPP/SLIP) Interface (12.73.223.208)
Modem - Lucent Win Modem
Modem - U.S. Robotics 56K Fax PCI

Looks like something I experienced with Windows XP and a ATI-radeon. Somehow (probably due to a random keypress I made) the Video output was now the primary display for my graphics card, so I had to connect a TV to the TV-out on the computer and configure my display settings from that.

You could also try pressing ctrl-alt-t, I believe that is the cycle-between-displays key combination for some display adapters.

are there any other commands i should try before i restart? i have to wait like an hour so i dont want to do it without more options.

If this occurs with both Windows and Linux, it's most likely a hardware problem (something about the boot process is causing the monitor to lose signal). Check your cables, make sure the videocard is firmly seated in the slot, and make sure that your BIOS is set to look for the correct card first (if your motherboard is capable of choosing between AGP and PCI slots for video input, and one of your two cards is in fact an AGP card).

What I suspect is that your S3 SuperSavageDDR is being chosen as your main video input, which I would imagine is not appropriate (does that card even do 2D?). What you want is for both OSes to recognize your ProSavageDDR as the main card, and the SuperSavage as a supplemental card.

To be honest, I'd just remove the SuperSavage temporarily, install my OSes and get them working, then re-insert the SuperSavage and figure it out from there. But I'm a lazy bum .