Should I get a new HDD? (kernel data inpage error)

Status
Not open for further replies.

Nelson Gregorio

Honorable
Sep 26, 2013
5
0
10,510
I've been using an old(er) HDD to watch/store movies, play/store games, while the OS/programs run on a SSD.

Yesterday I had 2 bsod (KERNEL_DATA_INPAGE_ERROR (7a))
Judging by the reallocated sector count, can I assume the hdd is dying and caused the 2 bsod?
Should I get a new one?
Should I look into other possible causes for the bsod?

Minidump:
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: fffff6fc80a22e08, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000000f4c4880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff901445c1390, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

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

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

TRAP_FRAME: ffffd00021a77550 -- (.trap 0xffffd00021a77550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960001c1600 rsp=ffffd00021a776e8 rbp=fffff901447914d0
r8=0000000000000001 r9=fffff901445c1390 r10=0000000000000000
r11=fffff90140723e10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
win32k!IsMessageAllowedByFilterEx+0x68:
fffff960`001c1600 4384140a test byte ptr [r10+r9],dl ds:fffff901`445c1390=??
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff801180024cf to fffff80117fdc9a0

STACK_TEXT:
ffffd000`21a771d8 fffff801`180024cf : 00000000`0000007a fffff6fc`80a22e08 ffffffff`c000000e 00000000`0f4c4880 : nt!KeBugCheckEx
ffffd000`21a771e0 fffff801`17ebd7f8 : 00000000`00000002 ffffd000`21a77348 ffffd000`9a958c00 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1561f
ffffd000`21a772d0 fffff801`17ef6b7a : ffffd000`9a958c00 ffffe000`4a5ed380 00000000`00000000 ffffd000`fffffffe : nt!MiIssueHardFault+0x184
ffffd000`21a77390 fffff801`17fe6c2f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x5ba
ffffd000`21a77550 fffff960`001c1600 : fffff960`001c1518 00000000`00000000 00000000`00000800 ffffd000`21a777e8 : nt!KiPageFault+0x12f
ffffd000`21a776e8 fffff960`001c1518 : 00000000`00000000 00000000`00000800 ffffd000`21a777e8 fffff801`17f4ded1 : win32k!IsMessageAllowedByFilterEx+0x68
ffffd000`21a776f0 fffff960`000acbd8 : fffff901`447914d0 ffffd000`21a778e0 00000000`00000200 fffff901`407df310 : win32k!IsMessageAllowedAcrossILByReceiver+0x5c
ffffd000`21a77740 fffff960`0015a85a : fffff901`4088edd0 fffff801`17f02068 00000000`00000001 00000000`00000200 : win32k!xxxInterSendMsgEx+0x228
ffffd000`21a77860 fffff960`001a3ac6 : 00000000`00000800 00000000`00000000 ffffe000`4a5ed380 00000000`00000200 : win32k!xxxSendMessageCallback+0xca
ffffd000`21a77920 fffff960`001a3a5a : fffff901`4088edd0 00000000`00000800 ffffd000`21a77aa8 fffff960`001c2c5c : win32k!xxxSendNotifyMessage+0x46
ffffd000`21a779b0 fffff960`000de120 : 00000000`0003078a 00000000`0003078a 00000000`000002b7 ffffe000`48c179c0 : win32k!xxxWrapSendNotifyMessage+0x52
ffffd000`21a77a10 fffff801`17fe81b3 : ffffe000`4a5ed380 ffffd000`21a77b80 00000000`02fdf1e8 00000000`0d8db860 : win32k!NtUserMessageCall+0xf0
ffffd000`21a77a90 00007ffb`f9b5102a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02fdf1c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffb`f9b5102a


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!IsMessageAllowedByFilterEx+68
fffff960`001c1600 4384140a test byte ptr [r10+r9],dl

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: win32k!IsMessageAllowedByFilterEx+68

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 54ee5a22

FAILURE_BUCKET_ID: X64_0x7a_c000000e_win32k!IsMessageAllowedByFilterEx+68

BUCKET_ID: X64_0x7a_c000000e_win32k!IsMessageAllowedByFilterEx+68
SMART data
HD Tune: ST315003ST31500341AS Health

ID Current Worst ThresholdData Status
(01) Raw Read Error Rate 112 88 6 180379964 Ok
(03) Spin Up Time 100 92 0 0 Ok
(04) Start/Stop Count 97 97 20 3822 Ok
(05) Reallocated Sector Count 37 37 36 2581 Ok ---- (in yellow)
(07) Seek Error Rate 81 60 30 138233604 Ok
(09) Power On Hours Count 84 84 0 14123 Ok
(0A) Spin Retry Count 100 100 97 8 Ok ---- (in yellow)
(0C) Power Cycle Count 99 99 20 1575 Ok
(B8) (unknown attribute) 100 100 99 0 Ok ---- (in yellow)
(BB) (unknown attribute) 98 98 0 2 Ok
(BC) (unknown attribute) 100 100 0 0 Ok
(BD) (unknown attribute) 1 1 0 199 Ok
(BE) Airflow Temperature 66 47 45 571605026 Ok
(C2) Temperature 34 53 0 34 Ok
(C3) Hardware ECC Recovered 49 24 0 180379964 Ok
(C5) Current Pending Sector 100 100 0 3 Ok
(C6) Offline Uncorrectable 100 100 0 3 Ok
(C7) Ultra DMA CRC Error Count 200 200 0 0 Ok
(F0) Head Flying Hours 100 253 0 14044 Ok
(F1) (unknown attribute) 100 253 0 1950979285 Ok
(F2) (unknown attribute) 100 253 0 -257540156 Ok

Power On Time : 14123
Health Status : Ok
 
Solution
Hey there, Nelson!

Unfortunately, it seems like your HDD is severely damaged. It's most probably the cause for the BSOD and the SMART data gives it away! If you can still access it, I strongly recommend to backup all the data from it ASAP!
After you have done this, check your warranty period and contact the HDD manufacturer's tech support and send an RMA request! You should be able to get a replacement.

Hope this helped! Good luck!
SuperSoph_WD
Hey there, Nelson!

Unfortunately, it seems like your HDD is severely damaged. It's most probably the cause for the BSOD and the SMART data gives it away! If you can still access it, I strongly recommend to backup all the data from it ASAP!
After you have done this, check your warranty period and contact the HDD manufacturer's tech support and send an RMA request! You should be able to get a replacement.

Hope this helped! Good luck!
SuperSoph_WD
 
Solution
If there is important data on it I suggest either burning it to disk, or unplug and remove the drive now. Plug it back in once you have a new disk and copy it over. The longer you leave it spinning in your computer even when not accessing it, the more it will wear down.
 
Status
Not open for further replies.