stack-protector: Kernel stack is corrupted

Hardware Support
1

Hey, I've been chasing a hardware problem for a while and I'm stuck. Here's the whole story.

It started on Windows — random crashes with MEMORY_MANAGEMENT (0x1A) errors. The Windows Memory Diagnostic came back saying the computer has a memory problem, so I started testing.

The laptop has 2 usable RAM slots. Here's what I found testing sticks one at a time:

  • ADATA stick #4438 in slot 1: passed
  • ADATA stick #4438 in slot 2: failed
  • ADATA stick #4461 in slot 1: failed
  • New Kingston stick in slot 1: passed

So I figured slot 2 was dead and just ran the new Kingston stick alone in slot 1. That seemed fine for a while.

Now I'm running Zorin OS 18 (Ubuntu-based) on the same machine, still with just the Kingston in slot 1, and I got this:

KERNEL PANIC!
Please reboot your computer.
stack-protector: Kernel stack is corrupted in: schedule_hrtimeout_range_clock+0x116/0x128

A few extra details that might matter:

  • dmesg shows no EDAC memory errors, but the RAM is non-ECC so I don't think EDAC would catch anything anyway
  • The BIOS throws a bunch of ACPI errors on every boot (AE_TYPE / AE_AML_BUFFER_LIMIT)
  • I've also seen web pages render completely broken (no CSS, text overlapping), which makes me wonder if files are getting corrupted on disk

What's bugging me is that the same class of failure shows up on Windows AND Linux, with a brand new stick, in the slot that supposedly tested fine. At this point I suspect the memory controller or the motherboard itself rather than the RAM.

Does that sound right? Is there anything else worth testing before I take it to a repair shop? Thanks!

WhatsApp Image 2026-07-23 at 08.38.27
WhatsApp Image 2026-07-23 at 08.38.271600×1200 81 KB

2

Most likely this is due to memory failure....you can at start hit esc key or tab key to get into the grub screen then move down to the memtest 86 and see if it see something there.... maybe a memory module is failing or cpu might be or even a motherboard failure.. but start with basics run the mem test and see what it shows and post results here...Please

Ans also did you update to the 7.0 kernel and this happened maybe also try choosing a differnt kernel and see if that solves the problem

3

Welcome to the Forum!

Try to boot in the older 6.17 Kernel and check if it still happens. To do that, choose on the GRUB Menu ''Advanced Options'' and there choose the one with the 6.17 Kernel and without ''Recovery Mode''.

Also: Are Secure Boot and Fast Boot in BIOS disabled? Is Fast Start-Up in Windows disabled?

1 Like
4

I would just install 1 memory module in your computer since some motherboards do not like mixed memory brands or types. In addition you can test the memory modules one at a time in your computer until you find the bad memory module causing your issues.

1 Like