multiple OS installs on both HDD & SSD over 6 months...still BSODs

Ok, fresh & rested eyes are tackling this again. I installed the 2 drivers previously mentioned: RAID: Marvell* SATA Driver & AHCI: Intel® Rapid Storage Technology Driver for Intel Desktop Boards. I however did NOT install the following related updated driver, RAID: Intel® Rapid Storage Technology Driver for Intel Desktop Boards for the two reasons. I just want to make sure my reasons are correct. First of all, I don't plan on using RAID. Secondly, after reading the "Purpose" & "How to install" sections in the detailed description of this driver, I felt it unwise or unnecessary to install this particular driver. I just want to make sure I'm correct.

In regard to the chipset drivers, I again used the Chipset INF Update Utility to verify that I had the latest drivers, at least according to that utility. I do indeed have the same one that it installs and did it again just for good measure. I'm just not sure if that installs a merely valid set of chipset drivers OR the very latest chipset drivers. Also to be safe, I also updated to the latest Intel Mgmt Engine driver although I'm not sure how relevant that is.

I found something that may possibly be very significant. I downloaded and installed the latest JMicron JMB36X Controller drivers especially in light of the latest release notes. I'm not sure what they control exactly but I suspect it would be very important if they are pertinent to my Intel Z68 SATA connectors (2 of which are SATA 6.0 Gb/s connectors & 4 of which are SATA 3.0Gb/s connectors) as my OS SSD is connected via that. If they however only control my unused eSATA connection then I guess it isn't as significant. In any case it is now updated.

I'm still holding off on physically re-installing my AMD video card and driver until I can eliminate the current round of ongoing BSODs. I just experienced another BSOD while using my method (mentioned in my initial post) of speeding up the eventual and inevitable BSOD. It may be noteworthy that again while doing so, Microsoft Security Essentials service stopped approximately 3 times during the full scans of my BSOD-inducing stress regimen. MSE notified that service had stopped, submitted an error report to MS and prompted a restart of service which I followed by then restarting the full scan each time. I'm still not sure what influence, if any, my continuing to use Driver Verifier in this manner may be having.

Attaching the files compiled after the most recent BSOD.

With everything updated, I would suggest disabling Verifier. It is probably at least contributing to your test method causing crashes. Verifier puts the system in a state where it intentionally stresses drivers to cause crashes if drivers are not working properly. Often, the crashes end up being false positives if questionable drivers have already been updated/removed.

We should focus on whether your system will run normally without the driver stress testing.

To disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:

verifier /reset

-> Restart your computer.

I got pretty desperate. I had another BSOD or 2 that pointed somewhat towards MSE according to WhoCrashed. I know that doesn't necessarily mean anything...at least with what little I understand...about what I don't understand. So knowing full well it likely wasn't the cause, I still chose to uninstall MSE. i know I lost my mind...I know. I just had to because all the MSE errors under my weirdly designed stress test were bugging the heck out of me. After uninstalling I tried my voodoo stress test again. Sure enough I had another BSOD. This one was surprisingly even more quick than the rest as I hadn't even opened all the programs for my usual stress test. So I satisfied my curiosity that MSE had apparently no root causation in the matter...hopefully.

Well, I had an epiphany shortly thereafter. I built a very similar machine for another member of my family using the i5 2500k proc and supposedly the same RAM but packaged as 2 x 4 GBs. Why the heck don't I try that RAM and then run my stress test and try to clarify the finicky RAM scenario??? Why didn't I think of that earlier. That was my second ever build, right after this one, and I was wishing my personal machine was as rock-solid. Trying not to get ahead of myself yet as I still have some time before I can declare any small victories. But not only is it currently passing my voodoo stress test...so far. I literally opened every single program on my computer and made sure those that were the most CPU &/or RAM intensive were also doing something. I'm constantly running programs in order to utilize between 5 and 7GBs of RAM out of the lesser 8GBs I'm now testing with out of the other machine...and she's handling it well all the way around. I don't know whether to laugh or cry...I think both are appropriate. I want to do this a few more hours and then undo my act of desperation by re-installing MSE after my brief loss of sanity.

