winryan said:
WSE installed. Ran a scan which did not find any problems.

About the verifier...I noticed that with the BSOD scan I ran to collect the info for you, it collected 19 mini dmp files. There is no doubt that I experienced 19 crashes between the time of running verifier having my system be unable to boot, having windows restore the system to a previous state that it could run from, and then send this info to you, so I believe the info sent to you was too long a time after I ran verifier for that info to be included in the report At least that's my guess on why no information was present about the info that could have been obtained in the .dmp files while I did have the verifier enabled (which made my system unbootable)

I am doing no type of overclocking etc at all.

Now after paying close attention to the time at which my BSOD crashes are occuring, they are actually happening at a constant amount of time after bootup! It's almost exactly an hour from the time I log in to windows. I'm assuming that's pretty important in diagnosing this and that having a trace or log of some sort looking at what's going on right before the crash would be useful?

In any case, I am proceeding to do the disk checks and system file checks you have requested now.

As always, thanks for the help!
Thank you for that info. One hour after reboot indicates that your Crucial M4 does not have the up to date firmware. See https://www.sevenforums.com/crashes-d...ld-boot-3.html

It would have been nice from the start to know you were using an SSD drive, but at least we had the information in our Blue Screen crash reports.
Code:
Model	M4-CT128M4SSD2