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.
DESKTOP-G0E5FEB-01-06-2016_214959,64.zip
Sorry for the wall of text.
PS. I have updated both the BIOS and drivers (first through Windows Update and then Driver Booster)
WarningPrograms that claim to update your drivers install either the wrong or corrupted drivers.
If you have installed any driver with Driver Booster 3, please remove them as it may cause trouble.
An easy way to remove these drivers is through a system restore point prior the use of it.
A 0x12B & 0xC4 where the 0xC4 does not flag a driver only means the memory is the cause which of course was already clear with the Windows Memory Diagnostics test.
Please remove 1 stick and run the memory test again, if it has finished switch with the other stick and run the test again. Then switch from slot and run the test, then switch stick and run the test again.
This should help identify what stick/slot is faulty if you note the results of the tests
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
DESKTOP-G0E5FEB-02-06-2016__94047,97.zip
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: