diff --git a/Stack-Trace-Guide-for-Citra.md b/Stack-Trace-Guide-for-Citra.md
new file mode 100644
index 0000000..7abfd76
--- /dev/null
+++ b/Stack-Trace-Guide-for-Citra.md
@@ -0,0 +1,20 @@
+#Stack trace on Windows
+* Download and install [Visual Studio 2015 Community](https://www.visualstudio.com/vs/community/).
+* Download the [nightly build](https://github.com/citra-emu/citra-nightly/releases), [source code](https://github.com/citra-emu/citra-nightly/releases) and [debug symbols](https://ci.appveyor.com/project/citrabot/citra-nightly/build/artifacts) (__make sure they have the same commit hash__). If you've compiled your own [msvc build](https://github.com/citra-emu/citra/wiki/Building-for-Windows#msvc-build-for-windows), then skip this and the following step.
+![1](http://i.imgur.com/8A47XHp.png)
+![2](http://i.imgur.com/41G9NQq.png)
+* Extract them and place the .pdb files from the debug symbols into the nightly build folder.
+* Run Citra and initiate the crash. If you've compiled your own msvc build, then run Citra from `./citra/build/bin/Release`.
+* A message box will pop up, select Debug.
+![3](http://i.imgur.com/g0WHuiQ.png)
+* Another message box will pop up, make sure "New instance of Microsoft Visual Studio 2015" is selected and select Yes.
+![4](http://i.imgur.com/e2i6iB5.png)
+* Visual Studio will start up and ask for the file in the source code. Find the file in the source code that you extracted. In this example, it's debug_utils.cpp. This step is unnecessary if you've compiled yourself.
+![5](http://i.imgur.com/4IhMreO.png)
+* A message box will pop up, select Break.
+![6](http://i.imgur.com/dPf0zrc.png)
+* Copy or screenshot the Call Stack. If the Call Stack window isn't showing, then select Debug -> Windows -> Call Stack. To maximize the window, right click on the Call Stack window and select Float, then maximize window icon.
+![7](http://i.imgur.com/oBIzFk3.png)
+* Next to the Disassembly will be the file in the source code, screenshot the window.
+![8](http://i.imgur.com/sz5KqxB.png)
+* Upload the two screenshots in your issue report.
\ No newline at end of file