New
#1
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" at How to receive help diagnosing Blue Screens and Windows crashes, 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
System:
ASUS M4A78-E
Phenom II X4 2.8ghz
6gb Patriot Viper DDR2 1066 (3x2gb)
BFG GeForce 9800 GTX+ OC
Windows 7 x64 Ultimate
Intel X25-V 40gb SSD with Windows install
Seagate 1TB HDD for files
Code:-------------------------------------------------------------- Microsoft ฎ Windows Debugger Version 6.12.0002.633 AMD64 Copyright ฉ Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\051211-11247-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\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 Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Machine Name: Kernel base = 0xfffff800`02a5f000 PsLoadedModuleList = 0xfffff800`02c9ce50 Debug session time: Thu May 12 15:08:27.653 2011 (UTC - 4:00) System Uptime: 1 days 18:55:21.105 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039d89a5738c8, 0, fad470d4ba6ea2ed, 101} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 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 Patching Policy for x64-Based Systems 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 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 fffff80002acf740 STACK_TEXT: fffff880`031a85d8 00000000`00000000 : 00000000`00000109 a3a039d8`9a5738c8 00000000`00000000 fad470d4`ba6ea2ed : 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
Quote