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!

How about February's 24, 2021— KB4601382 (OS Builds 19041.844 and 19042.844) update? You still get BSOD after this update?

I've had very similar problems recently - multiple BSoDs per day, ntoskrnl.exe related at seemingly random times, and nothing so far seems to fix it. The KB4601382 update didn't seem to help at all. To an extent I'm glad that it's not just me with this issue because it sounds like it must be some kind of windows update problem but it also appears like nobody really knows the cause which is almost as frustrating as the actual problem! I just wish the audio would somehow auto-mute so I didn't have to experience the crash in such a visceral way. But that's just wishful thinking...

Try replacing the cpu. It worked for me.

I disabled updates until March 18th, just in case one of them breaks the system again. I'll look into disabling them until such a time, the problem gets fixed. I'd rather deal with outdated OS than with crashing one...

Unfortunately for me since I reinstalled Windows very recently it's either 1703 or 20H2. I guess I'll either clean reinstall again back to 1703 or try and rollback because the amount of BSoDs I have atm is frankly depressing. And from what I read from this thread and elsewhere, replacing the CPU might have worked for you it *shouldn't* be the solution for this problem that several people with different systems all seem to be experiencing in a short space of time. If I had the spare money for a replacement, I'd probably just go and get a new computer at this point.

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

Anonymous

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!

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

Anonymous

2021-02-28T13:05:24+00:00

How about February's 24, 2021—KB4601382 (OS Builds 19041.844 and 19042.844) update? You still get BSOD after this update?
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-28T17:46:48+00:00

I've had very similar problems recently - multiple BSoDs per day, ntoskrnl.exe related at seemingly random times, and nothing so far seems to fix it. The KB4601382 update didn't seem to help at all.

To an extent I'm glad that it's not just me with this issue because it sounds like it must be some kind of windows update problem but it also appears like nobody really knows the cause which is almost as frustrating as the actual problem!

I just wish the audio would somehow auto-mute so I didn't have to experience the crash in such a visceral way. But that's just wishful thinking...
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-28T18:01:30+00:00

Try replacing the cpu. It worked for me.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-28T18:01:39+00:00

I disabled updates until March 18th, just in case one of them breaks the system again. I'll look into disabling them until such a time, the problem gets fixed. I'd rather deal with outdated OS than with crashing one...
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-28T21:03:38+00:00

Unfortunately for me since I reinstalled Windows very recently it's either 1703 or 20H2. I guess I'll either clean reinstall again back to 1703 or try and rollback because the amount of BSoDs I have atm is frankly depressing.

And from what I read from this thread and elsewhere, replacing the CPU might have worked for you it *shouldn't* be the solution for this problem that several people with different systems all seem to be experiencing in a short space of time. If I had the spare money for a replacement, I'd probably just go and get a new computer at this point.
Was this answer helpful?

0 comments No comments