"ntoskrnl.exe" BSOD Windows 7

james0912 · 25 Feb 2012

For the past few days now, I have been receiving blue screens. When I play games for around 30mins the BSOD shows up and I have to restart my computer.

Each time, the cause of the error reports has been "ntoskrnl.exe".

I've attached 2 dmp files to this post.

Any help is appreciated! Thanks.

ePeen · 25 Feb 2012

Dump one shows ks.sys as culprit (Kernel CSA Library), and dump two shows usbaudio.sys as the culprit. Both of these actually causing the crash are highly unlikely, so I recommend enabling Driver Verifier. This will force a crash when it locates the driver in question at fault and hopefully give us an answer.

Code:

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : usbaudio.sys ( usbaudio!USBType1CompleteCallback+143 )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3039326437353862
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff88002d8b798 -- (.exr 0xfffff88002d8b798)
ExceptionAddress: fffff88004f83f97 (usbaudio!USBType1CompleteCallback+0x0000000000000143)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff88002d8b840 -- (.trap 0xfffff88002d8b840)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=41fffa8005169bc0 rbx=0000000000000000 rcx=fffffa8003d68210
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004f83f97 rsp=fffff88002d8b9d0 rbp=fffffa80052c82d0
 r8=fffffa8003af54f0  r9=0000000000000000 r10=fffff88002d63b80
r11=fffff88002d8ba38 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
usbaudio!USBType1CompleteCallback+0x143:
fffff880`04f83f97 488908          mov     qword ptr [rax],rcx ds:8270:41fffa80`05169bc0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ecbc2e to fffff80002ed3ed0

