Skip to main content
perh15839954
perh15839954
Participant
December 12, 2024
Answered

Premiere Elements 2025 crash when two monitors

  • December 12, 2024
  • 1 reply
  • 773 views

Installed 2025 yesterday - so far very pleased with the new interface! But one thing:

I use two monitors, say 1 and 2, and tried the feature of having the Program Monitor on one screen and the rest (timeline etc) on the other. 

If I have the timeline on screen 1 and the Program monitor on screen 2 - it works fine.

If I have the timeline on 2 and the Program monitor on 1 my PC suddenly restart... 

I have reproduced this twice - have anyone else experienced this?

 

Here's some info on my PC (in Swedish):

Enhetsnamn Lenovo
Processor AMD Ryzen 9 6900HX with Radeon Graphics 3.30 GHz
Installerat RAM-minne 32,0 GB (31,2 GB går att använda)
Enhets-ID 85C7BD2F-709D-4112-81F3-183C76936F79
Produkt-ID 00325-80000-00000-AAOEM
Systemtyp 64-bitars operativsystem, x64-baserad processor
Windows 11 Home
Version 23H2
Installerad ‎2023-‎04-‎27
OS-version 22631.4602


This topic has been closed for replies.
Correct answer Ann Bens

Not seeing this on my system: could be a graphics card issue.

Make sure you have the most current driver installed.

Your OS needs updating.

1 reply

Ann Bens
Community Expert
Ann BensCommunity ExpertCorrect answer
Community Expert
December 12, 2024

Not seeing this on my system: could be a graphics card issue.

Make sure you have the most current driver installed.

Your OS needs updating.

perh15839954
perh15839954Author
Participant
December 12, 2024

Thanks for quick answer!

 

I can add that I have no problems running PrEl 2024 on two monitors.

 

I notice that the dates on my Windows system seem old, but when my Premiere crashed the first time yesterday it triggered a reboot, which automatically installed the latest cumulative pack from Windows, so it should be uptodate. The second crash was obviously after the Windows upgrade. I will check for new graphics drivers.

perh15839954
perh15839954Author
Participant
December 12, 2024

OK - there was actually an update for the NVIDIA card... After upgrading I have not been able to reproduce the error (yet) so it seems to have been a driver issue (again).

(To my defense I can mention that I subscribe to a Norton service that promise to keep all my drivers uptodate automatically, so I thought everything was fine. Obviously they can't handle graphic cards... Disappointing, but now I know I have to check myself).

 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices