DROWSE Startup Crash Report: Find and Send Your Logs

DROWSE Crashes Before You Can Play? Start Here

A black screen followed by a sudden return to the desktop can stop your night in DROWSE before it begins. Your DROWSE startup crash report gives Milky Coco Games diagnostic files to help investigate that launch failure. To send a DROWSE startup crash report, open %localappdata%\Drowse\Saved\Crashes, compress every crash folder into one ZIP, and email it privately to contact@milkycocogames.com.

That is the developer’s requested next step for the startup problem where the game begins loading, then closes. If the folder is missing or empty, tell the team that instead.

The reported failure follows a specific sequence: launch DROWSE, see a black screen, watch loading begin, and land back on the desktop. Reinstalling, verifying file integrity, and running as administrator had already been tried in that case, with the crash continuing.

If that matches your situation, describe the sequence clearly. “The game won’t run” leaves out the moment that matters; “it starts loading on a black screen, then closes to the desktop” gives the team a much clearer starting point.

What you encounter	What to include in your message
Black screen before the game closes	Describe the black screen and what happens afterward
Loading begins, followed by a desktop crash	Explain that loading starts before the application exits
Crash folders are present	Attach all folders and their contents in one ZIP
Crash location is missing or empty	State which of those outcomes you encountered

You do not need to diagnose the underlying cause yourself. Your job is to capture what happens and deliver the files the developer requested.

Find and Package Your DROWSE Startup Crash Report

The crash folder sits inside your Windows local application data. Use the developer’s direct path to reach it rather than searching through the game’s installation directory.

Open the crash folder

Press Windows + R, paste the following path into the Run box, and press Enter:

%localappdata%\Drowse\Saved\Crashes

Check what opens. The useful distinction is whether you can see crash folders, whether the location opens but contains nothing, or whether Windows cannot open the location.

Keep the folder path exactly as written. You do not need to replace %localappdata% with your Windows username or manually build a longer address.

Include every crash folder

If folders are present inside Crashes, select all of them and compress them into a single ZIP file. Keep every file inside those folders included.

The requested attachment is the complete collection, rather than a screenshot of the directory or one file that looks important. Resist the temptation to choose only the newest folder: the developer specifically asked for all crash folders.

A DROWSE startup crash report is useful here because it preserves diagnostic material from the failure. A written description helps explain your experience, while the attachment gives the team files to investigate.

Step	Action	Detail to preserve
Open Run	Press Windows + R	Use the Windows Run box
Open the location	Paste %localappdata%\Drowse\Saved\Crashes and press Enter	Keep the complete path
Select the folders	Select every folder inside Crashes	Include all crash folders
Create the archive	Compress the selected folders into one ZIP	Include every file they contain
Send the report	Attach the ZIP to your support email	Send it privately

Before sending, check that your ZIP contains the folders and their contents. An archive containing only a shortcut, a folder screenshot, or your written notes would leave out the requested crash files.

Keep the original folders in place while preparing the attachment. There is no need to reorganize the diagnostic files to make them look cleaner; preserving the contents is the priority.

Send the Report With a Clear Description

Email your ZIP attachment to contact@milkycocogames.com. Milky Coco Games specifically asks players to send crash files privately by email instead of posting them publicly.

Use a subject line that identifies the game and the failure immediately:

DROWSE startup crash report — black screen, then desktop

In the message, describe what happens from launch until the crash. Keep the order straightforward. Does the screen go black? Does loading begin? Does the game close before you reach gameplay? Include only the details that match your experience.

Then summarize troubleshooting you have actually completed. If you already reinstalled DROWSE, verified its files, or tried running it as administrator, say so. Those actions were unsuccessful in the reported startup case, so the useful follow-up was collecting crash files.

Do not copy another player’s troubleshooting history into your email. The team needs your sequence of events and your attempted actions.

Email element	What to write
Subject	Identify DROWSE and the startup crash
Failure description	Explain what appears onscreen before the game closes
Troubleshooting	List only actions you actually tried
Crash-folder result	Say whether folders were present, missing, or empty
Attachment	Include the single ZIP containing all crash folders and files

A message you can adapt

Use this example only if it matches what happens on your PC:

Hello Milky Coco Games,

DROWSE opens to a black screen, begins loading, and then closes to the desktop.

I found crash folders at %localappdata%\Drowse\Saved\Crashes and attached one ZIP containing all of those folders and their files.

My troubleshooting so far: [describe only the actions you have completed].

