Restarturący się komputer pomocy!

Witam, mam problem z restartującym sie komputerem.

Po zainstalowaniu WinDbg i obejrzeniu plików zrzutu dalej nie bardzo wiem co się dzieje z moim komputerem. Czy ktoś może mi pomóc?

Załączam info z WinDbg

Pierwsze:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp2_gdr.090206-1233

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553420

Debug session time: Tue Aug 18 04:41:07.593 2009 (GMT+2)

System Uptime: 1 days 17:00:54.140

Loading Kernel Symbols

Loading User Symbols

Loading unloaded module list

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c07b9ec8, c000000e, f73d9384, 18e84860}

Probably caused by : atapi.sys ( atapi!ChannelQueryBusRelation+2f )

Followup: MachineOwner


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: c07b9ec8, lock type that was held (value 1,2,3, or PTE address)

Arg2: c000000e, error status (normally i/o status code)

Arg3: f73d9384, current process (virtual address for lock type 3, or PTE)

Arg4: 18e84860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:


ERROR_CODE: (NTSTATUS) 0xc000000e - Okre

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: f7aa7cdc – (.trap 0xfffffffff7aa7cdc)

ErrCode = 00000010

eax=84b46ba8 ebx=84bc88b8 ecx=00003d32 edx=84bd52d4 esi=84495008 edi=84bd50e8

eip=f73d9384 esp=f7aa7d50 ebp=f7aa7d60 iopl=0 nv up ei pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246

atapi!IdePortScanBus:

f73d9384 8bff mov edi,edi

Resetting default scope

LAST_CONTROL_TRANSFER: from 80511f59 to 804f8b0f

STACK_TEXT:

f7aa7bb0 80511f59 0000007a c07b9ec8 c000000e nt!KeBugCheckEx+0x1b

f7aa7be0 80512a7f 8191f670 c07b9ec8 f73d9384 nt!MiWaitForInPageComplete+0x1c7

f7aa7c60 8051bfc0 c07b9ec8 f73d9384 c07b9ec8 nt!MiDispatchFault+0x2b5

f7aa7cc4 8053f92c 00000008 f73d9384 00000000 nt!MmAccessFault+0x7b4

f7aa7cc4 f73d9384 00000008 f73d9384 00000000 nt!KiTrap0E+0xcc

f7aa7d4c f73dbc7f 84bd50e8 84bcb260 84bd5030 atapi!IdePortScanBus

f7aa7d60 8056aed3 84bd5030 84bdf878 8055a47c atapi!ChannelQueryBusRelation+0x2f

f7aa7d74 80534006 84bcb260 00000000 84bc88b8 nt!IopProcessWorkItem+0x13

f7aa7dac 805c4d5a 84bcb260 00000000 00000000 nt!ExpWorkerThread+0x100

f7aa7ddc 805411e2 80533f06 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

atapi!ChannelQueryBusRelation+2f

f73dbc7f 57 push edi

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: atapi!ChannelQueryBusRelation+2f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atapi

IMAGE_NAME: atapi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107b4d

FAILURE_BUCKET_ID: 0x7a_c000000e_atapi!ChannelQueryBusRelation+2f

BUCKET_ID: 0x7a_c000000e_atapi!ChannelQueryBusRelation+2f

Followup: MachineOwner


kd> lmvm atapi

start end module name

f73cc000 f73e3480 atapi (pdb symbols) c:\symbols\atapi.pdb\25228DED4EEC41F29756FC1568E4B63F1\atapi.pdb

Loaded symbol image file: atapi.sys

Mapped memory image file: c:\symbols\atapi.sys\41107B4D17480\atapi.sys

Image path: atapi.sys

Image name: atapi.sys

Timestamp: Wed Aug 04 07:59:41 2004 (41107B4D)

CheckSum: 000208FA

ImageSize: 00017480

File version: 5.1.2600.2180

Product version: 5.1.2600.2180

File flags: 0 (Mask 3F)

File OS: 40004 NT Win32

File type: 3.7 Driver

File date: 00000000.00000000

Translations: 0409.04b0

CompanyName: Microsoft Corporation

ProductName: Microsoft® Windows® Operating System

