I’ve played this game before the Lazertag update and everything ran fine. Nowadays this game will crash my computer after 10 minutes making me have to reset it. I’m running the game on it’s lowest settings and limited the framerate down to 30. No matter what I’ve tried the results have been the same. TU is the only game on steam that has this issue.
[0615/212011:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0615/212011:WARNING:channel.cc(359)] RawChannel write error
[0617/213200:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/213202:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/213202:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/213204:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214751:WARNING:ipc_channel_win.cc(370)] Unable to create pipe “\.\pipe\chrome.4044.7.23437735” in client mode: The system cannot find the file specified. (0x2)
[0617/214751:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214751:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214752:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214752:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214755:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214757:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214759:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214801:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214801:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0617/214801:WARNING:channel.cc(359)] RawChannel write error
[0617/214801:ERROR:ipc_channel_win.cc(217)] pipe error: 109
[0617/214802:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214802:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214802:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0617/214802:ERROR:ipc_channel_win.cc(512)] pipe error: 232
[0617/214802:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214803:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214803:ERROR:ipc_channel_win.cc(512)] pipe error: 232
[0617/214803:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0617/214803:ERROR:ipc_channel_win.cc(512)] pipe error: 232
[0617/214803:ERROR:ipc_channel_win.cc(512)] pipe error: 232
[0617/214803:ERROR:ipc_channel_win.cc(217)] pipe error: 109
[0617/214809:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214809:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214809:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0617/214809:WARNING:channel.cc(359)] RawChannel write error
[0617/214834:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214855:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0617/214855:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0617/214855:WARNING:channel.cc(359)] RawChannel write error
[0704/151334:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0704/151508:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0704/151508:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0704/151508:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0704/151508:WARNING:raw_channel_win.cc(532)] WriteFile: The pipe is being closed. (0xE8)
[0704/151510:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0704/151615:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0704/151615:WARNING:audio_sync_reader.cc(112)] AudioSyncReader::Read timed out, audio glitch count=1
[0704/151615:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
[0704/161822:WARNING:raw_channel.cc(208)] Shutting down RawChannel with write buffer nonempty
I (like many people here I’d assume) would love advice soon
Back when I was adjusting voltage and clock speeds for overclocking my CPU, besides Intel Burn Test and prime95, I used Tower Unite for practical gaming tests because it stresses my components so much compared to other demanding games.
So this could be another case where your computer is not properly built or configured for high-resource usage.
What is the actual type of your computer’s crash exactly? Is it blue screen? If so, what does the error message say?
Is your CPU overclocked? What are your specs for your PSU (power supply)?
Your CPU might be overheating, but I need more details to help you on this one.
You can try updating your graphics drivers if they aren’t up to date, verifying game integrity, or just flatout reinstalling the game through a clean install - meaning finding instructions to clear out all TU files.
Also, looking for that “RawChannel with write buffer…” problem I found a bunch of emulation problems, that is if you are emulating Windows OS to play this game.
Very weird question, are you playing TU with a emulated Windows OS on a Mac? I found a thread saying Wine’s Mac driver isn’t supposed to support an emulated desktop.
Another potential fix, if you’re on Ubuntu, is to update some libraries and graphics drivers.
Thank you all for responding. My computer isn’t emulating Windows nor is it Mac or Ubuntu. If anything I just have to see if my card does need a driver update. As for what crashes happen: Both of my monitors go black and I can hear the sounds of my fans going wild. So I think it’s safe to assume that the game overheats my computer.This is one of the few games where I can hear my computer fans much easier because of how loud it is.
Like I mentioned in the original response, your CPU might be overheating. If you have never experienced this issue before and your PC is fairly dated (since you’re still on Windows 7), there are a few possible causes:
Thermal paste dried out, breaking its contact.
Thermal paste was originally poorly applied, resulting a bad contact issue under heavy load (there are not many general use applications/games I know that stresses as much as TU).
Your CPU is dying.
Sudden crash with no BSOD could also mean your PSU (power supply) is dying.
Let’s assume it has to do with your CPU overheating. When did you last apply the thermal paste? Was an experienced PC builder involved?
When did you buy the CPU, or the PC if it was prebuilt?
@ilipitagaon
I built my computer over two years ago. Back then my CPU had that preinstalled thermal paste so the paste drying out wouldn’t be out of the question.
I do reapply my thermal paste every 2 years, although the general advice is to reapply every year. Honestly, I’ve never had a case where the thermal paste dried out personally (one of my OC’d rig runs 24/7), but it does happen to many others fairly often.
I would download a program called prime95, and let it run for about 10 minutes while monitoring the temperature. If your PC crashes while having a very high temperature it’s definitely overheating.
A CPU suddenly starts overheating on a rig that you’ve been using just fine for a long time when:
Thermal paste misapplied or dried out.
You’ve added more HDDs or other heat-generating components. Do not underestimate this. You need more fans for this.
Bad air circulation. Dusts built up on your filters in your case or your coolers (CPU, GPU). Cleaning out will improve the circulation. Check rear, front, top and bottom and clean them out. Decent computer cases make it very easy to clean them.
A slowly dying CPU. Consumer level computer parts degrade relatively fast. Keep running at a high temperature would cause it to accelerate the process. If this has happened, usually giving them more voltage does the job, but in a couple of years it would be wise to just switch to a new CPU. If a CPU requires more voltage, it usually throttles hard to the point where the watchdog will throw a blue screen of death so I highly doubt this is your issue.
