Windows 8.1 Crashing

[mj77]

Hi , it's the same problem , with PT 11.1 / win 8.1 pro 64 bit :

1.When session is blank , quitting with no problem. but ..
2. When session has a couple of VI's (NI Battery 4 & Kontakt 5) and some plu ins ( iZotope's ozone 5 on the mastering , with Nomad Factory's MagneticII & cosmic) the session plays well , exports fine , but when quitting PT , it crashes.

Note : also the same Elastic Audio problem from the 11.0.2 , even when applying the same solution for the EA problem.

my CPU is AMD Phenom II x6 1090T / 8GB ram , 3 separate HDDs , Gigabyte Mobo ,ATI Firepro 3d graphics.
I hope that this problem get's to an end very soon , I really don't get how such industry standard DAW has such stupid bugs in it.

[notedmusic]

Originally Posted by The Weed

11.1 works fine for me on Windows 8.1 Pro. Have you done ALL of the optimizations?

Cheers,

All optimized.

As I mentioned in another thread- autosave is totally destroyed.
It crashes extremely frequently.

I'd daresay 9/10 times- oh man, oh man. Not good. Not good at all.
Fresh Win install.

[notedmusic]

Originally Posted by mj77

Hi , it's the same problem , with PT 11.1 / win 8.1 pro 64 bit :

1.When session is blank , quitting with no problem. but ..
2. When session has a couple of VI's (NI Battery 4 & Kontakt 5) and some plu ins ( iZotope's ozone 5 on the mastering , with Nomad Factory's MagneticII & cosmic) the session plays well , exports fine , but when quitting PT , it crashes.

Note : also the same Elastic Audio problem from the 11.0.2 , even when applying the same solution for the EA problem.

my CPU is AMD Phenom II x6 1090T / 8GB ram , 3 separate HDDs , Gigabyte Mobo ,ATI Firepro 3d graphics.
I hope that this problem get's to an end very soon , I really don't get how such industry standard DAW has such stupid bugs in it.

Yeah I'm with you. Avid please... fix it- like yesterday.

Lol but at least you can save your sessions...

P.S. I think ADMIN mode changes file locations (?)
When I run it without ADMIN I do not have the elastic audio issue provided I use the EA fix.

[notedmusic]

Originally Posted by Bob Olhsson

The Read Me for 11.1.1 says that it supports 8.1!

Well. I don't think that's the case because it won't save my files.
Once I can make music again I'll say it supports windows 8 lol

[notedmusic]

Originally Posted by Darryl Ramm

And not that this helps directly, but compatibility mode is quite different than real Windows 7 running on a real physical PC, its using a hypervisor/vitualization technology, and many physical devices are not directly accessible etc... all the last thing you want to run a DAW in. Just not worth worrying about.

---

So but the main question with Pro Tool crashing would be.. what exact crash report do you get (past detail here from the Windows Error report message) and what happens if you remove *all* third party plugins from Pro Tools? (physically move the file out of the AAX folder and restart)... this should be one of the first tests you do with any Pro Tools crashing or other instability/memory leak/CPU burn problems. Folks are reporting simmialr problems to what you are seeing and, many times it does appear to be plugin related. if removing all the plugins fixes the problem, then put them back in batches until you can find the offending plugin.


---

BTW the WD20EARS-00MVWB0 drive you have is a WDC Caviar Green drive, these are just toxic for Pro Tools audio file use. You just have "Archives" on it so hopefully you are not using for an actual audio/session drive.

The crash report is a windows error message:
"Pro Tools application has stopped working."
The green drive is not a session drive But thank you- good to know!

Ok, I'll try it without anything. But I think that even using XPAND will crash PT.

[notedmusic]

I can upload some crashlogs. :)

I hope someone can make sense of it.

But when I went to upload it said "invalid file type."

How can I upload my DLOG/DMP file?

[Darryl Ramm]

I was not after the Pro Tools log files, I was asking for the Windows Error Reporting crash message.

[notedmusic]

Originally Posted by Darryl Ramm

I was not after the Pro Tools log files, I was asking for the Windows Error Reporting crash message.

There is nothing to say about it. It's a generic "application has stopped working" message.

[Darryl Ramm]

No the system know what happened, at least why the program was killed. Start at the Windows Event Log.

Start here http://www.devopsonwindows.com/sleut...ication-crash/

[notedmusic]

Originally Posted by Darryl Ramm

No the system know what happened, at least why the program was killed. Start at the Windows Event Log.

Start here http://www.devopsonwindows.com/sleut...ication-crash/

Here you go!
Anything useful? (Thanks!)

Event Log:
Faulting application name: ProTools.exe, version: 11.1.1.195, time stamp: 0x52c2bd72
Faulting module name: ntdll.dll, version: 6.3.9600.16408, time stamp: 0x523d5305
Exception code: 0xc0000374
Fault offset: 0x00000000000f387c
Faulting process id: 0x1b64
Faulting application start time: 0x01cf0ea4641aebd7
Faulting application path: C:\Program Files\Avid\Pro Tools\ProTools.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 2b9b4e66-7a9d-11e3-826a-60a44c64accb
Faulting package full name:
Faulting package-relative application ID: