You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

BSOD Help - Minidump included - First post

Hello.. this is my first post on any computer help website. I have been having BSOD error crashes for the last month and need to stop them from recurring. I have followed the steps on the "How to receive help diagnosing Blue Screens and Windows crashes" thread, and this is the text that is generated from WinDbg.

Can someone please help me make some sense of it? I have no idea what I am looking at. Thank you

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: a3a039d89a5738c8, Reserved
Arg2: 0000000000000000, Reserved
Arg3: fad470d4ba6ea2ed, Failure type dependent information
Arg4: 0000000000000101, 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

Thanks for the advice with memtest, but I bought all of the components for this computer used, so I did a thorough memtest after I bought the RAM to make sure it was good. The test came back with 0 errors every time. I have been running the same sticks in the same slots for almost 6 months now, and the crashes have only been occuring for about the last month. Any other ideas? Thanks again.

Here is a post I made on another website which may contain useful information: