Question Constant BSOD - SYSTEM_SERVICE_EXCEPTION | PAGE_FAULT_IN_NONPAGED_AREA

Jun 24, 2019
3
0
10
0
Having constant BSOD after installing new RAM.

On Mon 6/24/2019 7:45:51 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062419-6015-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFFCB2A1BCB8565)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFCB2A1BCB8565, 0xFFFFFC057AE1E0C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 6/24/2019 2:27:49 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062419-4734-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8023B641891)
Bugcheck code: 0x50 (0xFFFF91822DDF89E0, 0x0, 0xFFFFF8023B641891, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

On Mon 6/24/2019 2:04:20 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\062419-4890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BC8A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801617E07F7, 0xFFFFA082A7786700, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

These are the crash dumps, Ive tried just about all I could. Some help would be appreciated.

There is also about 5 more of the same thing.
Thanks
 
You wrote, "... after installing new RAM", but don't list a part number or link to the memory.

The problem is likely your choice of memory. The ntfs.sys file is crashing because of an incorrect or faulty RAM set-up.
 
Jun 24, 2019
3
0
10
0
You wrote, "... after installing new RAM", but don't list a part number or link to the memory.

The problem is likely your choice of memory. The ntfs.sys file is crashing because of an incorrect or faulty RAM set-up.
Sorry, I bought Corsair Vengeance RGB Pro (2x8) 16gb Set
 

ASK THE COMMUNITY

TRENDING THREADS