Frequent BSODs after completely clean Windows 10 Pro install

Semx11 · 27 Jul 2018

Hi there,

Around a week ago, my old Windows install was completely screwed and so was my SSD. In an effort to resolve these issues I ordered a new NVMe M.2 SSD (250GB) and did a completely clean install using a bootable USB stick that I created using Windows' official tool.

Unfortunately the installation didn't go very smoothly, I had to retry a few times, and try out different ports/USB drives before it finally completed without errors.

I suspected something went wrong, so I ran the following checks:

chkdsk /f /r - I looked at the logs using Event Viewer, which said it detected some errors and it repaired them.
sfc /scannow - It indicated that it found some issues, but it couldn't repair it.
DISM /Online /Cleanup-Image /RestoreHealth - It indicated that it repaired some things.
sfc /scannow - It indicated that it found some issues, and repaired them.

I rebooted between each step, and when I run sfc /scannow right now, it says it can't find any integrity violations, which is good.

Between these checks I got multiple BSOD's, 7 so far since Tuesday. 5 of them were MEMORY_MANAGEMENT, 1 was PAGE_FAULT_IN_NONPAGED_AREA, and the other was SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

(NB: I recently replaced my RAM (2x8 = 16 GB DDR4 @ 3.000 MHz) under warranty as it was faulty. This was on my old installation. I don't expect my RAM to be faulty, but I'm willing to try everything.)

According to BlueScreenViewer, all 7 of these crashes were caused by ntoskrnl.exe. This was the reason I tried to fix the problem with chkdsk, sfc and dism. Unfortunately the crashes are still occuring.

The crashes seem to happen at random as soon as I click on something. This could be closing a tab, minimizing a window, closing an application (e.g. HWMonitor). It can literally be anything.

I've tried to Google the error codes, I tried to analyze the minidumps using an online tool, or read related threads on this forum, but unfortunately no luck so far.

If anyone here could point me into the right direction that would be greatly appreciated.

Thank you,

Sem

PS: I have attached the ZIPs created by both the normal and the beta collection tool. The minidumps of the last 4 BSODs are included, the first 3 already got deleted unfortunately. I did include the text files of the first 3 crashes that were generated by BlueScreenViewer. If I need to attach anything else please let me know.

AS185 · 27 Jul 2018

Hey Semx11,
You might need to revert your overclock to default values in the BIOS. If Windows loads and operates without error's, then it's best to leave it like that however if doesn't work, you will need to re-install Windows. I had error's like that before and it was all due to unstable overclock on my ram.

Semx11 · 27 Jul 2018

AS185 said:

-snip-

I'll try disabling XMP. It's a simple button in my bios, I don't overclock anything manually. In case it doesn't work, you said I'll need to reinstall Windows - however, I just did. This install is only 4 days old. I haven't even installed most of my programs on it, just the usual (chrome, discord, etc). So I'm 99% sure it will be something else.

I'm still looking for someone to look into the minidumps, as I'm sure there might be more info in it. Thank you :)

AS185 · 27 Jul 2018

It's amazing, how many thread's there is already related to a topic similar to your's and 85% of the time, it's all memory related due to an overclock or wrong BIOS configuration. But hey, your the expert on it, if you simply just cut-off people's post's. Oh and last but not least, thanks for reading my post

Ztruker · 27 Jul 2018

Accordinfg to the WER data in msinfo32.nfo you had 16 bluescreens since 7/24. There were only 4 dumps in the zips you uploaded.

3 of the 4 are identical to this:

Code:

BugCheck 1A, {41792, fffff0befae90048, 20000000000, 0}
Probably caused by : memory_corruption ( ONE_BIT )

Code:

SYMBOL_NAME:  ONE_BIT
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP:  0
STACK_COMMAND:  .thread ; .cxr ; kb
FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT
PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_ONE_BIT

So the likelihood of RAM being the cause is quite high. You have 16GB. If you test it with memtest86+ it will take 12 hours or so, but that's where you need to start.
===================================================
Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

RAM will accept and keep random patterns of data sent to it
There are no errors when different parts of memory try to interact
There are no conflicts between memory addresses

Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

Warning

MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

Note

MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

Take a picture when done and post in the forum please.

Semx11 · 28 Jul 2018

Thank you, I will try this when I get home and post back with results once 8 or more passes have completed.

Just to make sure, do I need to disable XMP while running memtest86+? Or can I keep it on?

Thanks

cwsink · 28 Jul 2018

You are overclocking the integrated memory controller of your CPU if you're using DDR4-3000 settings. The highest setting officially supported by Intel for your CPU is DDR4-2400. Your memory and your motherboard may be able to use DDR4-3000 settings without any problem but that doesn't mean your CPU's IMC will. Able to boot does not necessarily equal stable when overclocking.