KERNEL_DATA_INPAGE_ERROR while moving file

[vieekk]

Yesterday I got a KERNEL_DATA_INPAGE_ERROR BSoD while moving a file from my internal SATA 2 drive to an external drive. The file transfer just froze, after I while I tried to cancel and the BSoD came short thereafter. After reboot the computer was very slow, it was like indexing the internal drive and accessing anything from it took quite a bit of time, but it was resolved after something like ten minutes.

My specs are up to date and I'm attaching an SF file. The computer lives today, but will it for long?

 

[Pauly]

Hello vieekk

According to your dump file there was an error with your disk i would recommend you run some tests on your HDD
Hard Drive Diagnostic Procedure
http://www.sevenforums.com/tutorials/433-disk-check.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc500cf858, ffffffffc0000185, 1ee869880, fffff8a019f0b000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36bea )
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.
[U][B]If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185[/B],[/U]
[U][B]it means the disk subsystem has experienced a failure[/B].[/U]
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc500cf858, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc0000185, error status (normally i/o status code)
Arg3: 00000001ee869880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a019f0b000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
 
ERROR_CODE: (NTSTATUS) [B][U]0xc0000185 - The I/O device reported an I/O error.[/U][/B]
DISK_HARDWARE_ERROR: [B][U]There was error with disk hardware[/U][/B]
[B][U]BUGCHECK_STR:  0x7a_c0000185[/U][/B]
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  uTorrent.exe
CURRENT_IRQL:  0
DEVICE_OBJECT: fffffa800b492c58
TRAP_FRAME:  fffff88011f660a0 -- (.trap 0xfffff88011f660a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a019f0b000 rbx=0000000000000000 rcx=0000000fffffffff
rdx=fffff98062300000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032b233c rsp=fffff88011f66230 rbp=fffff88011f66280
 r8=0000098000000000  r9=0000000004680000 r10=0000058000000000
r11=00000000015c0000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!MmCopyToCachedPage+0x1dc:
fffff800`032b233c 488b38          mov     rdi,qword ptr [rax] ds:fffff8a0`19f0b000=0000000000000000
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800032f4552 to fffff80003286fc0
STACK_TEXT:  
fffff880`11f65d88 fffff800`032f4552 : 00000000`0000007a fffff6fc`500cf858 ffffffff`c0000185 00000001`ee869880 : nt!KeBugCheckEx
fffff880`11f65d90 fffff800`032adcbf : fffffa80`09eec740 fffff880`11f65f00 fffff800`034b9600 fffffa80`09eec740 : nt! ?? ::FNODOBFM::`string'+0x36bea
fffff880`11f65e70 fffff800`03294589 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`00000493 : nt!MiIssueHardFault+0x28b
fffff880`11f65f40 fffff800`032850ee : 00000000`00000000 fffff8a0`19f0b000 00000000`00000100 00000000`00000000 : nt!MmAccessFault+0x1399
fffff880`11f660a0 fffff800`032b233c : fffff780`c0000000 75fbfff3`91ec460c 00000000`00000000 fffffa80`08ff11f0 : nt!KiPageFault+0x16e
fffff880`11f66230 fffff800`032af42e : fffff980`62300000 00000000`04680000 fffff880`00000000 00000000`00001000 : nt!MmCopyToCachedPage+0x1dc
fffff880`11f66420 fffff800`032af9e4 : fffffa80`0b319190 00000000`04680000 fffff880`11f66560 00000000`000c0000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`11f66510 fffff880`0124dbf6 : 00000000`00000000 fffff880`11f66780 fffffa80`0704c320 00000000`00000000 : nt!CcCopyWrite+0x194
fffff880`11f665a0 fffff880`0124e1a3 : fffffa80`0704c320 fffffa80`0b492900 fffff880`11f66700 fffff880`11f66700 : Ntfs!NtfsCommonWrite+0x3390
fffff880`11f66750 fffff880`0117abcf : fffffa80`0b492c10 fffffa80`0b492900 fffffa80`0a2d8630 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`11f66810 fffff880`011796df : fffffa80`0849cde0 00000000`00000001 fffffa80`0849cd00 fffffa80`0b492900 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`11f668a0 fffff800`0358adfb : 00000000`00000001 fffffa80`0abda970 00000000`00000001 fffffa80`0b492900 : fltmgr!FltpDispatch+0xcf
fffff880`11f66900 fffff800`03595863 : fffffa80`0b492c58 00000000`00000000 fffffa80`0abda970 fffff880`009eb180 : nt!IopSynchronousServiceTail+0xfb
fffff880`11f66970 fffff800`03286253 : 00000000`00000501 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x7e2
fffff880`11f66a70 00000000`74832e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02f6f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74832e09
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36bea
fffff800`032f4552 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36bea
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
FAILURE_BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+36bea
BUCKET_ID:  X64_0x7a_c0000185_nt!_??_::FNODOBFM::_string_+36bea
Followup: MachineOwner
---------

 

[vieekk]

Hello vieekk

According to your dump file there was an error with your disk i would recommend you run some tests on your HDD
Hard Drive Diagnostic Procedure
http://www.sevenforums.com/tutorials/433-disk-check.html

Thank you, but from your first link I'm a little bit confused about what to download for Samsung, since Seagate has taken over and the other Samsung link is a 404. I will definitely perform a chkdisk at some point in time, but I'm told that can take a LOT of time. How long?

I tried doing a benchmark with HD Tune also, see attachments. It seems to perform in a similiar manner to other drives of the same mark and model?

Edit: I made a Quick Scan in HD Tune too, all green there. I've only received the BSoD at one time.

 

[Pauly]

Try seatools from seagate thats where most samsung support docs will point you
SeaTools | Seagate

Dont know exactly how long disk check would take but would say hours not days, you can always start it overnight

 

[vieekk]

Try seatools from seagate thats where most samsung support docs will point you
SeaTools | Seagate

Dont know exactly how long disk check would take but would say hours not days, you can always start it overnight

It failed on the Short Drive Self Test, but passed on S.M.A.R.T. Check and Short Generic. Haven't done any of the long ones yet, how long are they? The computer was very slow about an hour ago...

 

[Pauly]

I would guess upto few hours for some long tests

 

[vieekk]

It failed overnight on the Long Generic too, but when I did the Short DST today again it passed.

 

[x BlueRobot]

Do have a separate drive? It seems you have some disk failure; have you performed a Disk Check (chkdsk) yet?

 

[vieekk]

Do have a separate drive? It seems you have some disk failure; have you performed a Disk Check (chkdsk) yet?

I have an encrypted external USB drive, but I am considering buying an SSD tomorrow. Might as well if this disk is going to hell.

I haven't performed a chkdisk yet, being afraid of the long processing times. But if I install Win7 on a SSD and do the chkdisk on the perhaps faulty disk I can terminate the check without damaging the disk physically, only the data? (I have already backed up the data.)

 

[x BlueRobot]

I don't think Disk Check will damage your drive physically, but it may corrupt some your data, here's the warning from the tutorial:

Once the Disk Check scan starts, DO NOT STOP the scan to prevent possible damage to the data on your hard drive.

You can always run the test overnight.