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!

yes, i saw you on reddit. I am the one who asked you if this is a cpu problem or a code problem.

Repost from Reddit . These are things I found out: RAM profile settings have no effect. I'm waiting for thermal paste to test CPU voltage and frequency adjustment as a solution. The problem usually happens when watching movies via YouTube, or from HDD with MPC-HC. The only game that crashed the OS for me was Minecraft with metric ton of mods - it's both CPU and memory heavy. I played KSP 1.10.1 with metric ton of mods with no problems. Epic Game Store app causes even more BSODs. Almost no problems with Steam. Neither SFC, CHKDSK, nor DISM solves any problems. This is also not a RAM problem at all. Clean OS install doesn't solve it. Switching power profile in Windows power settings from AMD balanced to Microsoft balanced makes the OS slightly more stable. Slightly. The type/value of bugcheck error related to ntoskrnl, as far as I can tell, doesn't really matter. I did a bit debugging on the memory dumps Windows provides. It looks like ntoskrnl.exe messes up some data stored either in cache or in RAM. Usually some register data is missing from the dump. This data corruption happens on kernel level causing CPU/system to loose track of which program has which memory reserved, what interrupts are set up, and where code execution should go after tripping one or returning from Interrupt Service Routine, data structures get mangled. Dumps indicate that web browser is usually the victim, sometimes Steam app or EGS app, on rare occasions a driver gets chewed up too. I neither have skills nor source code to solve this problem. The suggestion that locking CPU clock might fix it points to the way clock boosting is managed by OS. I think the problem is caused by the way OS is handling the clock change. I think it goes like this (it's my idea supported only by my imagination and knowledge developed while programming 8-bit microcontrollers): Kernel registers a need for some clock boosting or throttling back. Kernel sends command to the hardware. It doesn't stop normal code execution. Hardware changes the clock and VCore accordingly. This happens between two clock cycles. If this happens while CPU is fetching data between cache and RAM or between cache and registers, data gets sometimes mangled due to sudden voltage change. This causes execution of current opcode command to go wrong. CPU detects problem, throws an error and halts normal code execution. It switches to Kernel Interrupt Service Routine for that error. Kernel ISR can't recover from data mangling, throws a bugcheck error and dumps memory. On reboot the clock and voltage is reset. Locking the clock causes hardware to ignore any clock change commands from Kernel. BIOS updates for some motheboards probably include a fix - hardware waits for completion of opcode command execution, locks the CPU, changes the clock and voltage, resumes. The way we do it with microcontrollers. Mind you, this is only my theory, and I have no proof to support it. For now the only solution is to lock the clock, update everything, including BIOS, and hope that M$ will fix their kernel-level software, as the solutions provided in firmware/drives provided by manufacturers are just workarounds for the root cause. If anyone wants, I can provide more minidumps and memdumps I collected since reinstalling the OS...

i'm on the same boat. 3600xt and a asrock b550 pg. It crashes on idle with that error code, problems started in december and tried a lot of thing, nothing worked. I'm not sure if the last windows uopdate revelaed a hardware problem or it's just a buggy MS code. Anyway, my PC is very unstable and almost unusable.

Hate to say I'm having the same problem. CPU is a Ryzen 5 3600, motherboard a MSI Tomahawk B450. Most of my dumps indicate ntoskrnl.exe +3f5780. Crashes are guaranteed if the computer is idle for a few hours.

My PC started crashing in the middle of the night while it was idle every night. It has always been pretty stable for the past year. I don't have any overclocking enabled. A few of these crashes have had dumps pointing to the same error: ntoskrnl.exe + 3f5780 Looking back, the crashes started immediately after Windows update applied KB4598242, KB4586876 and KB4598481 on Jan. 13th. I uninstalled the first two packages but was not allowed to uninstall KB459481. The problems continued after I uninstalled the first two. I have since reapplied those and all updates, including updating to 20H2 and all optional driver updates. I updated my BIOS to the latest and graphics drivers to the latest and still am crashing while idle once a day or so. System Info: CPU: Ryzen 7 3800X RAM: G.Skill Ripjaws V 3600MHz CL19 2x16GB Motherboard: ASRock X570 Steel Legend Wifi GPU: ASUS Radeon RX 5700 XT 8GB SSD: Intel 660p 1.02TB M.2-2280 NVMe PSU: EVGA 750W 80+ Gold OS: Windows 10 Home 10.0.19042 (currently)

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-01-27T18:05:37+00:00

yes, i saw you on reddit. I am the one who asked you if this is a cpu problem or a code problem.
Was this answer helpful?

0 comments No comments
Anonymous

2021-01-27T17:35:44+00:00
Repost from Reddit. These are things I found out:
1. RAM profile settings have no effect. I'm waiting for thermal paste to test CPU voltage and frequency adjustment as a solution.
2. The problem usually happens when watching movies via YouTube, or from HDD with MPC-HC. The only game that crashed the OS for me was Minecraft with metric ton of mods - it's both CPU and memory heavy. I played KSP 1.10.1 with metric ton of mods with no problems.
3. Epic Game Store app causes even more BSODs. Almost no problems with Steam.
4. Neither SFC, CHKDSK, nor DISM solves any problems. This is also not a RAM problem at all. Clean OS install doesn't solve it.
5. Switching power profile in Windows power settings from AMD balanced to Microsoft balanced makes the OS slightly more stable. Slightly.
6. The type/value of bugcheck error related to ntoskrnl, as far as I can tell, doesn't really matter. I did a bit debugging on the memory dumps Windows provides. It looks like ntoskrnl.exe messes up some data stored either in cache or in RAM. Usually some register data is missing from the dump. This data corruption happens on kernel level causing CPU/system to loose track of which program has which memory reserved, what interrupts are set up, and where code execution should go after tripping one or returning from Interrupt Service Routine, data structures get mangled. Dumps indicate that web browser is usually the victim, sometimes Steam app or EGS app, on rare occasions a driver gets chewed up too. I neither have skills nor source code to solve this problem.
7. The suggestion that locking CPU clock might fix it points to the way clock boosting is managed by OS. I think the problem is caused by the way OS is handling the clock change. I think it goes like this (it's my idea supported only by my imagination and knowledge developed while programming 8-bit microcontrollers):
- Kernel registers a need for some clock boosting or throttling back.
- Kernel sends command to the hardware. It doesn't stop normal code execution.
- Hardware changes the clock and VCore accordingly. This happens between two clock cycles.
- If this happens while CPU is fetching data between cache and RAM or between cache and registers, data gets sometimes mangled due to sudden voltage change.
- This causes execution of current opcode command to go wrong. CPU detects problem, throws an error and halts normal code execution. It switches to Kernel Interrupt Service Routine for that error.
- Kernel ISR can't recover from data mangling, throws a bugcheck error and dumps memory.
- On reboot the clock and voltage is reset.
Locking the clock causes hardware to ignore any clock change commands from Kernel. BIOS updates for some motheboards probably include a fix - hardware waits for completion of opcode command execution, locks the CPU, changes the clock and voltage, resumes. The way we do it with microcontrollers.

Mind you, this is only my theory, and I have no proof to support it.

For now the only solution is to lock the clock, update everything, including BIOS, and hope that M$ will fix their kernel-level software, as the solutions provided in firmware/drives provided by manufacturers are just workarounds for the root cause.

If anyone wants, I can provide more minidumps and memdumps I collected since reinstalling the OS...
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2021-01-27T16:42:14+00:00

i'm on the same boat. 3600xt and a asrock b550 pg. It crashes on idle with that error code, problems started in december and tried a lot of thing, nothing worked. I'm not sure if the last windows uopdate revelaed a hardware problem or it's just a buggy MS code. Anyway, my PC is very unstable and almost unusable.
Was this answer helpful?

0 comments No comments
Anonymous

2021-01-27T13:51:15+00:00

Hate to say I'm having the same problem. CPU is a Ryzen 5 3600, motherboard a MSI Tomahawk B450.

Most of my dumps indicate ntoskrnl.exe +3f5780. Crashes are guaranteed if the computer is idle for a few hours.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2021-01-27T13:31:34+00:00
My PC started crashing in the middle of the night while it was idle every night. It has always been pretty stable for the past year. I don't have any overclocking enabled. A few of these crashes have had dumps pointing to the same error: ntoskrnl.exe + 3f5780

Looking back, the crashes started immediately after Windows update applied KB4598242, KB4586876 and KB4598481 on Jan. 13th. I uninstalled the first two packages but was not allowed to uninstall KB459481. The problems continued after I uninstalled the first two. I have since reapplied those and all updates, including updating to 20H2 and all optional driver updates. I updated my BIOS to the latest and graphics drivers to the latest and still am crashing while idle once a day or so.

System Info:
- CPU: Ryzen 7 3800X
- RAM: G.Skill Ripjaws V 3600MHz CL19 2x16GB
- Motherboard: ASRock X570 Steel Legend Wifi
- GPU: ASUS Radeon RX 5700 XT 8GB
- SSD: Intel 660p 1.02TB M.2-2280 NVMe
- PSU: EVGA 750W 80+ Gold
- OS: Windows 10 Home 10.0.19042 (currently)
Was this answer helpful?

0 comments No comments