Blue Screens 0x109 CRITICAL_STRUCTURE_CORRUPTION

mbalzar said:

Hi everyone,

I've been getting BSODs recently on my desktop. They've all been the same code - as above. I'm running Windows 7 Home Premium x64.

I've run Memtest86+ (about 6 hours, 4 passes) and Windows Memory Diagnostic and have not found any errors in my memory.

Attached are my minidumps. Any help would be greatly appreciated.

These are still pointing to memory corruption.

If you are overclocking-stop

I would continue testing with memtestx86 qnd run a system file check
(type cmd in search>right click and run as admin>sfc /scannow)

It might also be a heat, or power supply issue. I would download cpu-z, and gpu-z (both free) to keep an eye on the temps

You might also want to find out how rum power your video card needs and how much the psu can supply to the video rail.


Let us know if you need help

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 (3)\041010-16536-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\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 Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Fri Apr  9 21:27:11.105 2010 (GMT-4)
System Uptime: 0 days 0:19:39.791
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d899ab55e1, b3b7465eec28280f, fffff80002d9e8ec, 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: a3a039d899ab55e1, Reserved
Arg2: b3b7465eec28280f, Reserved
Arg3: fffff80002d9e8ec, 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 fffff80002ad6f00

STACK_TEXT:  
fffff880`031a85d8 00000000`00000000 : 00000000`00000109 a3a039d8`99ab55e1 b3b7465e`ec28280f fffff800`02d9e8ec : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002d9eb11 - nt!PspInsertThread+225
    [ 98:18 ]
1 error : !nt (fffff80002d9eb11)

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

Bug Check 0x109: CRITICAL_STRUCTURE_CORRUPTION

Thanks for the quick replies.

Anyway, everything is running at stock speed - nothing is overclocked.

I ran memtestx86 for another 10 passes. No errors have come up. Also ran the system file check and no problems were found. The RAM is Corsair DDR3-1333 (PC3-10600) (2x2gb).

Current temperatures are (at idling)
AMD Phenom II X4 965: 31 degrees Celsius
Radeon 5770: 30.5 degrees Celsius

At load
AMD Phenom II X4 965: 51 degrees
Radeon 5770: 77 degrees (Furmark)

So I don't think heat is the cause..especially since I can stress test my computer without any difficulty. Most of the Blue screens have occurred with minimal system load (e.g. MS Word, Foobar2000, Windows Live Messenger and Mozilla Firefox running).

The power supply is a Zalman ZM600-HP 600W ATX. This can supply 12VDC to the GPU. I'm not sure how to find out how much the GPU needs but I think that is enough?

Also, is it possibly a driver issue? I was using a Netgear WG111v2 and this appears to have non-Windows 7 compatible drivers (which I just realised). Seems like a shot in the dark though, but I'm running my desktop cut off from the net to see if it is the problem.