Avid Pro Audio Community

Avid Pro Audio Community

How to Join & Post  •  Community Terms of Use  •  Help Us Help You

Knowledge Base Search  •  Community Search  •  Learn & Support


Avid Home Page

Go Back   Avid Pro Audio Community > Pro Tools Software > Windows

Reply
 
Thread Tools Search this Thread Display Modes
  #21  
Old 09-15-2024, 06:04 PM
Darryl Ramm Darryl Ramm is online now
Member
 
Join Date: Nov 2010
Location: USA
Posts: 20,201
Default Re: Could not create a new document because Access violation occurred, unable to read

Yes I'd try installing the Avid plugins you want and test occasionally as you go. Kinda hoping you find something here that breaks things so this does not stay a mystery.

BTW in any of this is there any clue in the log files? (C:\Users\<username>\AppData\Local\Avid\Logs) any errors or warnings? They are pretty cryptic but one thing to look at is the log files where Pro Tools crashed... and the ones where it now starts up OK...you may be able to infer what is the very next thing it was trying to do when it crashed before.

Last edited by Darryl Ramm; 09-15-2024 at 06:17 PM.
Reply With Quote
  #22  
Old 09-16-2024, 11:45 PM
tonygoodall tonygoodall is offline
Member
 
Join Date: Jul 2000
Location: uk
Posts: 206
Default Re: Could not create a new document because Access violation occurred, unable to read

some excerpts of the log:

error seems to start with Progress: Building Edit Window...


133868.249997,056e8,0f09: Progress: Loading Plugins
133868.250027,056e8,00e0: InternalProToolsProgress. Message: Loading Plugins, level: 1
133868.254754,056e8,0e24: PlugInLoaderUtils: Skipping 0 unauthorized plugins
133868.254790,056e8,00e0: TMenuManager::InvalidateMenus - force=true
133868.397485,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133868.492000,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133868.492895,056e8,0b08: Sys_Socket::Initialize
133868.499115,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\JSONSchemaValidator.dll can't be gotten
133868.499489,02cb4,007d: WASAPI IAudioCaptureClient::GetBuffer AUDCLNT_S_BUFFER_EMPTY (0x8890001)
133868.501743,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\CrashReporter.dll can't be gotten
133868.501932,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\crashpad_glue.dll can't be gotten
133868.510295,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\atmos_storage.dll can't be gotten
133868.510355,02cb4,007d: WASAPI IAudioCaptureClient::GetBuffer AUDCLNT_S_BUFFER_EMPTY (0x8890001)
133868.510928,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\AvOmfToolkit.dll can't be gotten
133868.511155,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\libjpegV4.dll can't be gotten
133868.512408,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\AVX2_Plug-Ins\PXF\PXFPlugin.acf can't be gotten
133868.513293,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\AVX2_Plug-Ins\PXF\xqilla23_vc142_x64_u.dll can't be gotten
133868.514609,056e8,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\PTSL.dll can't be gotten
133868.518058,056e8,0e0d: Component: AAE.dll, 24.6.0.149, c:\Program Files\Avid\Pro Tools\AAE.dll, 17/06/2024 17:20:24
133868.518064,056e8,0e0d: Component: AAFCOAPI.dll, 1.1.6, c:\Program Files\Avid\Pro Tools\AAFCOAPI.dll, 21/02/2024 13:44:50



