Recurring ntoskrnl.exe crashes and BSODs on a new PC with random BugCheck causes and different drivers - help needed!

Anonymous
2020-12-26T09:53:33+00:00

AVE...

I have a constant problem with running Windows 10 on a new PC. First crashes were caused by faulty PSU, but I replaced it already. Other components (CPU, GPU, motherboard, SSD, RAM) are brand new. I have two old hard drives too, but I use them for storage only.

I have random BSODs with random BugCheck errors, all indicating the culprit to be ntoskrnl.exe with address 3f5780. No matter what I do, I can't avoid BSODs 3-5 times a day. Things I did:

  1. DISM and SFC, multiple times. Found some corrupt files on two occasions, fixed them, no results.
  2. Driver Verifier #1, found problems with ene.sys (Gigabyte RGB Fusion and related bloatware). Cleared it all out and removed offending file. Didn\t work.
  3. Driver Verifier #2, this time it was AmdTools64.sys, removed all amd*.sys files just in case. Didn't help.
  4. Driver Verifier #3, Avast VM driver sys file this time. At that point I decided it's not the drivers, it's something else.
  5. I ran MemTest 86 on my memory (which is overclocked by XMP profile). No errors. Also state of overclocking has no effect on the BSODs.
  6. I checked temperatures, ran AIDA64 stability tests, ran Fumark test on GPU, no problems with that since PSU was replaced.
  7. Last night I ran Media Creation Tool to overwrite the entire OS. I had 3 BSODs since, including one while writing this.

I had following BugChecks (as shown by BlueScreen View):

0x0000003b (00000000c0000005, fffff8056b0087de, ffffc58c841def40, 0000000000000000)

0x00000001 (00007ff9f8a0c074, 0000000000000000, 000000000000ffff, ffff8707`88461b80)

0x00000139 (000000000000001e, ffffdd09f7f28f50, ffffdd09f7f28ea8, 0000000000000000)

0x00000139 (000000000000001e, ffffcb0f5f40cf50, ffffcb0f5f40cea8, 0000000000000000)

All logs, minidumps and last memory dump file are here:

https://drive.google.com/file/d/1dL6jaLUunthZNOxaFSTEAC2VT5g4iNaj/view?usp=sharing

EDIT:

Just had another BSOD. This time with XMP disabled. BlueScreen View says:

0x00000133 (0000000000000000, 0000000000000501, 0000000000000500, fffff800444fa320)

with ntoskrnl.exe+3f5780, as always. File version: 10.0.19041.685 (WinBuild.160101.0800).

HELP!

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

102 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-02-07T01:29:33+00:00

    Yes, perhaps it's also MS to blame, but AMD needs to work together. And, in my case, why it's not a more widespread issue? Shouldn't all of the 3600xt be affected? I still think there nay hw something wrong with my cpu.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-07T01:34:50+00:00

    Nm, i went as far as 8 days w/o bsod and they came back altogether. There is no fix right now.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-02-07T06:48:30+00:00

    Had the same issue happen. Rebuilt my PC about a week ago and ive had maybe 6 crashes all with this same error code. Totally up to date on everything too. 

    MSI B450-A Max Pro 

    Corsair 16GB 3200 Ram (no XMP)

    Ryzen 3600

    Not entirely sure what happened. This is pretty frequent.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-02-07T07:14:41+00:00

    Some people have the same problems with Intel CPUs. So I think the issue is platform-agnostic. I am sure it stems from the way Windows 10 changes clocks and voltages for CPU on the kernel level...

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  5. Anonymous
    2021-02-07T08:02:27+00:00

    Okay, switching power plan to the one with max performance worked, for now at least. No BSODs, no random freezes. It increases CPU clocks and adjusts voltages to provide performance, of course. But it also doesn't changes them back to eco mode, or at least changes them much less.

    Other things that help:

    1. When installing Nvidia GPU drivers, choosing advanced mode, "Clean install" and installing only graphics driver and PhysX driver decreases number of BSODs.
    2. Clock locking works, and one can lock them at any frequency, not only base one. Temperature/cooling is the limiting factor. W10 can't mess up frequency switchover when it can't bypass BIOS/Chipset lock.
    3. Changing CPU to different model might work for some. CPUs are not created equal, it's the nature of manufacturing process. The spread of parameters can be quite wide. Just google for "BC547 datasheet" (it's a common bipolar transistor) and check the "DC Voltage gain" parameter - it differs from unit to unit, despite the fact entire batch is made on a single silicon die the size of small plate. And CPU transistors are much, much smaller in size than this common single transistor.

    I was considering a downgrade to Windows 7 too, as this issue is only on Win10, and I have licence for both.

    I'll keep you informed.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments