PC keeps crashing randomly

Wonderclam

Distinguished
Jul 24, 2012
194
5
18,685
I have Windows 7 64-bit with all the latest updates. I have a Gigabyte Z77-D3H motherboard, 8GB of DDR3 RAM, intel i5 2500k CPU, EVGA Geforce GTX 570 videocard

My video drivers are up to date, all drivers are up to date. I get a blue screen randomly and the computer reboots. Here's the log from Windows:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFAE8006C61B2A
BCP2: 0000000000000000
BCP3: FFFFF8000F7CF62C
BCP4: 0000000000000007
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Anyone have any idea? I ran memtest86 and no problems.
 
Possibly one or more bad RAM modules. Test them with memtest86+ which runs from a bootable CD: http://www.memtest.org/.
Download the Pre-Compiled Bootable ISO (.zip), extract the ISO file and create a CD from it with IMGBurn: http://www.filehippo.com/download_imgburn/

Boot your faulty PC from that CD to launch the memory testing software.
 

Wonderclam

Distinguished
Jul 24, 2012
194
5
18,685
I keep getting this. THis is from WhoCrashed. Does anyone know what this means? Or can point out a section of this forum or another forum that has people who know? I'm getting desperate.

On Thu 11/1/2012 5:20:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\110112-24024-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0xFFFFFA8025D25010, 0x2, 0x1, 0xFFFFF8000F73C376)
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.