InternalName: atapi.sys

OriginalFilename: atapi.sys

ProductVersion: 5.1.2600.2180

FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)

FileDescription: IDE/ATAPI Port Driver

LegalCopyright: © Microsoft Corporation. All rights reserved.

Drugie:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp2_gdr.090206-1233

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553420

Debug session time: Tue Aug 18 09:24:33.421 2009 (GMT+2)

System Uptime: 0 days 4:39:02.968

Loading Kernel Symbols

Loading User Symbols

Loading unloaded module list

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 84a6a8d0, 84a6aa44, 805c77ca}

unable to get nt!KiCurrentEtwBufferOffset

unable to get nt!KiCurrentEtwBufferBase

Probably caused by : hardware_disk ( +f8 )

Followup: MachineOwner


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: 84a6a8d0, Terminating object

Arg3: 84a6aa44, Process image file name

Arg4: 805c77ca, Explanatory message (ascii)

Debugging Details:


unable to get nt!KiCurrentEtwBufferOffset

unable to get nt!KiCurrentEtwBufferBase

PROCESS_OBJECT: 84a6a8d0

IMAGE_NAME: hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: 00000000

PROCESS_NAME: CSRSS.EXE

EXCEPTION_RECORD: f788b9d8 – (.exr 0xfffffffff788b9d8)

ExceptionAddress: 75b4b399

ExceptionCode: c0000006 (In-page I/O error)

ExceptionFlags: 00000000

NumberParameters: 3

Parameter[0]: 00000008

Parameter[1]: 75b4b399

Parameter[2]: c000000e

Inpage operation failed at 75b4b399, due to I/O error c000000e

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Instrukcja spod “0x%08lx” odwo

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000006 - Instrukcja spod “0x%08lx” odwo

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 75b4b399

EXCEPTION_PARAMETER3: c000000e

IO_ERROR: (NTSTATUS) 0xc000000e - Okre

EXCEPTION_STR: 0xc0000006_c000000e

FAULTING_IP:

+f8

75b4b399 ?? ???

BUGCHECK_STR: 0xF4_IOERR_C000000E

FOLLOWUP_IP:

+f8

75b4b399 ?? ???

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware_disk

SYMBOL_NAME: +f8

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xF4_IOERR_C000000E_+f8

BUCKET_ID: 0xF4_IOERR_C000000E_+f8

Followup: MachineOwner


kd> lmvm hardware_disk

start end module name

Odłącz fizycznie napęd(y) CD/DVD od płyty głównej.

Daj znać czy problem się powtarza.

Dzięki spróbuję i dam znać :smiley:

Zainstaluj program HD Tune i daj screeny z zakładki Health i Error Scan.

Wykonałam scan HD Tunem ale jak mam załaczyć screeny???

Dodane 20.08.2009 (Cz) 11:20

Załączam zrzut dmp z dzisiaj a jak mi ktoś podpowie jak załaczyć sreeny z HD Tune to będę wdzięczna :smiley:

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 2600.xpsp_sp2_gdr.090206-1233

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553420

Debug session time: Thu Aug 20 07:36:45.640 2009 (GMT+2)

System Uptime: 1 days 0:31:55.187

Loading Kernel Symbols

Loading User Symbols

Loading unloaded module list

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c07ba0a0, c000000e, f7414642, 153e7860}

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

Followup: MachineOwner


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: c07ba0a0, lock type that was held (value 1,2,3, or PTE address)

Arg2: c000000e, error status (normally i/o status code)

Arg3: f7414642, current process (virtual address for lock type 3, or PTE)

Arg4: 153e7860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:


ERROR_CODE: (NTSTATUS) 0xc000000e - Okre

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: f7ab3a5c – (.trap 0xfffffffff7ab3a5c)

ErrCode = 00000010

eax=00760018 ebx=8463d008 ecx=00000000 edx=0000000c esi=84af01d8 edi=00000000

eip=f7414642 esp=f7ab3ad0 ebp=f7ab3b24 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:

f7414642 53 push ebx

Resetting default scope

LOCK_ADDRESS: 805513e0 – (!locks 805513e0)

