[Løst] BSOD - DirectX og andre ting

[dannyboy92]

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]

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

[dannyboy92]

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]

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

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

 

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

 

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

 

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

 

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

 

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

 

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:

------------------

[dannyboy92]

Etter som jeg har googla litt, tror jeg det eneste jeg kan gjøre er å enten flashe og oppdatere BIOSen min, eller skifte til w vista. Ettersom dette virker som et windows7 64bit relatert problem. Men har lest endel plasser at flashing av bios hjalp.

 

Tenkte jeg skulle vente på svar hær før jeg gjorde noe, siden jeg aldri før har flashet en bios.

 

Tusen takk får hjelp Vært morro å fått en pc som har funka skikkelig får en gangs skyld

[dannyboy92]

Legger ved ting etterhvert som jeg finner ut/kommer på relevante ting og skrive. I det jeg presser start knappen på kabinettet (coolermaster haf x black) kommer det et pip. Ikke et langt ett, bare et pip. Antar at det ikke er normalt heller.

 

Specs:

 

Asus P8p67 evo

750w psu Corsair ATX

Dominator 4gb x2 1600mhz cl9

Geforce GTX 570

A70 CPU fan (Kontakten er 3pinns, men jeg kobla den til en 4pinner på hovedkortet. Vifta fungerer, men dette kan vell ikke være problemet?)

2x Samsung f3 1tb

1x SSD OMZ 120gb

 

Får stadig vekk bluescreens, både når jeg starter å spille, og utenom.

[dannyboy92]

Har oppdatert BIOS, tenker på å reinstallere windows. Kjøre memory test, graphictest. Funker ikke noe av det så har hvertfall ikke jeg peiling.

[Dunno1987]

Hmm, jeg sliter litt med samme problemet. Feilkoden ligner veldig på den du får (3b, og noe minne greier).

 

Kjørte Memtest i 13 timer, men fant ingenting. Har en følelse av at det er SSD'ene mine, tre stk Intel 80GB i RAID0.

 

 

Bare et forslag, oppdater firmware og kjør feilsøk på SSD'en. Og si ifra hvis du finner ut feilen, for da vil jeg gjerne vite det

 

Her er debugen min i hvert fall, ser rimelig likt ut?

 

 

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\Minidump\011811-27112-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 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`01a11000 PsLoadedModuleList = 0xfffff800`01c4ee50

Debug session time: Tue Jan 18 18:31:34.432 2011 (UTC + 1:00)

System Uptime: 1 days 4:35:59.927

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

......

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 3B, {c0000005, fffff88007d2a817, fffff8800b772900, 0}

 

Probably caused by : atikmdag.sys ( atikmdag+90817 )

 

Followup: MachineOwner

---------

 

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

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

atikmdag+90817

fffff880`07d2a817 8b4820 mov ecx,dword ptr [rax+20h]

 

CONTEXT: fffff8800b772900 -- (.cxr 0xfffff8800b772900)

rax=0000000000000000 rbx=fffffa8006d4b3f0 rcx=fffffa8007a541f0

rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8008092010

rip=fffff88007d2a817 rsp=fffff8800b7732d0 rbp=fffffa8007a541f0

r8=0000000000000015 r9=fffff880080ec970 r10=0000000000000000

r11=fffff8800b773420 r12=0000000000000000 r13=fffffa800668c010

r14=0000000000000001 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

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

atikmdag+0x90817:

fffff880`07d2a817 8b4820 mov ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????

Resetting default scope

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

BUGCHECK_STR: 0x3B

 

PROCESS_NAME: dwm.exe

 

CURRENT_IRQL: 0

 

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88007d2a817

 

STACK_TEXT:

fffff880`0b7732d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x90817

 

 

FOLLOWUP_IP:

atikmdag+90817

fffff880`07d2a817 8b4820 mov ecx,dword ptr [rax+20h]

 

SYMBOL_STACK_INDEX: 0

 

SYMBOL_NAME: atikmdag+90817

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: atikmdag

 

IMAGE_NAME: atikmdag.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 4cef1f94

 

STACK_COMMAND: .cxr 0xfffff8800b772900 ; kb

 

FAILURE_BUCKET_ID: X64_0x3B_atikmdag+90817

 

BUCKET_ID: X64_0x3B_atikmdag+90817

 

Followup: MachineOwner

---------

 

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

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

atikmdag+90817

fffff880`07d2a817 8b4820 mov ecx,dword ptr [rax+20h]

 

CONTEXT: fffff8800b772900 -- (.cxr 0xfffff8800b772900)

rax=0000000000000000 rbx=fffffa8006d4b3f0 rcx=fffffa8007a541f0

rdx=0000000000000000 rsi=0000000000000015 rdi=fffffa8008092010

rip=fffff88007d2a817 rsp=fffff8800b7732d0 rbp=fffffa8007a541f0

r8=0000000000000015 r9=fffff880080ec970 r10=0000000000000000

r11=fffff8800b773420 r12=0000000000000000 r13=fffffa800668c010

r14=0000000000000001 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

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

atikmdag+0x90817:

fffff880`07d2a817 8b4820 mov ecx,dword ptr [rax+20h] ds:002b:00000000`00000020=????????

Resetting default scope

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

BUGCHECK_STR: 0x3B

 

PROCESS_NAME: dwm.exe

 

CURRENT_IRQL: 0

 

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88007d2a817

 

STACK_TEXT:

fffff880`0b7732d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x90817

 

 

