Hi cluberti, Thanks for those suggestions, I don't have any drive encryption applications installed and after changing the paging file size manually and setting it the dump size to "Complete" I found it still would not resolve the problem. Undeterred by this drop back I decided to do some "out side the box" thinking. My first hunch was based on the fact that I knew I was having problems with my antivirus software so I decided to just disable it and see if that changed anything. To my surprise when I manually initiated the BSOD the crash dump file was created and the computer restarted. Since Avast Antivirus has several on-access scanners (I was running 4 out of the 7) I decided to turn each of them off one by one to see which one was causing the problem. A while later I found out it was the standard shield provider that seemed to be causing the problem. After disabling it I made my system hang and forced a BSOD, to my surprise I found that it didn't want to create a crash dump file despite having the specific on access scanner disabled. In order to make my system hang I need the Messenger on-access scanner enabled so I can't completely disable Avast antivirus in order to make my system hang. This just proves that my AV software is the cause of this problem and I will be explaining these findings to the developers. In the meantime I just want to thank you for helping me make sure everything inside the box was properly looked at so I could move to the outside .