Help with this BSOD plz

Please run Blue Screen of Death (BSOD) Posting Instructions and upload the file here, Screenshots and Files - Upload and Post in Seven Forums

I will try to help you with this problem. You only had one dump file in the upload and it is hard to analyze from just one dump file. Also basically it did not give much information. Have you changed or added any hardware or software recently? It there any application or activity that usually causes these crashes? Any information you can give will help us out a lot. What the dump file said was

Code:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff900c1ed72c0

Hopefully that is a driver or software problem. Please make sure this is your Motherboard and update any drivers found there (Motherboards - SABERTOOTH 990FX R2.0 - ASUS) also please make sure the Firmware is up to date on your SSD.

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.


Then I would like you to try Driver Verifier. This will make your computer feel a little sluggish, but that is normal. Please use it for a minimum of 24 hours of actual use, not just idling. If there is any activity that causes these crashes, please do them repeatedly. There are no restrictions on what you can do. Do whatever you would like. If you are overclocking, please set everything back to defaults. Please create a restore point before you start. The link to how to do that is below. Please sort the drivers by provider and select all drivers not provided by Microsoft. The idea is to cause them to crash and catch the faulty driver in the crash. But, be sure to create a restore point before beginning.

   Warning

Be sure to create a System Restore point before proceeding further System Restore Point - Create

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.

What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.

   Warning

Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

OK, just give it a try. We may have to run it a bit longer. But, we'll see what happens.