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
---------
