Repeated Windows 10 Crashes BSOD

Question

Repeated Windows 10 Crashes BSOD

Kim Yuna 0

I’ve been dealing with repeated system crashes, and honestly, I’m exhausted from running the same troubleshooting steps over and over with no real solution. The crashes happen randomly, often when running demanding applications or gaming.

I’ve tried almost everything multiple times:

I’ve run sfc /scannow and chkdsk /f /r several times, but the crashes persist. I’ve reinstalled NVIDIA drivers using DDU, and even rolled back to older drivers, yet nothing changes. I also ran Windows Memory Diagnostic, and no issues were found. Additionally, I’ve checked for malware and unnecessary software, but the problem remains.

At this point, I’m really frustrated with repeatedly doing the same fixes without getting anywhere.If anyone has experienced similar issues or has alternative solutions, I’d really appreciate your insights.

Thanks in advance!

Geoff McKenzie 865 Reputation points

2025-03-18T01:07:38.0633333+00:00

Hi Kim.

May I suggest providing more information.

Start by providing the bug check codes (available in event logs hopefully). There should be a stop code and 4 parameters.

Also, if there is a dump file created, you can analyse the dump file which may reveal clues as to the casue.

E.g. WHEA type errors may point to Hardware/overheating or other codes may reference a driver or other software by name and/or the stack trace in the dump may reveal a likely culprit.

Good luck
Kim Yuna 0 Reputation points

2025-03-18T04:23:43.09+00:00

Hi Geoff,

Thanks for your suggestion! I've analyzed the minidump files and found multiple bug checks, including KERNEL_SECURITY_CHECK_FAILURE, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and MEMORY_MANAGEMENT.
Geoff McKenzie 865 Reputation points

2025-03-18T04:50:10.07+00:00

Hi Kim,

Can you please provide the 4 parameters of the Bug check information.

When I have a look at just the bug check codes (without the parameter infromation and without the stack trace information), it could be a number of causes.

E.g. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management

My intuition is you may have a suspect memory module (my personal history with 7E and 1A has been probably 60% hardware 35% third-party driver). But could be anything.

The parameters and stacktrace from the dump may help IF they are consistent (review multiple dumpfiles).

When not consistent I lean towards Memory/RAM. I see you have run Windows Memory Diagnostics which is a good start. It may be worth running a memory diagnostics tool outside of windows. See if your harware vendor provides a tool. Some BIOS come with a tool you may be able to use.

Also, if you have mutiple RAM modules, consult your main board manual, and see if you can remove half of them. Run diags and the game, then swap over to the other half. See if errors happen more or less often on each set (remembering that the system will be under greater load with half the RAM).

Finally, in rare cases, I have seen similar errors created by a dodgy CPU/mainboard. In this case there is very little consistency between the error codes, parameters and indicated caller in the stack traces. Again, see if you can find tools from the mainboard vendor/BIOS and or CPU manufacturer.

Good luck
Kim Yuna 0 Reputation points

2025-03-18T05:00:19.6733333+00:00

Hi Geoff,

Thanks for your response! Here are the bug check codes along with their four parameters from the minidump analysis:

KERNEL_SECURITY_CHECK_FAILURE (0x139)

Parameters: 0x4, 0xFFFFAD8D82B47240, 0xFFFFAD8D82B47198, 0x0

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (0x1000007E)

Parameters: 0xFFFFFFFFC0000005, 0xFFFFF80325B03B71, 0xFFFFF981AA1796F8, 0xFFFFE5816FD52920

MEMORY_MANAGEMENT (0x1A)

Parameters: 0x403, 0xFFFFFC7E3F0FFF60, 0xA000001D2C4E867, 0xFFFFFC0C54000460

TIMER_OR_DPC_INVALID (0xC7)

Parameters: 0x8, 0x1, 0xFFFFB1025A191D50, 0x100000

PAGE_FAULT_IN_NONPAGED_AREA (0x50)

Parameters: 0xFFFFF8020753F410, 0x0, 0xFFFFF8021754D6BC, 0x0

2 answers

Your answer

Geoff McKenzie 865 Reputation points

2025-03-18T01:07:38.0633333+00:00

Hi Kim.

May I suggest providing more information.

Start by providing the bug check codes (available in event logs hopefully). There should be a stop code and 4 parameters.

Also, if there is a dump file created, you can analyse the dump file which may reveal clues as to the casue.

E.g. WHEA type errors may point to Hardware/overheating or other codes may reference a driver or other software by name and/or the stack trace in the dump may reveal a likely culprit.

Good luck
Kim Yuna 0 Reputation points

2025-03-18T04:23:43.09+00:00

Hi Geoff,

Thanks for your suggestion! I've analyzed the minidump files and found multiple bug checks, including KERNEL_SECURITY_CHECK_FAILURE, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, and MEMORY_MANAGEMENT.
Geoff McKenzie 865 Reputation points

2025-03-18T04:50:10.07+00:00

Hi Kim,

Can you please provide the 4 parameters of the Bug check information.

When I have a look at just the bug check codes (without the parameter infromation and without the stack trace information), it could be a number of causes.

E.g. https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x139--kernel-security-check-failure

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management

My intuition is you may have a suspect memory module (my personal history with 7E and 1A has been probably 60% hardware 35% third-party driver). But could be anything.