STACK_TEXT:  
fffff880`02d8a878 fffff800`02ecbc2e : 00000000`00000002 00000000`00000000 fffff880`02d8aff0 fffff800`02f00e28 : nt!KeBugCheck
fffff880`02d8a880 fffff800`02ef9bed : fffff800`030e0c24 fffff800`03019a3c fffff800`02e62000 fffff880`02d8b798 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02d8a8b0 fffff800`02f01250 : fffff800`03021b5c fffff880`02d8a928 fffff880`02d8b798 fffff800`02e62000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02d8a8e0 fffff800`02f0e1b5 : fffff880`02d8b798 fffff880`02d8aff0 fffff880`00000000 fffffa80`05169b90 : nt!RtlDispatchException+0x410
fffff880`02d8afc0 fffff800`02ed3542 : fffff880`02d8b798 fffffa80`05169c30 fffff880`02d8b840 00000000`00000000 : nt!KiDispatchException+0x135
fffff880`02d8b660 fffff800`02ed1e4a : 00000000`00000000 fffffa80`03c3aae0 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`02d8b840 fffff880`04f83f97 : 00000000`00000000 fffffa80`05c1ea10 fffffa80`05169b90 fffffa80`05169c30 : nt!KiGeneralProtectionFault+0x10a
fffff880`02d8b9d0 fffff800`02ed6516 : fffffa80`03af5803 00000000`00000000 00000000`00000000 00000000`00000f00 : usbaudio!USBType1CompleteCallback+0x143
fffff880`02d8ba40 fffff880`1493d5d9 : fffffa80`05c1e050 fffffa80`03db2900 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02d8bb20 fffff880`1493dab7 : fffffa80`06703902 fffffa80`03af54f0 00000000`ffffffff fffffa80`05c1eea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02d8bc00 fffff880`1493b64f : fffffa80`05c1eea8 fffffa80`05c1e1a0 fffffa80`05c1f040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02d8bc60 fffff880`1492cf89 : fffffa80`05c1e050 00000000`00000000 fffffa80`05c1ee02 fffffa80`05c1eea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02d8bca0 fffff800`02edf5dc : fffff880`02d63180 fffffa80`05c1eea8 fffffa80`05c1eec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02d8bcd0 fffff800`02edc6fa : fffff880`02d63180 fffff880`02d6df80 00000000`00000000 fffff880`1492cdb0 : nt!KiRetireDpcList+0x1bc
fffff880`02d8bd80 00000000`00000000 : fffff880`02d8c000 fffff880`02d86000 fffff880`02d8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbaudio!USBType1CompleteCallback+143
fffff880`04f83f97 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  usbaudio!USBType1CompleteCallback+143

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbaudio

IMAGE_NAME:  usbaudio.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

FAILURE_BUCKET_ID:  X64_0x1E_0_usbaudio!USBType1CompleteCallback+143

BUCKET_ID:  X64_0x1E_0_usbaudio!USBType1CompleteCallback+143

Followup: MachineOwner

BugCheck A, {fffff88003163020, 2, 0, fffff80002ed8815}

Probably caused by : ks.sys ( ks!KsQueueWorkItem+52 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff88003163020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ed8815, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031070e0
 fffff88003163020 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExQueueWorkItem+75
fffff800`02ed8815 654c8b242520000000 mov   r12,qword ptr gs:[20h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Everything.exe

TRAP_FRAME:  fffff88002f92980 -- (.trap 0xfffff88002f92980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800418eb70
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed8815 rsp=fffff88002f92b10 rbp=fffffa8004789002
 r8=fffffa800418eba8  r9=fffff88003607744 r10=fffff88002f63b80
r11=fffff88003610910 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!ExQueueWorkItem+0x75:
fffff800`02ed8815 654c8b242520000000 mov   r12,qword ptr gs:[20h] gs:ffff:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed0469 to fffff80002ed0f00

STACK_TEXT:  
fffff880`02f92838 fffff800`02ed0469 : 00000000`0000000a fffff880`03163020 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f92840 fffff800`02ecf0e0 : fffffa80`05ce8e02 fffff800`030745f8 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f92980 fffff800`02ed8815 : 00000000`00000000 fffffa80`0667bc00 fffffa80`0510ad20 fffff880`03e935c2 : nt!KiPageFault+0x260
fffff880`02f92b10 fffff880`0360786e : fffffa80`04789450 fffffa80`04273ef0 00000000`00000002 fffffa80`04273ef0 : nt!ExQueueWorkItem+0x75
fffff880`02f92b80 fffff880`03603779 : fffffa80`04273b08 fffffa80`04789000 fffffa80`04789450 fffff800`02e196e5 : ks!KsQueueWorkItem+0x52
fffff880`02f92bb0 fffff880`0360b628 : fffffa80`04273b08 fffffa80`039d2870 fffffa80`04273c00 fffffa80`047891b0 : ks!CKsPin::Process+0x85
fffff880`02f92be0 fffff880`0518f3ac : 00000000`00000000 fffff800`02e197d8 fffffa80`047890a0 fffffa80`0454d010 : ks!KsPinAttemptProcessing+0x8c
fffff880`02f92c10 fffff800`02ed3516 : fffffa80`0454d323 fffff800`02e1ac02 00000000`00000000 00000000`00000000 : usbaudio!USBCaptureCompleteCallback+0x1a8
fffff880`02f92c70 fffff880`03ea45d9 : fffffa80`050fe050 fffffa80`04789400 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f92d50 fffff880`03ea4ab7 : fffffa80`06930502 fffffa80`0454d010 00000000`ffffffff fffffa80`050feea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f92e30 fffff880`03ea264f : fffffa80`050feea8 fffffa80`050fe1a0 fffffa80`050ff040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f92e90 fffff880`03e93f89 : fffffa80`050fe050 00000000`00000000 fffffa80`050fee02 fffffa80`050feea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f92ed0 fffff800`02edc5dc : fffff880`02f63180 fffffa80`050feea8 fffffa80`050feec0 00000000`0000ffff : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f92f00 fffff800`02ed7065 : 00000000`00000000 fffffa80`06b2db60 00000000`00000000 fffff880`03e93db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f92fb0 fffff800`02ed6e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06434bd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ks!KsQueueWorkItem+52
fffff880`0360786e 488d4f48        lea     rcx,[rdi+48h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  ks!KsQueueWorkItem+52

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bca9f

FAILURE_BUCKET_ID:  X64_0xA_ks!KsQueueWorkItem+52

BUCKET_ID:  X64_0xA_ks!KsQueueWorkItem+52

Followup: MachineOwner

james0912 · 28 Feb 2012

Thank you for replying ePeen, I used driver verifier and the next time it crashed it said was due to usbport.sys

ePeen · 28 Feb 2012

My pleasure, have you solved this or do you need assistance? If so, please attach the verifier enabled dump.

james0912 · 28 Feb 2012

Ya, I'm still getting the same problem. Here is the minidump with verifier enabled.

It says caused by : dxgkrnl.sys
No idea what that means

ePeen · 28 Feb 2012

Both of the dumps attached are not verifier enabled. Mind double checking you've zipped up and attached the correct dump file(s)?

james0912 · 28 Feb 2012

Ok, I ran driver verifier again and followed the guide you sent me, this is the dump file I received.

writhziden · 02 Mar 2012

Code:


Loading Dump File [D:\Kingston\BSODDmpFiles\james0912\022812-33711-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Tue Feb 28 22:15:11.534 2012 (UTC - 7:00)
System Uptime: 0 days 0:19:44.970
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880077a7c18, fffff880077a7470, fffff880012cc0ad}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCheckAttributeRecord+19d )

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

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880077a7c18
Arg3: fffff880077a7470
Arg4: fffff880012cc0ad

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


EXCEPTION_RECORD:  fffff880077a7c18 -- (.exr 0xfffff880077a7c18)
ExceptionAddress: fffff880012cc0ad (Ntfs!NtfsCheckAttributeRecord+0x000000000000019d)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880077a7470 -- (.cxr 0xfffff880077a7470)
rax=0000000000000001 rbx=fffff980055e3d58 rcx=0000000000000048
rdx=0000000000001000 rsi=fffffa8004ef2c40 rdi=fffff980055e3d58
rip=fffff880012cc0ad rsp=fffff880077a7e50 rbp=00000000000000a0
 r8=fffff980055e3dd8  r9=0000000000000001 r10=0000000000000400
r11=fffffa8005e15180 r12=fffffa8005e15180 r13=fffff8a0027d5a98
r14=0000000000000000 r15=fffff980055e3da8
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
Ntfs!NtfsCheckAttributeRecord+0x19d:
fffff880`012cc0ad 0f88c59e0300    js      Ntfs! ?? ::NNGAKEGL::`string'+0x90bb (fffff880`01305f78) [br=0]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x24

PROCESS_NAME:  BlackCipher.ae

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from fffff880012cc7b5 to fffff880012cc0ad

STACK_TEXT:  
fffff880`077a7e50 fffff880`012cc7b5 : fffffa80`05e15180 fffffa80`04607840 00000000`00000046 00000000`000000a0 : Ntfs!NtfsCheckAttributeRecord+0x19d
fffff880`077a7ec0 fffff880`012c24dc : fffffa80`04ef2c40 fffffa80`05e15180 fffff8a0`027d5a98 fffff8a0`027d5a01 : Ntfs!NtfsReadMftRecord+0x344
fffff880`077a7f70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsLookupInFileRecord+0x6c


FOLLOWUP_IP: 
Ntfs!NtfsCheckAttributeRecord+19d
fffff880`012cc0ad 0f88c59e0300    js      Ntfs! ?? ::NNGAKEGL::`string'+0x90bb (fffff880`01305f78)

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  Ntfs!NtfsCheckAttributeRecord+19d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc14f

STACK_COMMAND:  .cxr 0xfffff880077a7470 ; kb

FAILURE_BUCKET_ID:  X64_0x24_VRF_Ntfs!NtfsCheckAttributeRecord+19d

BUCKET_ID:  X64_0x24_VRF_Ntfs!NtfsCheckAttributeRecord+19d

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

Loading Dump File [D:\Kingston\BSODDmpFiles\james0912\022812-32401-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e90e50
Debug session time: Tue Feb 28 21:54:47.265 2012 (UTC - 7:00)
System Uptime: 0 days 0:04:05.951
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002cd335d, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+5d )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cd335d, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KiIpiProcessRequests+5d
fffff800`02cd335d 488bc7          mov     rax,rdi

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efb0e0
 ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0x1E_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  VHMultiWriterE

CURRENT_IRQL:  e

LAST_CONTROL_TRANSFER:  from fffff80002d04a17 to fffff80002cc4f00

STACK_TEXT:  
fffff880`06da3128 fffff800`02d04a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02cd335d 00000000`00000000 : nt!KeBugCheckEx
fffff880`06da3130 fffff800`02cc4542 : fffff880`06da3908 00000000`02490430 fffff880`06da39b0 fffff880`02d64180 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`06da37d0 fffff800`02cc2e4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`06da39b0 fffff800`02cd335d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`06da3b40 fffff800`02cd131a : 00000000`02490430 fffff880`06da3ca0 00000000`00000003 00000000`7efaa000 : nt!KiIpiProcessRequests+0x5d
fffff880`06da3c20 00000000`67411e82 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x12a
00000000`02b9f340 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x67411e82


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiIpiProcessRequests+5d
fffff800`02cd335d 488bc7          mov     rax,rdi

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KiIpiProcessRequests+5d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!KiIpiProcessRequests+5d

BUCKET_ID:  X64_0x1E_c0000005_VRF_nt!KiIpiProcessRequests+5d

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

Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...
Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
Thanks to JMH for helping with my understanding of this crash.

Thanks to Dave76 for help understanding possible causes.

Your hard disk may have errors on it:

Disable Driver Verifier: Start Menu -> All Programs -> Accessories -> Right Click Command Prompt -> Run as administrator ->
verifier /reset
-> Restart the computer.
Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
Use HD Diagnostic to find your hard disk manufacturer and to find the manufacturer's diagnostics. Run those diagnostics and run all tests to determine if the drive is faulty.