Hi I wanted to know what is causing my computer to crash, I never gotten a BSOD before and I've had my computer for 3 months so far. It just started when I'm playing a particular game and it my computer crashes. This is the dump files I got and hopefully someone can tell me what is going on.

System Information (local)

computer name: XANXUS windows version: Windows 8.1 , 6.2, build: 9200 windows dir: C:\Windows Hardware: ASUSTeK COMPUTER INC., SABERTOOTH 990FX R2.0 CPU: AuthenticAMD AMD FX(tm)-9590 Eight-Core Processor AMD586, level: 21 8 logical processors, active mask: 255 RAM: 17070952448 total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 6/29/2015 9:22:00 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\062915-11609-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x150CA0) Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF801181F54C0) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft Windows Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Mon 6/29/2015 9:22:00 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: fltmgr.sys (fltmgr!FltGetRequestorProcess+0xB64) Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF801181F54C0) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\fltmgr.sys product: Microsoft Windows Operating System company: Microsoft Corporation description: Microsoft Filesystem Filter Manager Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask
BTW  Who crashed and Blue screen view are wrong more often than they are correct

the forum won't let me post any links until it has verify my account. How do I do that?

while you are waiting for verification you can simply change the HTTP:// to HXXP:// to post the link

If you are being told you cant post a link, or embed a picture (or any other restriction) you just need to post to this thread saying your account has not been validated
Look for the verify your account thread that is stuck to the top of the page.
http://social.technet.microsoft.com/Forums/en-US/home?forum=reportabug
Read more here http://social.technet.microsoft.com/Forums/windows/en-US/9fe32cfb-ed1c-4b9d-93d9-7ff32b0106a3/verify-your-account-16?forum=reportabug

 Here are the dump files and my PC specs hopefully you can analyze them to see what is going with my pc. hxxps://www.dropbox.com/s/jmmq5vdtanlvfhm/Minidump%20files.zip?dl=0

These crashes were related to memory corruption (probably caused by Symantec). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)