FOLLOWUP_IP:

atikmdag+90817

fffff880`07d2a817 8b4820 mov ecx,dword ptr [rax+20h]

 

SYMBOL_STACK_INDEX: 0

 

SYMBOL_NAME: atikmdag+90817

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: atikmdag

 

IMAGE_NAME: atikmdag.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 4cef1f94

 

STACK_COMMAND: .cxr 0xfffff8800b772900 ; kb

 

FAILURE_BUCKET_ID: X64_0x3B_atikmdag+90817

 

BUCKET_ID: X64_0x3B_atikmdag+90817

 

Followup: MachineOwner

---------

 

 

 

[dannyboy92]

Heihei Ser ikke ut som det er helt det samme problemet vi lider av, ta en titt på denne. Gjorde en google søk får deg.

 

http://www.overclock.net/ati-drivers-overclocking-software/420875-possible-solution-atikmdag-driver-crash.html

 

 

Tror problemet mitt er fikset faktisk. Formaterte windowsen min, installerte alt på nytt, og var litt mer forsiktig av valg av drivere istedet får å istallere alle utilitys som var tilgjengelig. Har ikke fått en BSOD enda, og har spillt endel

[Chavalito]

Noe av det første som bør sjekkes ved BSODer, er minnet og hvilken hastighet og spenning det kjører på. Er disse to feil oppsatt, kan det føre til BSOD, og jeg tviler på at Memtest vil finne feil på minnet for det ikke er snakk om fysiske feil. Så sjekk i BIOS minnehastighet og spenning til minnet. Minnet må også være av typen Non-ECC, Un-buffered Memory.

Jeg hadde selv masse BSOD med nettopp Dominator (dog DDR2 og 1066MHz) minne på grunn av feil minnehastighet og spenning.

 

dannyboy92, du sier: "A70 CPU fan (Kontakten er 3pinns, men jeg kobla den til en 4pinner på hovedkortet. Vifta fungerer, men dette kan vell ikke være problemet?)" Der skal være en egen kontakt for CPU viften, ligger ofte helt ute på kanten av hovedkortet i nærneten av CPU sokkelen og er merket CPU_FAN eller noe slikt. CPU viften bør absolutt kobles til denne da BIOS kan tro at CPU viften ikke kjører hvis den er koblet til en annen kontakt.

Endret 19. januar 2011 av Chavalito

[dannyboy92]

Ja, men når jeg plugga til CPU vifta til ''cpufan'' pinn'en så funka den ikke. den var 3pinn.. Satte cpu vifta på fan slotten en halv cm unna, som jeg også tror er cpu fan, bare med 4pins. Sporet på kontakten på vifta passet mye bedre dær, en på 3pinnen. Syns det var litt rart, men vifta går, og har bra temp på riggen min.

[dannyboy92]

ang spenning på ram, jeg kjører på 1.650v, som var standard. Søkte opp på google, og det skulle være greit når de ikke er klokka.

Endret 19. januar 2011 av dannyboy92

[Chavalito]

Tja, rart at vifta ikke funka da du prøvde i CPU_FAN kontakten, men funker den okay nå og temperaturen er fin, så er det jo bare å la det være sånn. Dog litt rart da.

 

Regner med at du brukte den Asus DVDen med drivere, og der er det absolutt en fordel å velge drivere selv. Ellers kan det faktisk hende at det blir installert drivere som ikke har noe der å gjøre. Angående de hard diskene som vises som "eksterne" så er det slik på madamen sin PC også, men alle diskene virker helt fint.

[Stegz]

Du må putte boot-disken din i en av de mørkeblå sata-slottene. Da vil du ikke lenger få "No harddisk is detected" ved oppstart.

 

Jeg har imidlertidig et lite problem med CPU-vifta. Den går på max kontinuerlig selv om temperaturen ligger på 27 grader idle. Vifta er koblet til den hvite 4-pin viftekontakten øverst på kortet. Noen som vet hva som er galt?

[Balthier]

Noen som vet hva som er galt?

 

Viften reguleres ikke gjennom BIOS, OS eller hardvare begrensninger.

[dannyboy92]

Du må putte boot-disken din i en av de mørkeblå sata-slottene. Da vil du ikke lenger få "No harddisk is detected" ved oppstart.

 

Jeg har imidlertidig et lite problem med CPU-vifta. Den går på max kontinuerlig selv om temperaturen ligger på 27 grader idle. Vifta er koblet til den hvite 4-pin viftekontakten øverst på kortet. Noen som vet hva som er galt?

 

Samme 4slot pinnen min er på det. Å vifte kontakten på 470'n er 3pins.. Har ikke sjekka rpm'en på vifta mi enda, men tror den ligger på ca 1900 rundt hele tidn 25-30grader uklokket.