Resource @ nt!PiEngineLock (0x805513e0) 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 : 0x805513e0

Thread Count : 0

Thread address: 0x00000000

Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80511f59 to 804f8b0f

STACK_TEXT:

f7ab3930 80511f59 0000007a c07ba0a0 c000000e nt!KeBugCheckEx+0x1b

f7ab3960 80512a7f 818b8d44 c07ba0a0 f7414642 nt!MiWaitForInPageComplete+0x1c7

f7ab39e0 8051bfc0 c07ba0a0 f7414642 c07ba0a0 nt!MiDispatchFault+0x2b5

f7ab3a44 8053f92c 00000008 f7414642 00000000 nt!MmAccessFault+0x7b4

f7ab3a44 f7414642 00000008 f7414642 00000000 nt!KiTrap0E+0xcc

f7ab3acc f740b51f 84af01d8 8463d008 00000000 ftdisk!FtpReferenceDependantVolume

f7ab3ae4 804ee003 84af0120 8463d008 00000000 ftdisk!FtDiskInternalDeviceControl+0x51

f7ab3af4 f78e5bd3 84bdcac0 84040000 00000000 nt!IopfCallDriver+0x31

f7ab3b24 f78e697e 84af0120 84b0e7b0 84b0f7e0 PartMgr!PmQueryDependantVolumeList+0x83

f7ab3b6c f78e6e8a 84b400d8 8451987c 8451993c PartMgr!PmBuildDependantVolumeRelations+0xd5

f7ab3b98 f78e700d 84b400d8 c00000bb 84519960 PartMgr!PmQueryRemovalRelations+0x7f

f7ab3bd4 804ee003 84b40020 84519860 f7ab3c54 PartMgr!PmPnp+0x17c

f7ab3be4 805870a1 00000003 84b0f460 f7ab3c7c nt!IopfCallDriver+0x31

f7ab3c10 804f5ba9 84b40020 f7ab3c30 f7ab3c7c nt!IopSynchronousCall+0xb7

f7ab3c58 80588072 00000003 84b0f7e0 00000001 nt!IopQueryDeviceRelations+0x45

f7ab3c80 80588c31 00000000 00000003 00000001 nt!IopProcessRelation+0xfa

f7ab3ca8 8058e4a4 84b0f7e0 00000003 f7ab3d18 nt!IopBuildRemovalRelationList+0x41

f7ab3d34 8058ec70 f7ab3d70 806d0778 e2159048 nt!PiProcessQueryRemoveAndEject+0x262

f7ab3d50 8058edc9 f7ab3d70 849121c8 8055a47c nt!PiProcessTargetDeviceEvent+0x2a

f7ab3d74 80534006 849121c8 00000000 84bc7020 nt!PiWalkDeviceList+0xfd

f7ab3dac 805c4d5a 849121c8 00000000 00000000 nt!ExpWorkerThread+0x100

f7ab3ddc 805411e2 80533f06 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

ftdisk!FtDiskInternalDeviceControl+51

f740b51f eb31 jmp ftdisk!FtDiskInternalDeviceControl+0x84 (f740b552)

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


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: c07ba0a0, lock type that was held (value 1,2,3, or PTE address)

Arg2: c000000e, error status (normally i/o status code)

Arg3: f7414642, current process (virtual address for lock type 3, or PTE)

Arg4: 153e7860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:


ERROR_CODE: (NTSTATUS) 0xc000000e - Okre

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: f7ab3a5c – (.trap 0xfffffffff7ab3a5c)

ErrCode = 00000010

eax=00760018 ebx=8463d008 ecx=00000000 edx=0000000c esi=84af01d8 edi=00000000

eip=f7414642 esp=f7ab3ad0 ebp=f7ab3b24 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:

f7414642 53 push ebx

Resetting default scope

LOCK_ADDRESS: 805513e0 – (!locks 805513e0)

Resource @ nt!PiEngineLock (0x805513e0) 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 : 0x805513e0

Thread Count : 0

Thread address: 0x00000000

Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80511f59 to 804f8b0f

STACK_TEXT:

f7ab3930 80511f59 0000007a c07ba0a0 c000000e nt!KeBugCheckEx+0x1b

