MatLab crashing on Windows 11 Pro during data analysis. Memory leak and insufficient RAM likely not cause of crash. What is the cause of this problem? Log file below:
57 views (last 30 days)
Show older comments
MATLAB Log File: C:\Users\5D1GN34\AppData\Local\Temp\matlab_crash_dump.3536-1
------------------------------------------------
MATLAB Log File
------------------------------------------------
--------------------------------------------------------------------------------
Access violation detected at 2025-01-06 12:01:59 -0500
--------------------------------------------------------------------------------
Configuration:
Crash Decoding : Disabled - No sandbox or build area path
Crash Mode : continue (default)
Default Encoding : UTF-8
Deployed : false
Graphics Driver : Intel Intel(R) UHD Graphics 770 Version 4.5.0 - Build 32.0.101.6078
Graphics card 1 : Intel Corporation ( 0x8086 ) Intel(R) UHD Graphics 770 Version 32.0.101.6078 (2024-9-13)
Java Version : Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
MATLAB Architecture : win64
MATLAB Entitlement ID : 11489718
MATLAB Root : C:\Program Files\MATLAB\R2024a
MATLAB Version : 24.1.0.2689473 (R2024a) Update 6
OpenGL : hardware
Operating System : Microsoft Windows 11 Pro
Process ID : 3536
Processor ID : x86 Family 6 Model 183 Stepping 1, GenuineIntel
Session Key : 8637783e-410b-4785-aca1-370d21a228d6
Window System : Version 10.0 (Build 22631)
Fault Count: 1
Abnormal termination:
Access violation
Current Thread: 'MCR 0 interpreter thread' id 21816
Register State (from fault):
RAX = 00007ffa9a9d9a91 RBX = 000000f1723f7eb8
RCX = 38738b49306b8b49 RDX = 000000f1723f7e48
RSP = 000000f1723f7e08 RBP = 0000000000000001
RSI = 0000000000000001 RDI = 0000000000000018
R8 = 0000000000000000 R9 = 0000000000000001
R10 = 00007ffb2de00000 R11 = 000000f1723f7da0
R12 = 000002b22d910c10 R13 = 000000f1723f83f8
R14 = 000002b3fc1fb4a0 R15 = 0000000000000001
RIP = 00007ffa92586357 EFL = 00010246
CS = 0033 FS = 0053 GS = 002b
Stack Trace (from fault):
[ 0] 0x00007ffa92586357 C:\Program Files\MATLAB\R2024a\bin\win64\libmwir.dll+00090967 MathWorks::ts::Type::GetOperandAsType+00000007
[ 1] 0x00007ffa92466905 C:\Program Files\MATLAB\R2024a\bin\win64\libmwlxetypes.dll+00026885 MathWorks::lxe::xvalue::~xvalue+00000037
[ 2] 0x00007ffa92f802ca C:\Program Files\MATLAB\R2024a\bin\win64\m_lxe.dll+06357706 MathWorks::lxe::function_handle::invoke+00000506
[ 3] 0x0000000000000001 <unknown-module>+00000000
[ 4] 0x000000f1723f7f20 <unknown-module>+00000000
[ 5] 0x000002b22d910c10 <unknown-module>+00000000
1 Comment
Walter Roberson
on 8 Jan 2025
That traceback looks really short to me, as if MATLAB had barely started up, instead of being generated part-way through a calculation.
Answers (1)
Image Analyst
on 8 Jan 2025
MATLAB crashes create a crash dump file (like the one you listed). I believe those files are automatically sent to the Mathworks, though you may have to approve the transmission to them. Once they get the crash dump file, they will respond by email. Unfortunately (in my case) you usually get that it was caused by an unknown issue.
If you want, you can upload your data and source code files here, and any other required files (such as data files or DLLs), and see if any of us can reproduce the crash.
Does your data analysis depend on any custom binary files, such as a DLL?
If you want immediate help, you can call them on the telephone and ask for technical support, though I'd first try to upgrade to R2024b first to see if that solves the problem.
If you're doing telephone support, they will first ask if they can drive your computer remotely to observe the problem. If they can't fix it then, then they will ask you to send all required files to them for them to investigate offline, and then they'll get back to you with the results of their investigation
0 Comments
See Also
Categories
Find more on Startup and Shutdown in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!