TechSpot

Vista x86 Ultimate. BSOD- Freaky!

By harvsingh
May 7, 2007
  1. Hi all. I have a an Asus P5WD2-e Premium board running with a 2.66 Pentium D (805) 775 socket.

    2 GB Ram.

    2x 150 Sata 2 on PCI-e Raid Silicon Image 3132 Mirror
    4 x 300 Sata 2 running on Intel Raid 5. (900GB)

    I am getting intermittant BSOD. Sometimes.. no BSOD.. but just hangs,reset only to get it working.

    I am posting the 2 log files... as you can see.. different errors... where do i go? Thanks in advance for your help.

    Opened log file 'c:\debuglog.txt'
    1: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    1: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    Loading Kernel Symbols
    ...................................................................................................................................................................................
    Loading User Symbols

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

    KERNEL_STACK_INPAGE_ERROR (77)
    The requested page of kernel data could not be read in. Caused by
    bad block in paging file or disk controller error.
    In the case when the first arguments is 0 or 1, the stack signature
    in the kernel stack was not found. Again, bad hardware.
    An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
    C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
    the data could not be read from the disk due to a bad
    block. Upon reboot autocheck will run and attempt to map out the bad
    sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
    file is on a SCSI disk device, then the cabling and termination should be
    checked. See the knowledge base article on SCSI termination.
    Arguments:
    Arg1: c000009d, status code
    Arg2: c000009d, i/o status code
    Arg3: 00000000, page file number
    Arg4: 01955000, offset into page file

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


    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR: 0x77_c000009d

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 81ccc677 to 81cd85c9

    STACK_TEXT:
    836f7c2c 81ccc677 00000077 c000009d c000009d nt!KeBugCheckEx+0x1e
    836f7cb0 81cccacc c04161d8 000742f4 00000001 nt!MiMakeOutswappedPageResident+0x471
    836f7d38 81cccba2 84c854f8 836f7d58 00000000 nt!MiInPageSingleKernelStack+0x208
    836f7d6c 81cb3957 84c85568 00000000 836f7dc0 nt!KiInSwapKernelStacks+0x43
    836f7d7c 81e254a8 00000000 836fc680 00000000 nt!KeSwapProcessOrStack+0x83
    836f7dc0 81c9145e 81cb38d4 00000000 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiMakeOutswappedPageResident+471
    81ccc677 cc int 3

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4549ae00

    SYMBOL_NAME: nt!MiMakeOutswappedPageResident+471

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x77_c000009d_nt!MiMakeOutswappedPageResident+471

    BUCKET_ID: 0x77_c000009d_nt!MiMakeOutswappedPageResident+471

    ========================================================
    file 2

    Opened log file 'c:\debuglog.txt'
    1: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    1: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
    Loading Kernel Symbols
    ...................................................................................................................................................................................
    Loading User Symbols

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

    KERNEL_DATA_INPAGE_ERROR (7a)
    The requested page of kernel data could not be read in. Typically caused by
    a bad block in the paging file or disk controller error. Also see
    KERNEL_STACK_INPAGE_ERROR.
    If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
    it means the disk subsystem has experienced a failure.
    If the error status is 0xC000009A, then it means the request failed because
    a filesystem failed to make forward progress.
    Arguments:
    Arg1: c04beff8, lock type that was held (value 1,2,3, or PTE address)
    Arg2: c000009d, error status (normally i/o status code)
    Arg3: 58156860, current process (virtual address for lock type 3, or PTE)
    Arg4: 97dff1da, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


    OVERLAPPED_MODULE: Address regions for 'cdfs' and 'NAVENG.SYS' overlap

    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR: 0x7a_c000009d

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    TRAP_FRAME: 82c2fa50 -- (.trap 0xffffffff82c2fa50)
    .trap 0xffffffff82c2fa50
    ErrCode = 00000010
    eax=97dff1da ebx=00000000 ecx=86f49360 edx=00000000 esi=871637e8 edi=86f49320
    eip=97dff1da esp=82c2fac4 ebp=82c2faec iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
    netbt!TdiAddressDeletion:
    97dff1da 0000 add byte ptr [eax],al ds:0023:97dff1da=00
    .trap
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 81c1f7bd to 81cd85c9

    STACK_TEXT:
    82c2f8ac 81c1f7bd 0000007a c04beff8 c000009d nt!KeBugCheckEx+0x1e
    82c2f910 81c2a7d3 82c2f968 81d123c0 00000060 nt!MiWaitForInPageComplete+0x1df
    82c2f9c0 81caaf05 97dff1da 00000000 00000000 nt!MiDispatchFault+0xe07
    82c2fa38 81c8fa74 00000008 97dff1da 00000000 nt!MmAccessFault+0x1119
    82c2fa38 97dff1da 00000008 97dff1da 00000000 nt!KiTrap0E+0xdc
    82c2fac0 8c3d6a32 86f49360 86f49340 86b61720 netbt!TdiAddressDeletion
    82c2faec 8c3d6f01 8c3d91a0 86f49320 00000000 TDI!TdiNotifyPnpClientList+0x132
    82c2fb10 8c3d72f4 87965728 00000000 964ae338 TDI!TdiExecuteRequest+0x175
    82c2fb48 8c3d7547 00f49320 0000000c 82c2fbd4 TDI!TdiHandleSerializedRequest+0x1aa
    82c2fb58 964a711a 86f49320 00000010 82c2fc98 TDI!TdiDeregisterNetAddress+0xf
    82c2fbd4 964a7513 87885290 00000000 871a7498 tdx!TdxProcessAddressChangeRoutine+0x22e
    82c2fbf0 828682fa 00000000 82c2fc98 82c2fca0 tdx!TdxNaAddressChangeEvent+0x7d
    82c2fc58 99344480 82c2fc8c 81fa4f00 86fdf9a0 NETIO!NsiParameterChange+0x73
    82c2fcf8 99345877 86bb5128 870cf37c 82c2fd2c tcpip!IppNotifyAddressChangeAtPassive+0x12c
    82c2fd08 828634cd 86bb5128 81cfde3c 8717d6e0 tcpip!IppCompartmentNotificationWorker+0x11
    82c2fd2c 81d8c88c 8717d6e0 870cf37c 870f47c8 NETIO!NetiopIoWorkItemRoutine+0x2f
    82c2fd44 81c78e18 870f47c8 00000000 84c86d78 nt!IopProcessWorkItem+0x2d
    82c2fd7c 81e254a8 870f47c8 82c24680 00000000 nt!ExpWorkerThread+0xfd
    82c2fdc0 81c9145e 81c78d1b 00000001 00000000 nt!PspSystemThreadStartup+0x9d
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    TDI!TdiNotifyPnpClientList+132
    8c3d6a32 e981000000 jmp TDI!TdiNotifyPnpClientList+0x1b8 (8c3d6ab8)

    SYMBOL_STACK_INDEX: 6

    SYMBOL_NAME: TDI!TdiNotifyPnpClientList+132

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: TDI

    IMAGE_NAME: TDI.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP: 4549b346

    FAILURE_BUCKET_ID: 0x7a_c000009d_TDI!TdiNotifyPnpClientList+132

    BUCKET_ID: 0x7a_c000009d_TDI!TdiNotifyPnpClientList+132

    Followup: MachineOwner
    ---------
     
  2. cpc2004

    cpc2004 TS Rookie Posts: 2,044

    The analysis report tells you that it is disk hardware error.

    >>>>
    DISK_HARDWARE_ERROR: There was error with disk hardware
    <<<<
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.