Kernel_data_inpage_error in Windows 8.1

Hi, I am encountering a blue windows 8.1 screen that says the computer has encountered an error and will restart. The error message is kernel_data_inpage_error
I have attached the following files, including the files from minidump, system info, and dxdiag info.
https://www.dropbox.com/sh/tsa3fbuwjx7b5tu/eRvKqLciZB
Thank you, Matt.

These crashes were related to memory corruption (probably caused by a driver).
Please run these tests to verify your memory and find which driver is causing the problem.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't
know what it is you probably are not overclocking.
Since it is more likely to be a driver please run verifier first.
1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)
Co-Authored by JMH3143
BugCheck 7A, {5, 0, 2000, ffffe00112d2fca0}
Probably caused by : memory_corruption ( nt!MiPfCompleteCoalescedIo+a9 )
Followup: MachineOwner
1: 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: 0000000000000005, lock type that was held (value 1,2,3, or PTE address)
Arg2: 0000000000000000, error status (normally i/o status code)
Arg3: 0000000000002000, current process (virtual address for lock type 3, or PTE)
Arg4: ffffe00112d2fca0, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS
BUGCHECK_STR: 0x7a_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: SkyDrive.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff800c31f9411 to fffff800c315ffa0
STACK_TEXT:
ffffd001`d5e2e2a8 fffff800`c31f9411 : 00000000`0000007a 00000000`00000005 00000000`00000000 00000000`00002000 : nt!KeBugCheckEx
ffffd001`d5e2e2b0 fffff800`c30327cf : ffffd001`d5e2e368 00000000`00000000 ffffe001`0d871dd8 00000000`c0000017 : nt!MiPfCompleteCoalescedIo+0xa9
ffffd001`d5e2e300 fffff800`c3087dea : ffffe001`14b25510 ffffd001`d5e2e3c1 00000000`00000000 00000000`00000010 : nt!MiPfCompletePrefetchIos+0xbb
ffffd001`d5e2e330 fffff800`c339f04b : 00000000`00000010 ffffe001`14b25510 00000000`00000000 00000000`00000001 : nt!MiPrefetchVirtualMemory+0x3fa
ffffd001`d5e2e420 fffff800`c339d0e6 : 00000000`00001113 00000000`00001113 00000000`00001113 00000000`00000000 : nt!MmPrefetchVirtualMemory+0xe3
ffffd001`d5e2e510 fffff800`c33a334e : ffffd001`d5e2e620 00000000`00000000 ffffd001`00000002 00000000`00000002 : nt!PfpPrefetchPrivatePages+0x1f2
ffffd001`d5e2e5d0 fffff800`c33a367e : ffffc001`1353f000 ffffc001`1353f000 ffffd001`d5e2e7f0 00000000`00000000 : nt!PfpPrefetchRequestPerform+0x22a
ffffd001`d5e2e740 fffff800`c33a185c : 00000000`00000001 00000000`00000001 ffffc001`1353f000 ffffe001`123cacd0 : nt!PfpPrefetchRequest+0x11e
ffffd001`d5e2e7c0 fffff800`c33a0e22 : ffffe001`57ebf670 00000000`00000000 00000000`00000000 e0011260`cd70ff01 : nt!PfSetSuperfetchInformation+0x13c
ffffd001`d5e2e8a0 fffff800`c316b7b3 : ffffe001`0d93b080 00000088`5848b8d0 00000000`00000000 00000000`00000000 : nt!NtSetSystemInformation+0xda
ffffd001`d5e2eb00 00007ff8`fe04c3fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000088`57ebf608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`fe04c3fa
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiPfCompleteCoalescedIo+a9
fffff800`c31f9411 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiPfCompleteCoalescedIo+a9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5318053f
IMAGE_VERSION: 6.3.9600.17041
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: a9
FAILURE_BUCKET_ID: 0x7a_0_nt!MiPfCompleteCoalescedIo
BUCKET_ID: 0x7a_0_nt!MiPfCompleteCoalescedIo
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7a_0_nt!mipfcompletecoalescedio
FAILURE_ID_HASH: {63a51029-9032-9aa8-88b4-99fa48519c80}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Similar Messages

Windows 8.1 kernel_data_inpage_error BSOD

Hey there, had a windows update last night when i logged off, did the usual update and shut down, and it carried on this morning when i switched my PC on.
Since then i have had 3 lock ups of sorts, everything stops responding but the mouse still moves, only way was to hold the power button down on my tower and restart that way.
I then had a BSOD with windows 8.1 kernel_data_inpage_error, iv done a ram check/test and all was fine, scanned/checked my C drive, all is fine, however, doing the /scannow it is saying found corrupt files but was unable to fix some, details in the
CBS log iv attached the log, any help please? :)
http://1drv.ms/1tp6fxb
I also looked for a mini dump file but i couldnt see/find the minid ump folder

We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers
were loaded, and what was responsible.
Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here
If you have any questions about the procedure please ask
If you are using Blue screen view, who crashed, or a similar application, don't. They are wrong at least as often as they are correct
Wanikiya and Dyami--Team Zigzag

Blue Screen, kernel_data_inpage_error, disk drives missing on reboot

I just bought a new laptop, ASUS ROG G750JW, and installed a Mushkin Chronos 240GB SSD. I clean installed Windows 8.1 Pro on the SSD, and kept the original 750GB HDD, as well as a 500GB HDD, as secondary drives. I have been having rather random blue screens.
I had to disable auto-restart to see the error message: kernel_data_inpage_error.
The fun part is that when I soft restart after the blue screen, my hard drives are missing from the BIOS. I have to completely power down and then restart it for the HDDs to be detected. Since all 3 drives go missing, I can be rather confident that the problem
is not caused by any one of the drives (i.e. my SSD is not defective).
The problem originally occurred when I was installing Office 365 - the laptop would blue screen every time I tried starting the installation. However, each attempt would proceed a little further and eventually Office installed, so I can't use that as a reliable
test. Other occurrences have been, as far as I can tell, completely random. I was noticing that the BSOD occurred often enough during Windows Update installs, but I could not find any significant correlation when I compared my event log to my update
log. I was able to install the most recent Windows 8.1 Update released this Tuesday with no problems.
I have run diagnostics on all of my drives, which come back completely green. I have run chkdsk and sfc /scannow, none of which reported any errors. I have also run Driver Verifier according to the instructions
in this article which did catch several "0x000000c4" bug checks, which I was able to narrow down to the miniport driver.
My last action was to disable checking this driver in Driver Verifier, and I have not since experienced any problems. I have just finished running a 2+ hour long stability test using AIDA64 portable trial version, which caused no problems.
Since my drives go missing when this happens (whether as a cause or effect, I do not know), I have no memory dumps or event logs to share. I have since configured Windows to save memory dumps to my laptop, but with no reliable way to cause the blue screen,
I've been unable to capture a dump yet.
Soooo who wants to help me fix this? I've been offered warranty RMAs by both ASUS and Mushkin, but until I can reliably reproduce the error and confirm the cause, I'm not sending anything back (cause I don't know
what to send!).

Jay
If you don't have dmps lets take a look at your event viewer logs
Please provide us with your Event Viewer administrative logs by following these steps:
Click Start Menu
Type eventvwr into Search programs and files (do not hit enter)
Right click eventvwr.exe and click Run as administrator
Expand Custom Views
Click Administrative Events
Right click Administrative Events
Save all Events in Custom View As...
Save them in a folder where you will remember which folder and save as Errors.evtx
Go to where you saved Errors.evtx
Right click Errors.evtx -> send to -> compressed (zipped) folder
Upload the .zip file to Onedrive or a file sharing service and put a link to it in your next post
If you have updated to win 8.1 and you get the error message "the system cannot find the file specified" it is a known problem. The
work around is to edit the registry. If you are not comfortable doing this DONT. If you are, backup the key before you do
Press Win+"R" and input regedit
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"
Wanikiya and Dyami--Team Zigzag

T60 KERNEL_DATA_INPAGE_ERROR

Hello,
I've got an 8'ish year old T60 with all original components except the fan. I've been getting a KERNEL_DATA_INPAGE_ERROR for about two years now. I understand it's typically due to a failure of the HDD or the hard drive connecting cables. In more rare cases it can also be a memory/processor/motherboard. It's annoying, but manageable. Sometimes it happens 3 times in two hours... actually it just restarted on me in the middle of typing this! Other days it doesn't restart for days. But it has gotten progressively worse.
I've run memtest to check the RAM - no problems. I've ran multiple HDD tests - no problems. I've run disk repair utilities - either no problems or it reports it fixed all issues. The CPU temperature never rises above 73 degrees, and it rarely goes above 65 degrees, so overheating is not an issue. My total available HDD memory has not decreased at all (still at the original 88.2GB), so it doesn't seem like an imminent HDD failure. I've had no noticeable data loss. Sometimes when it restarts it launches the disk repair utility, does the repair and then boots fine. Other times it gives odd messages, like there is no drive to boot from, or a fan error, but after a reboot there is no issue.
With the experience of the T60 users on the forum, I wanted to ask, am I looking at a HDD failure, or a HDD connector cable failure?
If the HDD fails, my plan is to purchase a HGST Travelstar 7200rpm SATA III 32MB Cache 1TB.
If the cable fails, I have no idea if it's possible to replace.
I routinely backup all my data, so that's not an issue. So far this is more of a nuisance, but it seems to be getting worse by the week. Any thoughts?

Hello.
This definitely sounds like bad sector issues on your HD, and since it's been going on for a
long time, it's way past due to swap it out. In a T60, there is no cable, the SATA port is directly
attached to the motherboard, and if this was a failure in the soldering, you'd have much more
serious issues at hand.
Have you checked your drive for bad sectors registered in the SMART data of the drive itself?
Running all kinds of tools to repair it, including chkdsk only blocks those sectors, which will
continue to multiply after repairs. This is only a certain grace period you get when they start
appearing and a drive swap is absolutely recommended at the first sign of such failure.
The fastest way to view the SMART data is to fire up a Linux LiveCD and view the HD status
in the Disk Utility there, or you can use f.e. this tool in Windows. There are many others.
HDTune
Give it a whirl and see if your problem doesn't lie in a rapidly deteriorating drive.
ThinkPad W540 (20BG) - i7-4800MQ/24GB // ThinkPad T440s (20AQ) - i7-4600U/12GB
ThinkPad T440p (20AW) - i7-4800MQ/16GB // ThinkPad Helix (3698-6EU) - i5-3337U/4GB
ThinkPad W520 (4282-W4Q) - i7-2720QM/32GB // ThinkPad T400 (2767-W1C) - P9500/8GB
ThinkPad T61 (7665-CTO) - T7700/4GB // ThinkPad T60p (8741-C2G) - T7400/4GB

KERNEL_DATA_INPAGE_ERROR (7a)

Hi,
Getting blue screen error......
I am running Windows 7 and it is a Dell xps L401x Laptop. I already formatted my laptop. check with CHKDSK various tool of Hiren booCD but nothing found.
finally i run the debug and get the report which is paste below due to lack of knowledge i am unable to know the exect
problem and solution...Thanks
link for mini dump file
https://onedrive.live.com/redir?resid=6CB3B43C2BD0BF32!107&authkey=!AFzXv8urMjarb-Q&ithint=file%2cdmp
Debugging report...............
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081114-21762-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a1890
Debug session time: Mon Aug 11 20:05:01.977 2014 (UTC - 7:00)
System Uptime: 0 days 8:57:27.329
Loading Kernel Symbols
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fc40044088, ffffffffc000000e, 77fdf860, fffff88008811087}
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : hardware ( RTKVHD64+198087 )
Followup: MachineOwner
2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88008811087, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
r8=fffffa8006292000 r9=0000000000000000 r10=fffff88007dbe440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x198087:
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
Resetting default scope
MISALIGNED_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
LAST_CONTROL_TRANSFER: from fffff80002f46752 to fffff80002ed3bc0
STACK_TEXT:
fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RTKVHD64+198087
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_ip_misaligned_rtkvhd64.sys
FAILURE_ID_HASH: {a2776c08-6e06-71ea-9f78-79cfb284ff53}
Followup: MachineOwner
2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88008811087, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
r8=fffffa8006292000 r9=0000000000000000 r10=fffff88007dbe440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x198087:
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
Resetting default scope
MISALIGNED_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
LAST_CONTROL_TRANSFER: from fffff80002f46752 to fffff80002ed3bc0
STACK_TEXT:
fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RTKVHD64+198087
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_ip_misaligned_rtkvhd64.sys
FAILURE_ID_HASH: {a2776c08-6e06-71ea-9f78-79cfb284ff53}
Followup: MachineOwner
2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88008811087, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
r8=fffffa8006292000 r9=0000000000000000 r10=fffff88007dbe440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x198087:
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
Resetting default scope
MISALIGNED_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
LAST_CONTROL_TRANSFER: from fffff80002f46752 to fffff80002ed3bc0
STACK_TEXT:
fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RTKVHD64+198087
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_ip_misaligned_rtkvhd64.sys
FAILURE_ID_HASH: {a2776c08-6e06-71ea-9f78-79cfb284ff53}
Followup: MachineOwner
2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88008811087, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
r8=fffffa8006292000 r9=0000000000000000 r10=fffff88007dbe440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x198087:
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
Resetting default scope
MISALIGNED_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
LAST_CONTROL_TRANSFER: from fffff80002f46752 to fffff80002ed3bc0
STACK_TEXT:
fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RTKVHD64+198087
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_ip_misaligned_rtkvhd64.sys
FAILURE_ID_HASH: {a2776c08-6e06-71ea-9f78-79cfb284ff53}
Followup: MachineOwner
2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88008811087, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
r8=fffffa8006292000 r9=0000000000000000 r10=fffff88007dbe440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x198087:
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
Resetting default scope
MISALIGNED_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
LAST_CONTROL_TRANSFER: from fffff80002f46752 to fffff80002ed3bc0
STACK_TEXT:
fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RTKVHD64+198087
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_ip_misaligned_rtkvhd64.sys
FAILURE_ID_HASH: {a2776c08-6e06-71ea-9f78-79cfb284ff53}
Followup: MachineOwner
2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88008811087, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
r8=fffffa8006292000 r9=0000000000000000 r10=fffff88007dbe440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x198087:
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
Resetting default scope
MISALIGNED_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
LAST_CONTROL_TRANSFER: from fffff80002f46752 to fffff80002ed3bc0
STACK_TEXT:
fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RTKVHD64+198087
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_ip_misaligned_rtkvhd64.sys
FAILURE_ID_HASH: {a2776c08-6e06-71ea-9f78-79cfb284ff53}
Followup: MachineOwner
2: 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: fffff6fc40044088, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 0000000077fdf860, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88008811087, 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: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
TRAP_FRAME: fffff88007dbe4a0 -- (.trap 0xfffff88007dbe4a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000c00000bb rbx=0000000000000000 rcx=000000000000001b
rdx=fffffa80064db000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88008811087 rsp=fffff88007dbe630 rbp=fffffa800666fc0f
r8=fffffa8006292000 r9=0000000000000000 r10=fffff88007dbe440
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
RTKVHD64+0x198087:
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h] ds:00000001`18b4ffc2=????????????????
Resetting default scope
MISALIGNED_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
LAST_CONTROL_TRANSFER: from fffff80002f46752 to fffff80002ed3bc0
STACK_TEXT:
fffff880`07dbe188 fffff800`02f46752 : 00000000`0000007a fffff6fc`40044088 ffffffff`c000000e 00000000`77fdf860 : nt!KeBugCheckEx
fffff880`07dbe190 fffff800`02efa91f : fffffa80`054341c0 fffff880`07dbe300 fffff800`0310e540 fffffa80`054341c0 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`07dbe270 fffff800`02ee11b9 : 00000000`00000000 00000000`00000008 ffffffff`ffffffff fffff880`04465ae9 : nt!MiIssueHardFault+0x28b
fffff880`07dbe340 fffff800`02ed1cee : 00000000`00000008 fffff880`08811087 00000000`ffffff00 00000000`00000005 : nt!MmAccessFault+0x1399
fffff880`07dbe4a0 fffff880`08811087 : 00000000`00000000 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 : nt!KiPageFault+0x16e
fffff880`07dbe630 00000000`00000000 : 00000000`00000005 ffff0000`0fa372cc fffffa80`0666f2d0 fffff880`07dbe7b0 : RTKVHD64+0x198087
STACK_COMMAND: kb
FOLLOWUP_IP:
RTKVHD64+198087
fffff880`08811087 ffb45807ffb458 push qword ptr [rax+rbx*2+58B4FF07h]
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: RTKVHD64+198087
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
BUCKET_ID: X64_IP_MISALIGNED_RTKVHD64.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_ip_misaligned_rtkvhd64.sys
FAILURE_ID_HASH: {a2776c08-6e06-71ea-9f78-79cfb284ff53}
Followup: MachineOwner
2: kd> lmvm hardware
start end module name
2: kd> lmvm hardware
start end module name

