Kernel Data Inpage Error AND clock interrupt not received BSODs

See Title. No pattern has developed when the crashes happen. When idle, Kernel Data Inpage error occurs and clock interrupt not received on secondary processor occurs all the time. Happens very frequently. More than once or twice a day. I will be attaching some DMP files but connection keeps getting reset right now.

I RMA'd or replaced pretty much everything in my build including: CPU, Motherboard, PSU.

Ran Memtest on 1 stick of RAM minimum of 8 times. Repeated for all 4 sticks of ram.

Updated BIOS

Tried without NAV.

Tried running with 2 sticks of ram at a time, then replaced the ram with the other 2 sticks.

Reinstalled windows on different HDDs.

Replaced Thermal paste on heatsink (went with Arctic Silver 5)
^This is when the Kernel Data Inpage Error showed its face.

Ran Chkdsk. Fine.

Gonna Run memtest86 for about 24 hours starting now.




!!!The MEMORY.DMP file is too big to upload. its like 535MB any suggestions? Do We need this?

Welcome aboard, Raven45.

► Uninstall Norton Internet Security. Use Microsoft Security Essentials - Free Antivirus for Windows

Code:

fffff880`03377c08  fffff880`03eecd5eUnable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
 SYMEVENT64x86+0x19d5e

► Update nVidia Driver.

• Download and install |MG| Driver Fusion (Driver Sweeper) 1.1.1 Download.
• Reboot the computer in Advanced Boot Options, safe mode. Search Driver Fusion in your start menu, and remove all components of your nVidia display driver.
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, follow option two to search for the appropriate driver for your system automatically, and install it.

Code:

fffff880`03377888  fffff880`100dbd84Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x254d84
fffff880`03377890  00000000`00000000
fffff880`03377898  00000000`00000000
fffff880`033778a0  00000000`00000000
fffff880`033778a8  fffff880`100dbd84 nvlddmkm+0x254d84
fffff880`033778b0  00000000`00000000
fffff880`033778b8  00000000`00000000
fffff880`033778c0  00000000`00000000
fffff880`033778c8  fffff880`100dbd84 nvlddmkm+0x254d84
fffff880`033778d0  00000000`00000000
fffff880`033778d8  fffff880`03377bf0
fffff880`033778e0  fffffa80`07ce6000
fffff880`033778e8  fffff880`10091416 nvlddmkm+0x20a416
===========================================================
kd> nvlddmkm
       ^ Syntax error in 'nvlddmkm'
0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0fe87000 fffff880`10ba5000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Feb 10 07:32:58 2012 (4F347AD2)
    CheckSum:         00D075A7
    ImageSize:        00D1E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

► upgrade the network driver:

1] download the network card driver from manufactuer's website.
2] Then reinstall the driver:
3] Click the Start Button, type "devmgmt.msc" (without quotation marks) in the Start Menu Search box and press Enter.
4] Double click to expand "Network adaptors".
5] Right click your network card and click Uninstall.
6] Check "Delete driver software for this device" check box, click OK.
7] Restart the computer

If windows does not auto configure the appropriate drivers at startup, install the downloaded one manually.


Let us know the results.

There was no need to run memtest, at least upto that stage.

Well, you may not report back, if you like :) It is not a compulsion.

The MEMORY.DMP file usually heavily compresses when slapped into a zip, rar, 7z or some other compressed format. You can then upload it to a 3rd party filesharing site.

Just be aware that clock watchdog timeout problems usually can be very tricky to analyze, even by a professional.

As for the inpage error, during an I/O operation involving grabbing kernel data from the disk failed, because of a spontaneous disk disconnect (STATUS_DEVICE_NOT_CONNECTED). The drive involved here has to be the one where either Windows or the paging file resides. It obviously was very transitory otherwise it would not have been able to write the crashdump to your drive if it was still in a state of disconnect. So there's a prob with either that drive, or an issue with your disk controller on your mobo. Giving that you installed Windows on two separate HDs and this still showed up, I'm concerned that it may be the latter. How many of these errors have you experienced? It may be fixed by a CHKDSK /F run followed by an SFC /SCANNOW, or updating BIOS and motherboard drivers (especially for drive controller), as well as any existing firmware for your HDs, but other then that it may require hardware replacement.

Oh, and you may wanna check your cabling to ensure they're all fit snugly, especially the data/power cables for your drive(s) on both mobo and drive ends.

Analysts:

As I always repeat, minidumps are pretty much worthless on 0x101 bugchecks. Absolutely worthless. Don't bother.

For the 0x7A bugcheck:

Code:

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

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

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000009d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  1

LAST_CONTROL_TRANSFER:  from fffff80002f0b7fc to fffff80002ed4040

STACK_TEXT:  
fffff880`033d97e8 fffff800`02f0b7fc : 00000000`0000007a 00000000`00000020 ffffffff`c000009d fffffa80`07f86078 : nt!KeBugCheckEx
fffff880`033d97f0 fffff800`02ebdf17 : fffffa80`07f86010 00000000`c000009d 00000000`00000000 fffffa80`07f860a8 : nt! ?? ::FNODOBFM::`string'+0x4bed0
fffff880`033d98b0 fffff800`02eb09ff : fffffa80`06754040 fffffa80`06754090 00000000`00000000 00000000`00000000 : nt!IopCompletePageWrite+0x57
fffff880`033d98e0 fffff800`02edb42d : fffffa80`06754040 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`033d9960 fffff800`02ed75cb : 00000103`08c27c01 00000000`00000000 fffff8a0`00000000 fffff880`033d9a10 : nt!KiCommitThreadWait+0x3dd
fffff880`033d99f0 fffff800`02e6ea7f : fffffa80`00000002 fffff880`033d9ce0 00000000`00000001 fffffa80`00000013 : nt!KeWaitForMultipleObjects+0x271
fffff880`033d9ca0 fffff800`031736e6 : fffffa80`06754040 457fefe2`d36b4dfa 00000000`00000080 00000000`00000001 : nt!MiModifiedPageWriter+0xcf
fffff880`033d9d00 fffff800`02eb2566 : fffff880`009b2180 fffffa80`06754040 fffff880`009bd0c0 a33c08e7`a20854b1 : nt!PspSystemThreadStartup+0x5a
fffff880`033d9d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4bed0
fffff800`02f0b7fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4bed0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4fa38fe2

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4bed0

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+4bed0

Followup: MachineOwner
---------

We can't garner more info from this minidump, but it's pretty much a solid guess that we're dealing with a drive-related issue.

Okay folks, thanks for the replies. I just got home from class today and got a NEW error. "A process or thread crucial to system operation has unexpectedly exited or been terminated." It was just coming out of sleep mode and poof.


In regards to:

Oh, and you may wanna check your cabling to ensure they're all fit snugly, especially the data/power cables for your drive(s) on both mobo and drive ends.

I did notice that my SSD had a funny drive-end connection. The data cable doesn't snap in like the rest. That being said, I decided not to put my OS on that drive for that reason. In fact I don't have much on there at all. Just a game. :P

So there's a prob with either that drive, or an issue with your disk controller on your mobo. Giving that you installed Windows on two separate HDs and this still showed up, I'm concerned that it may be the latter. How many of these errors have you experienced? It may be fixed by a CHKDSK /F run followed by an SFC /SCANNOW, or updating BIOS and motherboard drivers (especially for drive controller), as well as any existing firmware for your HDs, but other then that it may require hardware replacement.

I just updated my BIOS a few days ago. Will run CHKDSK /F and SFC /SCANNOW respectively now. I've experienced this error far far too many times. I sent back a motherboard once. I couldn't pin the problem to the motherboard though so I didn't send it back again. Do you think asus will accept another return? Even after so long of having it? :/



Will report back.. Thanks.

UPDATE: To not double post, I'll let you know that chkdsk /f and sfc /scannow came back fine