Windows 10 BSOD System Service Exception and other crashes during LAN File transfer

Question

Crash List.pdf

Lately my PC has been crashing when I attempt to move data from my HDD to a local Synology NAS that is networked mapped. I'm attaching the report of the last two minidumps created by a software called BlueScreenView.

Answer 1

Thanks, was able to open both BlueScreenView screenshots

They show 2 crashes

1. Crash on 2/24/2026

Bug Check String: SYSTEM_SERVICE_EXCEPTION

Bug Check Code: 0x0000003b

Caused By Driver: ntoskrnl.exe

Crash Address: ntoskrnl.exe+3fd5c0

kernel OS component was where the crash manifested, NOT necessarily the root cause

2. Crash on 2/19/2026

Bug Check String: (not shown in the screenshot, but Code)

Bug Check Code: 0x00000139

Caused By Driver: ntoskrnl.exe

Crash Address: ntoskrnl.exe+3fd5c0

This code indicates a kernel corruption or bad pointer/invalidation

---

Both crashes point to ntoskrnl.exe , the core Windows kernel , but that’s just where the system blew up, not necessarily the real cause.

Common causes behind these codes are:

For 0x3B SYSTEM_SERVICE_EXCEPTION

• Faulting drivers returning bad pointers to the kernel
• Invalid memory access during I/O (storage or network)
• Antivirus / filter driver conflicts

For 0x139 KERNEL_SECURITY_CHECK_FAILURE

• Memory corruption
• Faulty hardware (RAM / storage)
• Bad drivers exposing bad pointer/data to the kernel

In short: something at a lower layer (driver or hardware) is corrupting memory and crashing the system.

---

Is the problem presenting just from this computer ?

Answer 2

Thanks, I was able to open both the screenshots you attached.

Thy show:

1st Crash on 2/24/2026

Bug Check String: SYSTEM_SERVICE_EXCEPTION

Bug Check Code: 0x0000003b

Caused By Driver: ntoskrnl.exe

Crash Address: ntoskrnl.exe+3fd5c0

kernel OS component was where the crash manifested, NOT necessarily the root cause

2nd Crash on 2/19/2026

Bug Check String

Bug Check Code: 0x00000139

Caused By Driver: ntoskrnl.exe

Crash Address: ntoskrnl.exe+3fd5c0

This code indicates a kernel corruption or bad pointer/invalidation

---

Both crashes point to ntoskrnl.exe (core Windows kernel)

Common causes behind these codes are:

• For 0x3B SYSTEM_SERVICE_EXCEPTION

Faulting drivers returning bad pointers to the kernel

nvalid memory access during I/O (storage or network)

Antivirus / filter driver conflicts

• For 0x139 KERNEL_SECURITY_CHECK_FAILURE

Memory corruption

Faulty hardware (RAM / storage)

Bad drivers exposing bad pointer/data to the kernel

---

Is the problem presenting just utilizing this computer ?

Answer 3

Hi , Thank you for reaching out!

My name is Stefano and it’s my pleasure to assist you today.

---

I still don't see the minidump file referring to your files transfer failure between your computer internal HDD to your Synology NAS.

Please attach one of the following (whatever is easiest for you):

• Screenshots of BlueScreenView showing the last 2 crashes (with the Bug Check String, Bug Check Code, and Caused By Driver columns visible), or
• The actual minidump files from

C:\Windows\Minidump\ (you can zip them), or

Copy-paste the text report BlueScreenView generates.