Es2launcher.exe Application Error ◎ «SAFE»

Then the sound started. A low, wet thump from her subwoofer. Thump. Thump. Thump. It wasn't a system beep. It was rhythmic. Organic.

Nothing happened. Then, a small, polite window appeared in the dead center of her screen.

"Press OK to continue."

It was 11:47 PM, and Lena was three keystrokes away from shipping the final build of Starfall Odyssey . Her finger hovered over the ‘Export’ button. The room was silent except for the hum of her PC, which had been running for thirty-six hours straight. Es2launcher.exe Application Error

The instruction at 0x745F3A1C referenced memory at 0x00000000. The memory could not be "read".

Her monitor flickered. The error text began to change. The hexadecimal addresses didn't look random anymore. They looked like coordinates. Latitude. Longitude. Her latitude. Her apartment building.

Lena ran for the door. She didn't make it. The last error window bloomed across all three of her monitors at once, huge and red: Then the sound started

The thumping stopped. The fans stopped. The lights in her apartment went out.

She clicked ‘OK.’ The window vanished. A second later, a new one popped up, identical except for the memory address. 0x745F3A1D. Then another. 0x745F3A1E. It was counting.

Lena blinked. "What?"

In the pitch black, a single line of green text appeared on her dead monitor, glowing like a wound:

She stood up, knocking her chair over. The thumping grew louder. Her phone buzzed on the desk. A text from an unknown number: "The memory could not be read. But it can be written."

She clicked.

She never pressed a thing. But the error clicked itself anyway.