Thank you for investigating.

Replace the bracketed text before sending. If your launch failure behaves differently, rewrite the opening sentence rather than forcing your experience into the example.

Your DROWSE startup crash report should make two things easy to understand: what failed and what you attached. A long account of every unrelated issue you have encountered can bury those details.

If you are also experiencing an in-game problem, describe it separately within the message. A crash before gameplay and a blocked objective after a phone call occur at different points, and a clear description keeps those symptoms distinct.

Handle a Missing Folder or an Empty Archive

Sometimes the crash-report location does not exist, or the Crashes folder opens without any folders inside. Milky Coco Games asks players to report either outcome.

If the path does not open, tell the team that the crash-report location is missing. If it opens but contains nothing, say that the folder is empty. Those are different results, so use the description that fits.

You can still report the startup failure without attaching crash files. Explain the launch sequence and state what happened when you checked the requested path.

For example:

DROWSE begins loading on a black screen and then closes to the desktop. I checked %localappdata%\Drowse\Saved\Crashes, but the folder is empty.

Or:

DROWSE crashes during startup. I tried opening %localappdata%\Drowse\Saved\Crashes, but Windows could not open that location.

A missing DROWSE startup crash report does not prevent you from contacting support. The developer’s instructions explicitly include this situation: tell the team when the location is absent or empty.

Avoid creating an empty ZIP just to provide an attachment. It would not contain the crash folders the team requested. A direct explanation gives them the relevant result without an unnecessary archive.

Keep the report focused

When you cannot provide files, the written description carries more of the explanation. Use a short checklist:

• Describe what appears when you launch DROWSE.
• Explain when the game closes.
• State whether the crash location is missing or empty.
• Include troubleshooting you have already completed.

Keep the same level of precision if crash folders are present. Finding files is only one part of the report; the team still needs to know what happened during the launch that prompted you to contact them.

Keep Startup Crashes Separate From Patch Fixes

DROWSE’s early updates address several in-game problems. Knowing what those changes cover helps you describe your issue accurately, especially if you have seen both a startup failure and a progression problem.

Version 1.01 fixes an apartment softlock that could block progress after the phone call. It also addresses looping item-storage audio and several smaller presentation and interaction issues.

Version 1.02 improves interaction with the beeper in a drawer and the pills in the medicine cabinet. It also adjusts music behavior, rat collisions, hospital navigation, and the clarity of several messages.

Those details identify specific gameplay situations. If your game closes during initial loading, describe that launch failure directly when preparing your DROWSE startup crash report.

Issue or situation	Relevant response
Black screen, loading, then desktop crash	Collect crash folders and email the ZIP privately
Apartment progression blocked after the phone call	Version 1.01 fixes this softlock
Difficulty interacting with the drawer’s beeper	Version 1.02 makes this interaction easier
Difficulty interacting with pills in the medicine cabinet	Version 1.02 improves this interaction
Confusing hospital objective messages	Version 1.02 adds or clarifies guidance

The distinction matters because “DROWSE is broken” can describe very different experiences. A game that never reaches gameplay needs a different description from one that runs but leaves you stuck in the apartment.

Use the exact symptom in your email. If you cannot get past startup, lead with that. If the problem occurs during gameplay, identify the location and action involved instead.

DROWSE is a first-person psychological horror game about Andrew’s late-night return to the office. You should be able to spend your attention exploring, inspecting items, and solving puzzles. When startup prevents that, a complete attachment and a clear message give Milky Coco Games useful material to investigate.

For the game’s official store page, visit DROWSE on Steam.

FAQ

Where is the DROWSE startup crash report folder?

Press Windows + R, paste %localappdata%\Drowse\Saved\Crashes, and press Enter. If crash folders are present, select all of them and compress them into one ZIP, including every file they contain.

Where should I send DROWSE crash files?

Attach the ZIP to an email addressed to contact@milkycocogames.com. Send crash files privately by email, as requested by Milky Coco Games, instead of uploading them publicly.

What should I do if the Crashes folder is empty or missing?

Email the developer and explain which result you encountered. Include a clear description of the startup failure and any troubleshooting you have already completed. You can report the problem without a crash-file attachment.

What if reinstalling and verifying files did not help?

Include those attempts in your message if you performed them. For the reported black-screen startup crash that persisted after reinstalling, file verification, and running as administrator, the developer’s next request was to collect the crash folders and send their complete contents in one ZIP.