Windows 10: BSOD Windows 10 build 1703 and 1709

Hey, i just checked the windows folder and there's no MEMORY.dmp in there, i even ran a search for it to make sure it wasn't me being blind lol

I do have hidden OS files visible etc, it's always the first thing i enable so that i can restore various things in my user accounts folder after a full OS wipe and reinstall *Smile

 

Any idea why one wasn't created? i couldn't find any info that applies to me, i have enough space on the windows drive, the pagefile is big enough too, i don't understand lol. this system is a royal pain in the you know what!

 

I'm still stuck with this.. i went all day yesterday without a single system crash, was gaming pretty hard too. will be continuing to test over the weekend, and i'll post any more dumps i get along the way anyways.

 

Corruption.
The system uses

• dump_*.sys drivers, used to write the data to dump,
• information collected from components
  • the name of the disk miniport driver
  • IO Manager structures that are needed for the process

to create dumps.


Copies of this information is stored in dump-context structures when you boot, the information is validated by a memory comparision. If it doesn't match no dump can be written.

 

Is there anything i can do to make the memory.dump happen when i next get a bsod? also, i've not had one bsod since the last dump i uploaded *Smile

I think that last bsod was directly caused by gears of war 4, that game has a lot of problems with the earlier creators update and the new creators update, the fact it happened after i flashed the bios on my motherboard to the latest release is a coincidence by the looks of it.

I'll keep using the system like i have been, playing games, browsing etc on a daily basis(i have lots of spare time at the moment lol).

 

You can run chkdsk, sfc and ram test, but much more can't be done using software.

 

I'd already done all of that before i wiped build 1709 from my ssd. *Smile

So far, i'm into day 5 i think of my system having not a single BSOD, so it does look like gears of war 4 was the reason behind that last dump that i didn't have a MEMORY.dmp for.

So this means that something was either wrong with the last flash of bios version F4(older bios version from the middle of the year some time), or the bios version i'm on now, F7a(latest stable release on gigabyte website) fixed the issue i was having but wasn't mentioned in the meager release notes.

Personally i think it's the former, if F4 had a problem that was fixed in later releases, then the problem would've been there from the first time i started the system, right?

 

4 weeks later and i've had zero crashes, the carefully flashed bios update fixed my issues and my system has been perfectly stable, so i've marked this as solved, and i want to thank axe0 for all of the help. *Smile