can't load win98se on raid zero drives

[elleon30033]

trying to reload win 98 se on top of itself after adding ram and getting errors repeatedly. Every time windows starts loading i get this error: SUWIN caused a General Protection Fault in module USER.EXE.....anybody ever heard of this....can you tell me why it is happening and if there is a work around.....i can't access my raid drives even in safe mode now and reloading is the only option to keep from losing my data. Does this sound like a virus or something that could be related to the new memory....any guidance would be most appreciated.....TIA.....best wishes

[elleon30033]

Ok, wanted to explain more clearly what happened. After changing hsf to the volcano 7, adding 256mb kingston ram stick to my other generic 256, and carefully changing all my flat ide cables to rounded, and adding heatsink to the ram courtesy of thermaltake, one active cooling (fan), one just the casing, and adding ram sinks to my video card GF2 mx 400, i started the system and got various errors, mostly windows explorer errors saying it would be shut down.....i finally got an error saying the registry had errors and i should reload windows...thats when the trouble got out of hand and the above error occured no matter how many times i tried to load win98se and no matter whether i loaded it from my hdd copy of setup or the cd. it finished once but never asked for my key which i thought was odd. rebooted, same old errors....what da hell can i do to get the reload to take so i can at least save my files to another disk, i am multi booting......win98se on raid 0, win2k on an individual drive to itself, and mandrake on a drive to itself. the op systems don't see each other but win2k and 98 see my 2 drives which are on an ultra 66 card. also added a bracket fan attached to the hdd rack, the vibrations couldn't cause that could it? i'm stumped ..need fresh ideas please..or better yet...a solution...that would be really nice.......lol:(

[BipolarBill]

It's the memory. Either the new Kingston is bad (unlikely) or the two brands/types don't get along. Check to be sure both are the same specs - CAS/CL, Mhz. Try removing the generic memory and test again.

[elleon30033]

Bipolar, I suspected that might be it. Funny thing is i'm ok in win2k. Just put the kingston in, it was not new...hmmm...is there a utility that i can use to test it? Again, as always, you rock dude, thanks.....it helps so much to know where to look...funny thing is the kingston has that active cooling heatsink sleeve on it, if its bad i go to destroy the cooling solution and man it looks so kewl yanno? On the flip, looks ain't worth **** if the thing is not solid. Let me know if you know of a way i can test the ram besides just removing the other.....which i will do tomorrow if its the only way. Now i can rest my mind...your advice is priceless .........again :D

[BipolarBill]

http://www.teresaudio.com/memtest86/