I also realize that I have NOT actually yet truly determined if the RAM itself is finicky bad...as in memtest86+ immune but still intermittently funky. I'll have to also try the other 2 slots...the ones that aren't the recommended config for running only 2 sticks...to find out if it may be something on the MB side such as the slots itself or whatever else it could be related to the MB...since I was originally running a 4 x 4GB config. I'm going to try those other 2 slots first then re-install MSE. Then I'll test the 1st 2 slots again re-adding MSE scans to the stress test and then test the opposite 2 slots, once again with MSE scans as part of the stress test. Then I'll re-install my AMD video card and repeat that same protocol.

If things are heading the way they appear to be heading, It has to be either the RAM or MB (RAM related). I'll have some specific questions later about how I should proceed with the RAM should I it definitely present as a RAM related issue. But I'll save that for when I've more precisely isolated the more exact issue.

OMG the horror! The horror of the past 6 months. I'd have been much more delighted to have gotten something to be tested as grossly defective right out of the box than what I've apparently been presented with...should the rest of my testing bear out that fact. My lesson as a learning enthusiast. I'll probably ALWAYS keep at least an extra two sticks of RAM on hand. I'll put it in a box with a glass top that's marked, "To prevent troubleshooting insanity, BREAK GLASS". I'll also take the absence of memtest errors (after well, well over 36 hours of passes this go round not counting the ones from January) with a grain of salt. Possible title for my new t-shirt, "It passed the memtest but it was still the figgin' RAM!" Maybe 50 bucks for a couple extra sticks of RAM to test with versus the time, effort & frustration I wasted in troubleshooting. In retrospect, 50 bucks sounds like an absolute bargain right now.

Alright, let me jump in on this testing you've done. I was actually planning to get there soon after you disabled Verifier if you still had issues. Run two of your modules at a time (8 GB), go put the other 8 GB back in the other system, and see how your system responds. If you can do the same stress testing with your 8 GB, try the other two modules. See if set 2 works just as well. If so, the RAM is likely fine and the problem lies in the BIOS settings.

This is common with 16 GB of RAM. BIOS settings are generally configured for 4 GB of RAM; they work well for up to 8 GB of RAM. Add another 8 GB to reach 16 GB, and things break down a bit. Do the tests I mentioned with your own RAM and post back how things go.

Also, please re-install MSE if you have not already done so. :)

I've tested down to find the offending stick. I'm now testing the the remaining 3 sticks under heavy stressing to be sure there are no more BSODs. I also think it might be a good ideal to test the 3 remaining sticks in a configuration that tests the currently empty DIMM socket just to confirm I have no possible problems with the sockets/MB. Anything else I may be missing? I'm also curious about any links you have that I can read over about the problems one might encounter when operating above 8 GBs of RAM in case I encounter that down the road. The only reason I went with 16GBs was so I could power through video editing with Sony Vegas Studio HD which I haven't yet even dared to attempt on this machine being scared of its instability/BSODs over the past months.

writhziden, I'm hopefully getting very close to being able to hit that green "Mark as Solved" button. I'm extremely appreciative of your help and patience!

Good steps to check the slots, as well. Sorry I failed to mention that, but I am glad you picked up on it. Well done!

https://www.sevenforums.com/crashes-d...ml#post1786965 -> Dave76 is one of our leading experts (possibly the best) with RAM on these forums.

I finally physically re-installed the video card put the machine to the stress test and I'm in ecstatic that this baby is finally stable after all these months. I'm a kid-on-xmas-morning kind of happy. The big bonus on top of that is having had the chance to see why this forum is so firggin busy. Some awesome help to be found all over the place. I've found myself chasing numerous other threads with their contained links & advice to learn a lot or at least where to go or begin. It has goten pretty addicting chasing other rabbit trails of knowledge & advice. I've learned as much directly related to troubleshooting my problem as I have about things not necessarily related to it but equally as important to know. Just a long-winded way to say...

THANKS @writhziden! Solved

I am very very happy to see your problem solved!!