Windows 7 Ultimate x64 - Blue Screen Crashing w/Debug


  1. Posts : 2
    Windows 7 Utlimate 64bit
       #1

    Windows 7 Ultimate x64 - Blue Screen Crashing w/Debug


    Hello all,

    I have a Windows 7 machine that is constantly crashing on me with a Bluescreen and I'm not quite sure what the issue might be.

    Here is the following crashdump report from Windows Debugger:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\Barry\Desktop\041210-27046-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\debug*Symbol information
    Executable search path is:
    Windows 7 Kernel Version 7600 UP Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a4d000 PsLoadedModuleList = 0xfffff800`02c8ae50
    Debug session time: Mon Apr 12 05:36:54.945 2010 (UTC - 6:00)
    System Uptime: 0 days 5:10:12.382
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff80002ac608d, 0, ffffffffffffffff}

    Probably caused by : ntkrnlmp.exe ( nt!KiCommitThreadWait+20d )

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

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ac608d, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

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


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    nt!KiCommitThreadWait+20d
    fffff800`02ac608d c3 ret

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf50e0
    ffffffffffffffff

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    BUGCHECK_STR: 0x1E_c0000005

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: chrome.exe

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from fffff80002afea17 to fffff80002abef00

    STACK_TEXT:
    fffff880`055a4f98 fffff800`02afea17 : 00000000`0000001e ffffffff`c0000005 fffff800`02ac608d 00000000`00000000 : nt!KeBugCheckEx
    fffff880`055a4fa0 fffff800`02abe542 : fffff880`055a5778 fffff900`c01558c0 fffff880`055a5820 fffffa80`02fa7890 : nt! ?? ::FNODOBFM::`string'+0x460da
    fffff880`055a5640 fffff800`02abce4a : 3d2ef357`93c76730 3d2ef357`93c76730 3fe62e42`fefa3800 3d2ef357`93c76730 : nt!KiExceptionDispatch+0xc2
    fffff880`055a5820 fffff800`02ac608d : 00fff800`02ac9ac1 fffff880`055a5b68 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
    fffff880`055a59b8 00fff800`02ac9ac1 : fffff880`055a5b68 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiCommitThreadWait+0x20d
    fffff880`055a59c0 fffff880`055a5b68 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`01d28170 : 0xfff800`02ac9ac1
    fffff880`055a59c8 00000000`00000000 : 00000000`00000000 00000000`00000001 fffffa80`01d28170 fffff880`02b0aade : 0xfffff880`055a5b68


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiCommitThreadWait+20d
    fffff800`02ac608d c3 ret

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: nt!KiCommitThreadWait+20d

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

    FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!KiCommitThreadWait+20d

    BUCKET_ID: X64_0x1E_c0000005_nt!KiCommitThreadWait+20d

    Followup: MachineOwner
    ---------
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    Hello Welcome to SF !!

    We need the Dump files to more troubleshooting https://www.sevenforums.com/crash-loc...d-problem.html

    - Captain
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:27.
Find Us