KERNEL_DATA_INPAGE_ERROR
Updated to 5.0 and I kept getting the blue screen of death. Managed to keep my machine running long enough to install 5.1 to see if that helped - it didn't. Now uninstalled both and keep getting the blue screen that has the KERNELDATA_INPAGEERROR on it. I haven't installed ANY other software or hardware on the machine, virus stuff is up to date so I can only presume it's something that the new version of iTunes has done.
Anyone else encountered this? What the **** do I do?!?
hi Mike!
what other CD ripping/burning software do you have installed on that machine? go into the "about" screen in each package to check on the
b precise name and version number.
(checking up on something here that happened every now and then on a 4.9 upgrade.)
love, b
Similar Messages
-
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 -
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 folderWe 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 -
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 -
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 namePlease 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 updatesI 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. -
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 -
Hi,
I need help for my HP Pavilion Notebook.
The Model Details are as below:
Model:dv4-1551dx
OS: WIndows 7 64 Bit
Place of Purchase: Best Buy at Torrance ,California
My Problem:
I am getting a Blue Screen Shut down with KERNEL_DATA_INPAGE_ERROR.
I have run the CHKDSK Repair, it ran for 12 hours and replaced a number of bad sectors. Then I ran the HDD Self test and got error that "Hard Disk Test Failed" and no reason code. I have gone through the forum and found that the experts always suggested to replace the Hard Disk. Can any of the experts can kindly help me with the following:
1.Do I need to replace the Hard Disk
2.If it is Yes, then how can I restore the system?
3.If I need to have the Restore Disk, unfortunaltely I do not have that. I am presently staying in Munich Germany. Can I order one for my Computer and Germany. I tried in the HP Deutschland website and it could not find my model number.
4.Is there any other way to get past the Blue Screen Error?
I will really appreciate your help in this regards.
Thanks a bunch in advance.Straciatella,
Here is a document that will show you how to create your own disk. You can use either blank DVD’s or a USB flash drive.
Here is a document that shows how to restore the system, I wouldn’t recommend this, mainly because you will have to replace the hard drive eventually.
Please respond back at your earliest convenience.
Thanks
Clicking the White Kudos star on the left is a way to say Thanks!
Clicking the 'Accept as Solution' button is a way to let others know which steps helped solve the problem! -
Hello,
somebody help, my T40 uses XP SP3 OS recently I always got a blue screen error and nothing to do but to restart again and again to get back on my workings. Here are some error prompted on my laptop; kernel_data_inpage_error, kernel_stack_inpage_error, unmountable_boot_volume... Some details below that I remember are; 0x00000077, 0x000000FA, 0x000000ED, etc... Kindly advise what to do.
thanks.make sure you update all your driver to the latest.
-
Blue Screen on RESUME on HP Vision All-in-One PC
Hi. For the past week or so my All-in-One PC has been crashing with a Blue Screen whenever it comes out of hibernation. It doesn't seem to matter if it went into hibernate on its own, or through the Start -> Sleep action. The blue screen usually points to a page fault error KERNEL_DATA_INPAGE_ERROR.
I've restored my system in an attempt to fix it. It did, for awhile, but earlier today it started up again.
Some web searching has made me suspect that this is a manifestation of issues with the Microsoft fix KB2670838 . Other users have reported blue screens after installing it (usually as a prerequisite to IE 10), though I haven't seem reports of it happening after a resume, as it is for me.
Have others hit this kind of issue? Any suggestions on resolving it?
I'm planning to uninstall this fix, to see if it helps. I'll report back.
This question was solved.
View Solution.I've isolated the patch that triggers the blue screen to this one:
AMD - Other hardware, Storage Controller - AMD SATA Controller
It's not a Microsoft patch, so there's no KB number, nor can it be uninstalled; you need to restore a previous configuration to correct the problem. However, restoring does work (I've done it three times now). When it's in place I get this blue screen coming out of Resume:
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : 00000000`00000020
Parameter 2 : ffffffff`c000009d
Parameter 3 : fffffa80`05eff7c8
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75c00
Removing the driver fixes the problem.
Hope this helps anyone else that might have hit this bug. Let me know if I can provide more info, or if you'd like an official bug report. -
Hi, I have a Toshiba Satellite L455D-S5976 with Windows 7 Home Premium and a 32-bit operating system. I've been having problems with getting BSODs for well over a month now (I was out of town for most of it), sometimes within a couple minutes of restarting it. It has even occurred in safe mode, and after I tried a system restore. I downloaded Blue Screen View to see if I could find what the problem was, and I got different results for various crashes. It says that the first one was on 03/26/14, which I don't really remember, and the next ones were on 05/09/14 and 05/10/14, before I had to leave, and upon returning, it began happening everyday. The most common file is easily ntkrnlpa.exe, which seems to be present in almost all the crashes, though there are several other files. I understand that I probably need to update or replace those drivers somehow, but I don't know anything about replacing or updating plugins. Can anyone provide any help?
Bug Check 0x1A: MEMORY_MANAGEMENT
Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL
Caused By Driver : atikmdag.sys <- display driver
Caused By Driver : halmacpi.dll <- from Windows (related to the HAL)
Bug Check 0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
Caused By Driver : Wdf01000.sys <- a Windows driver
"WDF Dynamic - Kernel Mode Driver Framework Runtime"
Bug Check 0x24: NTFS_FILE_SYSTEM
Caused By Driver : Ntfs.sys <- file-system driver
Bug Check 0x19: BAD_POOL_HEADER
Caused By Driver : Ntfs.sys
Bug Check 0xC5: DRIVER_CORRUPTED_EXPOOL
Caused By Driver : win32k.sys <- a Windows driver
Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Caused By Driver : Ntfs.sys
Caused By Driver : dxgmms1.sys <- a Windows driver related to graphics
"Microsoft DirectX Graphics MMS system"
Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR
Caused By Driver : disk.sys <- a Windows driver related to disk access
"PnP Disk Driver"
Wow. That's quite a conglomeration!
I suspect hardware trouble. Test the memory. Arrange for the test to run for several hours.
Diagnosing memory problems on your computer
Also run a thorough check on the hard drive.
Check a drive for errors
-Jerry -
After 13 years, can no longer recommend HP - Chronic MB problems on dv6t-7000 unheeded by HP support
I couldn't find anywhere else to voice this - my dv6t-7000 is just out of warranty and thus I don't qualify for email support. I have spent the past year in a back and forth battle with HP customer support and am finally calling it quits after 13 years of exclusively buying from them and recommending them to less tech-savvy friends and family.
I ordered this laptop around July 2012, eager to check out the benefits of Seagate's new 2nd-gen hybrid drives. Laptop arrived and was blazing fast, but starting getting some STOP errors (blue screens) pretty soon. Because this was coupled with hard drive errors, I didn't bother to dig too much into the problem and instead contacted HP, who (very quickly) shipped me a service box. I send them my laptop and get it back a couple of weeks later, but can't figure out what they changed (I later found out they just reflashed the BIOS).
Sure enough, I start getting the same errors again. Contact HP a second time and they recommend a replacement hard drive. Swapped the drives out and started fresh, but within a couple of weeks, the same errors popped up on the new drive. At some point around here, I was told I was being moved up to a Tier 2 support level, which didn't seem to make a difference in how much (or little) support seemed to pay attention to my own observations of the problem. Their process came across as (1) determine if support is needed and warranted (2) ship out prepaid service box (3) let the service department start from scratch to diagnose the issue.
I ended up sending the laptop to HP a third time, after clarifying the issue with the support reps I spoke with and giving them detailed instructions of the problems I had been observing, which seemed to point to a faulty hard drive cable or a related issue with the motherboard itself. The rep was very friendly and promised to relay this information to support before they got their hands on my laptop. Sent it in and again - no difference except a freshly installed operating system.
Before this third service call, I had freshly installed Windows 8, and if anything, the problem had gotten worse. I had run memtest with no errors on either sticks, ran SeaTools DOS with unspecified corruption errors, cleaned out the insides with compressed air, reinstalled WIndows 8 twice from scratch, ran dskchk and SFC countless times with unrepairable errors, run DISM a couple of times unsuccessfully, swapped out the CMOS battery, and was still basically experiencing a stop error every 1-2 days. I reinstalled Win8 after receiving my laptop back for the third time, and continued to have these problems. At this point I gave up trying to send it in to HP, because school was getting in the way of my ability to be without a laptop for 2 weeks at a time.
Currently, I cannot install Windows 8.1 and still experience KERNEL_DATA_INPAGE_ERROR and CRITICAL_PROCESS_DIED stop errors every 2-3 hours. I had one while writing this post, so hopefully I haven't forgotten to include anything. I don't mean to lay all of the blame on HP, but I don't like not having my input listened to or considered. It seems counterintuitive to me - this process could have taken 2 weeks to resolve instead of multiple months to fail and lose a customer in the process.
I bought HP knowing fully well that I was paying for high-end parts and not necessarily build quality. That's never been a problem in 13 years of buying laptops and PCs from them, as well as recommending them to friends and family - we know how to take proper care of expensive technology. But I'm realizing now that when you do get a dud, HP support seems to do everything in its power not to have to replace your laptop even when it's warranted. I will use this laptop until it can no longer function (hopefully a couple of months at least) and then consider another company for the first time in a long time. On the desktop end - well, I've been meaning to build a PC for a while now.I have forwarded your post to the right people for their review. You should hear back from someone shortly via Private Message on this forum.
OrnahP
HP Support Forums Moderator
Clicking the "Kudos Star" to the left is a great way to say thanks!
When your problem has been solved, accept the solution by clicking "Accept as Solution" to help other members in the future!
Rules of Participation -
I have had quite a few problems so this is gonna be a long one.
Hi everyone.
Recently (1½ weeks ago), i bought all the parts i needed for a new computer. Heres the list:
MSI K9N-Diamond
AMD Athlon64 X2 3800+ EE (Energy Efficient 65Watt) + Zalman CNPS9500-AM2 CPU cooler
Corsair XMS2 (2x 1024MB, DDR2-800, 5-5-5-12-T1)
Thermaltake 680Watt
- +3.3v = 28A
- +5v = 30A
- +121 = 14A
- +122 = 23A
- +123 = 15A
XFX GeForce 7900GT, 256MB PCI-E
2x WD Caviar Raid Edition 320GB SATAII, with NCQ
And a floppy drive
Problems started from day one. First time boot, i enter BIOS. Change various stuff (like disabling Seriel/Paralell ports, disabling IEEE1394, setting boot order, enabling RAID controller and enabling all devices). I then enter RAID controller setup (F10), put my 2 WD drives in a raid0 array for maximum performance.
Pop in my WinXP cd, boot, press F6, loading BOTH the required drivers from the floppy i made using MSI cd in my old computer. I see one big drive with roughly 600GB. I make one partition on 16GB for Windows. Choose quick NTFS format, and setup starts copying files.
Then the trouble started, after copying alot of files, i suddenly got a message that setup was unable to copy the file: ABC.XYZ
I just thought: Argh, my cd is probally dusty, Open cdrom, look at cd. No scratches, no dust, no fingerprints... I clean the Phantom dust off the CD at put it in again, but it still cant copy. I restart the computer, starting over from beginning, remove partition and make a new one.
But same results, the setup copies some files but the stops with an "unable to copy" error, only this time its another file.
I tried serveral times, everytim a new file at a new random location in the copy process.
As i have no spare Windows CD, i went to my old computer, downloaded a new WinCD, burned it and tried again... but same results.
I started looking around various forums and found that other ppl had problems with the raid controller, and disabling would fix their problems. I really want to run Raid0 so this is kinda a last resort for me, but i tried it anyways... Enter Raid setup and remove the strip, enter BIOS and disable RAID controller, reboot and retry installing windows.
To my surprise, Windows Setup could actually copy the files and install Windows with no problems whatsoever.
I looked on MSI website and found that a new BIOS was up with the following bugfix:
"Fixed system can not auto boot from Nvidia Stripe 465.77G when onchip raid is enable."
It sounded familar to my problem so I flashed the new BIOS, reset CMOS, booted and made the usual changes in BIOS, made a new strip array in Raid controller setup.
I proceed with installing Windows the same way as described above, but same "cannot copy file xyz.abc" error.
So i destroy the raid array, disable raid controller and install windows again on single disks.
Next problem.
After windows is installed, I install all the drivers from MSI CD and the Creative Sound Blaster CD. I have a Denon 5.1 Surround Reciever hooked up to Coaxial S/PDIF on my computer. In Creative speaker setup, i choose "5.1 Speakers" and click test... but i get no sound. I see the "Digital Output Only" option and enable it and test again... this time i get sound, but ONLY from front left and front right speakers. Furthermore, i NEED the analog output aswell so "Digital Output Only" option should not be enabled in my case. I checked Creative homepage and found this: "On all Audigy series cards, S/PDIF cannot be disabled". That leaves me to think that S/PDIF should work regardless of that "Digital Output Only" setting. Furthermore, when i activate that option, not only does it disable the analog output but also the analog input (Microphone in this case, which i need).
The weird thing is that analog output works fine with surround sound (tried with some 5.1 headphones).
Next problem
Now ive been running with singledisk setup (non raid) for a week. But i have an alarming amount of BSoD errors. Its not just one BSoD, but all kinds of different errors. It is noteable that most of these errors are disk or driver related. After I got alot of different, i started writing them down. Heres a few:
IRQL_NOT_LESS_OR_EQUAL
0x0A (0x0000FFDF, 0x00000002, 0x00000001, 0xSomeAddress)
"Typically due to a bad driver, or faulty or incompatible hardware or software. Technically, this error condition means that a kernel-mode process or driver tried to access a memory location to which it did not have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own)"
KERNEL_MODE_EXCEPTION_NOT_HANDLED
0x8E (0xC0000005, rest of parameters is junk)
"A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade)."
The following 2 errors happened alot while i was copying data from my old computer through network WHILE playing a game to kill time.
KERNEL_DATA_INPAGE_ERROR
0x7A (0xjunk, 0xC0000185, 0xjunk, 0xjunk)
This error gave me the filename Win32k.sys with the address being the same as parameter 3 in the error code.
"A page of kernel data was not found in the pagefile and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware."
KERNEL_STACK_INPAGE_ERROR
0x77 (0xC0000185, 0xC0000185, 0x00000000, 0x00Frandom)
"A page of kernel data requested from the pagefile could not be found or read into memory. This message also can indicate disk hardware failure, disk data corruption, or possible virus infection."
While downloading some lost data via BitTorrent and watching a movie (on the computer), I got this error a few times (30 or so minuttes apart):
DRIVER_IRQL_NOT_LESS_OR_EQUAL
0xD1 (0x00000064, 0x00000002, 0x00000001, 0xjunk)
A filename was supplied: NVTcp.sys (A quick search revealed this as being nVidia Firewall, so i unistalled nVidia NAM)
"The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile."
Also got a few 0xF4 errors.
Most of these errors suggest RAM failure, so i started testing with Memtest86+ and let it run over night. 10 passes, 0 errors.
Next problem
This one is a bit more serious to me. As you might have read above, i was downloading some lost data via BitTorrent. This is how i lost it.
I have an External Maxtor 300GB HDD with USB connection. I use this to store movies when i go to friends and such.
Yesterday i plugged it in for the first time using front panel USB, Windows popped up and told me new hardware installed and bla bla.
I browsed the HDD and i saw a "thumbs.db". I dont like those hidden windows files (and i have them disabled), so i fired up a search for Thumbs.db. When search was finished, i selected all and pressed delete. DING "Windows cannot delete Thumbs.db. File not found.". I browsed the file using explorer and tried deleting it, but same error.
Start->Run->CMD
g:\>chkdsk /f /r
CHKDSK cannot scan RAW-Filesystem.
The file system is NTFS btw. So i safely removed and replugged the device, this time windows did not recognice the device. I tried different USB port (still front panel) and the drive got installed but was unaccessible, until i reformated it.
Could this be connected to above bluescreen and potential hardware errors that the HDD got wiped when i plugged it in or is this just bad coincidence?
Please help!Disable memory EPP mode and retest. ("SLI-Ready Memory" from BIOS, enabled by default)
your board support(feature only on nVidia nForce 590 SLI that's mean only for K9N Diamond) this newest feature provide enhance performance via Enhanced Performance Profiles stored in SPD Memory. if your system memory do not support this feature and option is "Auto" or "Enabled" issues are expected. Sli Ready Memory:
EPP: This is an open memory standard put forth by Corsair and nVIDIA which takes over where JEDEC's SPD leaves off. As the Enhanced Performance Profiles description implies, it adds performance profiles to the memory SPD in addition to the conservative compatibility settings already programmed in. EPP compliant memory is dubbed "SLI Ready" memory on nVidia platforms (great marketing on nVIDIA's part) and allows the system to dynamically tighten up memory timings and increase voltages for better performance with no fuss. Whether you're a novice or experienced computer user, the benefits of EPP are immediate. Corsair is the initial memory manufacturer out the door with this new technology but others are already following suit.
Read more with details:
http://www.behardware.com/news/8167/nvidia-annonce-sli-memory-ou-epp.html
http://www.corsairmemory.com/corsair/pr/PR_Enhanced_Performance_Profiles_EPP.pdf
http://www.nvidia.com/object/IO_31187.html
http://www.legitreviews.com/article/345/3/ -
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
Maybe you are looking for
-
Purchase OS MOuntain Lion through Mac App Store but it stated error has occurred.
Hi, Need help here. I purchase OS X Mountain Lion tgrought Mac App Store but it stated an error has occured and it was not completely download. In the purchase box, the application is under "other purchase" and the button is blank. I can't resume dow
-
Upgrading to Lookout 6.7.1 from version 5.1 on new computer
Hi We recently upgraded to Lookout 6.7.1 from version 5.1 (build 8). We copied the database, Source Files, Process Files from the old computer to the new computer. We also attached the database in NI Max. We then updated the files when we opened them
-
Applet crashing the web browser
Hello group! I have just done a simple applet that is embedded in a html. Every time I close the html, the browser sends and error report. I am thinking that maybe I should have included a close method into the applet or aomething like that. Please,
-
Hi I have a little server side Class, which calls a c Library with jni under Linux public class NagJniLibrary implements NagJniLibraryIF static System.loadLibrary("NagJniLibrary"); public native double sin(double x); }if I use ant to buil
-
Why do i get a dialogue box appear before Firefox 4 will load?
When i turn on firefox 4 I get a dialogue box appear which says, Java Script Application. Type error:Components.classes [cid] is undefined. Ideas please