BSOD (New system)

[mcorrente]

I've got some occassional BSODs coming up on a new system. I don't have a problem RMA-ing hardware if necessary but I don't want to be sending in the wrong thing.

OS: Windows 7 Pro 64bit, OEM (installed by me)
System age: < 1 month
OS Install age: same

Any help would be appreciated. I'd love this to be a software/driver issue, but I don't think I'm that lucky. I've run memtest86 (my first experience with it, hopefully did it right) and didn't get any errors with all my modules in. Ran for 7+ cycles. Pretty sure I've updated all drivers, flashed motherboard, etc.

 

[wish]

Hi,
2 dmp = 0x1A (Memory Management)
1 dmp = 0x109 (CRITICAL_STRUCTURE_CORRUPTION)

It can be caused by bad RAM or 3rd drivers.
Have you tried memtest86 for each stick individually and with different slot?
Because the possibilities are:
- Mismatch pair of RAM
- Bad stick of RAM
- Bad motherboard slot
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Then I see you have several drivers that need to be updated:

WinRing0x64.sys Sat Jul 26 06:29:37 2008 → [URL="http://www.python.org/emacs/winring/"]WinRing[/URL]
SSLDrv.sys   Thu Jan 31 14:58:38 2008 → SSL VPN Net Extender 
spc1300.sys  Wed Dec 10 19:23:23 2008 → USB PC Camera 
spc1300c.SYS Sun Nov 09 23:14:15 2008 → USB PC Camera
phaudlwr.sys Wed May 07 02:40:14 2008 → [URL="http://www.support.philips.com/support/downloads.jsp?userLanguage=en&userCountry=gb"]Philips USB Audio Processing[/URL]
lmimirr.sys  Tue Apr 10 15:32:45 2007 → [URL="https://secure.logmein.com/US/home.aspx"]Miniport Driver or LogMeIn [/URL]
LMIRfsDriver.sys Mon Jul 14 09:26:56 2008 → [URL="https://secure.logmein.com/US/home.aspx"]Miniport Driver or LogMeIn[/URL]
RaInfo.sys   Fri Jan 04 10:57:14 2008 → LogMeIn/RemotelyAnywhere Kernel 
Rt64win7.sys Thu Feb 26 01:04:13 2009 → [URL="http://www.realtek.com.tw/downloads/"]Realtek NIC driver[/URL]
RTKVHD64.sys Fri Dec 25 02:41:24 2009 → [URL="http://www.realtek.com.tw/downloads/"]Realtek HD Audio[/URL]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a3a039d8a0e1453f, 0, 854c4196fec09310, 101}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

4: 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: a3a039d8a0e1453f, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 854c4196fec09310, 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

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


BUGCHECK_STR:  0x109

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002ebf740

STACK_TEXT:  
fffff880`033775d8 00000000`00000000 : 00000000`00000109 a3a039d8`a0e1453f 00000000`00000000 854c4196`fec09310 : nt!KeBugCheckEx


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  BAD_STACK

Followup: MachineOwner
---------

 

[mcorrente]

Thanks for the response. I'm re-running memtest now. I can't run on one module at a time because my bios won't even boot without memory installed in pairs. Here's what I'm doing (feel free to correct):

Step 1:
Module1 in Slot1
Module2 in Slot2

Step 2:
Module3 in Slot1
Module4 in Slot2

Step 3:
Module1 in Slot3
Module2 in Slot4

Step 4:
Module3 in Slot3
Module4 in Slot4

This all assumes I run 7 passes at each step with no error.

Regarding the drivers, there are some listed that I just downloaded from the mb manufacturer's website - does this list indicate that the drivers have a verified update available or simply that they appear to be old?

 

[mcorrente]

Alright, I think I might be lucky enough to have a RAM issue (as opposed to motherboard). Here's my memtest results. Note I forgot to write down the exact slots used for the first two runs, but all tests were run in the first two slots.

TEST  SLOT1       SLOT2       RESULT    SLOT1ERR   SLOT2ERR   PASSES
1     Module1     Module2     FAILED    1          1          4
2     Module3     Module4     SUCCESS                         7
3     Module3     Module1     FAILED    0          2          0
4     Module3     Module1     SUCCESS                         7
5     Module2     Module4     SUCCESS                         23
6     Module1     Module4     FAILED    1          1          1

I still need to test the other slots, but it seems like Module1 is the problem. Every time memtest failed, Module1 was in, and it never failed when Module1 wasn't in. The only question I have is that the errors per slot (as indicated by my list) indicate errors in the other slot at the same time in tests 1 and 6, but from what I read this doesn't necessarily mean that the module in that slot is bad because one bad module can cause errors in the other modules. Is that correct?

I still have to test the other slots overnight and want to run a longer test with Module3, but assuming both pass am I safe to assume my motherboard is fine and just RMA the bad module?

 

[wish]

You're doing good man
Yes, it seems your motherboard slot is fine.
So you need to find the bad module and RMA it.

 

[mcorrente]

Appreciate the help. Ran Module3 for about 20 passes with no problem. Popped in Module1 and got about 1500 errors before I could leave the room. Guess I got my answer.

Thanks for looking at the dump data and pointing me in the right direction.