Windows 10: BSOD Issues after updating Windows 10 to v.1551 10586.318

Hi support!

Since last sunday 29 of May, I have had the BSOD crashes 4 - 8 times a day.

I have rolled back, repaired and reinstalled my windows 10 and still get more or less the same errors (I think).
I tried with sfc /scannow only for it to tell that i have corrupted files that it couldn't solve, so after that I tried using DISM but error there too, tried pointing DISM to my Windows installation image only to get BSOD (I was away on a coffee break so can't tell at what stage it were at).

I ran Windows Memory Diagnostic only to get the response that Hardware problem of somekind (I guess it being the memory sticks)
I have tried running memtest86+ with no success as neither booting with a usb or a disk works, only getting a black screen with the typing marker moving about.

Attachment 82810

Sorry for the wall of text.

PS. I have updated both the BIOS and drivers (first through Windows Update and then Driver Booster)

:)

 

This battery is not available to use !!

hi,

build number is 10586.318 v.1511

 

windows 10 pro stuck in restart loop "your pc ran into a problem and needs to restart. We are just collecting some error info, and then we'll restart for you, stop code: 0xc000021a"

You can check this thread and follow the answer provided by Likhitha
V to resolve the issue with stop code: 0xc000021a error.

Update us on the results.

 

Hi

I started the first run of WMD with only one memory stick.

Another question as I wait, Can Windows Update during it's update done something? I wonder as i have had no problems before with my RAM sticks and the only oddity my comp have had was when my E: HDD thought it was Harry Houdini with disappearing and then reappearing.

If i recall from last sunday, the first time the update failed and the BSODs started after that, and after the reinstall all updates installed with no problems.

 

What fase was the update? If it was with the installation fase it was replacing files and that can do certain things sometimes.

 

The first time was a usual update from the version before v.1551. The second time was after the reinstall (the reinstall version was v.1551 as i got it from the mediacreationtool.exe) but was manual activated like the first time. The only difference being the version of windows 10 with the first being v.1224 and the second v.1551.

Neither were in the installation fase.

 

Then it would be either in the preparing fase for installation or the downloading fase, in both fases it wouldn't have done anything to your system that could cause problems.

 

Oh well might have been only a hiccup from Windows Update.

I have run one stick in both slots now with no errors and with the other one in reported faulty hardware instantly from the WMD. Safe to say that I can discard that one and get a new one?

 

It seems I was half sleepy when I posted and didn't check for overclocking as that sometimes can cause this error too.
I have 2 suggestions
1. Revert back the overclocking of the memory to the SPD setting, 2133MHz, 1.2v, 15-15-15--36
2. Replace the memory with a new kit.

 

Good morning

I will change the overclock settings as soon as possible and i have ordered a new memory kit.

I did have a another BSOD last night and I can see that in the event viewer warnings about my harddrive where the OS is installed wich is a SSD, that 0 of 1 systemlayers have been repaired

Attachment 82878

also would you be so kind to explain "SPD setting, 2133MHz, 1.2v, 15-15-15--36"

I guess SPD setting is Speed setting 2133MHz is base clock frequency and 1.2v is the voltage. I have no clue what the last ones are.

 

SPD = stock, the things I mentioned are the frequency, voltage and timings at stock.

A 0x3B caused by memory access violation caused by the memory.

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:

 

The SPD is usually done through XMP profiles, if that is also the case with your system then you would either need to set the XMP profile to the one that offers the best settings compared to the SPD or you need to disable it.

 

Ok will try to remember not to use Ccleaner or the harddrive equivalent , good thing that i saved the old attachment i sent here.

I changed the memory spd now to 2133MHz and voltage and the timings match up to your request.

It does use XMP but it were not required it seems like

 

Try to get another BSOD to see if removing the overclock helps, or run the Windows Memory Diagnostic again *Smile

 

I went and used Driver Verifier and had a BSOD DRIVER_VERIFIER_IOMANAGER_VIOLATION

Attachment 82879

Other then that i could take some time before I get a "real" BSOD