Keep getting random BSOD

It's very random. Sometimes when I go afk, I'll come back with a message that says it recovered from a crash. This has been happening a lot lately; about twice a day. I get a BSOD sometimes, but not as much as lately.

Chaoz said:

It's very random. Sometimes when I go afk, I'll come back with a message that says it recovered from a crash. This has been happening a lot lately; about twice a day. I get a BSOD sometimes, but not as much as lately.

These were probably caused by memory corruption. I would download memtestx86 and run it for 5 passes

Let us know the results

Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\New folder (4)\030110-24086-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e4fe50
Debug session time: Mon Mar  1 20:58:45.702 2010 (GMT-5)
System Uptime: 0 days 5:24:32.622
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8962196a1, b3b7465ee89e68cf, fffff80002d3bce0, 1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8962196a1, Reserved
Arg2: b3b7465ee89e68cf, Reserved
Arg3: fffff80002d3bce0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

Debugging Details:
------------------


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002c83f00

STACK_TEXT:  
fffff880`031a15d8 00000000`00000000 : 00000000`00000109 a3a039d8`962196a1 b3b7465e`e89e68cf fffff800`02d3bce0 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002d3bd2c - nt!KeUpdateTotalCyclesCurrentThread+4c
    [ e2:ea ]
1 error : !nt (fffff80002d3bd2c)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

I ran it for one pass; I seriously didn't know it would take so long. I'll try again tomorrow.

Chaoz said:

I ran it for one pass; I seriously didn't know it would take so long. I'll try again tomorrow.

]

No errors on the first pass?

The reason for 5 passes is to bleed the memory and see if it breaks, and to test for heat issues


Ken

zigzag3143 said:

Chaoz said:

I ran it for one pass; I seriously didn't know it would take so long. I'll try again tomorrow.

]

No errors on the first pass?

The reason for 5 passes is to bleed the memory and see if it breaks, and to test for heat issues


Ken

No errors on the first pass