@CubeAce

Hi Ray,

Quickly looking at your referenced thread, it was about what I created as Bug059, not the crashing issue that I have shown here. I just said that maybe the two are related, but this is different.

Please test what I show here.

John CB

@browj2

Hi John.

Have checked in VPX 14 and no, I can't replicate a crash on my system. I too am still using Win 10 but the Enterprise version.

Ray.

@CubeAce

Hi Ray,

Thanks for checking.

Watch this:

Is that what you did?

Thanks,

John CB

@browj2

Hi John

Like @CubeAce I cannot replicate the crashing in VPX 14 or MMS - both patched up to date.

Did you have a look at the perfmon reliability report to see if anything was logged there?

John EB

Crash and burn here (MMS 2023).

Tried to send the crash log, "can't, you may not be connected to the Internet". Yeh right.

Tried to display crash log: nothing happened.

👺

@AAProds

Hi Al,

Thanks for testing. I'm disappointed but relieved that someone else has the same problem.

@johnebaker

Hi John,

Here is the error message:

and the log:

----------------------------------------------------------------------
MAGIX Video Pro X14  04.06.2023  14:30
----------------------------------------------------------------------
CrashDump 20230604_143030_v20.0.3.181.dmp successfully written

Error in module "video_pro_x.exe" (Load address: 0x0000000140000000) to address 0x00000001400C0EB0 (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 000052f4)
  00000001400c0ea8   ba 3b 00 00 00 48 8b cf 
  00000001400c0eb0 > ff 90 d0 07 00 00 48 85 
  00000001400c0eb8   c0 74 29 80 bc 24 80 00 

video_pro_x.exe    06.03.2023  17:22      247909e0

Call stack:
Address   Frame
00000001400C0EB0  000000000014C310  QWinWidget::trUtf8+22D10
00000001400B7BD2  000000000014C340  QWinWidget::trUtf8+19A32
00000001400B7EB4  000000000014C370  QWinWidget::trUtf8+19D14
00007FFDFB2385CB  000000000014C580  MxQt::QObject::event+BB
00007FFE002549A0  000000000014C5B0  MxQt::QApplicationPrivate::notify_helper+110
00007FFE00253A23  000000000014CAF0  MxQt::QApplication::notify+18B3
00007FFDFB211B9A  000000000014CB60  MxQt::QCoreApplication::notifyInternal2+BA
00007FFDFB213915  000000000014CC20  MxQt::QCoreApplicationPrivate::sendPostedEvents+215
00007FFE6978377F  000000000014CC28  0001:0006277F C:\Program Files\MAGIX\Video Pro X14\Qt\Qt_x64\platforms\qwindows.dll
0000000050E4A950  000000000014CC30  0000:00000000 
0000000100000000  000000000014CC38  0000:00000000 C:\Program Files\MAGIX\Video Pro X14\video_pro_x.exe
0000000000603C70  000000000014CC40  0000:00000000 
00000000146E0C60  000000000014CC48  0000:00000000 

----------------------------------------------------------------------
MAGIX Video Pro X14  05.06.2023  10:23
----------------------------------------------------------------------
CrashDump 20230605_102329_v20.0.3.181.dmp successfully written

Error in module "(null)" (Load address: 0xFFFFFFFFFFFFFFFF) to address 0xFFFFFFFFFFCFFD6C (Exception 0xc0000005 "ACCESS_VIOLATION")

Main Thread   (ThreadID: 00006960)
  ffffffffffcffd64   ?? ?? ?? ?? ?? ?? ?? ?? 
  ffffffffffcffd6c > ?? ?? ?? ?? ?? ?? ?? ?? 
  ffffffffffcffd74   ?? ?? ?? ?? ?? ?? ?? ?? 

video_pro_x.exe    06.03.2023  17:22      247909e0

