I need help - I'm getting memory BSOD errors!

FalloutSeeker

Reputable
Dec 27, 2014
62
0
4,630
Hi. Everytime I play games for a couple of hours, I get a BSOD relate to ram. I don't know the problem - I tried so many things. I have the dump files below.

On Tue 7/28/2015 4:42:37 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFC0087A9D8C10)
Bugcheck code: 0x50 (0xFFFFC0087A9D8C10, 0x0, 0xFFFFF801B99CC78B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA



On Mon 7/27/2015 10:16:50 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072715-26687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14D220)
Bugcheck code: 0xA (0xFFFFFA801BD29668, 0x2, 0x0, 0xFFFFF803660593EA)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.



On Mon 7/27/2015 7:26:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072715-26125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x151C56)
Bugcheck code: 0x9F (0x4, 0x12C, 0xFFFFE0000C695040, 0xFFFFF801595A69B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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.



On Sun 7/26/2015 10:20:27 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072615-31140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14D220)
Bugcheck code: 0x139 (0x3, 0xFFFFD00023366690, 0xFFFFD000233665E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 

FalloutSeeker

Reputable
Dec 27, 2014
62
0
4,630




I'm afraid it's going to slowly kill my PC like what happened the last time where it did so. The OS slowly gets buggy and then bam, OS is gone. This only happened when I installed Windows 10; maybe W-10 is having to be the issue? The dump files are all leading to a different area involving memory, though I replaced them and tested with Memtest and they were concluded fine. I need this issue solved before I risk losing my data (I made a restore point, that's good, right?)

Mobo: Gigabyte f2a78m-d3h

RAM: Crucial Ballistix Sport 4GB Single DDR3 1600 MT/s (PC3-12800) CL9 @1.5V UDIMM 240-Pin Memory Module BLS4G3D1609DS1S00

PSU: Seasonic 620w Bronze Evo M12 2 Edition

CPU: AMD A10-5800K Trinity Quad-Core 3.8GHz (4.2GHz Turbo) Socket FM2 100W AD580KWOHJBOX Desktop APU (CPU + GPU) with DirectX 11 Graphic AMD Radeon HD 7660D

GPU: Noted in CPU.
 

FalloutSeeker

Reputable
Dec 27, 2014
62
0
4,630



Alright. I changed the Dram
Voltage my 0.06. I didn't change the cpu voltage because it's not over clocked and I'm not sure exactly what it is (doesn't tell me.) I'll keep you posted
 

FalloutSeeker

Reputable
Dec 27, 2014
62
0
4,630


I did what you said. I can only put the CPU NB from 1800 to 1900 MHz. I'll try that and keep you posted
 

FalloutSeeker

Reputable
Dec 27, 2014
62
0
4,630


There's all vcore load line calibration and that's at auto. When I hit it, it brings up options for extreme, medium, low, and standard. Same as NBVID Loadline Calibration.
 

FalloutSeeker

Reputable
Dec 27, 2014
62
0
4,630




I don't have overdrive enabled though. Does it say that?


 

FalloutSeeker

Reputable
Dec 27, 2014
62
0
4,630


Also, this only happens when I'm on the computer for sometime. Usually when I start up the computer it flashes, as if the drivers can't load. The issue happens faster if I use my PC to game and I have to turn off my computer and wait awhile for it to sort itself and return itself to a somewhat stable performance.
 

TRENDING THREADS