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!

I think this problem will never been fixed if you not RMA the processor. Because the problem is in the processor it self, not because of the OS. In my case, after I found out this issue, I RMA it, then the problem gone away. Hope this help someone :) The issue with your theory is that it works perfectly fine in Linux (Ubuntu-based OS).

Changing Power supply idle control in BIOS from Current to Typical seem to have fixed it for me

The only solution for the moment that really stops BSODs is locking the CPU from BIOS to a fixed frequency.

It could be different problems that different people are having and not all the same root cause. Any system that is overclocked and brand new systems that don't have a track record of stability are automatically suspicious to me and may not be the same problem I have with my non-overclocked, previously stable machine. On the other hand, problems with dynamic voltage changes could present itself in different ways. Sleep probably drops the voltage levels on various rails on the mobo the same way that the mobo can dynamically change the voltage levels to meet performance needs while actively using the CPU. Coming out of sleep then boosts up the rails again giving another opportunity for something to go wrong? I don't know. I hope some experts are working on this. I see a lot more recent google search results for this problem than I did a couple weeks ago, so it seems to be pretty widespread. In the meantime, I have disabled sleep mode in BIOS and will see if I stop finding my computer rebooted in the morning.

I switched plan in control panel, and I used MS high performance, as I didn't install any additional software from AMD, Gigabyte, Nvidia, nor KFA2. It's usually a pile of useless bloat. Additionally Gigabyte Fusion software for changing colors can cause BSODs on its own due to faulty SMBus driver, and KFA2 1-click overclocking software is a piece of garbage... My next test will be installing Epic Games Launcher, as it was source of many BSODs too...

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-06-29T14:38:03+00:00

I think this problem will never been fixed if you not RMA the processor. Because the problem is in the processor it self, not because of the OS.

In my case, after I found out this issue, I RMA it, then the problem gone away. Hope this help someone :)

The issue with your theory is that it works perfectly fine in Linux (Ubuntu-based OS).
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2021-03-04T11:03:11+00:00

Changing Power supply idle control in BIOS from Current to Typical seem to have fixed it for me
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2021-02-18T08:30:30+00:00

The only solution for the moment that really stops BSODs is locking the CPU from BIOS to a fixed frequency.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2021-02-12T22:15:42+00:00

It could be different problems that different people are having and not all the same root cause. Any system that is overclocked and brand new systems that don't have a track record of stability are automatically suspicious to me and may not be the same problem I have with my non-overclocked, previously stable machine. On the other hand, problems with dynamic voltage changes could present itself in different ways. Sleep probably drops the voltage levels on various rails on the mobo the same way that the mobo can dynamically change the voltage levels to meet performance needs while actively using the CPU. Coming out of sleep then boosts up the rails again giving another opportunity for something to go wrong? I don't know. I hope some experts are working on this. I see a lot more recent google search results for this problem than I did a couple weeks ago, so it seems to be pretty widespread.

In the meantime, I have disabled sleep mode in BIOS and will see if I stop finding my computer rebooted in the morning.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2021-02-08T08:16:20+00:00

I switched plan in control panel, and I used MS high performance, as I didn't install any additional software from AMD, Gigabyte, Nvidia, nor KFA2. It's usually a pile of useless bloat. Additionally Gigabyte Fusion software for changing colors can cause BSODs on its own due to faulty SMBus driver, and KFA2 1-click overclocking software is a piece of garbage...

My next test will be installing Epic Games Launcher, as it was source of many BSODs too...
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments