Resolve server crashes with memory management errors on WS C246M PRO Series motherboard

draft · equipment servermemory

Generated by docuprocessor (prompt article/v3) · 2026-04-22 07:01

Source thread

thread_id: spaces/AAAA05BdS6s/threads/Icr1dfZE7KY · 7 msgs · first 2024-05-25 · participants: Tech ATech BTech C

Tech A 2024-05-25 18:49

@all Hey guys, for Court DDS, their server has been crashing since yesterday, under different error codes, it seems to me that it might be a memory issue, tried to apply updates yesterday but it seems like that failed and it crashed twice again today, any ideas? is not a Dell server so can't use Server admin to check accurately, I think is custom built or not sure, Mobo is WS C246M PRO Series

Tech A 2024-05-25 18:49

(no text)

image/png 2024-05-25 12_45_20-Window.png

Two Windows crash reports from **5/25/2024 at 10:54:31 AM** show **Bugcheck code 0x1A** with parameters **(0x41792, 0xFFFFA07D85A02938, 0x2000000000, 0x0)**, identified as **MEMORY\_MANAGEMENT**. The first dump is a **Minidump** (`C:\Windows\Minidump\052524-20015-01.dmp`) and the second is a **Kernel memory dump** (`C:\Windows\MEMORY.DMP`). Both reports share identical bugcheck codes, names, descriptions, and analysis text noting a **corrupted PTE (Page Table Entry)** detected.

Tech A 2024-05-25 18:49

(no text)

image/png 2024-05-25 12_45_41-Window.png

Two Windows crash dump reports are visible. The first crash occurred on **5/25/2024 at 4:25:16 AM** with bugcheck code **0x1A (0x41792, 0xFFFF9C0000353208, 0x1000000000, 0x0)**, named **MEMORY_MANAGEMENT**, dump file: `C:\Windows\Minidump\052524-19125-01.dmp`. The second crash occurred on **5/24/2024 at 1:29:57 PM** with bugcheck code **0x3B (0xC0000005, 0xFFFFF801307C01D9, 0xFFFB20D92BA6E20, 0x0)**, named **SYSTEM_SERVICE_EXCEPTION**, dump file: `C:\Windows\Minidump\052424-21062-01.dmp`; a third dump file `052424-78359-01.dmp` is noted as corrupt at the bottom of the screen.

Tech A 2024-05-25 18:49

(no text)

image/png 2024-05-25 -212_45_41-Window.PNG

**Windows Event Viewer – System Log, Event ID 1001, BugCheck Error** A remote session (via LogMeIn) to a machine named **GAJJAR – SERVER** shows Event Viewer open on the **System** log, displaying **69,018 events**. The selected error entry (5/24/2024, 11:31:27 AM, Source: BugCheck, Level: Error, Event ID: 1001) reads: *"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffff9893d2f644a4, 0x0000000000000002, 0xfffff8032cf33f54, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: df13923c-ec64-476c-b7df-fa0085d2c3cd."* Computer name reported is **Server**, logged at 11:31:27 AM on 5/24/2024.

Tech B 2024-05-25 19:02

Lately we are having a bunch of server issues. I guess we need to try testing memory sticks. Maybe taking 1 out or bringing replacement sticks.

Tech A 2024-05-25 22:18

Just confirming, should I send this to operations ?

Tech C 2024-05-26 15:51

yes

---
title: "Resolve server crashes with memory management errors on WS C246M PRO Series motherboard"
category: equipment
tags: ["server", "memory"]
source_thread_id: "spaces/AAAA05BdS6s/threads/Icr1dfZE7KY"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T07:01:01"
participants: ["Tech A", "Tech B", "Tech C"]
---

# Resolve server crashes with memory management errors on WS C246M PRO Series motherboard

## Problem
A server with WS C246M PRO Series motherboard experienced multiple crashes over two days with different error codes indicating memory issues. The crashes included MEMORY_MANAGEMENT errors (bugcheck code 0x1A) with corrupted PTE (Page Table Entry) detection, SYSTEM_SERVICE_EXCEPTION errors (bugcheck code 0x3B), and PAGE_FAULT_IN_NONPAGED_AREA errors (bugcheck code 0x50). Windows updates attempted prior to the crashes failed, and the server continued crashing twice more the following day. The server is custom-built rather than a Dell system, preventing use of Dell Server Administrator for hardware diagnostics.

## Resolution
1. Test memory modules by removing one stick at a time to isolate faulty RAM
2. Bring replacement memory sticks to swap out potentially defective modules
3. Escalate to operations team for hardware replacement if memory testing confirms hardware failure

The issue was identified for escalation to operations based on the pattern of memory-related crashes and the need for physical hardware intervention.

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/Icr1dfZE7KY`
- Attachments:
  - ![2024-05-25 -212_45_41-Window.PNG](../attachments/Icr1dfZE7KY.-BL8fica0J8/2024-05-25 -212_45_41-Window.PNG) — **Windows Event Viewer – System Log, Event ID 1001, BugCheck Error**
  - ![2024-05-25 12_45_20-Window.png](../attachments/Icr1dfZE7KY.Gpp8GEgqsoY/2024-05-25 12_45_20-Window.png) — Two Windows crash reports from **5/25/2024 at 10:54:31 AM** show **Bugcheck code 0x1A** with parameters **(0x41792, 0xFFFFA07D85A02938, 0x2000000000, 0x0)**, identified as **MEMORY\_MANAGEMENT**. The first dump is a **Minidump** (`C:\Windows\Minidump\052524-20015-01.dmp`) and the second is a **Kernel memory dump** (`C:\Windows\MEMORY.DMP`). Both reports share identical bugcheck codes, names, descriptions, and analysis text noting a **corrupted PTE (Page Table Entry)** detected.
  - ![2024-05-25 12_45_41-Window.png](../attachments/Icr1dfZE7KY.MG1V1xm3T2c/2024-05-25 12_45_41-Window.png) — Two Windows crash dump reports are visible. The first crash occurred on **5/25/2024 at 4:25:16 AM** with bugcheck code **0x1A (0x41792, 0xFFFF9C0000353208, 0x1000000000, 0x0)**, named **MEMORY_MANAGEMENT**, dump file: `C:\Windows\Minidump\052524-19125-01.dmp`. The second crash occurred on **5/24/2024 at 1:29:57 PM** with bugcheck code **0x3B (0xC0000005, 0xFFFFF801307C01D9, 0xFFFB20D92BA6E20, 0x0)**, named **SYSTEM_SERVICE_EXCEPTION**, dump file: `C:\Windows\Minidump\052424-21062-01.dmp`; a third dump file `052424-78359-01.dmp` is noted as corrupt at the bottom of the screen.

Generated article

draft