133880.872954,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133881.017567,056e8,0d02: Performing TCommand: class TControlTracker
133881.017582,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133881.025132,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133881.041601,056e8,0000: Closed Dashboard Dialog
133881.045700,056e8,000f: TTrack::SetUID = D4!q5baaA3maaaGk
133881.046481,056e8,0033: SMgr_DSPCache::InstantiatePlugIn - pluginType: Native, name: "AudioInjection PlugIn", track "Audio Audition Track"
133881.046933,056e8,0033: SMgr_DSPCache::InstantiateMixer - pluginType: Native, numInputsDesired: 10, numOutputsRequired: 2, name: "Private Audition Bus"
133881.049645,056e8,0033: SMgr_DSPCache::InstantiateMixer - returning mixer spec (0000000064769B50). numActualInputs: 10, numActualOutputs: 2, err = 0
133881.049890,056e8,0033: SMgr_DSPCache::InstantiateMixer - pluginType: Native, numInputsDesired: 2, numOutputsRequired: 2, name: "Speakers 1-2"
133881.052577,056e8,0033: SMgr_DSPCache::InstantiateMixer - returning mixer spec (0000000064769A60). numActualInputs: 2, numActualOutputs: 2, err = 0
133881.126264,056e8,0033: SMgr_DSPCache::InstantiatePlugIn - pluginType: Elastic, name: "Polyphonic", track "Audio Audition Track"
133881.232530,056e8,000f: TTrack::SetUID = D4pJ0baaBFiaaaGk
133881.233429,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133884.204632,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133884.204752,056e8,0d02: Performing TCommand: New...
133884.204762,056e8,000f: CAbletonLinkManager::SetLaunchQuantize: launch quantize changed to 4
133884.204763,056e8,000f: CAbletonLinkManager::EnableStartStopSync: disabling
133884.204784,056e8,0f09: MakeProToolsDocForOpen command 10 project 00000000-0000-0000-0000-000000000000
133884.205313,056e8,0033: SMgr_DSPCache::FreeMixer - (0000000064769A60), pluginType: Native, inNumInputsUsed: 2, inNumOutputsUsed: 2, name: "Speakers 1-2"
133884.205410,056e8,0033: SMgr_DSPCache::FreeMixer - (0000000064769B50), pluginType: Native, inNumInputsUsed: 10, inNumOutputsUsed: 2, name: "Private Audition Bus"
133884.205568,056e8,0033: SMgr_DSPCache::FreePlugIn - pluginType: Native, name: "AudioInjection PlugIn", track "Audio Audition Track"
133884.206281,056e8,0033: SMgr_DSPCache::FreePlugIn - pluginType: Elastic, name: "Polyphonic", track "Audio Audition Track"
133884.268536,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.268563,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.268658,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.268678,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.268747,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.268767,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.268858,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.268877,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.269596,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.269618,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.269641,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.273109,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.273142,056e8,0e0f: CMN_TRACEASSERT Requested font was not found! (false) D:\ws\PT\release\2024\r2\ProTools\DFW\Imaging\DFW_ FontMap.cpp line 281
133884.288790,056e8,00e0: TMenuManager::InvalidateMenus - force=false



