- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Trying to profile an Unreal Engine 4-based application, suffering from rather frequent blue screens that are rendering this hopeless.
Unfortunately I can't get anything from the dump because I can't find kernel symbols (apparently I'm not alone https://social.msdn.microsoft.com/Forums/en-US/65db21ea-4c5b-4f24-ab26-0908479c977d/debug-symbols-for-4dac3b582a9147ecaed2644cb165222b1?forum=windbg ), so I'm not sure what else to say.
3: 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: ffffe60fc9f58310, 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: fffff802da49f9be, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
<SNIP>
*** ***
*************************************************************************
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F1
BIOS_DATE: 10/24/2012
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: Z77-HD4
BASEBOARD_VERSION: x.x
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
WRONG_SYMBOLS_TIMESTAMP: 5819bd1f
WRONG_SYMBOLS_SIZE: 820000
FAULTING_MODULE: fffff802da410000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5819bd1f
DUMP_TYPE: 1
BUGCHECK_P1: ffffe60fc9f58310
BUGCHECK_P2: 2
BUGCHECK_P3: 0
BUGCHECK_P4: fffff802da49f9be
READ_ADDRESS: *************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
<SNIP>
*** ***
*************************************************************************
Unable to get size of nt!_MMPTE - probably bad symbols
ffffe60fc9f58310
CURRENT_IRQL: 0
FAULTING_IP:
nt!KiCheckForKernelApcDelivery+fe
fffff802`da49f9be 498b4a30 mov rcx,qword ptr [r10+30h]
CPU_COUNT: 8
CPU_MHZ: d4b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 1B'00000000 (cache) 0'00000000 (init)
ANALYSIS_SESSION_HOST: TBS-BRADY
ANALYSIS_SESSION_TIME: 11-16-2016 14:17:51.0735
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff802da565629 to fffff802da55a510
STACK_TEXT:
ffff9481`76a06558 fffff802`da565629 : 00000000`0000000a ffffe60f`c9f58310 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff9481`76a06560 fffff802`da563c07 : 00000000`00000000 00000000`0004b000 ffff9481`76a06700 fffff802`da47a146 : nt!setjmpex+0x3ee9
ffff9481`76a066a0 fffff802`da49f9be : ffffe60f`c9f58000 fffff804`dfdf1786 00000000`00000282 ffffe60f`c9f0e000 : nt!setjmpex+0x24c7
ffff9481`76a06830 fffff802`da49f8e1 : ffffe60f`b7e47620 fffff802`da4ce500 ffffe60f`00000000 00000000`00000000 : nt!KiCheckForKernelApcDelivery+0xfe
ffff9481`76a068c0 fffff802`da4ad057 : ffffe60f`c3f5b740 fffff802`da8deb28 fffff802`da74bab8 fffff802`da74bc98 : nt!KiCheckForKernelApcDelivery+0x21
ffff9481`76a068f0 fffff802`da8cc1a3 : ffffe60f`b7e47300 ffff9481`76a06980 00000000`00000000 fffff802`da8e199d : nt!FsRtlAcquireHeaderMutex+0x237
ffff9481`76a06940 fffff802`da8c76be : 00000000`00000000 ffffe60f`b7e47300 00000000`00000000 ffffe60f`c3f5b740 : nt!KeUserModeCallback+0x5b3
ffff9481`76a06a80 fffff802`da84c2a0 : ffffe60f`b7e47300 00000000`00000000 ffffe60f`b7e47300 00000000`00000000 : nt!FsRtlGetFileSize+0x19d2
ffff9481`76a06ac0 fffff802`da565193 : ffffe60f`b7e47300 ffff9481`76a06b80 00000000`00000010 ffffe60f`bd412710 : nt!IoOpenDeviceRegistryKey+0x148
ffff9481`76a06b00 00007ffb`34ec58c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x3a53
000000ec`804cf6c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`34ec58c4
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 949bc9ed31f6f65b82927745a91c72095706179f
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 44b1e75a0f8bfc03454e521c838a99d1b55f7d87
THREAD_SHA1_HASH_MOD: bc100a5647b828107ac4e18055e00abcbe1ec406
FOLLOWUP_IP:
nt!KiCheckForKernelApcDelivery+fe
fffff802`da49f9be 498b4a30 mov rcx,qword ptr [r10+30h]
FAULT_INSTR_CODE: 304a8b49
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt_wrong_symbols!5819BD1F820000
FOLLOWUP_NAME: MachineOwner
BUGCHECK_STR: 5819BD1F
EXCEPTION_CODE: (NTSTATUS) 0x5819bd1f - <Unable to get error code text>
EXCEPTION_CODE_STR: 5819BD1F
EXCEPTION_STR: WRONG_SYMBOLS
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703
DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703_5819BD1F_nt_wrong_symbols!5819BD1F820000
TARGET_TIME: 2016-11-16T18:59:48.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-11-02 06:17:03
BUILDDATESTAMP_STR: 161102-0100
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.447.amd64fre.rs1_release_inmarket.161102-0100
ANALYSIS_SESSION_ELAPSED_TIME: ffc
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols_x64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_timestamp_161102-101703_5819bd1f_nt_wrong_symbols!5819bd1f820000
FAILURE_ID_HASH: {d82425fb-28f9-fe3c-99c4-cbc6653270b1}
Followup: MachineOwner
---------
With driver verifier, starting a project in VTune Amplifier triggers an immediate bugcheck due to vtss.sys
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION (d6)
N bytes of memory was allocated and more than N bytes are being referenced.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffffaa0a0f4e9000, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff8026d76f9a9, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
<snip>
*** ***
*************************************************************************
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 14393.447.amd64fre.rs1_release_inmarket.161102-0100
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F1
BIOS_DATE: 10/24/2012
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: Z77-HD4
BASEBOARD_VERSION: x.x
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
WRONG_SYMBOLS_TIMESTAMP: 5819bd1f
WRONG_SYMBOLS_SIZE: 820000
FAULTING_MODULE: fffff802b1617000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5819bd1f
DUMP_TYPE: 1
BUGCHECK_P1: ffffaa0a0f4e9000
BUGCHECK_P2: 0
BUGCHECK_P3: fffff8026d76f9a9
BUGCHECK_P4: 0
READ_ADDRESS: *************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
<snip>
*** ***
*************************************************************************
Unable to get size of nt!_MMPTE - probably bad symbols
ffffaa0a0f4e9000
FAULTING_IP:
vtss+f9a9
fffff802`6d76f9a9 668b02 mov ax,word ptr [rdx]
MM_INTERNAL_CODE: 0
CPU_COUNT: 8
CPU_MHZ: d4b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3a
CPU_STEPPING: 9
CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 1B'00000000 (cache) 0'00000000 (init)
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: TBS-BRADY
ANALYSIS_SESSION_TIME: 11-16-2016 15:11:22.0217
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff802b17b2a47 to fffff802b1761510
STACK_TEXT:
ffff9780`95905e98 fffff802`b17b2a47 : 00000000`00000050 ffffaa0a`0f4e9000 00000000`00000000 ffff9780`95906190 : nt!KeBugCheckEx
ffff9780`95905ea0 fffff802`b16bf5da : 00000000`00000000 00000000`00000000 ffff9780`95906190 ffff9780`959061e8 : nt!memset+0x453c7
ffff9780`95905f90 fffff802`b176aafc : 00000000`00000000 fffff802`b16ab54b ffffaa0a`00000001 fffff802`b1939d00 : nt!RtlRbRemoveNode+0x866a
ffff9780`95906190 fffff802`6d76f9a9 : fffff802`6d76fda0 ffff9780`959063ea ffff9780`95906768 fffff3f9`fcfe7aa0 : nt!setjmpex+0x23bc
ffff9780`95906328 fffff802`6d76fda0 : ffff9780`959063ea ffff9780`95906768 fffff3f9`fcfe7aa0 fffff3f9`fcfe7f38 : vtss+0xf9a9
ffff9780`95906330 fffff802`6d7700bb : 00700066`006d005c 0065002e`0070006d ffff0000`00650078 00000000`00012354 : vtss+0xfda0
ffff9780`95906630 fffff802`b1ae5ca3 : fffff802`b19528c8 ffff8184`26d32080 ffff8184`1de4d040 00000000`00000000 : vtss+0x100bb
ffff9780`95906660 fffff802`b1afb829 : 00000000`0000000a ffff8184`265a8d10 ffff8184`26d32080 00007ffc`eba4cfff : nt!NtFindAtom+0x703
ffff9780`959066c0 fffff802`b1ad91e0 : ffff8184`1c78ddb0 00000000`00000000 ffff8184`271af800 ffff9780`959068c0 : nt!MmCopyVirtualMemory+0x1e89
ffff9780`95906820 fffff802`b1ad6b4f : ffff9780`95906900 ffff9780`00000008 ffff8184`19a77080 00000000`00000001 : nt!NtMapViewOfSection+0x2980
ffff9780`959069a0 fffff802`b176c193 : 00000000`0000003c ffff8184`19b1bcc0 000001d9`28105ec0 000001d9`28105e01 : nt!NtMapViewOfSection+0x2ef
ffff9780`95906a90 00007ffc`ef405364 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x3a53
0000006c`94ace6c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`ef405364
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 18d8a631bd219a5904ed130829606979a2544e24
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a47170e0300cde5ec6347f38fa16cc5931ab8a02
THREAD_SHA1_HASH_MOD: 46ffa982c1396e062fb0c183a98d68f0f84bb3df
FOLLOWUP_IP:
vtss+f9a9
fffff802`6d76f9a9 668b02 mov ax,word ptr [rdx]
FAULT_INSTR_CODE: 66028b66
SYMBOL_STACK_INDEX: 4
FOLLOWUP_NAME: MachineOwner
BUGCHECK_STR: 5819BD1F
EXCEPTION_CODE: (NTSTATUS) 0x5819bd1f - <Unable to get error code text>
EXCEPTION_CODE_STR: 5819BD1F
EXCEPTION_STR: WRONG_SYMBOLS
PROCESS_NAME: ntoskrnl.wrong.symbols.exe
IMAGE_NAME: ntoskrnl.wrong.symbols.exe
MODULE_NAME: nt_wrong_symbols
SYMBOL_NAME: nt_wrong_symbols!5819BD1F820000
BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703
DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703
PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703_5819BD1F_nt_wrong_symbols!5819BD1F820000
TARGET_TIME: 2016-11-16T20:00:40.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-11-02 06:17:03
BUILDDATESTAMP_STR: 161102-0100
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.447.amd64fre.rs1_release_inmarket.161102-0100
ANALYSIS_SESSION_ELAPSED_TIME: 46b11
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols_x64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_timestamp_161102-101703_5819bd1f_nt_wrong_symbols!5819bd1f820000
FAILURE_ID_HASH: {d82425fb-28f9-fe3c-99c4-cbc6653270b1}
Followup: MachineOwner
---------
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
What analysis and exact options you use when expereience the BSOD? Do you you have call count or/and trip count collection levels enabled?
Your system seems running the latest and greatest Windows Server 2016 OS which was relased on November. We are currently working on the OS support enabling in the next release of VTune Amplifier and will contact you once have an updated vtss.sys driver version for a fix verification.
Regards, Katya
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ekaterina L. (Intel) wrote:
What analysis and exact options you use when expereience the BSOD? Do you you have call count or/and trip count collection levels enabled?
Last one I encountered the issue one was
Advanced Hotspots
- Hotspots, call counts, and stacks
- Analyze user tasks, events, and counters
I could try dropping the settings down if that might help mitigate it.
Ekaterina L. (Intel) wrote:
Your system seems running the latest and greatest Windows Server 2016 OS which was relased on November. We are currently working on the OS support enabling in the next release of VTune Amplifier and will contact you once have an updated vtss.sys driver version for a fix verification.
This workstation is running Windows 10 Professional, not Windows Server 2016. It's got "feature updates" deferred, but that's as far as we've gone in slowing down updates so far. Should we do more to slow down updates on systems with VTune? Windows 10 is pretty aggressive with its updating.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Brady,
We've sent you the vtss.sys driver updated version which has a potential fix for the problem. Did you have chance to try it?
Regads, Katya
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page