BugCheck 1E, {ffffffffc0000005, 0, 8, 0}
Probably caused by :[COLOR=#ff0000][U][B] Unknown_Image ( ANALYSIS_INCONCLUSIVE )[/B][/U][/COLOR]
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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+0
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032bc0e8
0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: [COLOR=#ff0000][U][B]from 0000000000000000 to 0000000000000000[/B][/U][/COLOR]
STACK_TEXT:
[COLOR=#ff0000][U][B]00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0[/B][/U][/COLOR]
STACK_COMMAND: kb
SYMBOL_NAME: [COLOR=#ff0000][B]ANALYSIS_INCONCLUSIVE[/B][/COLOR]
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: [COLOR=#ff0000][U][B]Unknown_Module[/B][/U][/COLOR]
IMAGE_NAME: [COLOR=#ff0000][U][B]Unknown_Image[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: [COLOR=#ff0000][U][B]INVALID_KERNEL_CONTEXT[/B][/U][/COLOR]
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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffe4b404adaba8, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: ffffe4b404adaba8, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
[COLOR=#ff0000][U][B]BugCheck 1E[/B][/U][/COLOR], {ffffffffc0000005, fffff8800141c86a, 1, 10}
[COLOR=#ff0000][U][B]Probably caused by : Unknown_Image [/B][/U][/COLOR]( Ntfs!NtfsFastIoCheckIfPossibleInternal+25e )
[COLOR=#ff0000][U][B]KMODE_EXCEPTION_NOT_HANDLED (1e)[/B][/U][/COLOR]
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: fffff8800141c86a, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000010, Parameter 1 of the exception
, which I would think should be a bit more recent, but perhaps not.Memory mapping Driver is a driver file from company ASUS belonging to product ATK Generic Function Service
fffff880`09704f08 fffff880`04d84d52Unable to load image [COLOR=#ff0000][U][B]igdkmd64.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]igdkmd64.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]igdkmd64.sys[/B][/U][/COLOR]
[B][U][COLOR=#ff0000] igdkmd64[/COLOR][/U][/B]+0x342d52
fffff880`09705878 fffff880`05a947f0Unable to load image[COLOR=#ff0000][U][B] athrx.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]athrx.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]athrx.sys[/B][/U][/COLOR]
[COLOR=#ff0000][U][B]athrx[/B][/U][/COLOR]+0x2897f0
fffff880`097089a8 fffff880`0124208aUnable to load image [COLOR=#ff0000][U][B]iaStor.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]iaStor.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=#ff0000][U][B]iaStor.sys[/B][/U][/COLOR]
[COLOR=#ff0000][U][B]iaStor[/B][/U][/COLOR]+0x3908a