Call stack:
Address   Frame
FFFFFFFFFFCFFD6C  000000000014C290  0000:00000000 
00000001400C0EB6  000000000014C310  QWinWidget::trUtf8+22D16
00000001400B7BD2  000000000014C340  QWinWidget::trUtf8+19A32
00000001400B7EB4  000000000014C370  QWinWidget::trUtf8+19D14
00007FFDFD9B85CB  000000000014C580  MxQt::QObject::event+BB
00007FFDFF9349A0  000000000014C5B0  MxQt::QApplicationPrivate::notify_helper+110
00007FFDFF933A23  000000000014CAF0  MxQt::QApplication::notify+18B3
00007FFDFD991B9A  000000000014CB60  MxQt::QCoreApplication::notifyInternal2+BA
00007FFDFD993915  000000000014CC20  MxQt::QCoreApplicationPrivate::sendPostedEvents+215
00007FFE27EE377F  000000000014CC28  0001:0006277F C:\Program Files\MAGIX\Video Pro X14\Qt\Qt_x64\platforms\qwindows.dll
0000000015AA01D0  000000000014CC30  0000:00000000 
0000000100000000  000000000014CC38  0000:00000000 C:\Program Files\MAGIX\Video Pro X14\video_pro_x.exe
000000000061D700  000000000014CC40  0000:00000000 
000000009709D410  000000000014CC48  0000:00000000 
 

John CB

@browj2

Hi John

I have removed a lot of the superfluous info from the crash log - did the Reliability Monitor ( perfmon / rel ) crash analysis method I linked to not give any details re the crashing?

Have you run a SFC check on your Windows installation?

John EB

@johnebaker

Hi John EB,

I just made a crash with VPX and then ran perfmon. Nothing shows.

Ran sfc /verifyonly

What to do now?

Thanks,

John CB

@browj2

Hi John

. . . . What to do now? . . . .

I would suggest, as SFC found issues, run it again to try to fix the issues it found. If that does not fix the problem then do a full system checkup, and also check drivers, GPU in particular, are up to date.

If the problem persists raise a Support ticket.

John EB

@browj2 @AAProds

Hi John, Al.

No I can't replicate the problem although you two have one thing in common. You are both using a version of the nvidia 3060. See if rolling back the latest nvidia driver does anything.

Ray.

@johnebaker

Hi John EB,

I have now done a sfc /scannow which says that many things were repaired. Rebooted, tried VPX, same error as I described.

BTW, I'm on Windows 10.22H2.

@CubeAce

Hi Ray,

You are both using a version of the nvidia 3060. See if rolling back the latest nvidia driver does anything.

I doubt that as my laptop does not have a separate graphics card, but I get the error with VPX.

For both you and John EB, did you do exactly as I showed in the video - clicked on one, then clicked on the other with nothing selected and with the first window, FX, open and doing nothing then clicking on the Mastering button? That is, without first closing the FX window?

John CB

@browj2 @johnebaker @AAProds

Hi John.

I have tried every which way I can think of John, including your examples.

Have you tried removing your additional, not Magix supplied vst's? Maybe one of those is setting it off. Do you have both 64 and 32 bit versions sitting on your computers? What about background apps? Last but not least make sure your Windows audio is set to use only 24 bit or less and 48kHz or less on all inputs and outputs.(including any that may be set to hidden such as the stereo mix.) Some vsts do not work well at higher sample rates and can cause crashes. Windows can often choose the highest sample and bit depths your inboard sound chip can use regardless of whatever other audio units you have using the system. I have known Windows updates to reset audio settings.

Ray.

Just tried my System 2 with MMS 2023: crashed as described by @browj2.

Yep same here, Mixer - FX - Mastering = crash

@browj2

Hi John

Finally managed to get a crash on my PC, have sent crash log to Magix and linked to the this topic.

Work around is to close dialogs before switching.

John EB

@Antiguo usuario

Thanks for checking and confirming.

@johnebaker

Hi John EB,

Thanks for going back, checking again, and sending it in.

I will send it in mentioning the other bugs with the Master strip.

@CubeAce

Hi Ray,

I don't see VST's being the problem. None are loaded into the Mixer, only scanned upon start up. I have almost none on my laptop. Even then, the crash should not happen.

John CB