f7ab3960 80512a7f 818b8d44 c07ba0a0 f7414642 nt!MiWaitForInPageComplete+0x1c7

f7ab39e0 8051bfc0 c07ba0a0 f7414642 c07ba0a0 nt!MiDispatchFault+0x2b5

f7ab3a44 8053f92c 00000008 f7414642 00000000 nt!MmAccessFault+0x7b4

f7ab3a44 f7414642 00000008 f7414642 00000000 nt!KiTrap0E+0xcc

f7ab3acc f740b51f 84af01d8 8463d008 00000000 ftdisk!FtpReferenceDependantVolume

f7ab3ae4 804ee003 84af0120 8463d008 00000000 ftdisk!FtDiskInternalDeviceControl+0x51

f7ab3af4 f78e5bd3 84bdcac0 84040000 00000000 nt!IopfCallDriver+0x31

f7ab3b24 f78e697e 84af0120 84b0e7b0 84b0f7e0 PartMgr!PmQueryDependantVolumeList+0x83

f7ab3b6c f78e6e8a 84b400d8 8451987c 8451993c PartMgr!PmBuildDependantVolumeRelations+0xd5

f7ab3b98 f78e700d 84b400d8 c00000bb 84519960 PartMgr!PmQueryRemovalRelations+0x7f

f7ab3bd4 804ee003 84b40020 84519860 f7ab3c54 PartMgr!PmPnp+0x17c

f7ab3be4 805870a1 00000003 84b0f460 f7ab3c7c nt!IopfCallDriver+0x31

f7ab3c10 804f5ba9 84b40020 f7ab3c30 f7ab3c7c nt!IopSynchronousCall+0xb7

f7ab3c58 80588072 00000003 84b0f7e0 00000001 nt!IopQueryDeviceRelations+0x45

f7ab3c80 80588c31 00000000 00000003 00000001 nt!IopProcessRelation+0xfa

f7ab3ca8 8058e4a4 84b0f7e0 00000003 f7ab3d18 nt!IopBuildRemovalRelationList+0x41

f7ab3d34 8058ec70 f7ab3d70 806d0778 e2159048 nt!PiProcessQueryRemoveAndEject+0x262

f7ab3d50 8058edc9 f7ab3d70 849121c8 8055a47c nt!PiProcessTargetDeviceEvent+0x2a

f7ab3d74 80534006 849121c8 00000000 84bc7020 nt!PiWalkDeviceList+0xfd

f7ab3dac 805c4d5a 849121c8 00000000 00000000 nt!ExpWorkerThread+0x100

f7ab3ddc 805411e2 80533f06 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

ftdisk!FtDiskInternalDeviceControl+51

f740b51f eb31 jmp ftdisk!FtDiskInternalDeviceControl+0x84 (f740b552)

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


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: c07ba0a0, lock type that was held (value 1,2,3, or PTE address)

Arg2: c000000e, error status (normally i/o status code)

Arg3: f7414642, current process (virtual address for lock type 3, or PTE)

Arg4: 153e7860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:


ERROR_CODE: (NTSTATUS) 0xc000000e - Okre

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: f7ab3a5c – (.trap 0xfffffffff7ab3a5c)

ErrCode = 00000010

eax=00760018 ebx=8463d008 ecx=00000000 edx=0000000c esi=84af01d8 edi=00000000

eip=f7414642 esp=f7ab3ad0 ebp=f7ab3b24 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:

f7414642 53 push ebx

Resetting default scope

LOCK_ADDRESS: 805513e0 – (!locks 805513e0)

Resource @ nt!PiEngineLock (0x805513e0) 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 : 0x805513e0

Thread Count : 0

Thread address: 0x00000000

Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80511f59 to 804f8b0f

STACK_TEXT:

f7ab3930 80511f59 0000007a c07ba0a0 c000000e nt!KeBugCheckEx+0x1b

f7ab3960 80512a7f 818b8d44 c07ba0a0 f7414642 nt!MiWaitForInPageComplete+0x1c7

f7ab39e0 8051bfc0 c07ba0a0 f7414642 c07ba0a0 nt!MiDispatchFault+0x2b5

