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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-01-27T07:38:04+00:00

    Thanks for the link, I suspected the boost thingy, so I switched power profile from AMD balanced to Microsoft balanced. Didn't help. I'll try manually setting the clocks and voltages next. I don't think RAM clock affects anything, it's the CPU boosting problem.

    My specs:

    • CPU: Ryzen 5 3600
    • RAM: G.Skill Ripjaws V 3600MHz CL18 2x16GB
    • Motherboard: Gigabyte B450 Aorus Elite
    • GPU: KFA2 RTX 2060 Super
    • SSD: XPG Gammix S11 Pro
    • PSU: Chieftec Smart Series 250-700W (did the upgrade there because previous PSU had problems with 12V line)
    • OS: Windows 10

    I've got to 2-10 BSODs a day, depending on what I am doing, phase of the moon, state of cat litter box, level of moodiness of the PC, etc. In other words it's random. I even switched to Chome (ugh!), didn't help. Yesterday my daughter watched a Youtube video, PC crashed 6 times in an hour. OTOH the same day, before and after, I watched multiple videos on YT without any crash, up until evening, when I had two more crashes.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-01-27T03:55:41+00:00

    I'm dealing with the same thing. May I ask what your system is? I found this post on reddit but no solution yet: https://www.reddit.com/r/buildapc/comments/kpjmqf/bluescreen\_every\_couple\_of\_hours\_ntoskrnlexe/?sort=new

    Was this answer helpful?

    0 comments