Please share the original DMP files for the BSOD.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Kernel_data_inpage_error & non-system disk error but everything running OK for a while

Hi,
can someone please help me out since I have a deadline in coming up and need my laptop to work properly!
I have windows 7 64bit running on a HP ProBook 6550b. My PC runs fine for about an hour, after an hour the screen freezes for 10 seconds and then I get the KERNEL_DATA_INPAGE_ERROR. He reboots and then I get the message 'Non-system disk or disk error'
Then I just shut down my PC and start it back up and everything works perfectly fine again for about 45 minutes. Then again the same problem.
I have tried multiple things. I executed a chkdsk /f /r This did find some problems. I tried and followed some instructions about changing the paging file settings. I ran a memtest. No errors with the memtest.
Finally I went in the BIOS and I did a HP harddrive test. This one failed almost immediately but I can just close the BIOS and start my PC and windows runs fine.
What can I do to resolve this problem other then buying a new harddrive. (I intend to buy a new laptop anyways in couple of months after I have passed my deadline and test period has finished. But for short term I really needs this to work.)
Many thanks!!
Johan
This question was solved.
View Solution.

Just in case someone else encouters this.
The problem was due to my SSD M4 hard drive. There was a problem with the firmware causing hourly crashes after the disk has been in use for more then +-5200 hours. Upgrading the firmware fixed this for me.

