BlueScreen :(?

Lirade bf3 innan och det har crashat 2 ggr idag pga detta.
Nån som vet va de e för fel är jag mycket tacksam för svar!!
Klockade prollen igår till 4.3ghz.

Problemsignatur:
Problemhändelsens namn: BlueScreen
OS-version: 6.1.7601.2.1.0.256.1
Språkvariant-ID: 1053

Ytterligare information om problemet:
BCCode: 1000007e
BCP1: FFFFFFFFC000001D
BCP2: FFFFF800024D8655
BCP3: FFFFF880027D6488
BCP4: FFFFF880027D5CE0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Filer som hjälper till att beskriva problemet:
C:\Windows\Minidump\042612-5350-01.dmp
C:\Users\Dan\AppData\Local\Temp\WER-15038-0.sysdata.xml

Läs vår sekretesspolicy online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x041d

Om sekretesspolicyn online inte är tillgänglig kan du läsa vår sekretesspolicy offline:
C:\Windows\system32\sv-SE\erofflps.txt

hur öppnar jag den filen?? eller var hittar jag den?

men kopierar jag den texten å söker i C: så hittar den inget?

aaa först ladda ner sen öppna

*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+72655 )

Followup: MachineOwner

?????? blir inte som jag vill...

ska testa när jag kommer hem från jobb!! vet nu att jag bara la till c\:symbols\
allt ska med alltså inkl SRV* ?

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff800024d8655, The address that the exception occurred at
Arg3: fffff880027d6488, Exception Record Address
Arg4: fffff880027d5ce0, Context Record Address

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

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {UNDANTAG} Ogiltig instruktion Ett f rs k gjordes att utf ra en ogiltig instruktion.

FAULTING_IP:
nt!KiCommitThreadWait+165
fffff800`024d8655 f0480fba6f3000 lock bts qword ptr [rdi+30h],0

EXCEPTION_RECORD: fffff880027d6488 -- (.exr 0xfffff880027d6488)
ExceptionAddress: fffff800024d8655 (nt!KiCommitThreadWait+0x0000000000000165)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT: fffff880027d5ce0 -- (.cxr 0xfffff880027d5ce0)
rax=0000000000000000 rbx=fffffa800a25b8c0 rcx=00000066afd31fb2
rdx=000000000003ce7f rsi=fffffa800a25b980 rdi=fffff80002657e80
rip=fffff800024d8655 rsp=fffff880027d66c0 rbp=fffffa800a25b8c0
r8=fffffa800a25b9a0 r9=00000000000000c5 r10=fffff80002466000
r11=fffffa800a25b900 r12=0000000000000000 r13=00002248b70b1013
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!KiCommitThreadWait+0x165:
fffff800`024d8655 f0480fba6f3000 lock bts qword ptr [rdi+30h],0 ds:002b:fffff800`02657eb0=0000000000000000
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 2

ERROR_CODE: (NTSTATUS) 0xc000001d - {UNDANTAG} Ogiltig instruktion Ett f rs k gjordes att utf ra en ogiltig instruktion.

LAST_CONTROL_TRANSFER: from fffff800024e51da to fffff800024d8655

FAILED_INSTRUCTION_ADDRESS:
nt!KiCommitThreadWait+165
fffff800`024d8655 f0480fba6f3000 lock bts qword ptr [rdi+30h],0

STACK_TEXT:
fffff880`027d66c0 fffff800`024e51da : fffffa80`0a5ff000 fffff880`05e6d6e6 00000000`000000c5 fffffa80`0a5ff000 : nt!KiCommitThreadWait+0x165
fffff880`027d6750 fffff880`05f6f0a9 : fffff880`00000002 fffff880`027d6b38 fffffa80`00000001 00000000`00000000 : nt!KeWaitForMultipleObjects+0x272
fffff880`027d6a10 fffff880`05f9dcfd : fffffa80`0c1f8010 fffffa80`0a552410 00000000`00000000 00000000`00000002 : dxgmms1!VidSchWaitForEvents+0xf5
fffff880`027d6a70 fffff880`05f6b29e : fffffa80`0a552410 ffffffff`feced300 fffffa80`0c1f8010 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x139
fffff880`027d6ab0 fffff880`05f97e7a : 00000000`00000000 fffffa80`0c1f8010 00000000`00000080 fffffa80`0a552410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
fffff880`027d6bc0 fffff800`0277cfda : 00000000`01242984 fffffa80`0a25b8c0 fffffa80`069d4450 fffffa80`0a25b8c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`027d6c00 fffff800`024d39c6 : fffff880`022d0180 fffffa80`0a25b8c0 fffff880`022dafc0 fffff880`01cff52f : nt!PspSystemThreadStartup+0x5a
fffff880`027d6c40 00000000`00000000 : fffff880`027d7000 fffff880`027d1000 fffff880`027d6540 00000000`00000000 : nt!KxStartSystemThread+0x16

FOLLOWUP_IP:
dxgmms1!VidSchWaitForEvents+f5
fffff880`05f6f0a9 8be8 mov ebp,eax

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgmms1!VidSchWaitForEvents+f5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1

STACK_COMMAND: .cxr 0xfffff880027d5ce0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_BAD_IP_dxgmms1!VidSchWaitForEvents+f5

BUCKET_ID: X64_0x7E_BAD_IP_dxgmms1!VidSchWaitForEvents+f5

Followup: MachineOwner