f7ab3a44 8053f92c 00000008 f7414642 00000000 nt!MmAccessFault+0x7b4

f7ab3a44 f7414642 00000008 f7414642 00000000 nt!KiTrap0E+0xcc

f7ab3acc f740b51f 84af01d8 8463d008 00000000 ftdisk!FtpReferenceDependantVolume

f7ab3ae4 804ee003 84af0120 8463d008 00000000 ftdisk!FtDiskInternalDeviceControl+0x51

f7ab3af4 f78e5bd3 84bdcac0 84040000 00000000 nt!IopfCallDriver+0x31

f7ab3b24 f78e697e 84af0120 84b0e7b0 84b0f7e0 PartMgr!PmQueryDependantVolumeList+0x83

f7ab3b6c f78e6e8a 84b400d8 8451987c 8451993c PartMgr!PmBuildDependantVolumeRelations+0xd5

f7ab3b98 f78e700d 84b400d8 c00000bb 84519960 PartMgr!PmQueryRemovalRelations+0x7f

f7ab3bd4 804ee003 84b40020 84519860 f7ab3c54 PartMgr!PmPnp+0x17c

f7ab3be4 805870a1 00000003 84b0f460 f7ab3c7c nt!IopfCallDriver+0x31

f7ab3c10 804f5ba9 84b40020 f7ab3c30 f7ab3c7c nt!IopSynchronousCall+0xb7

f7ab3c58 80588072 00000003 84b0f7e0 00000001 nt!IopQueryDeviceRelations+0x45

f7ab3c80 80588c31 00000000 00000003 00000001 nt!IopProcessRelation+0xfa

f7ab3ca8 8058e4a4 84b0f7e0 00000003 f7ab3d18 nt!IopBuildRemovalRelationList+0x41

f7ab3d34 8058ec70 f7ab3d70 806d0778 e2159048 nt!PiProcessQueryRemoveAndEject+0x262

f7ab3d50 8058edc9 f7ab3d70 849121c8 8055a47c nt!PiProcessTargetDeviceEvent+0x2a

f7ab3d74 80534006 849121c8 00000000 84bc7020 nt!PiWalkDeviceList+0xfd

f7ab3dac 805c4d5a 849121c8 00000000 00000000 nt!ExpWorkerThread+0x100

f7ab3ddc 805411e2 80533f06 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

ftdisk!FtDiskInternalDeviceControl+51

f740b51f eb31 jmp ftdisk!FtDiskInternalDeviceControl+0x84 (f740b552)

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


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: c07ba0a0, lock type that was held (value 1,2,3, or PTE address)

Arg2: c000000e, error status (normally i/o status code)

Arg3: f7414642, current process (virtual address for lock type 3, or PTE)

Arg4: 153e7860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:


ERROR_CODE: (NTSTATUS) 0xc000000e - Okre

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: f7ab3a5c – (.trap 0xfffffffff7ab3a5c)

ErrCode = 00000010

eax=00760018 ebx=8463d008 ecx=00000000 edx=0000000c esi=84af01d8 edi=00000000

eip=f7414642 esp=f7ab3ad0 ebp=f7ab3b24 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:

f7414642 53 push ebx

Resetting default scope

LOCK_ADDRESS: 805513e0 – (!locks 805513e0)

Resource @ nt!PiEngineLock (0x805513e0) 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 : 0x805513e0

Thread Count : 0

Thread address: 0x00000000

Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80511f59 to 804f8b0f

STACK_TEXT:

f7ab3930 80511f59 0000007a c07ba0a0 c000000e nt!KeBugCheckEx+0x1b

f7ab3960 80512a7f 818b8d44 c07ba0a0 f7414642 nt!MiWaitForInPageComplete+0x1c7

f7ab39e0 8051bfc0 c07ba0a0 f7414642 c07ba0a0 nt!MiDispatchFault+0x2b5

f7ab3a44 8053f92c 00000008 f7414642 00000000 nt!MmAccessFault+0x7b4

f7ab3a44 f7414642 00000008 f7414642 00000000 nt!KiTrap0E+0xcc

f7ab3acc f740b51f 84af01d8 8463d008 00000000 ftdisk!FtpReferenceDependantVolume

