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 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...

What do you mean by "max performance"? It's Razer high performance or Windows high performance?

As far as I can tell, it might affect single units only. I have 3600, and it had this problem. It is also rather unlikely that you would get a CPU from the same batch, as the batches are rather small, numbering in less than 40 units, IIRC. And about 10% (or more) of the cores are rejected as faulty/damaged... On related note, change of power plan still works for me... Ok. Great info. The power plan was changed from the control panel or amd ryzen Master? I tried tweaking from control panel(Even bios) but it didnt work (it showed as ryzen high performance in CP, is that what you are talking about or should i look somewhere else?).many thanks!

As far as I can tell, it might affect single units only. I have 3600, and it had this problem. It is also rather unlikely that you would get a CPU from the same batch, as the batches are rather small, numbering in less than 40 units, IIRC. And about 10% (or more) of the cores are rejected as faulty/damaged... On related note, change of power plan still works for me...

Okay, switching power plan to the one with max performance worked, for now at least. No BSODs, no random freezes. It increases CPU clocks and adjusts voltages to provide performance, of course. But it also doesn't changes them back to eco mode, or at least changes them much less. Other things that help: When installing Nvidia GPU drivers, choosing advanced mode, "Clean install" and installing only graphics driver and PhysX driver decreases number of BSODs. Clock locking works, and one can lock them at any frequency, not only base one. Temperature/cooling is the limiting factor. W10 can't mess up frequency switchover when it can't bypass BIOS/Chipset lock. Changing CPU to different model might work for some. CPUs are not created equal, it's the nature of manufacturing process. The spread of parameters can be quite wide. Just google for "BC547 datasheet" (it's a common bipolar transistor) and check the "DC Voltage gain" parameter - it differs from unit to unit, despite the fact entire batch is made on a single silicon die the size of small plate. And CPU transistors are much, much smaller in size than this common single transistor. I was considering a downgrade to Windows 7 too, as this issue is only on Win10, and I have licence for both. I'll keep you informed. Thanks for the info. In your point 3, when You said "changing cpu", it's referred to a different model or it could be the same one but from a different batch? I did that (i know, i told You) changing my 3600xt for a 3600 and it kinda worked BUT right now the cpu is on rma and i'm afraid that they Will give me a brand new 3600xt (same model, probably different batch). Thanks.

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-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
Anonymous

2021-02-08T08:00:10+00:00

What do you mean by "max performance"? It's Razer high performance or Windows high performance?
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-08T06:23:01+00:00

As far as I can tell, it might affect single units only. I have 3600, and it had this problem. It is also rather unlikely that you would get a CPU from the same batch, as the batches are rather small, numbering in less than 40 units, IIRC. And about 10% (or more) of the cores are rejected as faulty/damaged...

On related note, change of power plan still works for me...

Ok. Great info. The power plan was changed from the control panel or amd ryzen Master? I tried tweaking from control panel(Even bios) but it didnt work (it showed as ryzen high performance in CP, is that what you are talking about or should i look somewhere else?).many thanks!
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-08T06:13:22+00:00

As far as I can tell, it might affect single units only. I have 3600, and it had this problem. It is also rather unlikely that you would get a CPU from the same batch, as the batches are rather small, numbering in less than 40 units, IIRC. And about 10% (or more) of the cores are rejected as faulty/damaged...

On related note, change of power plan still works for me...
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-07T18:47:17+00:00
Okay, switching power plan to the one with max performance worked, for now at least. No BSODs, no random freezes. It increases CPU clocks and adjusts voltages to provide performance, of course. But it also doesn't changes them back to eco mode, or at least changes them much less.

Other things that help:

When installing Nvidia GPU drivers, choosing advanced mode, "Clean install" and installing only graphics driver and PhysX driver decreases number of BSODs.

Clock locking works, and one can lock them at any frequency, not only base one. Temperature/cooling is the limiting factor. W10 can't mess up frequency switchover when it can't bypass BIOS/Chipset lock.

Changing CPU to different model might work for some. CPUs are not created equal, it's the nature of manufacturing process. The spread of parameters can be quite wide. Just google for "BC547 datasheet" (it's a common bipolar transistor) and check the "DC Voltage gain" parameter - it differs from unit to unit, despite the fact entire batch is made on a single silicon die the size of small plate. And CPU transistors are much, much smaller in size than this common single transistor.

I was considering a downgrade to Windows 7 too, as this issue is only on Win10, and I have licence for both.

I'll keep you informed.
Thanks for the info. In your point 3, when You said "changing cpu", it's referred to a different model or it could be the same one but from a different batch? I did that (i know, i told You) changing my 3600xt for a 3600 and it kinda worked BUT right now the cpu is on rma and i'm afraid that they Will give me a brand new 3600xt (same model, probably different batch). Thanks.
Was this answer helpful?

0 comments No comments