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!

Nm, i went as far as 8 days w/o bsod and they came back altogether. There is no fix right now.

Yes, perhaps it's also MS to blame, but AMD needs to work together. And, in my case, why it's not a more widespread issue? Shouldn't all of the 3600xt be affected? I still think there nay hw something wrong with my cpu.

I got this problem several days ago. And I have done everything above, including change ram mhz to 2400 and disable cpu boost from bios Update bios to newest one. (Try to change RAM timing but I don't know how to overclock, so I give up this one) But still BSOD 2~4 times per day. Yesterday I tried to 1.update windows to newest again 2.use Device managent and DDU to uninstall my VGA driver (1650 super) and re-install it 3.replug my vga again Don't know why but it works well now. No BSOD for about 36 hours CPU: ryzen 3500x MB: MSI B450M-A Pro Max RAM: Crucial 8G 2666mhz * 2

It is not an AMD fault here, every time a new product is being released Microsoft and other OS companies needs to integrate the product in his drivers and updates in order to maintain compatibility. In your case maybe the 3600 have a proper software stability than 3600XT right now. Nowadays AMD CPUs are more profitable than Intel, but this is only my opinion based on how things turn out for each company. I'll blame Microsoft this time because of an update that does not work correctly, but I'm sure that they're on it and will solve the problem ASAP. Later edit : for all the people who encountered the problem please update us if you found a method to stop this without limiting the CPU's frequency from BIOS.

I do have the same issue. Just made my brand new PC last week and since then I encountered exactly the same BSOD problem due to ntoskrnl.exe +3f5780. In the first days I've got multiple BSODs like 15-30 per day. I recently modified the PSU Supply Idle Control (BIOS) from auto to Typical Current Idle and changed my RAM and It seems more stable (still 4-7 BSODs per day). I do have all the drivers, Windows and BIOS updates and everything updated anyway. My configuration: CPU: AMD Ryzen 7 3800XT 3.9GHz box MB: ASRock B550 Extreme4 RAM: 2x Corsair Vengeance LPX Black 16GB DDR4, 3000MHz, CL16 and 2x HyperX Fury 16GB(2x8GB) DDR4 PC4-25600 3200MHz CL16 HX432C16FB3K2/16 GPU: GIGABYTE GeForce GTX 780 Ti 3GB GDDR5 384-bit SSD: Kingston A2000, 1TB, NVMe, M.2 PSU: nJoy Woden 650, 650W Real Power, PFC Activ, 80 Plus Gold OS: Windows 10 At this point after I changed the GPU to be sure that is not an old GPU driver related problem in a brand new system, changed the RAM, did all the tests for memories, system files, or stress tests, not having any problem with cooling system and read almost everything related to this problem on such forums, I made my opinion that this problem is related to the newer Windows Updates. I'm almost sure that if I'm gonna install an older Windows (like an August 2020 edition or something) and don't apply the updates until now will work without being unstable. As far as I read in those forums and also this thread, everybody encountered this problem on brand new PCs (precisely brand new CPUs). If I'm not wrong and this issue exists because of an new Windows Update (November-December driver I guess) please release a new update that will solve this problem or at least give us a hotfix. Well, yes. I've made all of ghe above abd more (rma of gpu and m2, bios update, etc). Nothing worked. Even rolling back windows. The only thibg that showed some positive things was the cpu replacement (changing my 3600xt for a 3600). I've tested it for 18 hours w/o a crash, so i asked for rma of it. Its been more than a week since then, hopefully i will have an answer Next week. One thing i know, i wont ever buy amd again.

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-07T01:34:50+00:00

Nm, i went as far as 8 days w/o bsod and they came back altogether. There is no fix right now.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-07T01:29:33+00:00

Yes, perhaps it's also MS to blame, but AMD needs to work together. And, in my case, why it's not a more widespread issue? Shouldn't all of the 3600xt be affected? I still think there nay hw something wrong with my cpu.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-07T01:26:47+00:00

I got this problem several days ago.

And I have done everything above, including change ram mhz to 2400 and disable cpu boost from bios

Update bios to newest one.

(Try to change RAM timing but I don't know how to overclock, so I give up this one)

But still BSOD 2~4 times per day.

Yesterday I tried to

1.update windows to newest again

2.use Device managent and DDU to uninstall my VGA driver (1650 super) and re-install it

3.replug my vga again

Don't know why but it works well now. No BSOD for about 36 hours

CPU: ryzen 3500x

MB: MSI B450M-A Pro Max

RAM: Crucial 8G 2666mhz * 2
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-07T01:17:53+00:00

It is not an AMD fault here, every time a new product is being released Microsoft and other OS companies needs to integrate the product in his drivers and updates in order to maintain compatibility. In your case maybe the 3600 have a proper software stability than 3600XT right now.

Nowadays AMD CPUs are more profitable than Intel, but this is only my opinion based on how things turn out for each company.

I'll blame Microsoft this time because of an update that does not work correctly, but I'm sure that they're on it and will solve the problem ASAP.

Later edit: for all the people who encountered the problem please update us if you found a method to stop this without limiting the CPU's frequency from BIOS.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-07T00:19:22+00:00
I do have the same issue. Just made my brand new PC last week and since then I encountered exactly the same BSOD problem due to ntoskrnl.exe +3f5780.

In the first days I've got multiple BSODs like 15-30 per day. I recently modified the PSU Supply Idle Control (BIOS) from auto to Typical Current Idle and changed my RAM and It seems more stable (still 4-7 BSODs per day).

I do have all the drivers, Windows and BIOS updates and everything updated anyway.

My configuration:

CPU: AMD Ryzen 7 3800XT 3.9GHz box

MB: ASRock B550 Extreme4

RAM: 2x Corsair Vengeance LPX Black 16GB DDR4, 3000MHz, CL16 and 2x HyperX Fury 16GB(2x8GB) DDR4 PC4-25600 3200MHz CL16 HX432C16FB3K2/16

GPU: GIGABYTE GeForce GTX 780 Ti 3GB GDDR5 384-bit

SSD: Kingston A2000, 1TB, NVMe, M.2

PSU: nJoy Woden 650, 650W Real Power, PFC Activ, 80 Plus Gold

OS: Windows 10

At this point after I changed the GPU to be sure that is not an old GPU driver related problem in a brand new system, changed the RAM, did all the tests for memories, system files, or stress tests, not having any problem with cooling system and read almost everything related to this problem on such forums, I made my opinion that this problem is related to the newer Windows Updates.

I'm almost sure that if I'm gonna install an older Windows (like an August 2020 edition or something) and don't apply the updates until now will work without being unstable.

As far as I read in those forums and also this thread, everybody encountered this problem on brand new PCs (precisely brand new CPUs). If I'm not wrong and this issue exists because of an new Windows Update (November-December driver I guess) please release a new update that will solve this problem or at least give us a hotfix.
Well, yes. I've made all of ghe above abd more (rma of gpu and m2, bios update, etc). Nothing worked. Even rolling back windows. The only thibg that showed some positive things was the cpu replacement (changing my 3600xt for a 3600). I've tested it for 18 hours w/o a crash, so i asked for rma of it. Its been more than a week since then, hopefully i will have an answer Next week. One thing i know, i wont ever buy amd again.
Was this answer helpful?

0 comments No comments