Inventor 2020 Lag and Pounding Paging File???

phlyx · ‎12-03-2019

New workstations with Windows 10 (all updates), Radeon Pro WX 8200, and upgraded to Inventor 2020.2 and have hanging, lagging and crashing issues. Last week also had a couple BSOD's with MEMORY MANAGEMENT issue and issues with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (atikmpag.sys). Trying to work thru the issue(s) but today noticed that although we have 64GB RAM, when we're opening a large assembly or opening Inventor we only are using a small portion of our RAM but we're reading/writing like crazy to the Windows paging file (Hard Faults/sec using paging file).

We have OS managing paging file size and our files all exist on the network drives, so not sure why we're hitting the paging file so much which is also extremely s-l-o-w compared to the RAM.

Just curious if anyone has any hints or tips as we're struggling here.

All help is greatly appreciated.

johnsonshiue · ‎12-03-2019

Hi! A few things to try. Clean up %temp% folder. Install 2020.2 update. Move the target files locally. Do you see a difference? Do you access Appearance and Material Library through network?

Many thanks!

Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer

phlyx · ‎12-04-2019

Have had 2020.2 installed since it came out. Did a repair on Inventor. Windows 10 is completely up to date. Yesterday I ran Windows Memory Diagnostics, CHKDSK, disabled paging file / reboot / re-enable paging file (to rebuild), and last night ran MemTest86, all with no errors at all. Haven't cleaned up the temp file but could definitely do that quick.

The files we're working on at networked and so are the libraries. A couple times I would get the Picasso-like graphics splattering across my Inventor models (see below) and my computer has only crashed/BSOD when I am doing something in Inventor. That makes me think some issue between my graphics card and Inventor but posted a forum message asking for best settings for Radeon Pro software but got no replies, here or on AMD's forums.

mcgyvr · ‎12-04-2019

Screams graphics card driver issue to me..

If you are on the latest version try rolling back to an older driver version..

-------------------------------------------------------------------------------------------
Inventor 2023 - Dell Precision 5570

Did you find this reply helpful ? If so please use the Accept Solution button below.
Maybe buy me a beer through Venmo @mcgyvr1269

phlyx · ‎12-04-2019

Was thinking about that as it wasn't long ago I ungraded from AMD's 19Q3 to 19Q4. Rolling back to 19Q3 and see what that does. Thanks!

phlyx · ‎12-04-2019

Rolled the video driver back to 19Q3 and seems to be stable and lag not as bad as it was previously. Will give it some more time but would still like to know if there are particular settings in the Radeon Pro software that would help Inventor run smoother.

phlyx · ‎12-04-2019

Spoke too soon. Was plugging along and then all of a sudden both my monitors went black. After a few seconds of it not doing anything (was actually expecting a BSOD) I hit the ESC key and both monitors came back on and everything seemed fine except I had the message below in my Inventor window.

Kind of feel the video card is the issue talking with Inventor but not sure how to find out for sure. Seems when I had issues with the 19Q4 driver I got BSOD and with 19Q3 it just flakes out with Inventor but doesn't take Windows down.

RNDinov8r · ‎12-04-2019

For what it's worth, I work directly next to Phlyx...have an identical set up...literally. Save for the pictures stored in our "Pictures" Folder for screen savers...our machines are identical. Same mapped drives, same everything. I am running all the latest updates as well. I have have yet to get even one BSOD since running 2020. And when we use the benchmarking app, my machine consistently bench marks faster than his...this was the case even when we got the machines "vanilla" before we installed any inventor Add-ons or other engineering software (not IV related).

johnsonshiue · ‎12-04-2019

Hi! Graphics card can be one of the reasons. I suspect the network-shared appearance and material library could be an issue too. Try bringing everything local (Inventor files, appearance and material library, and design data). Does it work faster? If it is still slow, I believe the graphics card might be the problem.

Many thanks!

Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer

phlyx · ‎12-05-2019

The speed is not as much the issue as the BSOD and Inventor crashes. Looked at my event logs yesterday (posted below) and although the last couple were eDrawings and Logitech stuff, this happened when the screens blanked out as I was launching eDrawings when that happened and it seemed like the video card burped and those apps stopped responding and logged errors. Not sure if any of this shows anything:

ERROR LOGS:

12/4/2019 3:41:46 PM

Faulting application name: eDrawings.exe, version: 27.4.0.20, time stamp: 0x5d1d2053

