Yes I did. I followed the walkthrough on this forum in the sticky. System ran same as usual at the time. Play a video game for 30 minutes-hour and same BSOD.
I have no minidumps other than the one I attached to a post earlier in the thread using the Betalogs program that the folks at tenforums use. It contains a proper minidump. All of my currrent ones were either wiped when I reformatted and did a Clean Windows Install. Haven't BSOD'd since Monday night and those minidumps appear to have been automatically cleaned after a reboot or something. I'm not sure.
As I said earlier, I plan on doing a stress test again with my VR system tonight. Ran it for 8 hours yesterday with no crashes or BSODs which is promising.
*shrug* I can download 1.2 GB from most servers in a matter of about 2-3 minutes, but I understand. If everyone shoved out a 1.2 GB file for analysis that would definitely eat into bandwidth if you're a dedicated troubleshooter.
Yes. The interesting thing about the USB eXtensible drivers are that they were originally supported by Intel and not Microsoft. Intel handed the responsibility for driver support for those over to Microsoft somewhat recently. At least for my machine. In fact Intel is still providing driver support for Windows 7 and earlier until January 1st, 2019. I ran the Intel Chipset driver update yesterday... No idea if anything was out of date or wonky but the install process was notably having an effect on devices as it disabled and installed a variety of drivers.
Some of this could be coincidence as correlation does not mean causality, but the stability of my machine last night gives me hope I might have turned a corner. We'll see the next two days. I'm gonna make this laptop wish it was never assembled :grin1:
Weird, right? I noticed that the day I had the error and thought it funny. Then I thought maybe the value 26 was in Dec and changed it to Hex for the code listing (1A) and I kid you not the values for P1 SKIP 1A.... So in effect there isn't even a 26th value if we're assuming a sequential order.... :banghead:
Yeah. I have no idea how that would even be useful from a troubleshooting standpoint other than at the end of the line it comes down to bad hardware, and that's why I decided to follow the trail from the P2 value. P2 is the device address reporting the error if I'm not mistaken?
Absolutely. Ran 2 separate 8 pass tests to be sure with flying colors. Same with Prime 95 for the CPU. Ran all Prime 95 tests on the CPU for 16 hours without a single error. The last couple of weeks dealing with this have been really frustrating to the point where I was HOPING one of those stress tests would fail so I'd have some kind of answer on what was wrong, because I was sure the filesystem was good too after a complete reformat and reinstall of different versions of the Windows 10 iso.
Finding out there was a much more recent BIOS update than what was listed on the manufacturer's website might be promising too.
Time and lots cycles the next couple days will tell.
Thanks again for your support. I'll be sure to drop a few bucks in the donation bucket for your effort as well :thumbsup2:
[/QUOTE]
