TechSpot

Bsod Help Please

By Bradan
Mar 2, 2007
  1. Hi im a new member and im desperate for help, so hi guys

    ive been having these bsod crashes since I got my new system

    specs:
    gigabyte 965p s3
    core2duo allendale 1.8ghz
    2x1gb corsair value ram -667
    160gb western digital caviar SATA
    X1950 pro (asus)
    LG DVD rom
    Nmedia 500watt (12v1@16 12v2@18 3.3v@36 5v@40a)

    more info up in 5 sorry about that
     
  2. Bradan

    Bradan TS Rookie Topic Starter

    ok so it crashes randomly, like once in 35 minutes.

    but it will crash repeatedly while im installing anything. I suspect the ram or the harddrive. hard to say so far.

    HERES SOME DUMP FILES:



    Loading Dump File [C:\WINDOWS\Minidump\Mini030207-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Fri Mar 2 00:54:03.593 2007 (GMT-5)
    System Uptime: 0 days 0:03:43.296
    Loading Kernel Symbols
    .................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7A, {c07ba670, c000000e, f74ce642, 12982860}

    Probably caused by : ftdisk.sys ( ftdisk!FtDiskInternalDeviceControl+51 )

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

    0: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: c07ba670, lock type that was held (value 1,2,3, or PTE address)
    Arg2: c000000e, error status (normally i/o status code)
    Arg3: f74ce642, current process (virtual address for lock type 3, or PTE)
    Arg4: 12982860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR: 0x7a_c000000e

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

    TRAP_FRAME: f7a72a64 -- (.trap fffffffff7a72a64)
    ErrCode = 00000010
    eax=00760018 ebx=860eb780 ecx=00000000 edx=00000000 esi=86589940 edi=00000000
    eip=f74ce642 esp=f7a72ad8 ebp=f7a72b2c iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    ftdisk!FtpReferenceDependantVolume:
    f74ce642 53 push ebx
    Resetting default scope

    LOCK_ADDRESS: 8055a4e0 -- (!locks 8055a4e0)

    Resource @ nt!PiEngineLock (0x8055a4e0) Available

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
    Lock address : 0x8055a4e0
    Thread Count : 0
    Thread address: 0x00000000
    Thread wait : 0x0

    LAST_CONTROL_TRANSFER: from 80514ce0 to 804f9c37

    STACK_TEXT:
    f7a72930 80514ce0 0000007a c07ba670 c000000e nt!KeBugCheckEx+0x1b
    f7a72960 8051584d 8109ba38 c07ba670 f74ce642 nt!MiWaitForInPageComplete+0x1ca
    f7a729e0 8051f347 c07ba670 f74ce642 c07ba670 nt!MiDispatchFault+0x2c1
    f7a72a4c 80543568 00000008 f74ce642 00000000 nt!MmAccessFault+0x877
    f7a72a4c f74ce642 00000008 f74ce642 00000000 nt!KiTrap0E+0xd0
    f7a72ad4 f74c551f 86589940 860eb780 00000000 ftdisk!FtpReferenceDependantVolume
    f7a72aec 804eeeb1 86589888 860eb780 00000000 ftdisk!FtDiskInternalDeviceControl+0x51
    f7a72afc f78acbd3 865cb3f8 86044000 00000000 nt!IopfCallDriver+0x31
    f7a72b2c f78ad97e 86589888 86532c68 86580940 PartMgr!PmQueryDependantVolumeList+0x83
    f7a72b74 f78ade8a 864e40d8 864808c4 86480984 PartMgr!PmBuildDependantVolumeRelations+0xd5
    f7a72ba0 f78ae00d 864e40d8 c00000bb 864809a8 PartMgr!PmQueryRemovalRelations+0x7f
    f7a72bdc 804eeeb1 864e4020 864808a8 f7a72c5c PartMgr!PmPnp+0x17c
    f7a72bec 80591823 00000003 86587ee8 f7a72c84 nt!IopfCallDriver+0x31
    f7a72c18 804f6b05 864e4020 f7a72c38 f7a72c84 nt!IopSynchronousCall+0xb7
    f7a72c60 805927f4 00000003 86580940 00000001 nt!IopQueryDeviceRelations+0x45
    f7a72c88 805933a9 00000000 00000003 00000001 nt!IopProcessRelation+0xfa
    f7a72cb0 80598c1a 86580940 00000003 f7a72d20 nt!IopBuildRemovalRelationList+0x41
    f7a72d3c 805993e6 f7a72d78 806e4974 e15a9390 nt!PiProcessQueryRemoveAndEject+0x262
    f7a72d58 8059953f f7a72d78 865a7680 8056375c nt!PiProcessTargetDeviceEvent+0x2a
    f7a72d7c 80537757 865a7680 00000000 865c2b30 nt!PiWalkDeviceList+0xfd
    f7a72dac 805ce794 865a7680 00000000 00000000 nt!ExpWorkerThread+0xef
    f7a72ddc 805450ce 80537668 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    ftdisk!FtDiskInternalDeviceControl+51
    f74c551f eb31 jmp ftdisk!FtDiskInternalDeviceControl+0x84 (f74c5552)

    SYMBOL_STACK_INDEX: 6

    SYMBOL_NAME: ftdisk!FtDiskInternalDeviceControl+51

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: ftdisk

    IMAGE_NAME: ftdisk.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 3b7d8419

    FAILURE_BUCKET_ID: 0x7a_c000000e_ftdisk!FtDiskInternalDeviceControl+51

    BUCKET_ID: 0x7a_c000000e_ftdisk!FtDiskInternalDeviceControl+51

    Followup: MachineOwner
    ---------
     
  3. Bradan

    Bradan TS Rookie Topic Starter

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini030207-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Fri Mar 2 14:31:27.875 2007 (GMT-5)
    System Uptime: 0 days 0:47:16.576
    Loading Kernel Symbols
    ................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck F4, {3, 863d01d8, 863d034c, 805d1142}

    Probably caused by : ntkrpamp.exe ( nt!PspCatchCriticalBreak+75 )

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

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

    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 00000003, Process
    Arg2: 863d01d8, Terminating object
    Arg3: 863d034c, Process image file name
    Arg4: 805d1142, Explanatory message (ascii)

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


    PROCESS_OBJECT: 863d01d8

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

    BUGCHECK_STR: 0xF4

    EXCEPTION_RECORD: f78529d8 -- (.exr fffffffff78529d8)
    ExceptionAddress: 75b7b161
    ExceptionCode: c0000006 (In-page I/O error)
    ExceptionFlags: 00000000
    NumberParameters: 3
    Parameter[0]: 00000008
    Parameter[1]: 75b7b161
    Parameter[2]: c000000e
    Inpage operation failed at 75b7b161, due to I/O error c000000e

    LAST_CONTROL_TRANSFER: from 805d02e9 to 804f9c37

    STACK_TEXT:
    f7852520 805d02e9 000000f4 00000003 863d01d8 nt!KeBugCheckEx+0x1b
    f7852544 805d11ed 805d1142 863d01d8 863d034c nt!PspCatchCriticalBreak+0x75
    f7852574 8054060c 863d0420 c0000006 f78529b0 nt!NtTerminateProcess+0x7d
    f7852574 805004c5 863d0420 c0000006 f78529b0 nt!KiFastCallEntry+0xfc
    f78525f4 804fe4f6 ffffffff c0000006 f78529f8 nt!ZwTerminateProcess+0x11
    f78529b0 80501c03 f78529d8 00000000 f7852d64 nt!KiDispatchException+0x3a0
    f7852d34 80543ed7 00c8fbe8 00c8fc08 00000000 nt!KiRaiseException+0x175
    f7852d50 8054060c 00c8fbe8 00c8fc08 00000000 nt!NtRaiseException+0x33
    f7852d50 75b7b161 00c8fbe8 00c8fc08 00000000 nt!KiFastCallEntry+0xfc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    00c8fff4 00000000 00000000 00000000 00000000 0x75b7b161


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!PspCatchCriticalBreak+75
    805d02e9 5e pop esi

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!PspCatchCriticalBreak+75

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d

    FAILURE_BUCKET_ID: 0xF4_nt!PspCatchCriticalBreak+75

    BUCKET_ID: 0xF4_nt!PspCatchCriticalBreak+75

    Followup: MachineOwner
    ---------
     
  4. Bradan

    Bradan TS Rookie Topic Starter

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


    Loading Dump File [C:\WINDOWS\Minidump\Mini030207-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Fri Mar 2 15:16:08.609 2007 (GMT-5)
    System Uptime: 0 days 0:05:30.296
    Loading Kernel Symbols
    ......................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 77, {c000000e, c000000e, 0, 1c4000}

    Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+4f5 )

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

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: c000000e, status code
    Arg2: c000000e, i/o status code
    Arg3: 00000000, page file number
    Arg4: 001c4000, offset into page file

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


    ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

    DISK_HARDWARE_ERROR: There was error with disk hardware

    BUGCHECK_STR: 0x77_c000000e

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

    LAST_CONTROL_TRANSFER: from 805110e7 to 804f9c37

    STACK_TEXT:
    f7a8bcdc 805110e7 00000077 c000000e c000000e nt!KeBugCheckEx+0x1b
    f7a8bd50 80511f59 c07bd2d8 00035ed7 00000001 nt!MiMakeOutswappedPageResident+0x4f5
    f7a8bd8c 8053ed66 005c2da8 00000000 865bab30 nt!MmInPageKernelStack+0x149
    f7a8bda4 8053f236 865c2e08 805ce794 00000000 nt!KiInSwapKernelStacks+0x16
    f7a8bdac 805ce794 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
    f7a8bddc 805450ce 8053f1ba 00000000 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiMakeOutswappedPageResident+4f5
    805110e7 cc int 3

    SYMBOL_STACK_INDEX: 1

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d

    SYMBOL_NAME: nt!MiMakeOutswappedPageResident+4f5

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+4f5

    BUCKET_ID: 0x77_c000000e_nt!MiMakeOutswappedPageResident+4f5

    Followup: MachineOwner
    ---------
     
  5. Jakovasaur

    Jakovasaur TS Rookie

    Its a bit of a basic thing but i always say start small, try changing your Sata cable or at least making sure its secure this solved my problem with the HDD on my old PC but saying that I was getting resets as well as BSOD's so who knows.

    Make sure the drivers are bang up to date along with any BIOS updates once you've done that I'd go to the retailer about the suspect parts... unless of course some one gives you some really handy info ;)
     
  6. Bradan

    Bradan TS Rookie Topic Starter

    resolved, it was a conflict with the S.M.A.R.T. error checking device onboard with the nfts error checking. thanks tho
     
  7. Jakovasaur

    Jakovasaur TS Rookie

    Exellent :)
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...