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.