diff --git a/README.md b/README.md
index 63a38b6..82cdcd4 100644
--- a/README.md
+++ b/README.md
@@ -3,6 +3,8 @@
 
 For a mod list, please go to the [mod list page](MOD_LIST.md). All mod authors are properly credited.
 
+### [FAQ](faq/INDEX.md)
+
 ## Join & Play
 For the download link and server IP, [join my Discord server](https://discord.io/rayzrdevofficial) and ask me about it.
 
diff --git a/faq/INDEX.md b/faq/INDEX.md
new file mode 100644
index 0000000..6786dce
--- /dev/null
+++ b/faq/INDEX.md
@@ -0,0 +1,7 @@
+# FAQ
+Just some frequent questions I get.
+
+**Q:** Help! I installed the pack, but it crashes when I try to launch it!
+**A:** Please follow [these steps](TECHNIC_RAM.md) to make sure you have allocated enough RAM to Minecraft.
+
+_More questions coming soon! Stay tuned..._
\ No newline at end of file
diff --git a/faq/TECHNIC_RAM.md b/faq/TECHNIC_RAM.md
new file mode 100644
index 0000000..60b3540
--- /dev/null
+++ b/faq/TECHNIC_RAM.md
@@ -0,0 +1,30 @@
+# Technic RAM Fix
+By default when you [install the Technic Launcher](https://www.technicpack.net/download) it is set to only use 1 gigabyte of RAM. Most modpacks require more than this, so the packs crash when they launch (or launch/run slowly). It's very simple to fix this.
+
+### Step 1
+![Step 1](pictures/step-1.png)
+
+Click on the *Launcher Options* button in the Technic Launcher.
+
+### Step 2
+![Step 2](pictures/step-2.png)
+
+Select the *Java Settings* tab.
+
+### Step 3
+![Step 3](pictures/step-3.png)
+
+You should have a window open that looks like this. First, check that the *Minecraft Java Verison* is 64-bit. If it isn't, select a 64-bit version. If there are no 64-bit versions available, please download the latest 64-bit version [from Java's website](http://java.com/en/download/). Once that has installed, restart the Technic Launcher and repeat steps 1-3.
+
+### Step 4
+![Step 4](pictures/step-4.png)
+
+Edit your *Memory* setting to something preferably higher than 2 gigabytes. I run mine at 8 gigabytes, but my computer has a lot of RAM. You can always try setting the *Memory* setting to the max available value.
+
+### Step 5
+![Step 5](pictures/step-5.png)
+
+Your memory should now look something like this.
+
+
+***Congratulations!*** That's it.
\ No newline at end of file
diff --git a/faq/pictures/step-1.png b/faq/pictures/step-1.png
new file mode 100644
index 0000000..c33a0b4
Binary files /dev/null and b/faq/pictures/step-1.png differ
diff --git a/faq/pictures/step-2.png b/faq/pictures/step-2.png
new file mode 100644
index 0000000..2aca613
Binary files /dev/null and b/faq/pictures/step-2.png differ
diff --git a/faq/pictures/step-3.png b/faq/pictures/step-3.png
new file mode 100644
index 0000000..6e732f6
Binary files /dev/null and b/faq/pictures/step-3.png differ
diff --git a/faq/pictures/step-4.png b/faq/pictures/step-4.png
new file mode 100644
index 0000000..011d5e6
Binary files /dev/null and b/faq/pictures/step-4.png differ
diff --git a/faq/pictures/step-5.png b/faq/pictures/step-5.png
new file mode 100644
index 0000000..3a8e51e
Binary files /dev/null and b/faq/pictures/step-5.png differ