Re: kernel_data_inpage_error blue screen on Equium L40

does anyone know how to help solve my problem please? I get a blue screen of death randomly and then it takes around 30 mins or longer to load my laptop up properly again. It won't boot sometimes and I have to restart until in the f12 option I can see something that says 'SATA'
I have tried a system restore, uninstalling the trial of adobe illustrator I downloaded (from the official adobe website) and I have ran chkdsk, mcafee scans, malware bytes anti malware scan and they havn't found a problem. I can't use any cd,my drive hasn't worked for a while now.
I think the problem is getting worse because sometimes on the blue screen it says a process or thread has stopped working and I would still just be on my desktop not doing anything. I have had this problem for 2 weeks now which is also around the time when I got the illustrator trial,which I completely removed. Any help would be greatly appreciated.
I have also done all of the recent updates

I have vista 32-bit and its powered by microsoft but I don't know if that is the OS, I'm not that good when it comes to something other than browsing the internet. My DVD drive is broken so it doesn't read any discs, I have backed up my files in the E: drive. Is there a way I could do the recovery thing without the DVD?
thanks for replying..I did a crash test report and got this, maybe it will give better info :
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 17/12/2010 14:04:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121710-02.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x38D40)
Bugcheck code: 0x7A (0xFFFFFFFFC040E968, 0xFFFFFFFFC000009D, 0x7424B8C0, 0xFFFFFFFF81D2D000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. KERNEL_DATA_INPAGE_ERROR
On Fri 17/12/2010 02:41:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121710-01.dmp
This was probably caused by the following module: spsys.sys (spsys+0x7006C)
Bugcheck code: 0x7A (0xFFFFFFFFC05454A8, 0xFFFFFFFFC000009D, 0x69785860, 0xFFFFFFFFA8A9506C)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\spsys.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: security processor
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Wed 15/12/2010 14:03:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121510-02.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF87826020, 0xFFFFFFFF8782616C, 0xFFFFFFFF82472710)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. CRITICAL_OBJECT_TERMINATION
On Wed 15/12/2010 00:08:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121510-01.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8E7C6D90, 0xFFFFFFFF8E7C6EDC, 0xFFFFFFFF8245E710)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. CRITICAL_OBJECT_TERMINATION
On Tue 14/12/2010 10:21:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121410-01.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF87984BB0, 0xFFFFFFFF87984CFC, 0xFFFFFFFF82439710)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. CRITICAL_OBJECT_TERMINATION
On Mon 13/12/2010 17:23:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121310-03.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8E87FD90, 0xFFFFFFFF8E87FEDC, 0xFFFFFFFF8243C710)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. CRITICAL_OBJECT_TERMINATION
On Mon 13/12/2010 15:29:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121310-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x7A (0xFFFFFFFFC0601A70, 0xFFFFFFFFC000009D, 0xBF7C884, 0xFFFFFFFFC034E000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 13/12/2010 14:44:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121310-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xD09ED)
Bugcheck code: 0x7A (0xFFFFFFFFC04418B0, 0xFFFFFFFFC000009D, 0x79DF860, 0xFFFFFFFF883169ED)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
On Sun 12/12/2010 18:15:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121210-02.dmp
This was probably caused by the following module: mfehidk.sys (mfehidk+0x2DF8C)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8D7FED90, 0xFFFFFFFF8D7FEEDC, 0xFFFFFFFF82468710)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\drivers\mfehidk.sys
product: SYSCORE
company: McAfee, Inc.
description: McAfee Link Driver
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mfehidk.sys (McAfee Link Driver, McAfee, Inc.).
Google query: mfehidk.sys McAfee, Inc. CRITICAL_OBJECT_TERMINATION
On Sun 12/12/2010 13:22:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121210-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xCDB8D)
Bugcheck code: 0xF4 (0x3, 0xFFFFFFFF8DE9ED90, 0xFFFFFFFF8DE9EEDC, 0xFFFFFFFF82434710)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 11/12/2010 18:23:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121110-01.dmp
This was probably caused by the following module: iastor.sys (iaStor+0x475A)
Bugcheck code: 0x100000D1 (0x3, 0x2, 0x1, 0xFFFFFFFF8301075A)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x86
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: iastor.sys (Intel Rapid Storage Technology driver - x86, Intel Corporation).
Google query: iastor.sys Intel Corporation CUSTOM_ERROR
On Fri 10/12/2010 17:22:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\Mini121010-01.dmp
This was probably caused by the following module: pci.sys (pci+0x16624)
Bugcheck code: 0x7A (0xFFFFFFFFC0403820, 0xFFFFFFFFC000009D, 0x20296860, 0xFFFFFFFF80704624)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\pci.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Plug and Play PCI Enumerator
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

