Changing Power supply idle control in BIOS from Current to Typical seem to have fixed it for me
Recurring ntoskrnl.exe crashes and BSODs on a new PC with random BugCheck causes and different drivers - help needed!
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:
- DISM and SFC, multiple times. Found some corrupt files on two occasions, fixed them, no results.
- 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.
- Driver Verifier #2, this time it was AmdTools64.sys, removed all amd*.sys files just in case. Didn't help.
- Driver Verifier #3, Avast VM driver sys file this time. At that point I decided it's not the drivers, it's something else.
- 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.
- I checked temperatures, ran AIDA64 stability tests, ran Fumark test on GPU, no problems with that since PSU was replaced.
- 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.
102 answers
Sort by: Oldest
-
Anonymous
2021-03-04T11:03:11+00:00 -
Anonymous
2021-03-05T22:17:39+00:00 Same issue here. Only a year old high end custom build. Over the last month crashes daily. No overlocking, etc. No changes made other than windows updates.. ~
-
Anonymous
2021-03-08T05:04:33+00:00 Same issue ntoskrnl.exe+3f5a80. Just started having the crash after switching my fan and thermal paste. I can go a while without a crash, so i'm not sure what is causing it, i'm guessing a Windows update might have messed something up? Using a Ryzen 5 3600, Nvidia 2060 super.
-
Anonymous
2021-03-10T02:03:18+00:00 I have also been getting this issue intermittently over the last couple of days, today in particular it happened about three times, twice within an hour.
I have a Ryzen 2600X, and am on the latest BIOS version as well as the latest version of Windows
-
Anonymous
2021-03-19T02:40:52+00:00 Any update? still crashing?