BSOD! Happening while playing games.

You also had issues caused by the following drivers:

Intel Processor driver (intelppm.sys)
Intel(R) 82579V Gigabit Network Connection driver (e1c62x64.sys)
DirectX Graphics MMS (dxgmms1.sys)

Update the first two drivers. As to the graphics issue you continue to have, try the following:

Note: if you are running a RAID controller of any kind, backup your data before proceeding with the following steps
1. Shut down and turn off your computer.
2. Unplug the power supply from the outlet/surge protector
3. Hold down the power button for 30 seconds to close the circuit and drain capacitors (for your safety)
4. Unplug all peripherals from the motherboard (usb ports, usb cards, monitor connection, display card, memory modules, etc. so that all that is left is the CPU and CPU fan [typically these I leave alone as they are a pain to remove and replace])
5. Reseat all peripherals back in the motherboard securely.
6. Plug power back into the power supply
7. Start your computer and enter the BIOS
8. Reset BIOS to defaults.
9. Save and exit BIOS settings.
10. Start Windows and see if you continue to have display card issues.

writhziden said:

You had a memory error. Look through this guide: Diagnosing memory problems on your computer

Run it for at least 5 passes in extended mode.

Also, when you run this guide, follow the outline in part 3 of RAM - Test with Memtest86+ if memory errors are found. Continue the testing through the Windows memory testing utility, but follow those steps to diagnose bad memory modules/slots.

I got Corsair Vengeance DDR3 1600MHz 8GB CL8

Kit w/2x 4GB XMS3 modules, CL8-8-8-24, 1.5V, Vengeance Heatspreader, 240

But i have not change anything in my bios about the ram. Can this be tha cause??
Also seen that the mhz reads 1620mhz, not 1600mhz. Does this matter??

Ive tried to run Memory Diagnostics twice now. Once before format, and 1 after i installed Windows 7 fresh.
Both times the test has stopped early. First time it was on like 2% or something like that. Now it stopped on 20% on the first phase. With the extended test running.
This cant be normal :P

Installed Windows 7 last night, but havent been able to test programs that crash with it yet. But ran the memorytest but stopped working. Have ran memtest a few phases but got no error there.

Memtest can fail if you have bad memory, or if the memory is corrupted. To test for memory corruption:

1. Shut down and turn off your computer.
2. Unplug the power supply from the outlet/surge protector
3. Hold down the power button for 30 seconds to clear temporary memory of corruption
4. Plug power back into the power supply
5. Start your computer
6. Run Memtest again

If it fails after the above steps, then you should consider testing one module at a time in one slot at a time.

First BSOD after format....

Code:

Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Hantimilon\122911-17316-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304d670
Debug session time: Thu Dec 29 14:23:59.804 2011 (GMT-7)
System Uptime: 0 days 14:09:37.616
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002e878e2, fffff880077fb4a0, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002e878e2, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880077fb4a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!SwapContext_PatchXRstor+0
fffff800`02e878e2 0fae29          xrstor  [rcx]

CONTEXT:  fffff880077fb4a0 -- (.cxr 0xfffff880077fb4a0)
rax=0000000000000005 rbx=fffff880009ea180 rcx=fffff880077fccc0
rdx=0000000000000000 rsi=fffffa8007e32b60 rdi=fffffa8008384a10
rip=fffff80002e878e2 rsp=fffff880077fbe80 rbp=fffff880077fcc70
 r8=0000000000000000  r9=0000000000000009 r10=fffff80002e08000
r11=0000000000000000 r12=00000000fffa7000 r13=000000000bcdfd20
r14=fffffa8008e22250 r15=fffff880009eef40
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!SwapContext_PatchXRstor:
fffff800`02e878e2 0fae29          xrstor  [rcx]
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x3B

PROCESS_NAME:  swtor.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002e874da to fffff80002e878e2

STACK_TEXT:  
fffff880`077fbe80 fffff800`02e874da : 00000000`00000000 ffffffff`fffffffb 00000000`00000000 fffff880`077fc3e0 : nt!SwapContext_PatchXRstor
fffff880`077fbec0 fffff800`02e89f32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`077fc000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff80002e87803 - nt!SwapContext_PatchXSave+2
	[ 01:21 ]
    fffff80002e878e4 - nt!SwapContext_PatchXRstor+2 (+0xe1)
	[ 09:29 ]
    fffff80002e87aa3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf)
	[ 01:21 ]
    fffff80002e87b86 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3)
	[ 09:29 ]
4 errors : !nt (fffff80002e87803-fffff80002e87b86)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT_LARGE

STACK_COMMAND:  .cxr 0xfffff880077fb4a0 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

Followup: memory_corruption
---------

Another memory_corruption error. Have you gone through the steps of testing one module at a time?

I've done that before, they both got bsod...
Maybe it about time to order some new modules? :P

Hantimilon said:

I've done that before, they both got bsod...
Maybe it about time to order some new modules? :P

Probably is. I assume clearing any memory corruption did not help?