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-19T04:13:35+00:00

    I undestand that rma can be a PITA but yous should try anyway. My vendor told me that a lot of 3000 failed (and by a lot, i mean 10 out of 100 whereas intel had 1 of 100). They are AMD partners so it was a smooth process. Anyway, my system may crash again in a couple of hours, who knows. Right now, the system is stable for more than a week (7 days of testing, one day at home).

    It is the strangest issue i've seen in my almost 20 years of PC hobbie. MS could at least comment something...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-19T05:40:48+00:00

    I can understand failure rates, that's normal. But when lots of CPUs starts failing at the exact same time (speculating this is an actual CPU error, which for all we know might be a completely different issue), it is very sketchy. Especially considering people with Intel CPUs and laptops straight out of the box also reporting.

    It is a very weird issue, i have friends with the same CPU and same updates and their PCs are stable. However i'm the only one using a high refresh ratio, which is probably unrelated, but it definitely puts more stress to the CPU.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-02-23T12:33:52+00:00

    Just to add to the discussion. Here it happens on a PC with an old Intel i7 CPU (Socket 1156) and an old Asus P7P55D Deluxe.

    I applied the changes discussed here and no blue screen for about a week. Yesterday they started to come back. They happen mainly while the computer is on but not in use. I kept an eye on the task manager when they happened frequently. After between five to ten minutes of inactivity the system started to become busy (seemed to be Windows Defender) and shortly afterwards it crashed.

    The same system used to run stable. So I also think it is related to some Windows Update.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-02-26T10:16:28+00:00

    Hello again manubesada! :)

    Following your suggestion, I finally RMA my CPU. And yes you're right, my PC already been turned on almost 1 day but no BSOD till now..

    This is the weirdest issue on Windows I've ever had in my whole life!!!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2021-02-27T06:13:40+00:00

    There were many days since my last BSOD. So I decided to install Epic Games Launcher. I was also working at the time in other program, that didn't cause me any issues. Few hours after getting EGL I had another BSOD. And I lost 30 minutes worth of work. After reboot I set up EGL not to start with system and I'll be using only when installing and playing games...

    Was this answer helpful?

    0 comments