Computer Keeps Crashing.. Please Help

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680
I have had 15 crashes in the past week+few days. I have tried updating drivers, look on the internet and checked Microsoft website. I can figure it out.. thank you for your help!

Side note, I don't have my graphics card yet. (I am trying to download everything and get really for it, so i can play my game sooner.) Could that be the problem?

My Build:
http://pcpartpicker.com/user/tpskate/saved/Ng7G3C

The Bug Check Codes are:

0x00..
(Code) (Number of times) (Date)
D1 (1) 2/6/2015

A (2) 1/31/2015--2/2/2015

7A (1) 2/6/2015

1A (3) 1/31/2015--2/1/2015--2/2/2015

50 (6) 1/31/2015--2/7/2015

109 (2) 2/9/2015

Each one has had a problem with this file, ntoskrnl.exe, but there were three crashes that had to do with other files too, those are:

(Code)--(File)--(Date)
0x000000d1--afd.sys--2/6/2015

0x0000000a--tcpip.sys--1/31/2015

0x00000050--hal.dll--2/7/2105

If you need more info, I can try to get it.

Thank you for your help!
 
Solution
Almost certainly either bad RAM, or something memory related. Pretty much every BSOD being generated can be caused by a problem in the memory subsystem, and the fact all of them are getting spat out pretty much confirms it. There's either a problem with a RAM module, a RAM slot on the motherboard, or some other memory related problem.

Memtest is good at finding "hard" failures in RAM, but there's some failure modes it doesn't pick up reliably. As a test, run the system with only ONE of the sticks of RAM. Does the problem go away? If not, swap sticks, but use a different motherboard slot. If the problem occurs with each stick of RAM individually in two different physical slots, then there's likely a motherboard/settings problem...

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680


I have done a clean install since I posted this, but I am still getting crashes. I went ahead and ran the program. Here are the results.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 2/13/2015 11:12:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-6614-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x50 (0xFFFFFAB0051E302B, 0x0, 0xFFFFF800034BC79F, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 2/13/2015 11:12:22 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x50 (0xFFFFFAB0051E302B, 0x0, 0xFFFFF800034BC79F, 0x5)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 2/13/2015 10:28:59 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-6302-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x40C5F)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 standard 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.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680


As I posted the last reply, it crashed again. Here is the report for that one.

On Sat 2/14/2015 12:05:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-5288-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000376760, 0x4AC004018DEFD005, 0xFFFFFA800A7A65B0)
Error: MEMORY_MANAGEMENT
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 a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680


ok, so just to be sure. I take one out, Memtest. then replace with the other and memtest? and does it matter on the slot they are in?
 

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680


Alright, so I ran the test for each RAM, one at a time, and they both passed with a 100%
 

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680
Here is the new crash report.

On Sat 2/14/2015 3:28:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-5803-01.dmp
This was probably caused by the following module: afd.sys (afd+0x49DEF)
Bugcheck code: 0xD1 (0xFFFFF50014E6EC6D, 0x2, 0x1, 0xFFFFF880046DCDEF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 standard 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.
 
Almost certainly either bad RAM, or something memory related. Pretty much every BSOD being generated can be caused by a problem in the memory subsystem, and the fact all of them are getting spat out pretty much confirms it. There's either a problem with a RAM module, a RAM slot on the motherboard, or some other memory related problem.

Memtest is good at finding "hard" failures in RAM, but there's some failure modes it doesn't pick up reliably. As a test, run the system with only ONE of the sticks of RAM. Does the problem go away? If not, swap sticks, but use a different motherboard slot. If the problem occurs with each stick of RAM individually in two different physical slots, then there's likely a motherboard/settings problem.

Another thing to check is BIOS settings. I assume the RAM is running stock settings, correct timings, and the PC is not in any way OCd?
 
Solution

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680
also, I was running memtest again last night, in different slots, and it froze after 2 passes and 2 hours 40 minutes. there is no reason it should freeze, right? or is that just another crash?
 

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680


ok I ran both RAM modules, in two seprate slots. I played portal 2 to test them (it only requires 2GB of ram) and they both crashed before i hit 5 minutes (from boot up).

So i amuse I am to check the BIOS settings now. No it isn't OCd. I only changed one thing in the BIOS RAM settings. It read the RAM as 1600 and it is supposed to be 2133, so I changes that.
 

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680
ohh.. I didn't know that the CPU had that... My RAM is 2133 so I amused to to be ok if i changed it. I Just changed it to auto, which turns is back to 1600. I did the same portal 2 test and it work perfectly. I even played a few more test chambers to be sure.

So, sorry for the inconvenience. This was all user error.. I hope. Maybe this will help someone in the future.

Thank you for all your help!
 

MrTaylor

Honorable
Aug 28, 2014
100
0
10,680


I will let you know! I played for the longest time yesterday and no crash! It feels really good.