Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: SingleUserTS
kernel32.dll version: 10.0.14393.0 (rs1_release.160715-1616)
Machine Name:
Debug session time: Sat Mar 4 00:07:44.000 2017 (UTC - 5:00)
System Uptime: not available
Process Uptime: 0 days 0:14:30.000
Kernel time: 0 days 0:00:28.000
User time: 0 days 0:14:49.000
TRIAGER: Could not open triage file : e:\dump_analysis\program riage\oca.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp riage.ini, error 2
TRIAGER: Could not open triage file : e:\dump_analysis\program riage\user.ini, error 2
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
*** WARNING: Unable to verify timestamp for RoboRecall-Core-Win64-Shipping.dll
*** ERROR: Module load completed but symbols could not be loaded for RoboRecall-Core-Win64-Shipping.dll
***** OS symbols are WRONG. Please fix symbols to do analysis.
TRIAGER: Could not open triage file : e:\dump_analysis\program riage\guids.ini, error 2
Unable to load image C:\Windows\System32\ole32.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ole32.dll
*** ERROR: Module load completed but symbols could not be loaded for ole32.dll
*** WARNING: Unable to verify timestamp for LibOVRPlatform64_1.dll
*** ERROR: Module load completed but symbols could not be loaded for LibOVRPlatform64_1.dll
*** WARNING: Unable to verify timestamp for LibOVRP2P64_1.dll
*** ERROR: Module load completed but symbols could not be loaded for LibOVRP2P64_1.dll
*** WARNING: Unable to verify timestamp for LibOVRRT64_1.dll
*** ERROR: Module load completed but symbols could not be loaded for LibOVRRT64_1.dll
*** WARNING: Unable to verify timestamp for RoboRecall-PakFile-Win64-Shipping.dll
*** ERROR: Module load completed but symbols could not be loaded for RoboRecall-PakFile-Win64-Shipping.dll
*** WARNING: Unable to verify timestamp for nvwgf2umx.dll
*** ERROR: Module load completed but symbols could not be loaded for nvwgf2umx.dll
*** WARNING: Unable to verify timestamp for RoboRecall-Messaging-Win64-Shipping.dll
*** ERROR: Module load completed but symbols could not be loaded for RoboRecall-Messaging-Win64-Shipping.dll
*** WARNING: Unable to verify timestamp for d3d11.dll
*** ERROR: Module load completed but symbols could not be loaded for d3d11.dll
*** WARNING: Unable to verify timestamp for mctux.dll
*** ERROR: Module load completed but symbols could not be loaded for mctux.dll
*** WARNING: Unable to verify timestamp for RoboRecall-RenderCore-Win64-Shipping.dll
*** ERROR: Module load completed but symbols could not be loaded for RoboRecall-RenderCore-Win64-Shipping.dll
TRIAGER: Could not open triage file : e:\dump_analysis\program riage\modclass.ini, error 2
*** The OS name list needs to be updated! Unknown Windows version: 10.0 ***
FAULTING_IP:
KERNELBASE+17788
00007ff9`ac877788 488b8c24c0000000 mov rcx,qword ptr [rsp+0C0h]
EXCEPTION_RECORD: ffffffffffffffff – (.exr 0xffffffffffffffff)
ExceptionAddress: 00007ff9ac877788 (KERNELBASE+0x0000000000017788)
ExceptionCode: 00000001
ExceptionFlags: 00000000
NumberParameters: 0
PROCESS_NAME: RoboRecall-Win64-Shipping.exe
ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.
FAULTING_MODULE: 00007ff9af510000 ntdll
DEBUG_FLR_IMAGE_TIMESTAMP: 58b4f989
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
EXCEPTION_CODE: (Win32) 0x1 (1) - Incorrect function.
FAULTING_THREAD: 0000000000001bb8
BUGCHECK_STR: APPLICATION_FAULT_WRONG_SYMBOLS_INVALID_POINTER_READ_AFTER_CALL
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS_AFTER_CALL
DEFAULT_BUCKET_ID: WRONG_SYMBOLS_AFTER_CALL
IP_ON_HEAP: 00000003a8c1b000
The fault address in not in any loaded module, please check your build’s rebase
log at \bin\build_logs imebuild
trebase.log for module which may
contain the address if it were loaded.
FRAME_ONE_INVALID: 1
LAST_CONTROL_TRANSFER: from 00000003a8c1b000 to 00007ff9ac877788
STACK_TEXT:
00000073f24cc0f0 00000003
a8c1b000 : 0000000000000400 00000073
f24cca70 00007ff96c4127b8 00000000
00000001 : KERNELBASE+0x17788
00000073f24cc0f8 00000000
00000400 : 00000073f24cca70 00007ff9
6c4127b8 0000000000000001 00000000
00000000 : 0x3a8c1b000 00000073
f24cc100 00000073f24cca70 : 00007ff9
6c4127b8 0000000000000001 00000000
00000000 00007ff9ac877788 : 0x400 00000073
f24cc108 00007ff96c4127b8 : 00000000
00000001 0000000000000000 00007ff9
ac877788 00007ff900000000 : 0x73
f24cca70
00000073f24cc110 00000000
00000001 : 0000000000000000 00007ff9
ac877788 00007ff900000000 00000000
00000000 : RoboRecall_Core_Win64_Shipping+0x3a27b8
00000073f24cc118 00000000
00000000 : 00007ff9ac877788 00007ff9
00000000 0000000000000000 00000000
00000001 : 0x1
STACK_COMMAND: ~1s; .ecxr ; kb
FOLLOWUP_IP:
RoboRecall_Core_Win64_Shipping+3a27b8
00007ff9`6c4127b8 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: roborecall_core_win64_shipping+3a27b8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RoboRecall_Core_Win64_Shipping
IMAGE_NAME: RoboRecall-Core-Win64-Shipping.dll
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_AFTER_CALL_1_RoboRecall-Core-Win64-Shipping.dll!Unknown
Followup: MachineOwner