Re: Tutorial creating & using Hirens Boot CD & MemTest86 diagnostic stress testing tools for USB boot to Windows 10 PE & WinXPmini on BIOS & UEFI

On Fri, 16 Oct 2020 03:30:16 -0400, Andy wrote:

> Did you ever find the problem i would have rolled back the Nvidea driver i 
> had that problem once and rolling the driver back fixed it until they 
> relised a fixed updated driver the next month.

Hi Andy,

Thanks for sticking with this since there are three things I am wont to do:
1. I always (almost always, eventually) figure out the problem cause, and, 
2. I often try to learn as much as I can about debugging in the process, 
3. And, I sometimes write up the gory details in the form of tutorials.

Hence, everyone benefits from any troubleshooting we collectively do.

To that end of troubleshooting, I've learned a lot, and I've stress tested 
a lot, but I haven't yet definitively figured out the problem - but I do 
not think it's the Nvidia drivers, if only because the BSOD happened even 
after I had the Nvidia card removed from the system for months 
(since the AMD-based motherboard has its own graphics output).

So I put the Nvidia GeForce 210 card back into the PCI slot, and it 
BSOD'd with or without that specific graphics card being involved.

As you may be aware, I tested the memory (Memtest86 v4 for BIOS) for 
24 hours, but I still think it "may" be memory related simply because, 
consistently, when I reshuffle the memory, the boot-after-BSOD is 
successful every time, whereas if I don't reshuffle the memory cards, 
that's not always the case (yes, I know it's flimsy evidence).

I've tested all the drivers using Microsoft "Verifier.exe", and 
I've updated all the drivers that could be updated (using Dumo to 
tell me what's available), and I've identified the memory location 
where the BSOD occurred    
o ntoskrnl.exe (nt+0x3F3EA0)
  Bugcheck code: 0x139 (0x3, 0xFFFFF30F99097970, 0xFFFFF30F990978C8, 0x0)
o ntkrnlmp.exe (nt!setjmpex+0x8279)
  Bugcheck code: 0x139 (0x3, 0xFFFFF30F99097970, 0xFFFFF30F990978C8, 0x0)

I'm slowly coming to grips with how to proceed to debug _that_ error.
o Meanwhile I'm running a long-term physical test of the memory sticks

Right now, I have memory card 1 (of 4) in one of the four slots. 
It hasn't BSOD'd since I did that - but of course - that tells me nothing.

However, what I plan on doing is putting that memory card in all 
four slots, and if it still doesn't BSOD for a while, 
I'm gonna "presume" tentatively that it's not the slots.

I might then do the same with memory card 2, but overall, 
there are so many permutations and combinations I can run 
with the four memory slots and four memory cards that if ONE slot 
or ONE card is bad, I think the BSOD may finger it.

Dunno yet... but every single day I try something new; 
it's just that most of the time there's nothing to report.

Here's a synopses of some of the related threads though... 
o Windows 10 BSOD indicates a hardware problem - but what hardware is the problem? 
<https://alt.comp.os.windows-10.narkive.com/oL7PTNKu/windows-10-bsod-indicates-a-hardware-problem-but-what-hardware-is-the-problem>
<http://www.pcbanter.net/showthread.php?t=1110105>
<https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/u0ay9h777Wg>

o What's the one free Windows 10 driver update tool you prefer most & why?  
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/-yDz26GC6zA>

o Tutorial: How to update a driver that Windows just doesn't want to update 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/a23fY9CM6rY>

o Tutorial: How to delete a specific restore point in Windows 10 (e.g., after an errant program such as driverpack created it!) 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/MbtX0Y_U0dg>

o Tutorial creating & using Hirens Boot CD & MemTest86 diagnostic stress testing tools for USB boot to Windows 10 PE & WinXPmini on BIOS & UEFI 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/OlpQK3Uy7K8>

o What PC hardware diagnostic stress-testing freeware can you recommend? 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/a6aAvxnDRB8>

o What else in Win10 can we turn off that hinders successful rebooting after a BSOD event that can chew up the operating system? 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/DlMnG1klEhc>

o What does it mean when a CPU won't wake up from its S3 state? 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/YJw0idlompc>

o Is there an option to completely shut off a Windows 10 desktop (not just go to sleep, hibernate, or fastboot)? 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/WVUpUtA_ExA>

o Windows 10 v2004 update repeatedly fails to update non existent keyboard but keeps trying forever (how to stop that nonsense?) 
  <https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/Npcs-xbnQdU>

o Tutorial creating & using Hirens Boot CD & MemTest86 diagnostic stress testing tools for USB boot to Windows 10 PE & WinXPmini on BIOS & UEFI 
<https://groups.google.com/forum/#!topic/alt.comp.freeware/VWG0NNyGNHc>

o What PC hardware diagnostic stress-testing freeware can you recommend? 
<https://groups.google.com/forum/#!topic/alt.comp.freeware/dkkdOmL95d8>

o What does it mean when the Event Viewer (eventvwr.msc) says "Report Sent"?
<https://groups.google.com/forum/#!topic/alt.comp.microsoft.windows/WG9y9YNVeH4>

Together, there must be hundreds of annotated screenshots so people 
can see exactly what's going on, such as these in just one post 
in that last thread.
a. I received a BSOD today which I am methodically diagnosing step by step. 
   <https://i.postimg.cc/k4Hssdpr/bsod205.jpg> 
b. One of the score of steps is to see what the event viewer tells me. 
   <https://i.postimg.cc/0Qh3QmxJ/eventvwr01.jpg> 
c. I noticed some events cause a report to be generated and then "sent". 
   <https://i.postimg.cc/mZMpjPB8/eventvwr02.jpg> 
d. Others cause a report to be generated, but, apparently not to be "sent". 
   <https://i.postimg.cc/63ZcMPJy/eventvwr03.jpg> 
e. Still others, cause a report neither to be generated nor to be "sent". 
   <https://i.postimg.cc/sg2JkxCF/eventvwr04.jpg>