Custom Built PC Always BSODing

Toggle sidebar Toggle sidebar
S

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510
I have a custom built PC and either within an hour of gaming, 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. I have made sure all my drivers are up to date. I've ran a memtest on my ram and the results are at https://www.flickr.com/gp/135532782@N06/LZHc30
Please help me solve this problem because no matter what, I can't seem to fix it.
My PC specs 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

Minidumps:
1:
Dump File: 091715-5343-01.dmp
Crash Time: 9/17/2015 6:24:19 PM
Bug Check String: DRIVER_OVERRAN_STACK_BUFFER
bug check Code: 0x000000f7
Parameter 1: 00002a80`4fe3d4e0
Parameter 2: 0000e01e`c3c52d63
Parameter 3: ffff1fe1`3c3ad29c
Parameter 4: 00000000`00000000
Caused By Driver: ntoskrnl.exe
Caused By Address: ntoskrnl.exe+14e240
Processor: x64
Crash Address: ntoskrnl.exe+14e240
Full Path: C:\WINDOWS\Minidump\091715-5343-01.dmp
Processor Count: 4
Major Version: 15
Minor Version: 10240

2:
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

3:
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

The link to the previous thread is here. I had accidentally clicked on best answer for one of the solutions when I meant to reply so ignore that.
http://www.tomshardware.com/answers/id-2800305/bsod-custom-built.html
 
Solution
J
the second two errors are often related to errors coming from virutal memory system. IE errors reading pagefile.sys for example.

I would turn off the virtual memory in the system, delete the hidden system file c:\pagefile.sys
reboot and turn the pagefile back on.

guess, i would also check drive cables, make sure there is free space on the dirve, run crystaldiskinfo.exe to read the smart data from the drive.

the first bugcheck is a driver flowing its stack, I would update the ofending driver and run a malwarebytes scan because some malware will do this on purpose.

if you put the memory dumps on a server and post a link, often I can just give you the name of the bad drivers to update.

also, check your motherboard vendor for windows...
Sort by date Sort by votes
R

Rookie_MIB

Distinguished
Jul 27, 2013
1,970
10
20,965
I would say:

Step 1: disable all overclocks of CPU, RAM, and GPU
Step 2: reset BIOS to all 'defaults' (do a clear_cmos).
Step 3: disable all integrated hardware you aren't using.
Step 4: set your default boot drive (in case it was reset during the BIOS reset.
Step 5: save and reboot.

Get the system at the hardware level to run at complete stock to eliminate that as being a possibility due to a minor glitch in the OC. Then test things.
 
Upvote 0 Downvote
S

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510


I'm not over clocking at all.
 
Upvote 0 Downvote
S

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510


I installed windows 10 yesterday, having windows 7 before the new install.
 
Upvote 0 Downvote
S

Supernaafeh

Reputable
Jul 5, 2015
20
0
4,510


That is what I used to post all the details of the minidump files on here.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
the second two errors are often related to errors coming from virutal memory system. IE errors reading pagefile.sys for example.

I would turn off the virtual memory in the system, delete the hidden system file c:\pagefile.sys
reboot and turn the pagefile back on.

guess, i would also check drive cables, make sure there is free space on the dirve, run crystaldiskinfo.exe to read the smart data from the drive.

the first bugcheck is a driver flowing its stack, I would update the ofending driver and run a malwarebytes scan because some malware will do this on purpose.

if you put the memory dumps on a server and post a link, often I can just give you the name of the bad drivers to update.

also, check your motherboard vendor for windows 10 updates, many require specific driver updates for the lan and audio drivers.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom