Is there a way to see what is crashing a SPLAT project?

Author
Post
Essentials Only Full Version
LJB
Max Output Level: -60 dBFS
  • Total Posts : 1502
  • Joined: 2009/07/29 10:31:31
  • Location: South Africa
  • Status: offline
2018/03/15 10:32:06 (permalink)

Is there a way to see what is crashing a SPLAT project?

I've just rebuilt my entire C Drive and I can swop between my old and new C drives on boot. I would prefer to work on the new install though. Both drives run Win 10x64 Pro, with SPLAT Producer latest x 64.

However, any project that had any real mix work done to it just won't launch in my new SPLAT and simply gives the "Windows has encountered a problem" message. No indication of what is crashing it. Is there any log file or something I can access to see what's causing this?

Thanks in advance!

Ludwig Bouwer, One Big Room Studios.
--------------------
Cakewalk with all the trimmings / Win 10Pro 64 / Intel i7-7700 / Asus Prime Z270k / 16GB DDR4 / RME HDSP9652 / RME UFX / Black Lion Audio ADA8000 / ART MPA & ART Pro Channel / Focusrite Voicemaster Pro / Aphex 107

Check out my work at www.onebigroom.co.za
#1

5 Replies Related Threads
    DeeringAmps
    Max Output Level: -49 dBFS
    • Total Posts : 2614
    • Joined: 2005/10/03 10:29:25
    • Location: Seattle area
    • Status: offline
    Re: Is there a way to see what is crashing a SPLAT project? 2018/03/15 12:31:15 (permalink)
    Have you tried loading the project in "safe" mode? Hold down the shift key.
    Sounds like a plugin is the problem.
    Something that is a go-to? And its not registered correctly on the new drive?
    T

    Tom Deering
    Tascam FW-1884 User Resources Page
    Firewire "Legacy" Tutorial, Service Manual, Schematic, and Service Bulletins

    Win10x64
    StudioCat Pro Studio Coffee Lake 8086k 32gb RAM

    RME UFX (Audio)
    Tascam FW-1884 (Control) in Win 10x64 Pro
    #2
    chuckebaby
    Max Output Level: 0 dBFS
    • Total Posts : 13146
    • Joined: 2011/01/04 14:55:28
    • Status: offline
    Re: Is there a way to see what is crashing a SPLAT project? 2018/03/15 12:35:25 (permalink)
    How did you rebuild this new C drive ?
    Did you leave Windows installed on your old C Drive ?
     
    I would try safe mode as well. At least you can rule out that as a potential problem. However, the message "Windows has encountered a problem" is not something you typically see with a plug in problem. I don't know maybe it is.

    Windows 8.1 X64 Sonar Platinum x64
    Custom built: Asrock z97 1150 - Intel I7 4790k - 16GB corsair DDR3 1600 - PNY SSD 220GB
    Focusrite Saffire 18I8 - Mackie Control
       
    #3
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re: Is there a way to see what is crashing a SPLAT project? 2018/03/15 16:45:47 (permalink)
    One thing that really help me with my recent re build was to download and install the C++ library from Microsoft. Windows update doesn't always grab it. I was having issues and posted a quetion and someone pointed this out to me. I'll see if I can find the thread.
     

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #4
    Cactus Music
    Max Output Level: 0 dBFS
    • Total Posts : 8424
    • Joined: 2004/02/09 21:34:04
    • Status: offline
    Re: Is there a way to see what is crashing a SPLAT project? 2018/03/15 16:47:47 (permalink)
    Here's the link 
     
    https://www.microsoft.com/en-us/download/details.aspx?id=40784

     

    Johnny V  
    Cakelab  
    Focusrite 6i61st - Tascam us1641. 
    3 Desktops and 3 Laptops W7 and W10
     http://www.cactusmusic.ca/
     
     
    #5
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re: Is there a way to see what is crashing a SPLAT project? 2018/03/16 18:49:30 (permalink)
    Start with Windows Event Viewer. Sometimes, that's all you need to identify which component is causing the crash.
     
    You can also use the Windows Debugger. It's a little more obtuse, but I posted some basic instructions for its use in this old thread from 2014.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #6
    Jump to:
    © 2024 APG vNext Commercial Version 5.1