Microsoft (R) Windows Debugger Version 6.3.9600.

17237 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081014-7906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response
Time (ms)
Location
Deferred
srv*c:<local folder>*http://msdl.
microsoft.com/download/symbols
Symbol search path is: srv*c:<local folder>*http://msdl.microsoft.com/download/s
ymbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17031.amd64fre.winblue_gdr.140221-1952
Machine Name:
Kernel base = 0xfffff800`0987c000 PsLoadedModuleList = 0xfffff800`09b462d0
Debug session time: Sun Aug 10 05:14:55.112 2014 (UTC - 4:00)
System Uptime: 0 days 0:06:33.741
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*
*
*
Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {ffffc00121cf5ab8, 2, 1, fffff800098e2d08}
*** WARNING: Unable to verify timestamp for GUBootStartup.sys
*** ERROR: Module load completed but symbols could not be loaded for GUBootStart
up.sys
Probably caused by : GUBootStartup.sys ( GUBootStartup+1119 )
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: ffffc00121cf5ab8, memory referenced

Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800098e2d08, address which referenced memory
Debugging Details:
-----------------WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80009bd0138
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffc00121cf5ab8
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeWaitForSingleObject+138
fffff800`098e2d08 f00fba2f07

lock bts dword ptr [rdi],7

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: N360.exe
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
TRAP_FRAME: ffffd001ebd8ea40 -- (.trap 0xffffd001ebd8ea40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000626f rbx=0000000000000000 rcx=0000000000000000
rdx=ffffe0010057a580 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800098e2d08 rsp=ffffd001ebd8ebd0 rbp=0000000000000000
r8=0000000000000002 r9=ffffd001e03c0180 r10=fffff780000003b0
r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0
nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x138:
fffff800`098e2d08 f00fba2f07
lock bts dword ptr [rdi],7 ds:00000000`0000000
0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800099dbae9 to fffff800099cffa0
STACK_TEXT:
ffffd001`ebd8e8f8 fffff800`099dbae9 : 00000000`0000000a ffffc001`21cf5ab8
00`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd001`ebd8e900 fffff800`099da33a : 00000000`00000001 ffffe001`0057a440
00`09b57100 ffffd001`ebd8ea40 : nt!KiBugCheckDispatch+0x69
ffffd001`ebd8ea40 fffff800`098e2d08 : ffffe000`fd4b7680 ffffe001`01064080
00`00000798 fffff801`d06c09f0 : nt!KiPageFault+0x23a
ffffd001`ebd8ebd0 fffff801`d1b60119 : ffffc001`21cf5ab8 00000000`00000000
00`fc176d00 fffff800`00000000 : nt!KeWaitForSingleObject+0x138
ffffd001`ebd8ec60 ffffc001`21cf5ab8 : 00000000`00000000 ffffe000`fc176d00

000000
fffff8
000000
ffffe0
fffff8

00`00000000 00000000`00000000 : GUBootStartup+0x1119

ffffd001`ebd8ec68 00000000`00000000 : ffffe000`fc176d00 fffff800`00000000 000000
00`00000000 fffff801`d06aa4c9 : 0xffffc001`21cf5ab8
STACK_COMMAND: kb
FOLLOWUP_IP:
GUBootStartup+1119
fffff801`d1b60119 ??

???

SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: GUBootStartup+1119
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GUBootStartup
IMAGE_NAME: GUBootStartup.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d88514
FAILURE_BUCKET_ID: AV_GUBootStartup+1119
BUCKET_ID: AV_GUBootStartup+1119
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_gubootstartup+1119
FAILURE_ID_HASH: {ef9c9ada-6175-3787-d4ae-e2ef24bdab53}
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: ffffc00121cf5ab8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff800098e2d08, address which referenced memory
Debugging Details:
------------------

WRITE_ADDRESS: ffffc00121cf5ab8
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeWaitForSingleObject+138
fffff800`098e2d08 f00fba2f07

lock bts dword ptr [rdi],7

CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: AV
PROCESS_NAME: N360.exe
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
TRAP_FRAME: ffffd001ebd8ea40 -- (.trap 0xffffd001ebd8ea40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000626f rbx=0000000000000000 rcx=0000000000000000
rdx=ffffe0010057a580 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800098e2d08 rsp=ffffd001ebd8ebd0 rbp=0000000000000000
r8=0000000000000002 r9=ffffd001e03c0180 r10=fffff780000003b0
r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0
nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x138:
fffff800`098e2d08 f00fba2f07
lock bts dword ptr [rdi],7 ds:00000000`0000000
0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800099dbae9 to fffff800099cffa0
STACK_TEXT:
ffffd001`ebd8e8f8 fffff800`099dbae9 : 00000000`0000000a ffffc001`21cf5ab8
00`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffd001`ebd8e900 fffff800`099da33a : 00000000`00000001 ffffe001`0057a440
00`09b57100 ffffd001`ebd8ea40 : nt!KiBugCheckDispatch+0x69
ffffd001`ebd8ea40 fffff800`098e2d08 : ffffe000`fd4b7680 ffffe001`01064080
00`00000798 fffff801`d06c09f0 : nt!KiPageFault+0x23a
ffffd001`ebd8ebd0 fffff801`d1b60119 : ffffc001`21cf5ab8 00000000`00000000
00`fc176d00 fffff800`00000000 : nt!KeWaitForSingleObject+0x138
ffffd001`ebd8ec60 ffffc001`21cf5ab8 : 00000000`00000000 ffffe000`fc176d00
00`00000000 00000000`00000000 : GUBootStartup+0x1119
ffffd001`ebd8ec68 00000000`00000000 : ffffe000`fc176d00 fffff800`00000000
00`00000000 fffff801`d06aa4c9 : 0xffffc001`21cf5ab8
STACK_COMMAND: kb
FOLLOWUP_IP:
GUBootStartup+1119
fffff801`d1b60119 ??
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: GUBootStartup+1119

???

000000
fffff8
000000
ffffe0
fffff8
000000

FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GUBootStartup
IMAGE_NAME: GUBootStartup.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d88514
FAILURE_BUCKET_ID: AV_GUBootStartup+1119
BUCKET_ID: AV_GUBootStartup+1119
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:av_gubootstartup+1119
FAILURE_ID_HASH: {ef9c9ada-6175-3787-d4ae-e2ef24bdab53}
Followup: MachineOwner
--------2: kd> lmvm GUBootStartup
start
end
module name
fffff801`d1b5f000 fffff801`d1b68000 GUBootStartup T (no symbols)
Loaded symbol image file: GUBootStartup.sys
Image path: \??\C:\WINDOWS\System32\drivers\GUBootStartup.sys
Image name: GUBootStartup.sys
Timestamp:
Wed Jul 30 01:39:32 2014 (53D88514)
CheckSum:
000078E4
ImageSize:
00009000
Translations:
0000.04b0 0000.04e4 0409.04b0 0409.04e4