Preview of PDF document crashdumpdocx.pdf

Page 1 2 345109

Text preview

“Damn it” he cursed to himself, “Halo. Call Melissa.”
“Please power off all electronics. Melissa is not available at this time.”
Tapping a small button on his earpiece twice, the home computer’s screen was brought
up on his kitchen counter and he quickly typed into the search box, “halscope not
working, call halo support.”
Just as Jarod was about to hit the Return button the screen went an ugly shade of dark
blue, then quickly filled with white text.

A problem has been detected and Windows has been shut down to prevent damage to your computer.
A process thread crucial to system operation has unexpectedly exited or been terminated.
Check to make sure all hardware is properly installed
*** STOP:

(0x4661756C, 0x74792048756D, 0x616E204C, 0x6F676963)

Collecting data for crash dump ...
Initializing disk ...
Dumping physical memory to disk: 0, 1, 2, 3...

The computer counted from ​0 ​to ​100​ over the next ten seconds, and Jarod watched,
and tried to understand, ​Crash dump?
​ ​ ... Install all hardware​? It was probably just
another forced software update gone haywire he thought. In that moment, Jarod was not
the only one seeing this message, on every screen on the planet, every electronic
display available, the same message and countdown appeared. His son Peter was
watching the countdown as well. He was trying to make sense of the hex codes thinking
maybe he triggered some security feature that interrupted him from playing the puzzle
game on the screen he had ​borrowed ​from the school a few days ago, but much of the
world was watching the same screen, scratching their heads about what it meant and
asking all in unison, where in the Hell is the IT guy?

Chapter 2
Crash Dump

Collecting data for crash dump …