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!

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.

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.

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.

Yep, also getting very random BSODs, all pointing to ntoskrnl.exe 3f5780 or 3f5a80, sometimes when i restart my PC, sometimes when i'm gaming, sometimes a while after i close a game. Those were the cases so far, my pc is also brand new. SPECS: AMD Ryzen 5 3600X Gigabyte X570 UD Nvidia GeForce RTX 3070 ASUS TUF 16gb (2x8) RAM Corsair Vengeance RGB PRO 3000mhz Adata XPG 256GB NVME SSD Seagate Barracuda 2TB HDD EVGA 650W 80GOLD PSU Win 10 2004 No manual overclocks, just the manufacter ones. No Hardware errors found so far, after some tests. Every driver, including Chipset and BIOS up to date. Also High Performance mode doesn't work here either, also i don't use any of the RGB software mentioned previously.

In sleep mode CPU is turned off completely. Chipset is controlling the state of keyboard/mouse connected to USB/PS2. CPU voltages and clocks are dropped to zero, GPU is turned off, the same goes for hard drives, SSDs and other peripherals. Only RAM is powered on. In hibernation RAM can be turned off because its contents are dumped to system drive... I never had BSODs or reboots related to sleep mode. I don't use "hibernate", and I turn my PC off each night, when I'm going to sleep. I think it's a spectrum of problems with different severity, because some solutions work for some people, but for some almost nothing helps. I don't know, if my fiddling with BIOS helped, or fiddling with CPU socket, or maybe it was only that "High performance" power profile. Still no more BSODs, but I forgot to install Epic Games Launcher...

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-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-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-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-13T05:03:32+00:00

Yep, also getting very random BSODs, all pointing to ntoskrnl.exe 3f5780 or 3f5a80, sometimes when i restart my PC, sometimes when i'm gaming, sometimes a while after i close a game. Those were the cases so far, my pc is also brand new.

SPECS:

AMD Ryzen 5 3600X

Gigabyte X570 UD

Nvidia GeForce RTX 3070 ASUS TUF

16gb (2x8) RAM Corsair Vengeance RGB PRO 3000mhz

Adata XPG 256GB NVME SSD

Seagate Barracuda 2TB HDD

EVGA 650W 80GOLD PSU

Win 10 2004

No manual overclocks, just the manufacter ones. No Hardware errors found so far, after some tests. Every driver, including Chipset and BIOS up to date. Also High Performance mode doesn't work here either, also i don't use any of the RGB software mentioned previously.
Was this answer helpful?

0 comments No comments
Anonymous

2021-02-13T06:11:37+00:00

In sleep mode CPU is turned off completely. Chipset is controlling the state of keyboard/mouse connected to USB/PS2. CPU voltages and clocks are dropped to zero, GPU is turned off, the same goes for hard drives, SSDs and other peripherals. Only RAM is powered on. In hibernation RAM can be turned off because its contents are dumped to system drive...

I never had BSODs or reboots related to sleep mode. I don't use "hibernate", and I turn my PC off each night, when I'm going to sleep. I think it's a spectrum of problems with different severity, because some solutions work for some people, but for some almost nothing helps. I don't know, if my fiddling with BIOS helped, or fiddling with CPU socket, or maybe it was only that "High performance" power profile. Still no more BSODs, but I forgot to install Epic Games Launcher...
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments