diff --git a/docs/BlissRoms/build-guide.md b/docs/BlissRoms/build-guide.md
index a09cc1c..5fa0e03 100644
--- a/docs/BlissRoms/build-guide.md
+++ b/docs/BlissRoms/build-guide.md
@@ -173,6 +173,7 @@
 * Make sure you sourced `build/envsetup.sh`. This is especially common and worth suspecting if none of the build commands like `breakfast` and `lunch` work. If you have `repo sync`ed do this again.
 * Make sure you’re at the root of the build tree. Again, to quickly jump there, use `croot`.
 * Make sure you ran `breakfast` correctly and it did not error out. Missing device files will prevent successful builds.
+* Make sure your computer meets minimum requirements to compile AOSP. Chances are, you need more memory/CPU power to complete a build.
 * Make sure your computer itself isn’t faulty. HDDs usually die first, followed by RAM. SSDs rarely die but failure is not unheard of.  In extremely rare cases, your CPU may have a defect. If you're unsure, run a stress test using a program like Prime95.
 
 If something goes wrong and you've tried everything above, first use Google to look up your error! Most of the errors you encounter is due to misconfiguration and wrong commands entered. More often than not, Google will have the answer you are looking for. If you're still stuck and nothing fixes the problem, then ask us via our Telegram Build Support chat.