Apologies if this in the wrong area, feel free to move to the correct part of the forum if so.
I recently upgraded my computer by adding a pair of kingston 64GB SSDs in raid 0 and reinstalled win7. This worked fine and the computer was working without any issues. I then upgraded the ram going from 4 to 8GB and initially windows refused to boot. I discovered I'd reset the bios and lost the raid settings. Having reset the raid I tried to see if the machine would boot into windows and win 7 said it had to do a system repair as the data was corrupted. I tried this and from thern on the real problems started.
What happens now is that when booting from the Cd (so I can reinstall win7), the system starts fine, runs the post and then says windows is loading files. Once the starting windows appears in the middle of screen and the animation is just about to start running, the screen changes, the computer crashes and a thick red line appears across the top of the monitor.
Any suggestions on how I can stop this from happening and actaully get the machine up and running again?
Current system config:
Asus P5N-E Sli motherboard
Intel Q6600 CPU (not overclocked) 2.4GHz
8GB Kingston HyperX dual channel 800MHz CL 4-4-4-12
Nvidia 8800GT graphics card
Creative Audigy 2 sound card
Vantec PCi-E Sata card
Asus/ViXS TV tuner card
2x Kingston 64GB SSD
1x 500GB Seagate
1x 2TB Seagate
2x DVD burners
The voltage, CAS and speed of any given kit is qualified based on the usage of that kit alone. Two identical kits together might not work at their rated specs; you might have to increase voltage a bit or reduce CAS timings. This is one of the benefit of buying a quad-module kit: since it's tested as a whole, it should work at rated specs.
Assuming that your new RAM is DDR2 which it needs to be unless your motherboard handles DDR3 which I doubt, remove them and re-install your old RAM. If that don't solve the problem take out the SSD's and put them on another computer to run diags. If you don't have another computer to test on, don't use RAID and install the OS on one of the drives and it that works fine do the other. Time consuming but it might find the problem.