kt7a raid/1.2 t-bird/ultra lock ups and crashes

[Eis]

just installed a kt7a raid and a 1.2 t-bird and herucles profiet 2 ultra. been haveing all kinds of problems

1. when i install something or download that requires a restart i get errors or wont load got to go to safe mode then restart again.
2.random lock up and not responding.
3.some times installing a programs and it just stops.
4.some times it just fast as hell other slow

man i ready to take a shot gun to this, formated a lot thinking window not installed right.checked the irq and they seem fine.

irq
00 system time
001 standard 101/102-key or Microsoft Keyboard
02 Programmable interrupt controller
03 communication port {com2}
04 communication port {Com 1}
05 us robotics 56k voice int pnp
06 standard floppy controller
07 printer port [LPT 1]
08 system cmos/realtimeclock
09 acpi irq holder for pci steering
09 creative sb live! series
10 acpi irq holder for pci steering
10 nvidia geforce ultra
11 acpi irq holder for pci steering
11 acpi irq holder for pci steering
11 via tech 3038 pci to usb universal host controller
11 via tech 3038 pci to usb universal host controller
11 netgear ethernet pci adapter
11 sci irq used by acpi bus
12 ps/2 compatible mouse port
13 numeric data process
14 via bus master pci ide controller
114 primary ide controller {dual fifo}
15 via bus masterpci ide controller
15 secondary ide controller {dual fifo}

can some one help me please before i go to the nut house thanks
---------------------------------------------
my system:
kt7a raid mobo
1.2 t-bird
hercules profiet 2 ultra
256 [2x128] 133 ram
creativ lab soundblaster live xgamer
20 gig hd 5400 rpm {ide 1} master
24 gig hd 7200 rpm {ide 1} slave
hp 9100 cdr {ide 2} master
memorex 32x cd rom {ide 2} slave
4-1 4.26 drivers
400 watt power supply

 

[Pederv]

Something I tell every "brand new KT7" owner, use the CMOS jumper and reset the bios (with the system un-plugged). Sometimes it fixes random flakyness. Watch where your bios is assigning your devices. This is done during startup, not in windows. Sometimes windows will re-map an IRQ so it doesn't show a conflict but the bios will show that 2 devices are sharing an IRQ that shouldn't.