Newest dump attached doesn't show much via processes, just shoots a more than likely incorrect fault: ntkrnlmp.exe. One thing I can't believe I missed in the previous dumps... your Lycosa
driver is dated from 2008. Please update it
here and the firmware if that's available as well.
The Lycosa driver (as well as other Razer
drivers) is known for causing BSODs as of late after some studies. If you're still BSOD'ing after updating the Lycosa driver, let's move onto Memtest and Driver Verifier. I'd like you to run
both of these tests.
Memtest:
Read the following to test your memory for errors.
Driver Verifier:
Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.
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: fffff8a008198220, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: 0000000166a178c0, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88012790000, 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: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800d5fd4b0 -- (.trap 0xfffff8800d5fd4b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000005a4d
rdx=fffff88012790000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800034c5f6b rsp=fffff8800d5fd648 rbp=fffff8800d5fd7c8
r8=0000000000000000 r9=fffff8800d5fd688 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!RtlImageNtHeaderEx+0x3f:
fffff800`034c5f6b 66390a cmp word ptr [rdx],cx ds:2000:fffff880`12790000=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003555b52 to fffff800034e4c40
STACK_TEXT:
fffff880`0d5fd198 fffff800`03555b52 : 00000000`0000007a fffff8a0`08198220 ffffffff`c000009d 00000001`66a178c0 : nt!KeBugCheckEx
fffff880`0d5fd1a0 fffff800`0350c6cf : fffffa80`0dd9a010 fffff880`0d5fd310 fffff800`0371a500 fffffa80`0dd9a010 : nt! ?? ::FNODOBFM::`string'+0x37bba
fffff880`0d5fd280 fffff800`034f2f59 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x28b
fffff880`0d5fd350 fffff800`034e2d6e : 00000000`00000000 fffff880`12790000 fffff880`0d5fd700 00000000`00000000 : nt!MmAccessFault+0x1399
fffff880`0d5fd4b0 fffff800`034c5f6b : fffff800`034c60fa fffff880`12790000 fffff800`036ade60 fffff880`0d5fd700 : nt!KiPageFault+0x16e
fffff880`0d5fd648 fffff800`034c60fa : fffff880`12790000 fffff800`036ade60 fffff880`0d5fd700 fffff880`0d5fd6e0 : nt!RtlImageNtHeaderEx+0x3f
fffff880`0d5fd650 fffff800`035dfbfa : 00000000`00000000 00000000`00000000 fffff880`0d5fdb58 00000000`00000000 : nt!RtlImageNtHeader+0x1e
fffff880`0d5fd680 fffff800`035dfe51 : ffffffff`80000854 00000000`00000000 00000000`00000080 00000000`00000000 : nt!LdrpMapResourceFile+0x1aa
fffff880`0d5fd770 fffff800`035dff78 : 00000000`00000040 fffff800`035ddc32 00000000`ffffffbf 00000000`0000000b : nt!LdrLoadAlternateResourceModuleEx+0x181
fffff880`0d5fdb00 fffff800`038bed40 : 00000000`ffff0000 00000000`00000000 00000000`00000003 fffffa80`0c51a010 : nt!LdrpLoadResourceFromAlternativeModule+0x38
fffff880`0d5fdb50 fffff800`038bf456 : fffff880`01442000 fffff880`0d5fdbb8 00000000`00000000 00000000`00200040 : nt!LdrpSearchResourceSection_U+0x5c0
fffff880`0d5fdc70 fffff880`014824c9 : fffffa80`0a722180 00000000`00000000 ffff0000`0c1619c4 00000000`00000000 : nt!RtlFindMessage+0x46
fffff880`0d5fdce0 fffff800`0377ffee : fffff880`12335690 fffffa80`0cbf7b60 fffffa80`0dd39b60 00000000`00000080 : Ntfs!NtfsProcessRepairQueue+0x69
fffff880`0d5fdd40 fffff800`034d65e6 : fffff880`035db180 fffffa80`0dd39b60 fffff880`035e61c0 fffff880`01450cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0d5fdd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+37bba
fffff800`03555b52 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+37bba
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+37bba
BUCKET_ID: X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+37bba
Followup: MachineOwner