My windows 7 laptop keeps on turning up a BSOD- help!

I have a Dell Inspiron n5110 with Windows 7 Ultimate Installed. I've had the laptop close to 2 years now.
For the past week, it has been repeatedly turning up a blue screen with Kernel Data Inpage Error, code 0x0000007A.
One or twice it has also turned up the code 0x000000F4 and 'a process or thread crucial to system operation has unexpectedly exited or been terminated'.
This happens randomly every time I use my laptop. I restart, only to have it crash again. I ran disk check on all my drives and also checked my RAM, but no errors have turned up. I also ran a full antivirus scan and had no issues.
Please guide me as to what I should do. I have university access to the Microsoft store so I can reinstall my OS (or windows 8) if that would solve the problem.
Any help would be appreciated. Thank you.

Answer from previous discussion (Meghmala):
The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007Astates that the requested page of kernel data from the paging file could not be read into memory. It appears that
there are some issues with the hard disk.
Use check disk command for any errors on hard disk -
Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted.
For safety you can back up your data before using the check disk command.
Use the check disk commands as follows:
1. Click Start.
2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.
4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.
NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.
You may refer to the below mentioned link for more details -
http://msdn.microsoft.com/en-us/library/ms793989.aspx
Hope this helps. Let us know the results.
Rgds
Milos