f7ab3ae4 804ee003 84af0120 8463d008 00000000 ftdisk!FtDiskInternalDeviceControl+0x51

f7ab3af4 f78e5bd3 84bdcac0 84040000 00000000 nt!IopfCallDriver+0x31

f7ab3b24 f78e697e 84af0120 84b0e7b0 84b0f7e0 PartMgr!PmQueryDependantVolumeList+0x83

f7ab3b6c f78e6e8a 84b400d8 8451987c 8451993c PartMgr!PmBuildDependantVolumeRelations+0xd5

f7ab3b98 f78e700d 84b400d8 c00000bb 84519960 PartMgr!PmQueryRemovalRelations+0x7f

f7ab3bd4 804ee003 84b40020 84519860 f7ab3c54 PartMgr!PmPnp+0x17c

f7ab3be4 805870a1 00000003 84b0f460 f7ab3c7c nt!IopfCallDriver+0x31

f7ab3c10 804f5ba9 84b40020 f7ab3c30 f7ab3c7c nt!IopSynchronousCall+0xb7

f7ab3c58 80588072 00000003 84b0f7e0 00000001 nt!IopQueryDeviceRelations+0x45

f7ab3c80 80588c31 00000000 00000003 00000001 nt!IopProcessRelation+0xfa

f7ab3ca8 8058e4a4 84b0f7e0 00000003 f7ab3d18 nt!IopBuildRemovalRelationList+0x41

f7ab3d34 8058ec70 f7ab3d70 806d0778 e2159048 nt!PiProcessQueryRemoveAndEject+0x262

f7ab3d50 8058edc9 f7ab3d70 849121c8 8055a47c nt!PiProcessTargetDeviceEvent+0x2a

f7ab3d74 80534006 849121c8 00000000 84bc7020 nt!PiWalkDeviceList+0xfd

f7ab3dac 805c4d5a 849121c8 00000000 00000000 nt!ExpWorkerThread+0x100

f7ab3ddc 805411e2 80533f06 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

ftdisk!FtDiskInternalDeviceControl+51

f740b51f eb31 jmp ftdisk!FtDiskInternalDeviceControl+0x84 (f740b552)

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


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: c07ba0a0, lock type that was held (value 1,2,3, or PTE address)

Arg2: c000000e, error status (normally i/o status code)

Arg3: f7414642, current process (virtual address for lock type 3, or PTE)

Arg4: 153e7860, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:


ERROR_CODE: (NTSTATUS) 0xc000000e - Okre

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR: 0x7a_c000000e

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

TRAP_FRAME: f7ab3a5c – (.trap 0xfffffffff7ab3a5c)

ErrCode = 00000010

eax=00760018 ebx=8463d008 ecx=00000000 edx=0000000c esi=84af01d8 edi=00000000

eip=f7414642 esp=f7ab3ad0 ebp=f7ab3b24 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:

f7414642 53 push ebx

Resetting default scope

LOCK_ADDRESS: 805513e0 – (!locks 805513e0)

Resource @ nt!PiEngineLock (0x805513e0) 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 : 0x805513e0

Thread Count : 0

Thread address: 0x00000000

Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 80511f59 to 804f8b0f

STACK_TEXT:

f7ab3930 80511f59 0000007a c07ba0a0 c000000e nt!KeBugCheckEx+0x1b

f7ab3960 80512a7f 818b8d44 c07ba0a0 f7414642 nt!MiWaitForInPageComplete+0x1c7

f7ab39e0 8051bfc0 c07ba0a0 f7414642 c07ba0a0 nt!MiDispatchFault+0x2b5

f7ab3a44 8053f92c 00000008 f7414642 00000000 nt!MmAccessFault+0x7b4

f7ab3a44 f7414642 00000008 f7414642 00000000 nt!KiTrap0E+0xcc

f7ab3acc f740b51f 84af01d8 8463d008 00000000 ftdisk!FtpReferenceDependantVolume

f7ab3ae4 804ee003 84af0120 8463d008 00000000 ftdisk!FtDiskInternalDeviceControl+0x51

