[Løst] BSOD - DirectX og andre ting

dannyboy92 · 19. januar 2011

Hei allesammen.. bygde sammen pc'en min idag, åsså første spillet jeg lastet ned var CoD mw2. Det fryser midt i spillet. Lurer på om det kan være hdd'en som ikke er helt på topp.

Uploaded with ImageShack.us

Da jeg var ferdig og installere windows, kom ikke hddene opp i min datamaskin, kunn SSDen. Jeg gikk inn på datamaskin behandling og fixa de, etter som en guide jeg fant på google. Men CoD fungerer ikke. Har ikke testet andre spill enda.

Virker som mine interne hdd'er oppfører seg som externe. Vet ikke om det er det at pc'en slutter å lese fra hdd'en som gjør at spillet kræsjer. Siden cod er på en av samsung hdd'ene som oppfører seg externt, og windowsen er på ssd'en som oppfører seg som den skal?

Har lastet ned alt av windows updates. Har windows 7 ultimate btw.

Endret 19. januar 2011 av dannyboy92

dannyboy92 · 19. januar 2011

Speccs: https://www.diskusjon.no/index.php?showtopic=1289217

dannyboy92 · 19. januar 2011

Har lastet ned og installert nyeste Geforce GTX 570 Drivere, installert alle drivere/utility's til hovedkortet fra CD'en som fulgte med.

Jeg får fortsatt bluescreens etter noen minutter med spilling. Også en ting jeg nesten må peke ut, er at når jeg starter pc'en, så på bootscreen, står det ''No Hard Drives Detected''. Men jeg kommer meg innpå windows. Jeg har helt ærlig ikke peiling på slikt, siden dette er den første pcen jeg har bygd helt selv. Alt av deler SKAL være kompatible.

Geforce GTX 570

ASUS p8p67 evo motherboard

2500k Intel i5 1155 Sandy Bridge

Dominator 1600mhz 4gb x2 minne.

dannyboy92 · 19. januar 2011

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols;srv*c:\mss*http://msdl.microsoft.com/download/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621

Machine Name:

Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`03293e50

Debug session time: Wed Jan 19 21:27:00.625 2011 (UTC + 1:00)

System Uptime: 0 days 0:31:36.530

Loading Kernel Symbols

...............................................................

................................................................

.............................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details

Loading unloaded module list

......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff88010035475, fffff8800c08da00, 0}

Page 2011e3 not present in the dump file. Type ".hh dbgerr004" for details

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_PROCESS_HEAP::Free+65 )

Followup: MachineOwner

---------

0: 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: fffff88010035475, Address of the instruction which caused the bugcheck

Arg3: fffff8800c08da00, 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:

dxgmms1!VIDMM_PROCESS_HEAP::Free+65

fffff880`10035475 f60701 test byte ptr [rdi],1

CONTEXT: fffff8800c08da00 -- (.cxr 0xfffff8800c08da00)

rax=fffffa800691c660 rbx=fffffa800691c660 rcx=fffffa8006c23660

rdx=fff7f8a009617ce0 rsi=fffffa8006c23660 rdi=fff7f8a009617ce0

rip=fffff88010035475 rsp=fffff8800c08e3d0 rbp=fffff8a009c3bc00

r8=0000000000000001 r9=0000000000000001 r10=fffffffffffffffe

r11=fffff8800c08e480 r12=0000000000000000 r13=fffffa800bde0000

r14=0000000000000000 r15=fffff8a007b4d850

iopl=0 nv up ei pl zr na po nc

cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246

dxgmms1!VIDMM_PROCESS_HEAP::Free+0x65:

fffff880`10035475 f60701 test byte ptr [rdi],1 ds:002b:fff7f8a0`09617ce0=??

Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: iw4mp.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88010020b5a to fffff88010035475

STACK_TEXT:

fffff880`0c08e3d0 fffff880`10020b5a : fffff880`0c08e3f8 fffff8a0`01d2e790 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0x65

fffff880`0c08e400 fffff880`1001b523 : fffffa80`06e13750 00000000`00000000 fffff8a0`09c3bc00 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112

fffff880`0c08e4b0 fffff880`10001ecc : fffff8a0`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b

fffff880`0c08e580 fffff880`10d37c10 : 00000000`00000000 fffff8a0`09ee5000 fffff8a0`09ee5000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44

fffff880`0c08e5b0 fffff880`10d4a67c : fffffa80`0bdbc000 00000000`00000000 00000000`00000000 fffff8a0`09ee5068 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248

fffff880`0c08e6a0 fffff880`10d2f815 : 00000000`fffffeda fffff8a0`09a14520 fffff8a0`09ee5000 fffffa80`0bdbc000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c

fffff880`0c08e710 fffff880`10d6dca6 : 00000000`00000000 fffffa80`0bdbc000 fffff8a0`09a14520 fffff8a0`09a145a0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9

fffff880`0c08e740 fffff880`10d6d63c : fffff900`c1f4b6a0 00000000`00000000 00000000`00000001 fffff900`c1f4b6a0 : dxgkrnl!DXGPROCESS::Destroy+0xba

fffff880`0c08e7f0 fffff960`000c4c44 : 00000000`00000664 fffff900`c1f4b6a0 00000000`00000000 fffff900`c1f4b6a0 : dxgkrnl!DxgkProcessCallout+0x268

fffff880`0c08e880 fffff960`000c4337 : fffffa80`0beb2200 fffff880`0c08ebe0 00000000`00000000 fffff880`0c08ebe0 : win32k!GdiProcessCallout+0x244

fffff880`0c08e900 fffff800`033aba01 : fffffa80`0beb22a0 00000000`00000000 00000000`00000000 fffffa80`06fb5060 : win32k!W32pProcessCallout+0x6b

fffff880`0c08e930 fffff800`03384635 : 00000000`000000ff 00000000`00000001 fffffa80`78457300 fffffa80`071f2600 : nt!PspExitThread+0x561

fffff880`0c08e9f0 fffff800`030a31db : 00000000`00000100 fffffa80`06fb5120 00000000`00000001 fffff800`030cdb9d : nt!PsExitSpecialApc+0x1d

fffff880`0c08ea20 fffff800`030a3620 : 00000000`00000000 fffff880`0c08eaa0 fffff800`0338474c 00000000`00000001 : nt!KiDeliverApc+0x2eb

fffff880`0c08eaa0 fffff800`030c5a37 : fffffa80`06fb5060 00000000`000004d4 00000000`00000000 fffffa80`0da86d60 : nt!KiInitiateUserApc+0x70

fffff880`0c08ebe0 00000000`74082dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c

00000000`0a91f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74082dd9

FOLLOWUP_IP:

dxgmms1!VIDMM_PROCESS_HEAP::Free+65

fffff880`10035475 f60701 test byte ptr [rdi],1

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1!VIDMM_PROCESS_HEAP::Free+65

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME: dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

STACK_COMMAND: .cxr 0xfffff8800c08da00 ; kb

FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_PROCESS_HEAP::Free+65

BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_PROCESS_HEAP::Free+65