Random BSOD's and Screen Freezing/Crashing Please Help

A BCC 7F has loads of usual causes:

Code:

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

Usual causes:  Memory corruption, Hardware (memory in particular), 
Overclocking failure, Installing a faulty or mismatched hardware 
(especially memory) or a failure after installing it, 3rd party firewall, 
Device drivers, SCSI/network/BIOS updates needed, Improperly 
seated cards, Incompatible storage devices, Overclocking, 
Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80003eec248}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 00000000000006f8
Arg4: fffff80003eec248

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  vmt.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003edf569 to fffff80003edffc0

STACK_TEXT:  
fffff880`009f0c68 fffff800`03edf569 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009f0c70 fffff800`03edda32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f0db0 fffff800`03eec248 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`052dfee0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03edda32 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------

1. If you are overclocking any hardware, STOP. Reset any changed values back to default.
2. I hope you have uninstalled Kaspersky & installed MSE. Wait, you're having Norton as well!?
It's a No.1 BSOD causer. Please uninstall Norton and/or anything related to Norton.

• Norton Removal Tool

3. System Optimisers

Please remove the following software

Code:

Start Menu\Programs\Wise Registry Cleaner 4 Professional	Public:Start Menu\Programs\Wise Registry Cleaner 4 Professional	Public
Start Menu\Programs\Defraggler	Dakka-PC\Dakka:Start Menu\Programs\Defraggler	Dakka-PC\Dakka

This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner but make sure you back up the registry before making letting ccleaner delete anything. You may make use of the great in-built Disk Cleanup and Extended Disk Cleanup if required to do so, regarding de-frag utilities, I recommend yet again the in-built Disk Defragmenter - Open and Use & Puran Defrag which is much reliable compared to others.

Perform a System File Check:

• Click on the start
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Disk Check on your hard drive for file system errors and bad sectors on it:

• Disk Check

Check for a newer BIOS version:

Code:

BIOS Version/Date	American Megatrends Inc. 2105, 23/07/2010

Then test memory individually as mentioned in my previous post.

What about overclocking?

Dakka said:

I'm having to post this from my phone as the computer is checking the disk! I am not overclocking anything in fact I'm underclocking the ram I think, as it is not running at 1600

Why isn't it running at 1600?

Remove that stick and see if you're getting BSOD-s.

I've called a friend for help with ram settings.
Please wait for a reply.

Hi Dakka, enter BIOS/Advanced/Jumper free Configuration and scroll (down arrow) to Memory Clock Mode and set it to Manual. This will let you set your RAM frequency here.
Under DRAM Timing Mode set it to manual and DCT to Both.

Look at your RAM's label for the specs, and set timings and volts to those values or the closect you have a setting for.
Attachment 247335
Attachment 247336

This is only an example of a RAM label.

Attachment 247337

I recommend you use only the GSKill RAM, two different brands can cause issues, which may be your case. If possible get a matched set and don't use RAM purchased at different times even if the same model and brand.

The Phenom only natively supports DDR3-1333MHz which is why it has to be overclocked to get to stock specs.

Link to your motherboard manual, if you don't have one.
http://support.asus.com/Download.aspx?SLanguage=en&p=1&s=24&m=M4A785TD-V%20EVO/U3S6&os=30&ft=12&f_name=G4937_M4A785-M.zip#G4937_M4A785-M.zip