Skip to content

Segmentation fault Mystery Cache

Hidden : 12/2/2010
Difficulty:
4 out of 5
Terrain:
1.5 out of 5

Size: Size:   micro (micro)

Join now to view geocache location details. It's free!

Watch

How Geocaching Works

Please note Use of geocaching.com services is subject to the terms and conditions in our disclaimer.

Geocache Description:


The above coordinates are simply: WRONG

At the cache coordinates a lot of segmentation faults have been produced during the years but you will not be able to find the cache there.

Bug

Oh no, our computer has been invaded by a really nasty bug! Whatever we try to do, we just get segmentation faults.
But fear not, with your leet skillz you should be able to see the coordinates anyway. All you need is a lookup table and a bit of imagination!

So what is this all about? Well, that is for you to figure out! As soon as you have figured out what this is all about you just have to lookup what that message is. Sorry, I forgot one thing: For the very last part you need to use a bit of imagination to fix the segmentation fault. The very advanced mystery solver would of course not only use a lookup table and imagination to solve the mystery, he would also assemble his own little device to display the coordinates in bright red color!

Some people might think that a lookup table and a bit of imagination is not enough to solve this mystery. But I can assure you that it is enough. So what kind of lookup table do you need? Well, what kind of lookup table is useful when you want to display coordinates or other messages that consist mostly of digits? If you say ascii I would say that it is a bit of overkill. After all, you don't really need 7 bits to represent a digit, do you? Most people would agree that 7 letters is enough for that. And with the bit of imagination I hope you have, 6 letters would be enough. Not only is 6 letters enough to represent a digit, it is actually enough to also give you a hint on where this cache is hidden.

But if 6 letters is enough to represent a digit, why is the message coded with something that looks like 7-bit code? Tricky question, isn't it? First of all, if you look closely at the code you will see that it is actually more like 6-bit code. But still, far from the beauty of the 6 letters. Well, sometimes you just have to adapt to other people's standards. And this is one of those cases.

The cache is hidden close to the kind of device where segmentation faults sometimes occurred in the past, but thanks to modern techniques almost never nowadays.

15 00
53 70
63 00
71 73 00
57
57
77 02 00
47 00
30 30
63 00
53 73 00
73 71
30 02 00
06 00
37 04 15
07 00
01 00
04 15 53 04
35 47
01 36
67 00
53
76 36
07 37 00
47 15
35 00
06 00
56 76 00
56 47
07 00
04 07

Good luck and be careful not to be bitten by any bugs when searching for the cache!
Please do not upload any pictures of the hiding place!

You can check your answers for this puzzle on

Additional Hints (Decrypt)

nop_rst

Decryption Key

A|B|C|D|E|F|G|H|I|J|K|L|M
-------------------------
N|O|P|Q|R|S|T|U|V|W|X|Y|Z

(letter above equals below, and vice versa)