BSOD right after startup

Still the display is failing there.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.Still it is a display related issue.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.
______________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa800a4f0cd0, 6, 1, fffff88002c0c087}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiUpdateContextRunningTimeAtISR+2b )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffffa800a4f0cd0, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88002c0c087, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350b100
GetUlongFromAddress: unable to read from fffff8000350b1c0
 fffffa800a4f0cd0 Nonpaged pool

CURRENT_IRQL:  6

FAULTING_IP: 
dxgmms1!VidSchiUpdateContextRunningTimeAtISR+2b
fffff880`02c0c087 f0440fb1af90010000 lock cmpxchg dword ptr [rdi+190h],r13d

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880041f6880 -- (.trap 0xfffff880041f6880)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880041f6a70
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002c0c087 rsp=fffff880041f6a10 rbp=fffff880041f6a70
 r8=fffff880041f6b50  r9=0000000000000000 r10=fffff88002c0c2c0
r11=fffff880041f6a48 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
dxgmms1!VidSchiUpdateContextRunningTimeAtISR+0x2b:
fffff880`02c0c087 f0440fb1af90010000 lock cmpxchg dword ptr [rdi+190h],r13d ds:00000000`00000190=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d3129 to fffff800032d3b80

STACK_TEXT:  
fffff880`041f6738 fffff800`032d3129 : 00000000`0000000a fffffa80`0a4f0cd0 00000000`00000006 00000000`00000001 : nt!KeBugCheckEx
fffff880`041f6740 fffff800`032d1da0 : 00000000`00000000 00000000`00000001 00000000`00000001 fffffa80`08ff1000 : nt!KiBugCheckDispatch+0x69
fffff880`041f6880 fffff880`02c0c087 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`041f6bf8 : nt!KiPageFault+0x260
fffff880`041f6a10 fffff880`02c0c2fe : 41de72d8`1d20b8b8 fffff880`041f6b50 00000000`00000000 fffffa80`07ff99a0 : dxgmms1!VidSchiUpdateContextRunningTimeAtISR+0x2b
fffff880`041f6a50 fffff800`032cf42b : 00000000`00000002 00000000`00000000 fffffa80`07ff99a0 fffff880`009edec0 : dxgmms1!VidSchiUpdateNodeRunningTimeAtISR+0x3e
fffff880`041f6aa0 fffff880`02cd7901 : 00000000`0000001b fffff880`02c0c2c0 fffff880`041f6b50 fffffa80`08f50410 : nt!KeSynchronizeExecution+0x3b
fffff880`041f6ae0 fffff880`02c0c374 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000005 : dxgkrnl!DpSynchronizeExecution+0xd5
fffff880`041f6b20 fffff880`02c0b566 : 00000000`00000000 00000000`00000001 fffffa80`00000000 00000000`00000000 : dxgmms1!VidSchiUpdateNodeRunningTime+0x38
fffff880`041f6b80 fffff880`02c0b183 : fffffa80`08f50410 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiSelectContext+0xea
fffff880`041f6bf0 fffff880`02c37ff6 : 00000000`00000000 fffffa80`09e80b40 00000000`00000080 fffffa80`08f50410 : dxgmms1!VidSchiScheduleCommandToRun+0x8b
fffff880`041f6d00 fffff800`03571bae : 00000000`0b6acafe fffffa80`08d83b50 fffffa80`06ba1040 fffffa80`08d83b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`041f6d40 fffff800`032c48c6 : fffff880`009e9180 fffffa80`08d83b50 fffff880`009f3f40 fffff880`041f6e40 : nt!PspSystemThreadStartup+0x5a
fffff880`041f6d80 00000000`00000000 : fffff880`041f7000 fffff880`041f1000 fffff880`041f6680 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiUpdateContextRunningTimeAtISR+2b
fffff880`02c0c087 f0440fb1af90010000 lock cmpxchg dword ptr [rdi+190h],r13d

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiUpdateContextRunningTimeAtISR+2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dc13

FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+2b

BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiUpdateContextRunningTimeAtISR+2b

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`048f2000 fffff880`0539d000   nvlddmkm   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
    CheckSum:         00A8D47C
    ImageSize:        00AAB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You havent posted back the results of the tests you are suggested earlier.

warrior87 said:

i have ran memtest and found that i have an error, so i will now diagnose weather it is a ram module, slot, or motherboard

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.
It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.
It is a motherboard issue. The particular slot is bad.

If it is bad RAM, change it.

If it is a bad DIMM slot, better not use that slot.

Make it sure that all the RAM sticks are properly places, and clips are closed, too. Also make it sure that the HDDs are properly plugged. Check the SATA/power cables at both the ends.

If all is proper there, Follow it:
Troubleshooting Windows 7 Failure to Start