View Single Post
11 Jul 2011  
MvdB

Windows 7 64b Ultimate
 
 

Hello Medic, welcome to SF!

You've lots of dmps... I haven't the time yet to check them all but a recent one struck me as I don't see it often. Quote copied below for future reference.

Lets try:

1. Does it crash if you run in Safe Mode. It's a bummer to do, I know, but helps as in a quick check if it is HW and/or basic W7 drivers.

2. If no problem in Safe Mode: SFC /SCANNOW Command - System File Checker

Post back with results... next step is a lot of testing...of hw.

HTML 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: a3a039d89912b695, Reserved
Arg2: b3b7465eeb8f85eb, Reserved
Arg3: fffff800028fb5d0, 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:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002489d00

STACK_TEXT:  
fffff880`023a75d8 00000000`00000000 : 00000000`00000109 a3a039d8`9912b695 b3b7465e`eb8f85eb fffff800`028fb5d0 : 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
---------
My System SpecsSystem Spec