I agree with axe0 about the CDRom drive problem but it doesn't seem to cause the boot problem. In regards to that do you have Daemon Tools or Alcohol 120 installed?
The .dmp still shows the Volume Shadow Copy as the culprit.
You mentioned that your hard drive is getting low on space. How much free space do you have?
1. the new .dmp is still from the first mentioned BSOD I havent had a new bsod since then
2. Yes I do have Daemon Tools installed currently. The boot problem only occured when I tried to make use of Driver Verifier after loading into windows it would show my desktop for about 10 seconds, then it would corrupt the display, freeze and just sit there, I just simply reset, booted into safe mode and turned verifier off.
3. I did a massive cleaning as after the OP BSOD (which remains the only one) but at the time I think I had under 15 gigs of space left, after cleaning I have 64gb of space now.
Apologies for the late reply, when I got the email notification to your response, I was out of town for most of the day, didnt get back home till about 3:30am MST.
No problem with the late reply. I never know if I'm going to respond to someone the same day or the next day. Depends on what I have on my plate.
The reason I asked about Daemon Tools is because the CDROM problem is coming from SPTD and that's installed by Daemon Tools and Alcohol 120. I don't think it's installed as a part of Windows. You might try uninstalling/reinstalling the former with the latest version.
Doing the cleanup will probably eliminate the VSC problem if the problem was that there wasn't enough space for it. I periodically go to Accessories, System Tools and run Disk Cleanup on the C:. When it says how much space it can recover, I check the boxes to include Temporary Files and Recycle Bin (Temporary Internet Files is checked by default). Then I run it and reboot. I don't have to check the boxes every time because Windows remembers it after the first time. It won't tell you how much additional space it recovered but it is substantial if you work with Video editing/transcoding and other programs that generate a huge amount of temporary files.
After enabling Driver Verifier according to the instructions on the page you linked, I rebooted, and while windows began loading normally about...10 seconds the loading process corrupted the display (the background became corrupted I really cannot describe it adequately and my phone was dead the time so no pictures) and froze (the mouse cursor was unaffected but it was frozen in place) I left it for about 10 minutes and as nothing happened. I rebooted into safe mode and shut verifier off.
It's unfortunate to hear you won't attempt to fix the issue you experienced with driver verifier, but I do understand it.
However, if driver verifier doesn't produce a dump, I'm afraid we won't be of much help. Without additional dumps we can't provide the support needed to resolve BSOD crashes, nobody can.
I wrote it a little poor, but in post 10, you say you're not going to fix it.
With "It's unfortunate to hear you won't attempt to fix the issue you experienced with driver verifier" I meant the issue (system freeze and graphics problems) is likely caused by driver verifier as in it validated the actions taken by some drivers which resulted in a delay in performance and display.
In regards to the graphics driver, are you using the beta Crimson 16.2.1 or the Radeon 15.7.1?
Quote