BSOD occuring randomly and oftenly, errors 0x109 0x50 0x0a

Silweis · 18 Nov 2012

Hi,

I built a brand new pc around 2-3 months ago, and just after 10 days or so, BSOD began appearing.
They appear totally randomly : when browsing internet, when nothin in particular, even during start up.
It can get to a dozen of times in less than a hour.

Basically it's a brand new computer with parts that I have assembled myself.
But after just 10 days, these BSOD began appearing.
I tried to reformat my computer, to change my hard disk, to check if my drivers were up to date, I also did a ram check... but nothing worked.
So I assume that there is either an incompatibility problem or a problem with one of the component.
I still have guarantee for each part but I would need to know which one has a problem.

I tried driver chec and Memtest86+ but it didn't detect anything wrong, so I've done some chkdsk /f /r but did not find anything that might explain those BSOD.

I have attached the file as requested.

Can someone figure out what is the source of the problem ?

Regards.

Arc · 18 Nov 2012

Welcome aboard.

Code:

******************************************************************************
*                                                                             *
*                        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: a3a039d89894054c, Reserved
Arg2: b3b7465eeb11e436, Reserved
Arg3: fffff880018153d0, 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:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

STACK_TEXT:  
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff8800181547f - ndis!memcmp+af
    [ 08:0a ]
1 error : !ndis (fffff8800181547f)

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

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight, per RAM module per slot.

Let us know the results.

Silweis · 21 Nov 2012

Results :

Memtest detected nothing wrong in 8 passes on the RAM.

Now, it even refuses to let me access Windows desktop. :/

Arc · 21 Nov 2012

Troubleshooting Windows 7 Failure to Boot

Try it.