The parameters and stacktrace from the dump may help IF they are consistent (review multiple dumpfiles).

When not consistent I lean towards Memory/RAM. I see you have run Windows Memory Diagnostics which is a good start. It may be worth running a memory diagnostics tool outside of windows. See if your harware vendor provides a tool. Some BIOS come with a tool you may be able to use.

Also, if you have mutiple RAM modules, consult your main board manual, and see if you can remove half of them. Run diags and the game, then swap over to the other half. See if errors happen more or less often on each set (remembering that the system will be under greater load with half the RAM).

Finally, in rare cases, I have seen similar errors created by a dodgy CPU/mainboard. In this case there is very little consistency between the error codes, parameters and indicated caller in the stack traces. Again, see if you can find tools from the mainboard vendor/BIOS and or CPU manufacturer.

Good luck
Kim Yuna 0 Reputation points

2025-03-18T05:00:19.6733333+00:00

Hi Geoff,

Thanks for your response! Here are the bug check codes along with their four parameters from the minidump analysis:

KERNEL_SECURITY_CHECK_FAILURE (0x139)

Parameters: 0x4, 0xFFFFAD8D82B47240, 0xFFFFAD8D82B47198, 0x0

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (0x1000007E)

Parameters: 0xFFFFFFFFC0000005, 0xFFFFF80325B03B71, 0xFFFFF981AA1796F8, 0xFFFFE5816FD52920

MEMORY_MANAGEMENT (0x1A)

Parameters: 0x403, 0xFFFFFC7E3F0FFF60, 0xA000001D2C4E867, 0xFFFFFC0C54000460

TIMER_OR_DPC_INVALID (0xC7)

Parameters: 0x8, 0x1, 0xFFFFB1025A191D50, 0x100000

PAGE_FAULT_IN_NONPAGED_AREA (0x50)

Parameters: 0xFFFFF8020753F410, 0x0, 0xFFFFF8021754D6BC, 0x0

Answer 1

Hi Geoff,

Thanks for your response! Here are the bug check codes along with their four parameters from the minidump analysis:

KERNEL_SECURITY_CHECK_FAILURE (0x139)

Parameters: 0x4, 0xFFFFAD8D82B47240, 0xFFFFAD8D82B47198, 0x0

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (0x1000007E)

Parameters: 0xFFFFFFFFC0000005, 0xFFFFF80325B03B71, 0xFFFFF981AA1796F8, 0xFFFFE5816FD52920

MEMORY_MANAGEMENT (0x1A)

Parameters: 0x403, 0xFFFFFC7E3F0FFF60, 0xA000001D2C4E867, 0xFFFFFC0C54000460

TIMER_OR_DPC_INVALID (0xC7)

Parameters: 0x8, 0x1, 0xFFFFB1025A191D50, 0x100000

PAGE_FAULT_IN_NONPAGED_AREA (0x50)

Parameters: 0xFFFFF8020753F410, 0x0, 0xFFFFF8021754D6BC, 0x0

Answer 2

Geoff McKenzie 865

Hi Kim,

The fact that there is so much inconsitency in the errors indicates to me you have a hardware issue.

I cannot tell from these results if it is Memory/CPU or Main board.

Not all the codes you have above are shown in the references I linked above but Here are some of them....

KERNEL_SECURITY_CHECK_FAILURE (0x139) Parameters: 0x4, (doco reason "reserved")

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (0x1000007E), Parameters: 0xFFFFFFFFC0000005 (doco reason "0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.")

MEMORY_MANAGEMENT (0x1A) Parameters: 0x403 (Doco Reason "The page table and page frame numbers (PFNs) are out of sync. The error probably is a hardware error, especially if parameters 3 and 4 differ by only one bit")

So I will stick with my recommendations above regarding Hardware checks with non windows tools BIOS/Hardware vendor(s). And swapping memory. That is how I would try to narrow it down.

Good Luck

Kim Yuna 0 Reputation points

2025-03-18T05:40:42.5566667+00:00

Hi Geoff,

I ran MemTest earlier this morning, and I have some results to share.
Geoff McKenzie 865 Reputation points

2025-03-18T10:08:06.5633333+00:00

Hi Kim,

It looks like there are errors in there.

You may want to swap memory as described in the following video/article and/or try a newer version of memtest.

https://www.memtest86.com/troubleshooting.htm

Regards,

Geoff
Kim Yuna 0 Reputation points

2025-03-18T10:54:11.67+00:00

okay i'l try it thanks
Geoff McKenzie 865 Reputation points

2025-03-19T03:44:45.33+00:00

Let me know how you go - I am interested to see what you work out.
Kim Yuna 0 Reputation points

2025-03-19T04:09:52.1933333+00:00

this the result sir
Geoff McKenzie 865 Reputation points

2025-03-19T04:25:09.9633333+00:00

Did you do a test with both sticks of RAM in? Did that pass as well?

I am making an assumption that the above is two separate tests of each of your two 8Gb sticks of RAM.
Kim Yuna 0 Reputation points

2025-03-19T04:45:16.53+00:00

yes , im gonna buy a pair of new ram and gonna test it
Geoff McKenzie 865 Reputation points

2025-03-25T22:45:05.99+00:00

Hi Kim, How did you go with the new RAM?

Share via

Repeated Windows 10 Crashes BSOD

2 answers

Your answer