Two comments:

1) The Storport.sys driver (referenced in that BSOD on systems with >3GB RAM) only affects RAID or SCSI controllers, and not even all of those. WinDbg can read the module list from a memory dump and tell you if that driver is even loaded.

2) My giga-byte x38-DS4 board has been giving me fits with a pair of HyperX RAM lately. I got frustrated with the lack of response from the Kingston folks so I figured I'd go do one last check on the settings in the Motherboard Intelligent Tweaker settings. I compared the multiplier, voltage and standard timings to the specs and it was all good. What was NOT kosher was the advanced timings. Specifically, the Refresh to ACT Delay was defaulting to 42, where the module datasheet references 105. Soon as I changed that setting, BAM, no more issues. Ran all night last night with nary a hitch where it would reliably fail within 20 minutes on Prime95. I'm a pretty happy camper and quite a bit more wary from here on out of motherboard manufacturers' ability to properly configure my RAM for me. I'd suggest, since you have a mobo that'll allow you to tweak that stuff, that you go peek at the Crucial site and pull the datasheet for your specific RAM and see if it all matches.

Best of luck!