Faulting module name: dx11_2220_x64.hdi, version: 22.20.0.0, time stamp: 0x59b02b43

Exception code: 0xc0000005

Fault offset: 0x0000000000024138

Faulting process id: 0x345c

Faulting application start time: 0x01d5aadacf96b59b

Faulting application path: C:\Program Files\Common Files\eDrawings2019\eDrawings.exe

Faulting module path: C:\Program Files\Common Files\eDrawings2019\dx11_2220_x64.hdi

Report Id: 6bddeaa3-2b45-4754-897d-55944f8da52b

Faulting package full name:

Faulting package-relative application ID:

12/4/2019 3:41:45 PM

Faulting application name: LogiOptionsMgr.exe, version: 8.0.863.0, time stamp: 0x5d650f16

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0000000000000000

Faulting process id: 0x131c

Faulting application start time: 0x01d5aab6aafe377a

Faulting application path: C:\ProgramData\Logishrd\LogiOptions\Software\Current\LogiOptionsMgr.exe

Faulting module path: unknown

Report Id: f3a9e69b-ef77-447f-b4cc-b83640a7f1c2

Faulting package full name:

Faulting package-relative application ID:

12/4/2019 3:41:45 PM

Application: eDrawings.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: exception code c0000005, exception address 000000006C4F4138

12/4/2019 12:23:49 PM