Windows 8.1 Crashes with Dumps from desktop

I have experienced a number of crashes on a PC with Windows 8.1, and have analyzed the mini dumps and one full dump so far, and have seen a myriad of different crash results including IRQL_NOT_LESS_OR_EQUAL, KERNEL_DATA_INPAGE_ERROR, CRITICAL_PROCESS_DIED.
I've posted the raw dmp files, as well as txt files of the results from running them through the debugger here...
https://onedrive.live.com/redir?resid=F1640CE12DEBCE6B!130&authkey=!ABlrD4zyv8gT_SU&ithint=folder%2ctxt
I've ran memtest86 very thoroughly on the RAM with 0 errors, I've updated all of the drivers, ran chkdsk on the HDD, and cannot find any glaring errors, and the computer still seems to crash at random points in time with different applications running each
time. The computer is a custom build if the components matter, and each of the component can be found here...
http://pcpartpicker.com/p/zfmYqs

TTD
There is a very specific problem. The HD. I would go the HD maker and download their HD checking utility and run it
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Ken\Desktop\New folder\022015-12359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is:
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff800`5ba06000 PsLoadedModuleList = 0xfffff800`5bcdf250
Debug session time: Fri Feb 20 22:11:14.919 2015 (UTC - 5:00)
System Uptime: 0 days 23:53:22.598
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {fffff6fb400a1f28, ffffffffc000000e, 10d7b1880, fffff680143e5000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1561f )
Followup: MachineOwner
3: 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: fffff6fb400a1f28, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000010d7b1880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff680143e5000, 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: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8005bb7c4cf to fffff8005bb569a0
STACK_TEXT:
ffffd000`309d63e8 fffff800`5bb7c4cf : 00000000`0000007a fffff6fb`400a1f28 ffffffff`c000000e 00000001`0d7b1880 : nt!KeBugCheckEx
ffffd000`309d63f0 fffff800`5ba377f8 : 00000000`00000002 ffffd000`309d6558 ffffe001`d859cdd8 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1561f
ffffd000`309d64e0 fffff800`5ba70b7a : ffffe001`d859cdd8 ffffe001`d8385880 01000000`00000001 00000000`00000000 : nt!MiIssueHardFault+0x184
ffffd000`309d65a0 fffff800`5ba67941 : 01000000`00000001 00000000`00000080 fffff680`143e5000 00000000`00000080 : nt!MmAccessFault+0x5ba
ffffd000`309d6760 fffff800`5c0076f1 : ffffe001`d838eb00 00000028`00000000 ffffd000`00000000 00000000`00000004 : nt!MiCommitExistingVad+0x901
ffffd000`309d6890 fffff800`5bb621b3 : 00000028`6fd1e7a0 00000000`00044000 00000028`6f323878 00000000`00043ff0 : nt!NtAllocateVirtualMemory+0xfbd
ffffd000`309d6a90 00007ffb`db9b0f5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000028`6fd1d5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`db9b0f5a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+1561f
fffff800`5bb7c4cf cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+1561f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 54b0c2f7
IMAGE_VERSION: 6.3.9600.17630
BUCKET_ID_FUNC_OFFSET: 1561f
FAILURE_BUCKET_ID: 0x7a_c000000e_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x7a_c000000e_nt!_??_::FNODOBFM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7a_c000000e_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {5654bc57-9720-546c-de0e-76a002c66fe5}
Followup: MachineOwner
Wanikiya and Dyami--Team Zigzag

