BSOD on Custom Built PC

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510
I have a custom built PC and either within an hour of gamin, or around two hours of idling, my pc crashes with a BSOD. This has been happening since I built my PC. After running several tests I thought it could have been the motherboard so I had it replaced but the problem still occurs. All these occurred while using windows 7 so I updated to windows 10. Overnight while I was downloading windows updates I got another BSOD. The info of it is:
Dump File: 091615-7453-01.dmp
Crash Time: 9/16/2015 1:56:28 AM
Bug Check String: MEMORY_MANAGEMENT
bug check Code: 0x0000001a
Parameter 1: 00000000`00061941
Parameter 2: 00000000`6024f000
Parameter 3: 00000000`0000000f
Parameter 4: ffffd000`22444b00
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+14cc20
Processor: x64
Crash Address: ntoskrnl.exe+14cc20
Full Path: C:\WINDOWS\Minidump\091615-7453-01.dmp
Processor Count: 4
Major Version: 15
Minor Version: 10240

My PC parts are:
Graphics Card: GTX GeForce 960 2GB
Motherboard: MSI Z97s SLI Krait Edition
Processor: i5-4690k LGA1150
Memory: Corsair Force LS 120GB SSD
Memory: Corsair XMS3 2 x 4GB DDR3 1333 MHz ram sticks
Memory: Seagate Barracuda 1TB HDD
OS: Windows 10

If someone could explain to me what that bsod means and/or how to fix this issue, I would greatly appreciate it.
 

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510


I've ran the memtest before but that was over a month ago and had no issues running it for around four hours, however, I'll do it again. How long should I run the test this time?
 

blue_smoke

Honorable
Nov 10, 2013
720
0
11,160


24hrs
 

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510


Alright, I'll post back after the test is over.
 

Greg Gregorich

Distinguished
Feb 13, 2014
887
0
19,060
:
??!??!! LOL. OMG.i fol out of my chear :D

 
system is complaining of a PDE Page Directory Entry is corrupted. Used to track where data is located in memory and how it maps to virutal memory.

This can be a general memory errror, it can be corruption by a 3rd party driver. It can be a bad spot on your drive where c:\pagefile.sys is located.
it can be bad SATA drivers, or any thing to do with storage like firmware.

noramaly, you update the BIOS to a current version, or reset it to defaults then run memtest86. If it works as expected, then you boot windows,
start cmd as an admin then run
sfc.exe /scannow (to check for corrupt files)
then you would want to run
dism.exe /online /cleanup-image /restorehealth

this will go to microsoft servers and fix any corrupted core files you might have.
(if you did a windows 10 update it reports corruption found for everyone, dont worry too much about it)

after you run that you want to run a malwarebytes scan.

if you still have problems or don't find any problems, then you should put your memory dump file on a server and have it looked at.
It is very common for 3rd party utilities to corrupt data in memory and cause system crashes. Many people can not find the bad drivers and just do a clean install of windows 10 after it has been activated. Be sure to pick up driver updates from your motherboard vendor. Many put updates right after windows 10 shipped. (some machines require custom versions of drivers to work correctly, often to work around bugs in the version of a chipset on your motherboard)
 

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510


I accidentally clicked "Best Soltion" so please ignore that. Something I wanted to ask was that you said to upload my dump file on a server to have it looked at. What server and where would I go to upload it?
 

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510
I got two more blue screens. Once when playing Counter-Strike. The other while on YouTube. The descriptions of both of those are:
1:
Dump File: 091715-5234-01.dmp
Crash Time: 9/17/2015 2:57:59 PM
Bug Check String: MEMORY_MANAGEMENT
bug check Code: 0x0000001a
Parameter 1: 00000000`00061941
Parameter 2: 00000000`06477720
Parameter 3: 00000000`0000000d
Parameter 4: ffffd000`20d46b00
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+14e240
Processor: x64
Crash Address: ntoskrnl.exe+14e240
Full Path: C:\WINDOWS\Minidump\091715-5234-01.dmp
Processor Count: 4
Major Version: 15
Minor Version: 10240

2:
Dump File: 091715-5906-01.dmp
Crash Time: 9/17/2015 3:52:42 PM
Bug Check String: MEMORY_MANAGEMENT
bug check Code: 0x0000001a
Parameter 1: 00000000`00041284
Parameter 2: 00000000`0cf73000
Parameter 3: 00000000`00003b57
Parameter 4: fffff580`10804000
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+14e240
Processor: x64
Crash Address: ntoskrnl.exe+14e240
Full Path: C:\WINDOWS\Minidump\091715-5906-01.dmp
Processor Count: 4
Major Version: 15
Minor Version: 10240

If you could help me solve this issue I would really appreciate it. If not, could you tell me where to go and what to do to fix this.
 

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510


Since yesterday I asked to borrow my friends' RAM sticks. I've been using them instead of mine and since then everything has ran smoothly. Now do you know how I can test if the problem with my RAM sticks was a compatibility issue or whether or not they were faulty?
 
all you can do is update the BIOS to a current version or reset it to defaults
then run memtest86 to confirm it works as expected. If it fails then you have to look up the specifications of the RAM modules and confirm that the BIOS has correct settings (or slower settings) for your RAM. Then run the memtest86 again.
Sometimes you can pull RAM sticks out and run the tests to try to isolate/find a bad RAM stick or Slot on your motherboard. Then replace that RAM stick. Each slot on the motherboard may have slightly different timings, generally the closest the ram slot is to the CPU the faster it can be run. It is very common for people to buy RAM that specifies a 2T command clock cycles where the motherboard put in a 1 T clock cycle.
These are part of the secondary timings and often people just don't check the RAM for proper timing.
Often, motherboard BIOS updates update these default secondary timings after the motherboard is released. It is why you may want to update your BIOS before you start testing. (the other reason is to remove any automatic memory overclocks some BIOS versions provide)