svchost (10120,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 12:19:48 PM

The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 18768 and the required size was 43160.

12/4/2019 10:33:53 AM

svchost (18232,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 10:28:31 AM

svchost (6904,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 10:17:26 AM

svchost (18628,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 10:11:32 AM

Faulting application name: AUEPMaster.exe, version: 0.0.0.0, time stamp: 0x5d95488e

Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720

Exception code: 0xc0000409

Fault offset: 0x000000000006db8e

Faulting process id: 0x4260

Faulting application start time: 0x01d5aab2702b8654

Faulting application path: C:\Program Files\AMD\Performance Profile Client\AUEPMaster.exe

Faulting module path: C:\WINDOWS\System32\ucrtbase.dll

Report Id: eb38806c-730b-40c6-9755-6d85d3b021df

Faulting package full name:

Faulting package-relative application ID:

12/4/2019 10:09:13 AM

svchost (15480,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 10:01:32 AM

svchost (6980,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 9:50:51 AM

Windows cannot load the extensible counter DLL "C:\WINDOWS\system32\sysmain.dll" (Win32 error code The specified module could not be found.).

12/4/2019 9:50:51 AM (WARNING)

The Open procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed with error code The system cannot find the file specified.. Performance data for this service will not be available.

12/4/2019 9:32:44 AM

svchost (9680,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 8:42:06 AM

svchost (20204,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 8:35:58 AM

svchost (19332,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 8:32:41 AM (WARNING)

Unable to open the job object \BaseNamedObjects\WmiProviderSubSystemHostJob for query access. The calling process may not have permission to open this job. The first four bytes (DWORD) of the Data section contains the status code.

12/4/2019 8:21:00 AM

svchost (7132,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

12/4/2019 8:04:33 AM

Failed to initialize LanternRock SDK: 0x00040201. Reason: S_NO_OPTIN (telemetry not opted-in)

SOME ODD EARLIER MESSAGES THAT HAPPENED SEVERAL TIMES THE SAME:

12/3/2019 2:05:38 PM

Application 'C:\Windows\System32\SearchProtocolHost.exe' (pid 1452) cannot be restarted - Application SID does not match Conductor SID..

12/3/2019 2:05:38 PM

Application 'C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE' (pid 12268) cannot be restarted - Application SID does not match Conductor SID..

12/3/2019 2:05:38 PM

Application 'C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE' (pid 8160) cannot be restarted - Application SID does not match Conductor SID..

mcgyvr · ‎12-05-2019

@phlyx Swap graphics cards with @RNDinov8r if you want to know for sure..

If his starts crashing then that card may be defective..

-------------------------------------------------------------------------------------------
Inventor 2023 - Dell Precision 5570

Did you find this reply helpful ? If so please use the Accept Solution button below.
Maybe buy me a beer through Venmo @mcgyvr1269

phlyx · ‎12-05-2019

Looking at my dump files it shows the offending program was Inventor.exe. All the previous ones showed issues with atikmdag.sys and that was when I was running 19Q4

Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120319-7359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`41600000 PsLoadedModuleList = 0xfffff802`41a48170
Debug session time: Tue Dec  3 14:13:26.528 2019 (UTC - 5:00)
System Uptime: 0 days 5:49:33.396
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -vnt!KeBugCheckEx:
fffff802`417c14e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff868f`a8256820=000000000000001a
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061948, The subtype of the bugcheck.
Arg2: 0000000b000ad788
Arg3: 0000000000000001
Arg4: 0000000b000ad788

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 1

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on WS-SVEIX

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 1

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 71

    Key  : Analysis.System
    Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  1a

BUGCHECK_P1: 61948

BUGCHECK_P2: b000ad788

BUGCHECK_P3: 1

BUGCHECK_P4: b000ad788

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Inventor.exe

STACK_TEXT:  
ffff868f`a8256818 fffff802`418404c2 : 00000000`0000001a 00000000`00061948 0000000b`000ad788 00000000`00000001 : nt!KeBugCheckEx
ffff868f`a8256820 fffff802`417fc4df : 00000000`00000002 00000000`00000001 00000000`00000001 00000000`00000000 : nt!MiDereferenceIoPages+0x14af16
ffff868f`a82568b0 fffff802`588668a0 : 00000000`00000182 00000000`00000002 00000000`00000000 fffff802`00000000 : nt!MmUnlockPages+0x1b137f
ffff868f`a8256980 fffff802`588664ea : 00000000`00000000 fffff802`41c11730 ffff868f`a8256a40 ffff880f`83839f60 : dxgmms2!VIDMM_MDL_RANGE::Unlock+0x18
ffff868f`a82569b0 fffff802`58866325 : ffff880f`b0c8f8f8 ffff880f`a9356f20 ffffa501`566e5180 01000000`00100000 : dxgmms2!VIDMM_RECYCLE_HEAP_PHYSICAL_VIEW::UnlockRange+0xa6
ffff868f`a8256a50 fffff802`58868dd7 : ffff880f`a9356f20 ffff880f`a9356f88 ffff880f`b057c208 fffff802`41667d33 : dxgmms2!VIDMM_RECYCLE_RANGE::DebouncedUnlock+0x79
ffff868f`a8256ab0 fffff802`588bb703 : fffff802`5884e700 ffffdc04`873ceb98 ffff880f`00000001 ffffdc04`85cdcde0 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProcessDebounceList+0xdf
ffff868f`a8256b20 fffff802`58866c1c : 00000000`07a80000 00000000`07a80000 ffff880f`b004e610 00000000`00000000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::ProcessDebounceListsGlobally+0xbb
ffff868f`a8256bb0 fffff802`5886a9a3 : ffff880f`9939fb30 ffff880f`9939fb30 00000000`00000000 ffffdc04`87246ec8 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::UnlockAllocation+0x7c
ffff868f`a8256bf0 fffff802`5888269d : ffffdc04`87246001 ffff880f`af802210 ffff880f`9939fb30 ffff880f`b004e610 : dxgmms2!VIDMM_GLOBAL::UnlockAllocation+0x73
ffff868f`a8256c30 fffff802`58882076 : fffff802`5883c300 ffffdc04`87246001 fffff802`5883c300 ffffdc04`85cdcde0 : dxgmms2!VIDMM_SYSMEM_SEGMENT::UnlockAllocationRange+0xad
ffff868f`a8256ce0 fffff802`58882744 : ffff880f`9939fb30 ffff880f`9939fb30 ffffdc04`87247550 ffffdc04`00000000 : dxgmms2!VIDMM_SYSMEM_SEGMENT::ReleaseTemporaryResource+0xd6
ffff868f`a8256d20 fffff802`5886c61b : ffffdc04`87246000 00000000`00000000 ffffdc04`7d211400 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::EvictTemporaryAllocation+0x5c
ffff868f`a8256d50 fffff802`5886c8bf : ffffdc04`964a8c10 ffffdc04`87246000 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbf
ffff868f`a8256db0 fffff802`58860ed7 : 00000000`00000000 00000000`a0000000 00000000`00000000 ffff880f`acfb1930 : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x10f
ffff868f`a8256ec0 fffff802`5887001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_PAGE_TABLE::CommitPageTable+0x6b
ffff868f`a8256f10 fffff802`5886eb38 : 00000000`00000000 ffff880f`8bff1050 00000000`00000000 00000000`00080000 : dxgmms2!VIDMM_PAGE_TABLE::CommitVirtualAddressRange+0x36a
ffff868f`a8256ff0 fffff802`5889b4cc : ffff880f`8bff1050 ffff880f`8ab139c0 ffff868f`a8257590 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x9c8
ffff868f`a8257190 fffff802`5889b4cc : ffff880f`8b8b0010 ffff880f`8ab139c0 ffff868f`a8257590 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x2d35c
ffff868f`a8257330 fffff802`5886dd13 : ffff880f`8b8afd10 ffff880f`8ab139c0 ffff868f`a8257590 00000000`00000000 : dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x2d35c
ffff868f`a82574d0 fffff802`5886cbd3 : ffffdc04`96402910 ffffdc04`00000000 00000000`00000002 00000000`00000000 : dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x2e3
ffff868f`a8257640 fffff802`5885d2d6 : ffffdc04`87247750 ffffdc04`87247550 00000000`00000000 ffffdc04`96402910 : dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x423
ffff868f`a8257750 fffff802`5885d1be : ffffdc04`96402910 00000000`00000000 00000000`00000000 ffffdc04`7f6582f8 : dxgmms2!VIDMM_GLOBAL::PageInFaultedAllocation+0xb6
ffff868f`a82577b0 fffff802`5885d3a4 : ffffdc04`87246000 ffff868f`a8257af8 ffffdc04`8a763a00 ffff868f`a8257af8 : dxgmms2!VIDMM_GLOBAL::PageInDeviceInternal+0x18a
ffff868f`a8257830 fffff802`5887c267 : ffff868f`a8257968 ffff868f`a8257af8 00000000`00000000 ffff880f`834bb690 : dxgmms2!VIDMM_GLOBAL::TryPageInDevice+0x50
ffff868f`a8257870 fffff802`58888678 : 00000000`0000003c ffff868f`a82579e0 fffff802`58842114 fffff802`58842114 : dxgmms2!VIDMM_DEVICE::Resume+0x73
ffff868f`a82578e0 fffff802`58886ee9 : ffff880f`834bb610 006e0065`006d0001 00200022`005c0000 00660065`00720000 : dxgmms2!VIDMM_WORKER_THREAD::Run+0x1778
ffff868f`a8257ae0 fffff802`4172a7a5 : ffffdc04`7d211040 fffff802`58886ee0 ffff880f`834bb610 0022005c`006b006e : dxgmms2!VidMmWorkerThreadProc+0x9
ffff868f`a8257b10 fffff802`417c8b2a : ffffa501`566e5180 ffffdc04`7d211040 fffff802`4172a750 006e005c`0072005c : nt!PspSystemThreadStartup+0x55
ffff868f`a8257b60 00000000`00000000 : ffff868f`a8258000 ffff868f`a8251000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


SYMBOL_NAME:  dxgmms2!VIDMM_MDL_RANGE::Unlock+18

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.18362.449

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  18

FAILURE_BUCKET_ID:  0x1a_61948_dxgmms2!VIDMM_MDL_RANGE::Unlock

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {2c04018b-ed41-fda8-c977-acf978dc8933}

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

phlyx · ‎12-05-2019

Graphic diagnostic info in case that highlights something:

This Direct3D graphics driver is Microsoft WHQL certified
Graphics Hardware Description:
Advanced Micro Devices, Inc. AMD FirePro SDI (0x6868)

AIRViz Device Manager \ VirtualDeviceDx11
Feature Level 5_0
Performance Mode
Hardware Renderer
OGSScene.dll

Graphics driver file C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\amdxc64.dll is version 26.20.11024.1
The display is using 32-bit color

Inventor Version:

Build: 310, Release: 2020.2 - Date: Mon 11/11/2019
64-Bit Edition - 131072.00 GB

Loaded Inventor Add-Ins:

Assembly Bonus Tools
Simulation: Dynamic Simulation
Simulation: Frame Analysis
iCopy
Electrical Catalog Browser

System Information:

Operating System: 64-bit Microsoft Windows 10 Pro (Build 9200)
Language: English
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 0905
Processor: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (1 processor, 8 cores)
System Memory: 63.916 GB RAM

Graphics Device Information:

Renderer: HAL
Manufacturer: Advanced Micro Devices, Inc.
Chip Type: AMD FirePro SDI (0x6868)
DAC Type: Internal DAC(400MHz)
Graphics HW Memory: 11.993 GB
Display Mode: 1920 x 1080 (32 bit) (60 Hz)

Graphics driver file: C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\amdxc64.dll
Driver file version: 26.20.11024.1
Driver Date: 11 June 2019 0:00:00 UTC (Coordinated Universal Time)

Direct3D Graphics Device Information:

Adapter Description: Radeon (TM) PRO WX 8200
Vendor ID string: 0x00001002
Device ID string: 0x00006868
VendorID: 1002
DeviceID: 6868
SubSystemID: a0c1002
Revision: 0

Direct3D 10 / DXGI System Information:

Dedicated Video Memory: 11.993 GB
Dedicated System Memory: 0 MB
Shared System Memory: 31.958 GB

DxDiag System Information:

Operating System: Windows 10 Pro 64-bit (6.2, Build 9200) (18362.19h1_release.190318-1202)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 0905
Processor: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs), ~3.6GHz
System Memory: 65536MB RAM
Page File: 14923MB used, 54622MB available
DirectX Version: DirectX 12
DxDiag Version: 6.02.18362.0387

DxDiag Graphics Device Information:

DirectX Version: 12.0
DDI Version: 12
DDI Version Number: c
DxDiag WHQL Level: 0
Driver Signed Valid: True
Driver Signed: True
Manufacturer: Advanced Micro Devices, Inc.
Chip Type: AMD FirePro SDI (0x6868)
DAC Type: Internal DAC(400MHz)
Revision: Unknown
Graphics HW Memory: 45005 MB
Display Mode: 1920 x 1080 (32 bit) (60Hz)

Graphics driver file: C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0343957.inf_amd64_9c2f22bd67ac5f29\B343570\amdxc64.dll
Driver file version: 26.20.11024.0001
Driver Date: 6/10/2019 7:00:00 PM
WHQL Level: 1

Inventor Options Information:

Options = 0x00000000
Warning Options = 0x00000000

Graphics driver log information:

johnsonshiue · ‎12-05-2019

Hi! Do you have an integrated graphics card? Is it possible the machine might be running Inventor on the integrated graphics card as opposed to the dedicated graphics card. Try changing the AMD graphics setting so that Inventor runs on the dedicated graphics card.

Many thanks!

Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer

phlyx · ‎12-09-2019

Had that same thought but Device Manager doesn't even show the integrated video card so doubt it's using it:

Booted to BIOS last week and could not find anywhere to disable integrated video card as it seems it already is. Is there another way to check?

phlyx · ‎12-09-2019

And totally quirky. Had another engineer who was working for weeks with no issues, he just tell me this morning he would open Inventor, start a new part, draw a sketch, then extrude and as soon as he did the extrude Inventor would crash. Did it several times, same thing. Rebooted, same thing. I checked and he was running 2020.1 so had him installed the 2020.2 update. Same thing. Rebooted, same thing.

He experimented and found that if he ran Inventor and opened an existing part then he could create new parts without issues. But if he ran Inventor and the first thing he tried to do was create a new part Inventor would crash. Gotta love it 🙄

phlyx · ‎12-09-2019

Just checked and our new workstations use UEFI BIOS mode and in UEFI there is no way to disable the onboard video card.

johnsonshiue · ‎12-09-2019

Hi! You don't need to disable on-board graphics card. You can use graphics vendor tool to choose what program to run on the dedicated graphics card. Could you try it?

The crash you are talking about does sound like graphics related. If you can pick the driver profile, make sure you pick the one for CAD (or AutoCAD), not for gaming.

Many thanks!

Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer

Frederick_Law · ‎12-09-2019

I suspect video card over heating.

Open the case and make sure the fan still works. If not, you found the problem.

Take the video card out, blow all the dust out of the fan and heatsink.

Also vaccum the computer and clear dust on fans, heatsinks and vents.

Try to monitor temp on the video card. If possible increase fan speed to reduce heat build up.

Had similar problem on a few old nVidia Quadro.

johnsonshiue · ‎12-10-2019

Hi! We just recently notice that there could be a Windows dependency here. Try this.

1) Unplug network.

2) Turn off any Anti-Virus tool (including Microsoft Defender).

3) Run Inventor.

Does it run faster? I just want to know if it could be related to the system. You do want to turn on Anti-Virus tools afterwards.

Many thanks!

Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer

Community

Inventor 2020 Lag and Pounding Paging File???

Inventor 2020 Lag and Pounding Paging File???

Inventor 2020 Lag and Pounding Paging File???