My computer wanted to restart after the quarantine just now, so I let it.
Perhaps you were expecting a log made AFTER I had quarantined the items. I wasn't sure how to share the XML in any case.
I'll just move onto Seatools. Is this the instructional thread I should be looking at here.... SeaTools for DOS and Windows - How to Use
Edit: Assuming these are the correct instructions, it appears that I should use Option 2 although it seems a bit less simple than Option 1.
Didn't want to start this whole process last night, partly because I'm not sure what I'll be doing is the right thing to do... but I'm starting on Option 1 I suppose and hoping that's sufficient. I'll use option 2 if necessary. Let me know if this is the correct thing to do if you're around. Thanks.
Yes, go ahead with option one. Let us know the results.
I used Basic Test > Fix All > Fast. My drive passed. Is there any other info somewhere in this program that you need? Do I need to take a different test or even use Option 2? There's other values here that I've not seen before such as my firmware designation. I didn't know it was "SM14".
Option two can't hurt, all we can do at this point is grasp for hints by running tests.
I have no idea why your other BSOD produced a dump but none of these do, that doesn't make any sense.
I suppose I'll try Option 2 then.
Well, the most obvious difference is that all my other BSODs were 7A errors. The one I got yesterday, (Was it only that long ago?), wasn't a 7A error. Maybe these 7A errors are weird and don't want to produce a dumpfile.
I did do one thing prior to that tablet BSOD. I don't know how it could be related but it seemed like a good thing to do. I just turned off my backup and restore schedule. I'd had it scheduled to backup my system every month. Trouble is that I wanted it to backup onto my External HD but not until the schedule was made did I learn that the External HD was incompatible to backup due to it's large size... something about a "I/O Error" or something. It would need to be formatted evidently but I already had files on it from basic copying over actions from other drives, so I didn't bother with that. Again, however, I never did turn off the schedule so I wonder if my computer was trying to backup to something that didn't exist because the external wasn't plugged in and wouldn't have done the job anyways because it wasn't formatted, and maybe that buggered it up. Not sure obviously.
The fact that my 7A BSODs come around pretty reliably, usually within a day of a week, is curious to me. Generally they show up on Wednesday or Thursday. 10 of the 3 happened roughly a week after the last, and the ones that didn't happened within a day of the last, and recently I went two weeks without one. I can't be exactly sure on the days of the week of all of them, but I can say that most and possibly all have happened on a Wednesday or Thursday. The "on time" nature of them made me wonder if my backup schedule thing could possibly have any effect at all. It's a really loose correlation, but I don't know how connected all these functions actually are. Maybe my next 7A BSOD will give me a dumpfile though. Maybe somehow the schedule for my backups to a non compatible external HD had something to do with a lack of dumpfiles. Seems really unlikely.
I'm also curious in the Speccy data I shared a while back now said anything about my BIOS or about my system in general that could describe some sort of conflict or compatibility issue. I figure not since you didn't say anything initially. Seemed you were seeing a lot more in that data than I could looking at the link myself.
I was just looking at the temps in that Speccy report, which didn't look bad. I must have overlooked responding to that.
As for the Bugchecks you mentioned above, that wouldn't make a difference in creating the dumps.
I tried to boot Seatools DOS from a USB Flashdrive and followed the instructions carefully. However when booted it was stuck at the loading screen just saying "FreeDOS". It never got to the Seatools GUI as described in step 2 of PART II of the Seatools for DOS part of the Seatools thread.
Any suggestions as to why this could be and if I should troubleshoot it until I can get this Seatools for DOS to work, or should we move on?
In the meantime I can wait to see what my next BSOD brings. Perhaps these 7A files will produce a dumpfile finally, and assuming they stay on schedule I can expect one in the next few days. I'm not holding my breath though since I feel like the only reason it wouldn't make a dumpfile, unlike the tablet driver error, is because it's a different error.
Quote