Here are the settings that I commonly use.

I can not give you much more than I already have as Vegas die's without warning and without error code information.

Another BUG is loosing sound untill I reboot Vegas, this hapens when I adjust clips on the timeline.

These problems should just not exsist, selling this faulty programme is really bad marketing.

Below are my common settings that I use.

The version is 361

First I would change Pixel Format to 8-bit.

Plea to New Users -- Please Do Not set 32 Bit Pixel Format

@chris-minchin If after changing the to 8 bit as @matthias-krutz suggest, you can also change the 'GPU acceleration of video processing' to 'Off' (Preferences > Video tab). That will not be optimum for certain FX's, but it will make for a good test to determine if perhaps your GPU needs a different driver (either updated or previous).

Is their a particular reason to changed the pixel format to 32 bit floating? For most production this is not of benefit as expressed in the link @matthias-krutz provided.

@chris-minchin

Also use MEDIAINFO for details of the footage you are using please.

General
Complete name                            : C:\Users\User\Desktop\AEROCONTIKI\C0001.MP4
Format                                   : XAVC
Codec ID                                 : XAVC (XAVC/mp42/iso2)
File size                                : 230 MiB
Duration                                 : 36 s 960 ms
Overall bit rate mode                    : Variable
Overall bit rate                         : 52.3 Mb/s
Encoded date                             : UTC 2019-02-07 02:13:13
Tagged date                              : UTC 2019-02-07 02:13:13

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.2
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, RefFrames               : 2 frames
Format settings, GOP                     : M=1, N=12
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 36 s 960 ms
Bit rate mode                            : Variable
Bit rate                                 : 50.3 Mb/s
Maximum bit rate                         : 60.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 50.000 FPS
Standard                                 : PAL
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.485
Stream size                              : 222 MiB (96%)
Encoded date                             : UTC 2019-02-07 02:13:13
Tagged date                              : UTC 2019-02-07 02:13:13
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : xvYCC
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Big / Signed
Codec ID                                 : twos
Duration                                 : 36 s 960 ms
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 6.77 MiB (3%)
Encoded date                             : UTC 2019-02-07 02:13:13
Tagged date                              : UTC 2019-02-07 02:13:13

Other
Type                                     : meta
Duration                                 : 36 s 960 ms

The problem occurs when I move video clips or sound clips on the timeline, (but hey is that what the program is supposed to do!!!)

When the programe crashes I get a hourglass and the screen goes transparent white and will stay like this until I shut it down.

That is not normal behaviour of the program.
Nothing wrong with your file and nothing wrong with some move of an event ( as we call in this program a clip on the timeline)

On the laptop from signature those kind of files and haviour ones behave normal and play without a bunch of effects mostly in preview/full. So something has to be wrong with your file or your setup and/or settings.

To show you how it normally behaves in this program I will try it for you and give you a screenvideo of it, but therefore I need a short problemfile you have to give through a dropbox option or so, because it must not be changed by any website.

There is no warning or data dump file after it crashes and it does not reopen with my changes. All pretty bad!!

That is your own fault because the program has more than one possibilities to store your changes, f.i "the Advanced Save...." options in the menu Tools

That is your own fault because the program has more than one possibilities to store your changes, f.i "the Advanced Save...." options in the menu Tools

What I was referring to here was that Vegas has in the past when it has crashed displayed a form that says that Vegas has crashed, it also gives the option to "tick a box " to send the info back to Magix. This is not happening now.

I have set the advanced save option now, but before it seemed more stable therefore unnecessary.

Now I read your reaction I only want trying to help you, if you withdraw your ranting and warnings about Vegas Pro 16 because it is the best they ever made.
Besides that: Probably try to learn first how to handle and react on a decent way this user forum with its good options to store and react.😛

@chris-minchin did setting the pixel format to 8 bit and turning off GPU acceleration makes any change?

You may also want to reset Vegas Pro to it's original default installation settings, while holding down the 'Ctrl+Shift' keys, double left click on the Vegas Pro desktop shortcut and then click on 'Yes'. The default settings work on like 99% of the systems. Maybe something got twisted around as you were working on a solution.

It sounds like you are frustrated and I understand that. However, when you (and others here help you) find a solution and get this all worked out, you will probably find Vegas Pro stable and working properly.

Agreed. No need for 32 bit mode with 8 bit 420 footage. This is going to turn out to be a configuration or hardware issue. What is your audio interface? Any unusual hardware installed?

Also, footage looks normal, but what camera/device is it from?

OK, my camera is a Sony A77 mkii and that is what I use now, but the same problem happens with older footage from my Sanyo 1080i footage.

I have reset to 8 bit and reset GPU accereration to none, not sure what else I can do.

@chris-minchin are you new to Vegas Pro? As in, you haven't used any other version than this Vegas Pro 16? And, if so, it has never worked from the very start? If that is correct and you have done a reset, I agree with @Kinvermark this is most likely something in your system that does not agree with Vegas. Could be a driver or configuration of your GPU and perhaps something you have plugged into your system. Anything like a keyboard interface other than a standard keyboard, or anything else in your system that would be out of the norm, or most users would not need?

Also, @chris-minchin if you are new to Vegas, what was you using before?

I
have been using Sony Movie Studio going back for 15 years or so, I am not a
"Newbie" and to reiterate, Magix should NOT put out software that is
full of BUGS, I am a software developer and have written many packages over my
working life.

The fact that I got an error that was not "Error
trapped" shows a lack of discipline by the developers, and is very bad
practice.

While I appreciate the constructive help I cannot and will not
reverse my prior comments.

@chris-minchin I wasn't poking at your expertise but rather attempting to determine if you have had other NLE's working on your current box with success. I hope you to not read anything into my questions, they are asked to help you to determine what may be the cause. I have no desire to shape your opinion of the software, nor do your comments change mine, just an honest and earnest attempt to be productive.

So you did not have these issue using Sony Movie Studio on your current PC, is that correct?

I understand your position, maybe I too would feel the same as you had it not
been blatantly obvious to me that there are serious unaddressed flaws in Vegas
pro 16, it maybe the best version yet, but by my estimation they have a long way
to go to sort it out.

Movie Studio worked fairly well for me, with few crashes, but it
is of course much less useful for the type of projects that I am working on
now.

In the meantime I have taken on board and made the changes that
have been suggested and will see if I have less crashes.

Yes I am very disappointed in Vegas and angry that these issues
are unresolved, but will continue trying for now.

Thanks to everyone for their ideas.

@chris-minchin good luck for it.

Thanks :)

if you withdraw your ranting and warnings about Vegas Pro 16 because it is the best they ever made.

That is a bold statement and one I cant not agree with and many users will have different opinion too.

@chris-minchin

Whatever your claimed technical expertise, you are basing your opinion (and erroneous conclusions) on a sample size of one. The sooner you accept that your experience with Vegas is not universal, the closer you will be to a solution. If you actually get to work troubleshooting the issues you will likely get to the root of the problem - but some effort will be required. I suggest you try a different PC. Surely you know someone local who can help?

Kinvermark,
is showing his ignorance and unreserved support for a product that cannot be
defended given the facts.

To put it in simple terms: if an application terminates unexpectedly
it is not seeing the error because the programmer has not error trapped adequately.
Therefore the application freezes or shuts down.

This is sloppy programming!!