Hi
I installed Windows 7 Pro 64 bit a few weeks ago. And I have been having a few crashes.
Pretty sure this is driver related but am not able to interpret the mini dump. Can someone please have a look at the most recent file and help?
Would be really appreciated.
Many thanks.
Hi and welcome
this crash was pretty straight forward. Memory corruption. If this is a ine off BSOD i wouldn't worry. More info on this type of BSOD cn be found here http://www.carrona.org/bsodindx.html#0x00000109
I would
download memtestx86 and run it for at least 3 passes
run a system file check
type cmd in search>right click and run as admin> SFC /scannow
Let us know if you need help
Ken J+
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\010610-23937-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*d:\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.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c57e50 Debug session time: Wed Jan 6 12:00:57.912 2010 (GMT-5) System Uptime: 0 days 0:02:00.662 Loading Kernel Symbols ............................................................... ................................................................ ........................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039d8956b85e7, b3b7465ee7e85825, fffff80002af5f73, 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: a3a039d8956b85e7, Reserved Arg2: b3b7465ee7e85825, Reserved Arg3: fffff80002af5f73, 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 fffff80002a8bf00 STACK_TEXT: fffff880`031a15d8 00000000`00000000 : 00000000`00000109 a3a039d8`956b85e7 b3b7465e`e7e85825 fffff800`02af5f73 : nt!KeBugCheckEx STACK_COMMAND: kb CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt fffff80002af5f95 - nt! ?? ::FNODOBFM::`string'+240e2 [ 44:40 ] 1 error : !nt (fffff80002af5f95) 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 ---------
Quote