133926.828126,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133927.309042,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133927.312085,056e8,0f09: Progress: Updating Routing Coefficients...
133927.331698,056e8,0b07: SLnk_CommPreferences::GetCommunicationPort - 28282
133927.343386,056e8,0e0c: PtSess_RunTime::GetDocumentInfo - major version: 6, minor version: 5
133927.343393,056e8,0e0c: this build of Pro Tools supports up to major version: 6, minor version: 23
133927.345007,056e8,000f: TTrack::SetUID = Equ6KaqapIkaaaGk
133927.345162,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133927.347761,056e8,0033: SMgr_DSPCache::InstantiatePlugIn - pluginType: Native, name: "AudioInjection PlugIn", track "Audio Audition Track"
133927.348086,056e8,0033: SMgr_DSPCache::InstantiateMixer - pluginType: Native, numInputsDesired: 10, numOutputsRequired: 2, name: "Private Audition Bus"
133927.350001,056e8,0033: SMgr_DSPCache::InstantiateMixer - returning mixer spec (0000000073FDF0A0). numActualInputs: 10, numActualOutputs: 2, err = 0
133927.350164,056e8,0033: SMgr_DSPCache::InstantiateMixer - pluginType: Native, numInputsDesired: 2, numOutputsRequired: 2, name: "Speakers 1-2"
133927.351946,056e8,0033: SMgr_DSPCache::InstantiateMixer - returning mixer spec (0000000073FDFC80). numActualInputs: 2, numActualOutputs: 2, err = 0
133927.419704,056e8,0033: SMgr_DSPCache::InstantiatePlugIn - pluginType: Elastic, name: "Polyphonic", track "Audio Audition Track"
133927.504433,056e8,000f: TTrack::SetUID = Eu0jQbqaqEeaaaGk
133927.504976,056e8,00e0: TMenuManager::InvalidateMenus - force=false
133927.506088,056e8,0f09: Progress: Updating Routing Coefficients...
133927.522781,056e8,0f09: Progress: Building Edit Window...
133927.541635,056e8,0e0f: Access Violation: Thread "Main Thread (id=kThreadTableID_MainThread)"
Stacktrace:
00007FFC14185BA2 : DigiTraceStack + 0x0000000000000072 (DigiTrace.dll @ 0x00007FFC14180000)
00007FFB714E7217 : Sys_SEHandlerWin32::StructuredExceptionTranslator + 0x00000000000000E7 (CFnd.dll @ 0x00007FFB71290000)
00007FFC12DD3889 : <No Symbol> 0x00007FFC12DD3889 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD1A64 : <No Symbol> 0x00007FFC12DD1A64 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD194A : <No Symbol> 0x00007FFC12DD194A (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD218F : <No Symbol> 0x00007FFC12DD218F (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD21E9 : <No Symbol> 0x00007FFC12DD21E9 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD4019 : _CxxFrameHandler4 + 0x00000000000000A9 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
0000000003356C14 : TC_Private::Run + 0x00000000000FF884 (DFW.dll @ 0x0000000002E00000)
00007FFC2E8951DF : _chkstk + 0x000000000000012F (ntdll.dll @ 0x00007FFC2E7F0000)
00007FFC2E80E866 : RtlFindCharInUnicodeString + 0x0000000000000A96 (ntdll.dll @ 0x00007FFC2E7F0000)
00007FFC2E8941CE : KiUserExceptionDispatcher + 0x000000000000002E (ntdll.dll @ 0x00007FFC2E7F0000)
0000000002EC6595 : CRGBColor::CRGBColor + 0x0000000000000025 (DFW.dll @ 0x0000000002E00000)
0000000002F916DC : TSearchBox:perator= + 0x000000000000040C (DFW.dll @ 0x0000000002E00000)
0000000002F921EB : TSearchBox:perator= + 0x0000000000000F1B (DFW.dll @ 0x0000000002E00000)
0000000002F93815 : TSearchBox::TSearchBox + 0x0000000000000085 (DFW.dll @ 0x0000000002E00000)
0000000002F93777 : TSearchBox::_DefaultConstructor + 0x0000000000000027 (DFW.dll @ 0x0000000002E00000)
00000000031B8E58 : TViewServer::Reanimate + 0x00000000000001A8 (DFW.dll @ 0x0000000002E00000)
00000000031B46D4 : TView::ReadSubViews + 0x00000000000002D4 (DFW.dll @ 0x0000000002E00000)
00000000031A9CD0 : TView::ReadContainer + 0x0000000000000170 (DFW.dll @ 0x0000000002E00000)
00000000031B8E7B : TViewServer::Reanimate + 0x00000000000001CB (DFW.dll @ 0x0000000002E00000)
00000000031B46D4 : TView::ReadSubViews + 0x00000000000002D4 (DFW.dll @ 0x0000000002E00000)
00000000031A9CD0 : TView::ReadContainer + 0x0000000000000170 (DFW.dll @ 0x0000000002E00000)
00000000031B8E7B : TViewServer::Reanimate + 0x00000000000001CB (DFW.dll @ 0x0000000002E00000)
00000000031B46D4 : TView::ReadSubViews + 0x00000000000002D4 (DFW.dll @ 0x0000000002E00000)
00000000031A9CD0 : TView::ReadContainer + 0x0000000000000170 (DFW.dll @ 0x0000000002E00000)
00000000031B8E7B : TViewServer::Reanimate + 0x00000000000001CB (DFW.dll @ 0x0000000002E00000)
00000000031B46D4 : TView::ReadSubViews + 0x00000000000002D4 (DFW.dll @ 0x0000000002E00000)
00000000031A9CD0 : TView::ReadContainer + 0x0000000000000170 (DFW.dll @ 0x0000000002E00000)
00000000031B8E7B : TViewServer::Reanimate + 0x00000000000001CB (DFW.dll @ 0x0000000002E00000)
00000000031B46D4 : TView::ReadSubViews + 0x00000000000002D4 (DFW.dll @ 0x0000000002E00000)
00000000031A9CD0 : TView::ReadContainer + 0x0000000000000170 (DFW.dll @ 0x0000000002E00000)
00000000031B8E7B : TViewServer::Reanimate + 0x00000000000001CB (DFW.dll @ 0x0000000002E00000)
00000000031B98A6 : TViewServer::ReadViews + 0x0000000000000156 (DFW.dll @ 0x0000000002E00000)
00000000031B99F5 : TViewServer:oCreateViews + 0x0000000000000095 (DFW.dll @ 0x0000000002E00000)
00000000031B85FD : TViewServer::NewTemplateWindow + 0x000000000000002D (DFW.dll @ 0x0000000002E00000)
0000000017BBD67F : TProToolsDoc::GetProjectNotes + 0x00000000000B3D3F (ProTools_Green.dll @ 0x0000000015730000)
00000000179D806D : TProToolsDoc::GetTrackRange + 0x000000000000BBFD (ProTools_Green.dll @ 0x0000000015730000)
00000000179B6F96 : TPlayListCommand::ClearMIDIRegionDropData + 0x000000000000FB76 (ProTools_Green.dll @ 0x0000000015730000)
000000001667FAE8 : TProToolsDoc::GetDocFileLoc + 0x0000000000006518 (ProTools_Green.dll @ 0x0000000015730000)
000000001667F8DA : TProToolsDoc::GetDocFileLoc + 0x000000000000630A (ProTools_Green.dll @ 0x0000000015730000)
00000000030D6810 : TCommandHandler::PerformCommand + 0x00000000000002E0 (DFW.dll @ 0x0000000002E00000)
00000000030B1090 : TApplication::ProcessEvent + 0x0000000000000080 (DFW.dll @ 0x0000000002E00000)
00000000030B0F36 : TApplication::WakeUp + 0x0000000000000056 (DFW.dll @ 0x0000000002E00000)
00000000030B9F28 : MakeClientBackgroundBrush + 0x0000000000002888 (DFW.dll @ 0x0000000002E00000)
000000000309C42B : DFW_StThreadPollRequest_Suspend::Release + 0x000000000000167B (DFW.dll @ 0x0000000002E00000)
00007FFC2C7F82E1 : DispatchMessageW + 0x0000000000000741 (USER32.dll @ 0x00007FFC2C7E0000)
00007FFC2C7F7DA1 : DispatchMessageW + 0x0000000000000201 (USER32.dll @ 0x00007FFC2C7E0000)
000000000309199C : DFW_EventLoop::RunApplicationEventLoop + 0x00000000000000EC (DFW.dll @ 0x0000000002E00000)
0000000018139F86 : Cmn_Observable<CRegionInstance_Message>::NotifyObs ervers + 0x0000000000035556 (ProTools_Green.dll @ 0x0000000015730000)
0000000018139ED8 : Cmn_Observable<CRegionInstance_Message>::NotifyObs ervers + 0x00000000000354A8 (ProTools_Green.dll @ 0x0000000015730000)
000000001813C6BE : LaunchProTools + 0x000000000000176E (ProTools_Green.dll @ 0x0000000015730000)
000000014002633F : RstE_Session::`vbase destructor' + 0x000000000000813F (ProTools.exe @ 0x0000000140000000)
0000000140027DAE : RstE_Session::`vbase destructor' + 0x0000000000009BAE (ProTools.exe @ 0x0000000140000000)
00000001400180DE : Cmn_AssertException:perator= + 0x000000000000705E (ProTools.exe @ 0x0000000140000000)
000000014084359A : RstE_Session::`vbase destructor' + 0x000000000082539A (ProTools.exe @ 0x0000000140000000)
0000000140F46FEB : RstE_Session::`vbtable' + 0x0000000000510CCB (ProTools.exe @ 0x0000000140000000)
133927.545353,056e8,0e0f: System exception details: Access violation occurred, unable to read location: 0x0000000000000009, Thread: "Main Thread (id=kThreadTableID_MainThread)"
133927.545358,056e8,0e0f: Access Violation: Thread "Main Thread (id=kThreadTableID_MainThread)"
Stacktrace:
00007FFC14185BA2 : DigiTraceStack + 0x0000000000000072 (DigiTrace.dll @ 0x00007FFC14180000)
00007FFB714E7217 : Sys_SEHandlerWin32::StructuredExceptionTranslator + 0x00000000000000E7 (CFnd.dll @ 0x00007FFB71290000)
00007FFC12DD3889 : <No Symbol> 0x00007FFC12DD3889 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD1A64 : <No Symbol> 0x00007FFC12DD1A64 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD194A : <No Symbol> 0x00007FFC12DD194A (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD218F : <No Symbol> 0x00007FFC12DD218F (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD21E9 : <No Symbol> 0x00007FFC12DD21E9 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC12DD4019 : _CxxFrameHandler4 + 0x00000000000000A9 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
0000000003356C14 : TC_Private::Run + 0x00000000000FF884 (DFW.dll @ 0x0000000002E00000)
00007FFC2E8951DF : _chkstk + 0x000000000000012F (ntdll.dll @ 0x00007FFC2E7F0000)
00007FFC2E80E866 : RtlFindCharInUnicodeString + 0x0000000000000A96 (ntdll.dll @ 0x00007FFC2E7F0000)
00007FFC2E844945 : RtlRaiseException + 0x0000000000000195 (ntdll.dll @ 0x00007FFC2E7F0000)
00007FFC2C08FABC : RaiseException + 0x000000000000006C (KERNELBASE.dll @ 0x00007FFC2C030000)
00007FFC12DD2610 : <No Symbol> 0x00007FFC12DD2610 (VCRUNTIME140_1.dll @ 0x00007FFC12DD0000)
00007FFC2E894A26 : RtlCaptureContext2 + 0x00000000000004A6 (ntdll.dll @ 0x00007FFC2E7F0000)
00000000031B98A6 : TViewServer::ReadViews + 0x0000000000000156 (DFW.dll @ 0x0000000002E00000)
00000000031B99F5 : TViewServer:oCreateViews + 0x0000000000000095 (DFW.dll @ 0x0000000002E00000)
00000000031B85FD : TViewServer::NewTemplateWindow + 0x000000000000002D (DFW.dll @ 0x0000000002E00000)
0000000017BBD67F : TProToolsDoc::GetProjectNotes + 0x00000000000B3D3F (ProTools_Green.dll @ 0x0000000015730000)
00000000179D806D : TProToolsDoc::GetTrackRange + 0x000000000000BBFD (ProTools_Green.dll @ 0x0000000015730000)
00000000179B6F96 : TPlayListCommand::ClearMIDIRegionDropData + 0x000000000000FB76 (ProTools_Green.dll @ 0x0000000015730000)
000000001667FAE8 : TProToolsDoc::GetDocFileLoc + 0x0000000000006518 (ProTools_Green.dll @ 0x0000000015730000)
000000001667F8DA : TProToolsDoc::GetDocFileLoc + 0x000000000000630A (ProTools_Green.dll @ 0x0000000015730000)
00000000030D6810 : TCommandHandler::PerformCommand + 0x00000000000002E0 (DFW.dll @ 0x0000000002E00000)
00000000030B1090 : TApplication::ProcessEvent + 0x0000000000000080 (DFW.dll @ 0x0000000002E00000)
00000000030B0F36 : TApplication::WakeUp + 0x0000000000000056 (DFW.dll @ 0x0000000002E00000)
00000000030B9F28 : MakeClientBackgroundBrush + 0x0000000000002888 (DFW.dll @ 0x0000000002E00000)
000000000309C42B : DFW_StThreadPollRequest_Suspend::Release + 0x000000000000167B (DFW.dll @ 0x0000000002E00000)
00007FFC2C7F82E1 : DispatchMessageW + 0x0000000000000741 (USER32.dll @ 0x00007FFC2C7E0000)
00007FFC2C7F7DA1 : DispatchMessageW + 0x0000000000000201 (USER32.dll @ 0x00007FFC2C7E0000)
000000000309199C : DFW_EventLoop::RunApplicationEventLoop + 0x00000000000000EC (DFW.dll @ 0x0000000002E00000)
0000000018139F86 : Cmn_Observable<CRegionInstance_Message>::NotifyObs ervers + 0x0000000000035556 (ProTools_Green.dll @ 0x0000000015730000)
0000000018139ED8 : Cmn_Observable<CRegionInstance_Message>::NotifyObs ervers + 0x00000000000354A8 (ProTools_Green.dll @ 0x0000000015730000)
000000001813C6BE : LaunchProTools + 0x000000000000176E (ProTools_Green.dll @ 0x0000000015730000)
000000014002633F : RstE_Session::`vbase destructor' + 0x000000000000813F (ProTools.exe @ 0x0000000140000000)
0000000140027DAE : RstE_Session::`vbase destructor' + 0x0000000000009BAE (ProTools.exe @ 0x0000000140000000)
00000001400180DE : Cmn_AssertException:perator= + 0x000000000000705E (ProTools.exe @ 0x0000000140000000)
000000014084359A : RstE_Session::`vbase destructor' + 0x000000000082539A (ProTools.exe @ 0x0000000140000000)
0000000140F46FEB : RstE_Session::`vbtable' + 0x0000000000510CCB (ProTools.exe @ 0x0000000140000000)
133927.548280,056e8,0e0f: System exception details: Access violation occurred, unable to read location: 0x0000000000000009, Thread: "Main Thread (id=kThreadTableID_MainThread)"
Reply With Quote
  #23  
Old 09-16-2024, 11:46 PM
tonygoodall tonygoodall is offline
Member
 
Join Date: Jul 2000
Location: uk
Posts: 206
Default Re: Could not create a new document because Access violation occurred, unable to read

I did notice that this time I have not installed the HD Driver.
I have no idea if that makes a difference, and reluctant to tempt fate
Reply With Quote
  #24  
Old 09-16-2024, 11:46 PM
tonygoodall tonygoodall is offline
Member
 
Join Date: Jul 2000
Location: uk
Posts: 206
Default Re: Could not create a new document because Access violation occurred, unable to read

also not sure if installing Protools First and then normal full-fat PT makes a difference
Reply With Quote
  #25  
Old 09-17-2024, 01:18 AM
Darryl Ramm Darryl Ramm is online now
Member
 
Join Date: Nov 2010
Location: USA
Posts: 20,201
Default Re: Could not create a new document because Access violation occurred, unable to read

Quote:
Originally Posted by tonygoodall View Post
I did notice that this time I have not installed the HD Driver.
I have no idea if that makes a difference, and reluctant to tempt fate
Why are you installing the HD driver? That is only for HD Native and HDX Digilink cards/interfaces. If you have installed that mess before run the uninstallers now.

Log files are very handy...

I see mention of WASAPI, I hope you are not using a WASAPI audio device/driver. You should be using an ASIO4ALL driver with your interface. Try stuff with the ASIO device as the playback engine and don't go back to WASAPI (and you also should have Windows sound set to use an entirely different audio device, like the motherboard sound chipset).

So this happens when opening a session not just starting up Pro Tools. So what happens if you start Pro Tools and then create a new empty session (not from template).

I don't have a Windows machine within reach right now to compare logs to but you've got a pile of font errors. Did they also appear when Pro Tools started OK? The log does not identify the fonts missing but just logs an assert so that should not be hard for a developer to track down, or you might be able to just compare the fonts present when this works and when it does not. And then near the top of the crash stack there is unicode string handling routines that might be what is falling over here, maybe it's possible that if unicode characters/fonts are messed up that is causing the crash.

If font errors don't show up when this works OK then they are suspect and maybe you can track down what fonts are actually installed in each config. Since that *might* get into stuff like user %APPDATA% and usual messes there, it's might be worth tracking down where Pro Tools installs custom fonts to on Windows... If you are using a domain controller or have anything unusual there mention it now. I just don't have easy access to a Windows computer running Pro Tools right not. That's if the issue here if there is one at all is custom font's installed by Pro Tools but it might not be, and if it's related to fonts at all maybe you are missing something else, maybe something related to a locale setting or maybe Microsoft has broken something.

Same thing with all the Win32_ReadVersionInfo errors... do they appear in the log when Pro Tools works OK?

But you've got a detailed stack trace here, you should get it over to Avid support. They'll want to grab the crash dumps as well.
Reply With Quote
  #26  
Old 09-17-2024, 03:30 AM
Darryl Ramm Darryl Ramm is online now
Member
 
Join Date: Nov 2010
Location: USA
Posts: 20,201
Default Re: Could not create a new document because Access violation occurred, unable to read

OK and a quick look at a Windows machine with an old Windows 10 install and a fresh Pro Tools 2024.6 install show none of these font errors or Win32_ReadVersionInfo errors and everything starts up fine. Don't have Windows 11 on this system.
Reply With Quote
  #27  
Old 09-17-2024, 09:28 PM
Darryl Ramm Darryl Ramm is online now
Member
 
Join Date: Nov 2010
Location: USA
Posts: 20,201
Default Re: Could not create a new document because Access violation occurred, unable to read

And not sure what I was looking at but there most definitely are SysFileUtils_Win32_ReadVersionInfo errors in a normal startup of Pro Tools 2024.6 on Windows 10:

From my system:

3475.849895,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\JSONSchemaValidator.dll can't be gotten
3475.864517,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\CrashReporter.dll can't be gotten
3475.864966,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\crashpad_glue.dll can't be gotten
3475.897407,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\WINDOWS\SYSTEM32\UMPDC.dll can't be gotten
3475.904364,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\atmos_storage.dll can't be gotten
3475.905545,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\AvOmfToolkit.dll can't be gotten
3475.906186,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\libjpegV4.dll can't be gotten
3475.910151,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\AVX2_Plug-Ins\PXF\PXFPlugin.acf can't be gotten
3475.911447,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\AVX2_Plug-Ins\PXF\xqilla23_vc142_x64_u.dll can't be gotten
3475.918820,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\Program Files\Avid\Pro Tools\PTSL.dll can't be gotten
3475.920962,00528,0e0e: SysFileUtils_Win32_ReadVersionInfo version info of file c:\WINDOWS\SYSTEM32\TextShaping.dll can't be gotten

Now to the font related errors...

Pro Tools includes the Opus family of fonts, they are installed in C:\Windows\Fonts by the installer.

two additional fonts are packaged with Pro Tools under the Pro Tools Help folder. The installer puts links to them in C:\Windows\Fonts.

Deleting those links and all the font files did not stop Pro Tools 2024.6 from starting, and did not produce any font warnings like in your log, so unless I'm missing something else the font errors in your startup are probably pointing to a more systems related problem.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Access violation occurred, unable to read location JasperEads Pro Tools 11 6 10-10-2017 01:16 PM
Access violation occurred, unable to read location: 0x000000003E3FFFBA pm mastering studio Pro Tools 11 17 05-13-2015 02:37 PM
Could not create a new document because Access violation occurred, unable to read loc Mark Frith Pro Tools 11 6 03-26-2015 11:42 PM
Access Violation occurred, unable to read location: 0x00000000? Help! LarrySmileyEL Pro Tools 10 2 12-01-2014 09:03 AM
Access violation occurred, unable to read location: 0x00000000341CFEF2 live4live Pro Tools 11 2 05-28-2014 08:23 AM


All times are GMT -7. The time now is 09:26 PM.


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com