1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Bugcheck error

Discussion in 'Legacy Windows' started by markdui, 2007/03/26.

  1. 2007/03/26
    markdui

    markdui Inactive Thread Starter

    Joined:
    2007/03/26
    Messages:
    1
    Likes Received:
    0
    Any help with this would be appreciated. Being trying to figure this for awhile

    Microsoft (R) Windows Debugger Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [H:\Symbol\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*H:\Symbol*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 2000 Kernel Version 2195 (Service Pack 4) MP (2 procs) Free x86 compatible
    Product: Server
    Kernel base = 0x80400000 PsLoadedModuleList = 0x80485b00
    Debug session time: Thu Mar 22 10:51:56.000 2007 (GMT+8)
    System Uptime: 0 days 1:00:48.750
    Loading Kernel Symbols
    .....................Page 9d75 not present in the dump file. Type ".hh dbgerr004" for details
    ..................................................................................
    Loading User Symbols

    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {c0000005, f669946f, 1, 0}

    *** ERROR: Module load completed but symbols could not be loaded for otman5.sys
    Probably caused by : disk.sys ( disk!DiskDeviceControl+10ba )

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

    0: 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: c0000005, The exception code that was not handled
    Arg2: f669946f, The address that the exception occurred at
    Arg3: 00000001, Parameter 0 of the exception
    Arg4: 00000000, 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:
    disk!DiskDeviceControl+10ba
    f669946f c70001000000 mov dword ptr [eax],1

    EXCEPTION_PARAMETER1: 00000001

    EXCEPTION_PARAMETER2: 00000000

    WRITE_ADDRESS: 00000000

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x1E

    PROCESS_NAME: System

    EXCEPTION_RECORD: f685b84c -- (.exr fffffffff685b84c)
    ExceptionAddress: f669946f (disk!DiskDeviceControl+0x000010ba)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000001
    Parameter[1]: 00000000
    Attempt to write to address 00000000

    CONTEXT: f685b4a4 -- (.cxr fffffffff685b4a4)
    eax=00000000 ebx=88ba0e68 ecx=00000000 edx=00000000 esi=88ef30e8 edi=00000000
    eip=f669946f esp=f685b914 ebp=f685b900 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    disk!DiskDeviceControl+0x10ba:
    f669946f c70001000000 mov dword ptr [eax],1 ds:0023:00000000=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from f642216e to f669946f

    STACK_TEXT:
    f685b968 f642216e 88ef3030 88ba0e00 88ef3030 disk!DiskDeviceControl+0x10ba
    f685b980 8041eec9 88ef3030 88ba0e68 88ef3ee0 CLASSPNP!ClassAsynchronousCompletion+0x48
    f685b994 f6819d80 88ef3ee0 88ba0e68 88ba0e68 nt!IopfCallDriver+0x35
    f685b9b8 8041eec9 88ef3f98 88ba0e68 88ef3ce0 PartMgr!PmDeviceControl+0x8c
    f685b9cc f69006f4 88ef3ce0 88ba0e68 00000000 nt!IopfCallDriver+0x35
    f685b9f4 8041eec9 88ef3ce0 88ba0e68 88ef3740 Diskperf!DiskPerfDeviceControl+0x186
    f685ba08 bff19f42 88ba0f44 88ba0f68 88ba0f44 nt!IopfCallDriver+0x35
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f685ba2c bff14914 88ef3740 88ba0e68 002d1100 otman5+0xbf42
    f685baf8 bff12d35 88ef3740 88ba0e68 00000001 otman5+0x6914
    f685bb10 8041eec9 88ef3740 88ba0e68 8042cbe0 otman5+0x4d35
    f685bb24 f6424846 86bdc448 88ef3030 89063da0 nt!IopfCallDriver+0x35
    f685bd68 80421619 88ef3030 88ef3740 80478cfc CLASSPNP!GlobalPrintBufferSize+0x8c6
    f685bd78 80417b47 86bdc448 00000000 00000000 nt!IopProcessWorkItem+0xf
    f685bda8 80457838 86bdc448 00000000 00000000 nt!ExpWorkerThread+0xaf
    f685bddc 8046c8e6 80417a98 00000001 00000000 nt!PspSystemThreadStartup+0x54
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    FOLLOWUP_IP:
    disk!DiskDeviceControl+10ba
    f669946f c70001000000 mov dword ptr [eax],1

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: disk

    IMAGE_NAME: disk.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 3e25b9c9

    SYMBOL_NAME: disk!DiskDeviceControl+10ba

    STACK_COMMAND: .cxr 0xfffffffff685b4a4 ; kb

    FAILURE_BUCKET_ID: 0x1E_W_disk!DiskDeviceControl+10ba

    BUCKET_ID: 0x1E_W_disk!DiskDeviceControl+10ba

    Followup: MachineOwner
     
  2. 2007/03/29
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    Refer the following problem.
    http://www.windowsbbs.com/showthread.php?t=48569


     

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.