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!

mine didn't either and it crashed anyway uring browsing or just idling on desktop. I don't see the sleep config as a solution.

This clock/voltage change theory lines up with my experience. I just went a week without a blue screen, but the catch was my computer never went into sleep mode during that time . Something was keeping it awake. I decided to try manually putting it to sleep and it just restarted instead. Now I am back to finding the compute rebooted itself overnight. I tried another manual sleep and it restarted again. It sure seems like this has something to do with various power saving modes combined with something that changed in Windows updates pushed out in January.

I have the EXACT same problem. A temporary fix is to disable the BOOSTING feature of your CPU in your bios. I was BSOD multiple per day before, now it hasn't BSOD for over a week.

Same with me, using High Performance doesn't fix it. BSOD still showed up. Come on Microsoft, fix your problem!!!

Still crashing after February 9, 2021— KB4601319 (OS Builds 19041.804 and 19042.804) update. or they don't know or they don't care. Every day i see more of this problems but for some reason, there is almost no media coverage.

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-12T15:53:46+00:00

mine didn't either and it crashed anyway uring browsing or just idling on desktop. I don't see the sleep config as a solution.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-12T14:26:17+00:00

This clock/voltage change theory lines up with my experience. I just went a week without a blue screen, but the catch was my computer never went into sleep mode during that time . Something was keeping it awake. I decided to try manually putting it to sleep and it just restarted instead. Now I am back to finding the compute rebooted itself overnight. I tried another manual sleep and it restarted again. It sure seems like this has something to do with various power saving modes combined with something that changed in Windows updates pushed out in January.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-10T06:48:33+00:00

I have the EXACT same problem. A temporary fix is to disable the BOOSTING feature of your CPU in your bios. I was BSOD multiple per day before, now it hasn't BSOD for over a week.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-10T02:19:21+00:00

Same with me, using High Performance doesn't fix it. BSOD still showed up.

Come on Microsoft, fix your problem!!!
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-09T23:31:25+00:00

Still crashing after February 9, 2021—KB4601319 (OS Builds 19041.804 and 19042.804) update.

or they don't know or they don't care. Every day i see more of this problems but for some reason, there is almost no media coverage.
Was this answer helpful?

0 comments No comments