I have experienced a number of crashes on a PC with Windows 8.1, and have analyzed the mini dumps and one full dump so far, and have seen a myriad of different crash results including IRQL_NOT_LESS_OR_EQUAL, KERNEL_DATA_INPAGE_ERROR, CRITICAL_PROCESS_DIED. I've posted the raw dmp files, as well as txt files of the results from running them through the debugger here...

https://onedrive.live.com/redir?resid=F1640CE12DEBCE6B!130&authkey=!ABlrD4zyv8gT_SU&ithint=folder%2ctxt

I've ran memtest86 very thoroughly on the RAM with 0 errors, I've updated all of the drivers, ran chkdsk on the HDD, and cannot find any glaring errors, and the computer still seems to crash at random points in time with different applications running each time. The computer is a custom build if the components matter, and each of the component can be found here... 

http://pcpartpicker.com/p/zfmYqs

TTD

There is a very specific problem.  The HD.  I would go the HD maker and download their HD checking utility and run it

Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\New folder\022015-12359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: 
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff800`5ba06000 PsLoadedModuleList = 0xfffff800`5bcdf250
Debug session time: Fri Feb 20 22:11:14.919 2015 (UTC - 5:00)
System Uptime: 0 days 23:53:22.598
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fb400a1f28, ffffffffc000000e, 10d7b1880, fffff680143e5000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1561f )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb400a1f28, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 000000010d7b1880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff680143e5000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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


ERROR_CODE: (NTSTATUS) 0xc000000e - A device which does not exist was specified.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c000000e

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff8005bb7c4cf to fffff8005bb569a0

STACK_TEXT:  
ffffd000`309d63e8 fffff800`5bb7c4cf : 00000000`0000007a fffff6fb`400a1f28 ffffffff`c000000e 00000001`0d7b1880 : nt!KeBugCheckEx
ffffd000`309d63f0 fffff800`5ba377f8 : 00000000`00000002 ffffd000`309d6558 ffffe001`d859cdd8 ffffd000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1561f
ffffd000`309d64e0 fffff800`5ba70b7a : ffffe001`d859cdd8 ffffe001`d8385880 01000000`00000001 00000000`00000000 : nt!MiIssueHardFault+0x184
ffffd000`309d65a0 fffff800`5ba67941 : 01000000`00000001 00000000`00000080 fffff680`143e5000 00000000`00000080 : nt!MmAccessFault+0x5ba
ffffd000`309d6760 fffff800`5c0076f1 : ffffe001`d838eb00 00000028`00000000 ffffd000`00000000 00000000`00000004 : nt!MiCommitExistingVad+0x901
ffffd000`309d6890 fffff800`5bb621b3 : 00000028`6fd1e7a0 00000000`00044000 00000028`6f323878 00000000`00043ff0 : nt!NtAllocateVirtualMemory+0xfbd
ffffd000`309d6a90 00007ffb`db9b0f5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000028`6fd1d5e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`db9b0f5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+1561f
fffff800`5bb7c4cf cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+1561f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54b0c2f7

IMAGE_VERSION:  6.3.9600.17630

BUCKET_ID_FUNC_OFFSET:  1561f

FAILURE_BUCKET_ID:  0x7a_c000000e_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x7a_c000000e_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x7a_c000000e_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {5654bc57-9720-546c-de0e-76a002c66fe5}

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

Hmm, okay. I have ran checkdsk and crystal disk info with successful results. I will try downloading software from Western Digital to see if that finds anything different.

Ran both a quick scan as well as a full scan with the Western Digital software, and it found nothing out of the ordinary.

Hi TrogdorTheDragon,

For Bugcheck 0x7A, please also check:

Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR

You may also check at the resolution part and see if it could help here.

For Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL, that indicates there might be some drivers not working well.

Take a check into Device Manager and see if any drivers need to update.

If BSOD still happens, please upload the newly created dump file.

Besides, you may also check this at the vendor side, to make sure all the hardware are in good health.

Best regards

TTD

If you are still crashing upload the new DMPS