Tiger touch crash

[brian]

Tiger touch crash twice while running a live show, board running version 5 Titan software

[icke_siegen]

Please be in touch with your local Avo hero, or with repairs@avolites.com.

Please provide as many informations as possible:
- run the log collector, and have the resulting zip ready to send
- same with the current showfile
- please give information about connected peripherals, like: second screen, mouse, network, USB devices, MIDI
- if at all possible: can you try to describe under which condition the crash happened (what did you do in that moment)? How exactly did the crash appear? If the desk just went off, or showed a bluescreen, then it's likely a hardware thing. Or did just the software hang, wasn't responsive?

Generally: SORRY for the crash, Avolites will do whatever possible to prevent this. So, your detailled feedback is of high value.

[brian]

well at the moment im not in front of the console and will not be in front the console till tomorrow, so i will have the log and the show file for you tomorrow. the only thing i had connected to the console at the time of crash were 2 dmx lines nothing else, rite before the crash the board hangs for like 2 seconds and when i touch the touchscreen i get a blue screen, this exact same thing happened twice so i had to do a hard restart, but wen i restart i get the first boot up screen and it hangs there with the harddrive light remaining solid. i have to switch off the power for bout 15 seconds for it to boot up properly.

[niclights]

Blue screen definitely suggests a driver or hardware level fault rather than Titan. Event Viewer logs might give some clues if you wanted to look yourself. These are included in the log collection (along with showfiles).

Regarding the restart I would suggest that it had not hung but Windows was running a diskcheck following an unexpected shutdown. The 15 secs won't have been relevant but somehow you probably eventually got it into a state where didn't run the check.

Personally I'd run a recovery disk after collecting logs in case you had some sort of driver corruption.

[brian]

when i restarted it hangs at the POST ( power-on-self-test )

[niclights]

Then I reckon this must be a hardware problem. It might be as simple as something coming loose. I'd definitely contact service tomorrow.

[brian]

i definitely think something went loose because i opened up the console and made sure all connectors were connected securely, since that everything seems to work fine, i hope its OK now because i have a huge show at the end of the month and it will be a shame to go back to the high end systems road hog.

[niclights]

That would be a shame!

Another possibility might be power supply, either faulty PSU or local mains. Was there anything unusual about supply where you had the problem? Was it somewhere you work regularly or somewhere new?

[brian]

i always run my boards on a ups! what exactly am i looking for in the logs though?

[icke_siegen]

Searching the logs is somewhat like needle and haystack, but usually the only chance...

More to give you an impression, since it's hardware, start looking in the Windows Event Logs. But I guess you'll just get a very slight impression about how Windows is busy in the background. I'd say in your case (Blue Screen) there is a good chance nothing's showing up in the logs. Bluescreen means: the inner circle, the Sacro Sanctum, has died, and usually this also prevents writing the very fact into the logs.

[niclights]

I agree, the logs probably won't be very helpful.

UPS is useful. Hopefully that eliminates external factors. Regarding internal connections I would specifically check everything on the motherboard - ie. memory, power connections etc. and HDD power/data. I think it's unlikely any of the Usb bits could cause blue screen or halt at POST.