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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-02-02T19:12:00+00:00

    It looks like I might have accidentally fixed my problem yesterday, because I had no BSODs for over 26 hours. And I have no idea, how. Things I did in order:

    1. After shutting computer down I disconnected my entire setup from outlet. I removed heatsink and washed old thermal paste with isopropyl alcohol and some cotton pads (or whatever one calls the round thigies used to wipe makeup off). I removed the CPU from the socket and washed it too. I had to wash the bottom side too, as bit of thermal paste got between the pins - I used sewing needle to remove it. I also cleaned the socket for good measure. I reassembled it all back with new thermal paste, Silentium PC Pactum PT-2. I took the oportunity to also move some cabling around and make sure that all connections are solid.
    2. After power up it turned out that BIOS was reset to factory settings. So I switched XMP profile for memory back on, set the CPU fan to full blast, adjusted boot order and then set the CPU frequency to 3850MHz. Save and exit, and BSOD as soon as Windows 10 loaded. Bug Check 0X162, KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE.
    3. After reboot I went back to BIOS and disabled Precision Overdrive. Reboot, another BSOD. Don't remember, what it was exactly.
    4. Then after reboot I selected "Load optimized defaults" from BIOS options and redid changes from point 2, sans changing any clocks. Since then I had no problems. There were two updates to MS Defender since then too.

    So now I don't know, if this was solved in BIOS or by my messing with MB and CPU. Or by those two updates. Or by magic. I hope this lasts. If not, I'll inform you all here and on Reddit...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-02T05:51:11+00:00

    Both. That's why i want my parts replaced (the only thing that worked so far in ny casw waa cpu change). If only ms, amd or Intel made a statement, perhaps i could just sit and wait. But we dont know for sure what's going on.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-02-02T05:41:18+00:00

    For now you can either have max performance or stable OS. What is more important to you? For me it's stability. Till last December I had i5-2300 (2,6GHz x 4) and 8GB of RAM (1333MHz), and I didn't complain too much...

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-02-01T21:26:55+00:00

    Indeed, thats the problem. I know how to oc, but doing so eliminates my Ryzen 5 performance (wont go above 4.4). There is anothe big issue here (and i suspect its hardwaee related)

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-02-01T19:12:53+00:00

    And how is the boost is supposed to work if i disable it?

    Was this answer helpful?

    0 comments