Windows 8.1 Crashes with MiniDumps on desktop

I have experienced a number of crashes on a PC with Windows 8.1, and have analyzed the mini dumps, and have seen a myriad of different crash results including IRQL_NOT_LESS_OR_EQUAL, KERNEL_DATA_INPAGE_ERROR, CRITICAL_PROCESS_DIED. I've posted the raw dmp
files, as well as txt files of the results from running them through the debugger here...
https://onedrive.live.com/redir?resid=F1640CE12DEBCE6B!130&authkey=!ABlrD4zyv8gT_SU&ithint=folder%2ctxt
I've ran memtest86 very thoroughly on the RAM with 0 errors, I've updated all of the drivers, ran chkdsk on the HDD, and cannot find any glaring errors, and the computer still seems to crash at random points in time with different applications running each
time. The computer is a custom build if the components matter, and each of the component can be found here...
http://pcpartpicker.com/p/zfmYqs

I will also try to catch a full dump next time it crashes.

Problem with Threads and "plase wait..."-Window

Hi everyone,
I have a problem that I'm not able to solve in any way... I have a time-consuming task (a file decryption) which I execute in a separate thread; I've used the SwingWorker class, like suggested by sun-tutorial, and it works right. The problem is that I have to wait that the decryption have finished before continuing with program-execution. Therefore I would like to display a "please wait"-window while the task runs. I've tryed all the possible ways I know but the problem is always the same: the waitWindow is displayed empty, the bounds are painted but the contents no; it's only painted when the decrypt-task has finished. Please help me, I have no more resources....
decrypt-file code:
public class DecryptFile {
private String cryptedFileNameAndPath;
private ByteArrayInputStream resultStream = null;
// need for progress
private int lengthOfTask;
private int current = -1;
private String statMessage;
public DecryptFile(String encZipFileNameAndPath) {
    cryptedFileNameAndPath = encZipFileNameAndPath;
    //Compute length of task...
    // 0 for indeterminate
    lengthOfTask = 0;
public ByteArrayInputStream getDecryptedInputStream() {
    return this.resultStream;
   * Called from ProgressBarDemo to start the task.
public void go() {
    current = -1;
    final SwingWorker worker = new SwingWorker() {
      public Object construct() {
        return new ActualTask();
    worker.start();
   * Called from ProgressBarDemo to find out how much work needs
   * to be done.
public int getLengthOfTask() {
    return lengthOfTask;
   * Called from ProgressBarDemo to find out how much has been done.
public int getCurrent() {
    return current;
public void stop() {
    current = lengthOfTask;
   * Called from ProgressBarDemo to find out if the task has completed.
public boolean done() {
    if (current >= lengthOfTask)
      return true;
    else
      return false;
public String getMessage() {
    return statMessage;
   * The actual long running task. This runs in a SwingWorker thread.
class ActualTask {
    ActualTask () {
      current = -1;
      statMessage = "";
      resultStream = AIUtil.getInputStreamFromEncZip(cryptedFileNameAndPath); //here the decryption happens
      current = 0;
      statMessage = "";
}The code that calls decryption and displays waitWindow
      final WaitSplash wS = new WaitSplash("Please wait...");
      final DecryptFile cryptedTemplate = new DecryptFile (this.templateFile);
      cryptedTemplate.go();
      while (! cryptedTemplate.done()) {
        try {
          wait();
        } catch (Exception e) { }
      this.templateInputStream = cryptedTemplate.getDecryptedInputStream();
      wS.close();Thanks, thanks, thanks in advance!
Edoardo

Maybe you can try setting the priority of the long-running thread to be lower? so that the UI will be more responsive...

I install window 8 and Unfortunatly all drive format. And all drive mix, now i have only 1 DRIVE C. I want Bit locker Drive's data Back

Last sunday i install a window 8 and this window format my all drive & make it 1 drive (DRIVE C). Before all of this i have 5 drive in different size with 1 Bitlocker protect drive.
So i try data recovery software to recover my data. i got back all my data without that ( bitlocker ) protected drive.
so please guys help me how can i get back data from bitlocker protected drives.
please please help me.

Hi,
I sorry for your experience, but there is no way to recovery the data encryped by BitLocker untill now.
BitLocker is designed to make the encrypted drive unrecoverable without the required authentication. When in recovery mode, the user needs the recovery password or recovery key to unlock the encrypted drive. Therefore, we highly recommend
that you store the recovery information in AD DS or in another safe location.
Please refer to the link below for the statement:
http://technet.microsoft.com/de-de/library/ee449438(v=ws.10).aspx#BKMK_RecoveryInfo
Roger Lu
TechNet Community Support

HP LaserJet Enterprise 500 Color MFP M575 - Can't scan from Windows

We recently purchased and installed an HP LaserJet Enterprise 500 Color MFP M575 to be used as a networked all-in-one solution for a number of offices. I have been able to get it set up on our network and have installed the appropriate drivers on the requested Windows 7 x64 machines, and network printing works perfectly. However, it seems that despite the fancy scanning features available from the all-in-one itself (scan to email, scan to a network folder, etc.), I can't find any way to do an old-fashioned scan from Windows.
I have installed the full software solution available on the driver download page for the device, and while Windows lists the device as a "Multi Function Printer; Scanner" it does not recognize it as an actual scanner. The built-in Windows Fax and Scan simply reports that no scanners are installed. The software installation did not include the HP Solution Center (which I am used to seeing from my experience with various other HP all-in-one devices) or any equivalent for direct scanning. The driver download page for the device does not include any separate scanning drivers, so I can't be certain if they were included with the full installation or exist at all.Some of our staff also use Adobe Acrobat to scan, and even that fails to recognize the MFP as a scanner.
We'll eventually be setting up the device to scan directly to a network folder, but we need a fallback while IT takes their time getting it set up; I can't imagine that the simplest option is not available at all. I must be missing something here, any assistance would be greatly appreciated.
Edit: To add, I also ran the HP Print and Scan Doctor. Interestingly, it reports the device as a printer and only offers to "Fix Printing" without any sort of resolution for my scanning problem.

There is no change to this problem after 6 months since the last post. Put simply, and as stated in the previous posts, there is no way to scan a document and receive the image on your PC. If you are working with graphics for any length of time or want to create an image for inclusion as an image in a document or web page using this piece of equipment will not allow you to do so.
Great shame as every other function works well - it cannot be beyond the wit of HP to include a Windows application that enables you to scan an image, receive it in the software you are using at the time (e.g. Outlook, Word, Photoshop...) and use it in your work.
HP Printers several years older than this £1000+ Enterprise printer were able to do this simple job and have done so for a great many years. Just being able to use Microsoft's Fax and Scan would be start.

Windows no longer detecting my Audigy 4?(Non-P

Hey all. I've had my Audigy 4 (non-Pro) installed and working super for about 50 days, but it started giving me a weird problem. Windows was no longer detecting the card! It was weird. DX Diag, programs like EVEREST... they all report no sound card whatsoever.
Here are my PC specs:
XP Home Edition
Albatron K8X800 Pro
S754 3200+ ClawHammer
x 2 OCZ ELPE 52 MB(2-3-2-5)
Visiontek XTASY X850XT PE
x 80 GB SATA 2 Seagate, x 80 GB Maxtor
Some other things to note:
XP has been repaired. Went from Service Pack , updates, and all the way to Service Pack 2. The card requires XP w/SP2, yes, so I have that covered.
Onboard audio is disabled through the bios. I have AC'97 integrated audio on this.
My motherboard has fi've PCI slots - although I can only access 4 because my video card is in the way, and I have tried three of those and I get the same problem.
I have tried it in other PCs in my house, double-checked each time - so it is not ESD as I originally believed. It works just fine on those PCs. It is being not located only on MY PC.
So guys and gals, I do not know what to do... I am stumped. It's the weekend so I can't call Creative support until Monday. I don't want to request an RMA through my warranty because clearly it's just a problem with my PC. What should I do?!Message Edited by Celsius on -26-2005 07:36 PM

Device not recognized in iTunes

IPod Touch/Phone 4gens No Longer Detected in WINDOWS MY COMPUTER but OK in iTunes

Since I have not found help online regarding the above situation I'm looking for help accordingly. For most folks it's iTunes not detecting i-Devices, but my situation is unique.
It started last night after I was on the phone for hours with Norton regarding error messages I was getting with Internet Security. Those issues have been resolved.
Again: iTunes detects and interacts successfully with ALL my iDevices. Windows Vista > My Computer no longer does.
Please help.

Just now I performed the following:
Turned off and turned back on AMDS(Apple Mobile Device) Service.
Disabled Norton Internet Security, and tried checking if Windows would see my devices.
For anyone who has Windows Vista you are familiar with the notes that play when you plug in a USB device: "da-dunk!" Low-High note dadunk indicates connected. High-low indicates it was disconnected.
I can tell there is a problem because right after the Low-High dadunk in Vista I get a triple Low-note Du-du-dunk.
Please help!

Kernel_data_inpage_error in Windows 8.1

Similar Messages

Maybe you are looking for