f7ab3af4 f78e5bd3 84bdcac0 84040000 00000000 nt!IopfCallDriver+0x31

f7ab3b24 f78e697e 84af0120 84b0e7b0 84b0f7e0 PartMgr!PmQueryDependantVolumeList+0x83

f7ab3b6c f78e6e8a 84b400d8 8451987c 8451993c PartMgr!PmBuildDependantVolumeRelations+0xd5

f7ab3b98 f78e700d 84b400d8 c00000bb 84519960 PartMgr!PmQueryRemovalRelations+0x7f

f7ab3bd4 804ee003 84b40020 84519860 f7ab3c54 PartMgr!PmPnp+0x17c

f7ab3be4 805870a1 00000003 84b0f460 f7ab3c7c nt!IopfCallDriver+0x31

f7ab3c10 804f5ba9 84b40020 f7ab3c30 f7ab3c7c nt!IopSynchronousCall+0xb7

f7ab3c58 80588072 00000003 84b0f7e0 00000001 nt!IopQueryDeviceRelations+0x45

f7ab3c80 80588c31 00000000 00000003 00000001 nt!IopProcessRelation+0xfa

f7ab3ca8 8058e4a4 84b0f7e0 00000003 f7ab3d18 nt!IopBuildRemovalRelationList+0x41

f7ab3d34 8058ec70 f7ab3d70 806d0778 e2159048 nt!PiProcessQueryRemoveAndEject+0x262

f7ab3d50 8058edc9 f7ab3d70 849121c8 8055a47c nt!PiProcessTargetDeviceEvent+0x2a

f7ab3d74 80534006 849121c8 00000000 84bc7020 nt!PiWalkDeviceList+0xfd

f7ab3dac 805c4d5a 849121c8 00000000 00000000 nt!ExpWorkerThread+0x100

f7ab3ddc 805411e2 80533f06 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

ftdisk!FtDiskInternalDeviceControl+51

f740b51f eb31 jmp ftdisk!FtDiskInternalDeviceControl+0x84 (f740b552)

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


kd> lmvm ftdisk

start end module name

f740a000 f7428a80 ftdisk (pdb symbols) c:\symbols\ftdisk.pdb\370ADA20D01E457AB6AC095AF8D099681\ftdisk.pdb

Loaded symbol image file: ftdisk.sys

Mapped memory image file: c:\symbols\ftdisk.sys\3B7D84191ea80\ftdisk.sys

Image path: ftdisk.sys

Image name: ftdisk.sys

Timestamp: Fri Aug 17 22:52:41 2001 (3B7D8419)

CheckSum: 00028642

ImageSize: 0001EA80

File version: 5.1.2600.0

Product version: 5.1.2600.0

File flags: 0 (Mask 3F)

File OS: 40004 NT Win32

File type: 3.7 Driver

File date: 00000000.00000000

Translations: 0415.04b0

CompanyName: Microsoft Corporation

ProductName: System operacyjny Microsoft® Windows®

InternalName: ftdisk.sys

OriginalFilename: ftdisk.sys

ProductVersion: 5.1.2600.0

FileVersion: 5.1.2600.0 (XPClient.010817-1148)

FileDescription: Sterownik dysku FT

LegalCopyright: © Microsoft Corporation. Wszelkie prawa zastrzeżone.

W oknie programu kliknij na przycisk z dyskietką (Save screenshot).

Patrz :arrow:

http://msdn.microsoft.com/en-us/library/ms793989.aspx

Masz problem z dyskiem twardym - najprawdopodobniej bad sectory…

W logu wyraźnie pisze: DISK_HARDWARE_ERROR: There was error with disk hardware

Dopóki jeszcze system startuje zrób kopię swoich ważnych danych - pewnego razu nie odpalisz już komputera.

Czarny scenariusz, niestety jak najbardziej realny.

Czeka Cię wymiana HDD (chyba, że masz gwarancję).

Pozdrawiam.

Dzięki Olcia jak wykonać screenshoota to ja wiem nie wiedziałam tylko jak je zamieścić na forum.

Czarny scenariusz faktycznie się potwierdził, dysko do naprawy lub wymiany :? niestety…

dzięki za pomoc

:smiley: