Rare But Persistent BSODs. Most Shown to be Caused by ntoskrnl.exe?

Hanamc77 · 12 Jan 2014

It's been a little over a year since I built a custom computer, and for some odd reason it gets around four BSODs a month. I'll either get one while surfing the web, playing a game, or doing anything really. I've analyzed the dump files with WhoCrashed and it shows that ntoskrnl.exe is "probably" the cause of most the crashes. I don't know if that's really the case, but If I could get some help on this issue, I would really appreciate it.

I've included the SF Diagnostic Tool's gathered files in a zip.

Arc · 12 Jan 2014

That issue is not very rare, but rather frequent. Some malfunction in the storage subsystem. Most possibly a loose connection or a disc corruption.

Reseat the sata and power.

Also, if possible, change the SATA cable. Apply the SATA cable to another unused port on the motherboard. Make it sure that there is no loose connectio in the SATA connecting. Check all the screws holding the HDD with the stand. Make it sure all those are properly screwed.

Test your HDD using Data Lifeguard Diagnostic for Windows. Also let us see a screenshot of your hdd using CrystalDiskInfo - Software - Crystal Dew World .

Will decide the further steps seeing the results.
___________________________________________________________________________________________

Code:

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

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


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

PROCESS_NAME:  SteamService.e

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880033891f0 -- (.trap 0xfffff880033891f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=000000000000000f
rdx=fffff70000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000329ef68 rsp=fffff88003389380 rbp=0000000000007ffe
 r8=0000000000007fff  r9=fffff70000000ff8 r10=0000000000007ffd
r11=0000000000007ffa r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac po nc
nt!RtlFindClearBits+0xa8:
fffff800`0329ef68 4c0b02          or      r8,qword ptr [rdx] ds:0001:fffff700`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032ea752 to fffff80003277bc0

STACK_TEXT:  
fffff880`03388ed8 fffff800`032ea752 : 00000000`0000007a fffff6fb`80000000 ffffffff`c000009d 00000000`ca3d6880 : nt!KeBugCheckEx
fffff880`03388ee0 fffff800`0329e91f : fffffa80`07add940 fffff880`03389050 fffffa80`078a9978 fffffa80`07add940 : nt! ?? ::FNODOBFM::`string'+0x36c1a
fffff880`03388fc0 fffff800`0328528a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`00961000 : nt!MiIssueHardFault+0x28b
fffff880`03389090 fffff800`03275cee : 00000000`00000000 fffff700`00000008 fffffa80`018d5000 00000000`00000004 : nt!MmAccessFault+0x146a
fffff880`033891f0 fffff800`0329ef68 : 00000000`00000000 00000000`ffffffff 00000000`0000001e 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03389380 fffff800`03569aeb : 00000000`ffffffff fffff8a0`00000000 00000000`00000000 00000000`00000000 : nt!RtlFindClearBits+0xa8
fffff880`033893c0 fffff800`03565aea : ffffffff`ffffffff fffff880`033897e0 00000000`00000000 fffff680`003f7ef8 : nt!MiScanUserAddressSpace+0xdf
fffff880`03389410 fffff800`03276e53 : fffff880`033897f0 fffff800`03275dfd 00000000`00000000 00000000`7efdf318 : nt!NtSetInformationProcess+0x375
fffff880`03389760 fffff800`03273410 : fffff800`03565402 00000000`00000000 fffff800`03571fdf 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`033898f8 fffff800`03565402 : 00000000`00000000 fffff800`03571fdf 00000000`00000000 fffffa80`0353bf00 : nt!KiServiceLinkage
fffff880`03389900 fffff800`0356393c : 00000000`00004000 00000000`00040000 00000000`00000000 00000000`00001000 : nt!RtlCreateUserStack+0x122
fffff880`033899f0 fffff800`0356324a : fffffa80`078a95e0 fffff880`0338a858 fffffa80`0353b000 fffff880`0338a440 : nt!PspAllocateThread+0x5bb
fffff880`03389c10 fffff800`03567569 : fffffa80`00000004 00000000`00000000 00000000`00000001 fffff880`0338a440 : nt!PspCreateThread+0x1d2
fffff880`03389e90 fffff800`03276e53 : 00000000`001fffff 00000000`00000000 fffffa80`0353b740 fffff800`03294c8f : nt!NtCreateThreadEx+0x25d
fffff880`0338a5e0 fffff800`03273410 : fffff800`03569d88 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0338a7e8 fffff800`03569d88 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`0338a7f0 fffff800`034dc8fa : fffff8a0`0c63b790 00000000`00000000 00000000`00000000 fffffa80`078a95e0 : nt!RtlpCreateUserThreadEx+0x138
fffff880`0338a910 fffff800`034dd83e : 00000000`00000000 ffffffff`800017ec ffffffff`800017ec 00000000`00000001 : nt!EtwpInjectThread+0x9a
fffff880`0338a980 fffff800`034de21f : fffffa80`078a95e0 fffff8a0`0c63b790 fffffa80`06711a60 00000000`00000701 : nt!EtwpQueueNotification+0x19e
fffff880`0338aa10 fffff800`036244e6 : fffffa80`0361d010 fffffa80`0361d038 fffffa80`06711a60 00000000`00000000 : nt!EtwpSendDataBlock+0x3f
fffff880`0338aac0 fffff800`036c2de8 : fffffa80`035d73c0 fffff8a0`0c63b790 00000000`00000001 00000000`00000000 : nt!EtwpDisableTraceProviders+0x1a6
fffff880`0338ab40 fffff800`035cf2d6 : fffffa80`035d0000 00000000`00000001 00000000`c0000001 fffffa80`035f8020 : nt!EtwpStopLoggerInstance+0x58
fffff880`0338ab80 fffff800`035142ea : fffff8a0`0401f1c0 fffffa80`03618040 00000000`00000080 fffffa80`0353b740 : nt! ?? ::NNGAKEGL::`string'+0x42983
fffff880`0338ac00 fffff800`032688e6 : fffff880`009ee180 fffffa80`03618040 fffffa80`03563660 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0338ac40 00000000`00000000 : fffff880`0338b000 fffff880`03385000 fffff880`03389710 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+36c1a
fffff800`032ea752 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36c1a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+36c1a

BUCKET_ID:  X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+36c1a

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

Tobias · 12 Jan 2014

Seems like you have several HD-related BSoDs:

BugCheck 7A, {20, ffffffffc000009d, fffffa800746c7c8, 0}

"The KERNEL_DATA_INPAGE_ERROR bug check has a value of 0x0000007A. This bug check indicates that the requested page of kernel data from the paging file could not be read into memory. "

"0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk."

BugCheck 9F, {3, fffffa800432c050, fffff80000b9c3d8, fffffa8008ee7c60}
Probably caused by : disk.sys

Irp is active with 4 stacks 2 is current (= 0xfffffa8008ee7d78)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
cmd flg cl Device File Completion-Context
[ 0, 0] 0 0 00000000 00000000 00000000-00000000

Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e1 fffffa8004a81060 00000000 fffff88000eaff50-00000000 Success Error Cancel pending
\Driver\Disk partmgr!PmPowerCompletion
Args: 00000000 00000001 00000004 00000000
[ 16, 2] 0 e1 fffffa8004a81b90 00000000 00000000-00000000 pending
\Driver\partmgr
Args: 00000000 00000001 00000004 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa8004faf160

Args: 00000000 00000000 00000000 00000000

Check the SATA-cables, disconnect them and then connect them again, also update the drivers for your SATA-controller:

Marvell 91xx SATA 6G Controller
fffff880`01103000 fffff880`01190000 mv91xx Fri Oct 01 05:27:07 2010 (4CA5550B)
fffff880`011bf000 fffff880`011c7000 mvxxmm Fri Oct 01 05:26:49 2010 (4CA554F9)

You also have other old drivers which need updating:

Sonic CD/DVD driver (I'm not sure which program use this)
fffff880`011d2000 fffff880`011de040 PxHlpa64 Tue Oct 20 20:08:42 2009 (4ADDFCAA)

Renesas Electronics USB 3.0 Host Controller
fffff880`03e76000 fffff880`03ea6000 nusb3xhc Thu Sep 30 06:00:03 2010 (4CA40B43)
fffff880`0405a000 fffff880`04073000 nusb3hub Thu Sep 30 06:00:03 2010 (4CA40B43)

Bamboo
fffff880`04080000 fffff880`04088000 wacommousefilter Fri Feb 16 19:12:17 2007 (45D5F401)
fffff880`06ff3000 fffff880`06ff5a00 wacomvhid Tue Sep 22 01:29:14 2009 (4AB80C4A)

Logitech Keyboard
fffff880`041c8000 fffff880`041cbd80 LGBusEnum Tue Nov 24 02:36:48 2009 (4B0B38B0)

D-Link DWA-130 Wireless N USB Adapter
fffff880`05711000 fffff880`057d4000 RTL8192su Wed Sep 29 08:01:40 2010 (4CA2D644)

Intel(R) 82579V Gigabit Network Connection
fffff880`06400000 fffff880`06450000 e1c62x64 Thu Oct 28 17:42:28 2010 (4CC999E4)

Intel Management Engine Interface
fffff880`06fd6000 fffff880`06fe7000 HECIx64 Wed Oct 20 01:33:43 2010 (4CBE2AD7)

Hanamc77 · 12 Jan 2014

Alright, I checked the sata connections, replugged them and I changed the sata cable and port that goes to the HDD. The HDD did pass the Data Lifeguard test successfully and I've updated the old drivers. Here is also the screenshot you requested:

Thanks for all the help, guys! Now I'll just have to wait and see if that fixed the problem.

Arc · 13 Jan 2014

Ok, let us know how it is going :)

Hanamc77 · 31 Jan 2014

Since I made those changes I haven't experienced any crashes at all! Thanks guys, problem fixed!

Arc · 01 Feb 2014

You are welcome :)

Let us know for any further issue.