Blue Screen Of Death

[sofianmaster]

Goeiedag allemaal,

Ik heb regelmatig last van BSOD's en dankzij Dell's hulp heb ik iets met Windows Debugger kunnen maken. Na het probleem gezien te hebben(dxgkrnl) zat ik opeens vast. Wat zou ik nu moeten doen?

Hier is nog het dump filetje.

Loading Dump File [C:\Windows\Minidump\Mini122209-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*DownstreamStore*Symbol information

Executable search path is:

Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339

Machine Name:

Kernel base = 0x82444000 PsLoadedModuleList = 0x8255bc70

Debug session time: Tue Dec 22 19:14:16.658 2009 (GMT+1)

System Uptime: 0 days 9:59:19.617

Loading Kernel Symbols

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

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

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

.

Loading User Symbols

Loading unloaded module list

......

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4, 2, 1, 8e66f8ce}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for dxgkrnl.sys

*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys

Probably caused by : dxgkrnl.sys ( dxgkrnl+198ce )

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: 00000004, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000001, value 0 = read operation, 1 = write operation

Arg4: 8e66f8ce, address which referenced memory

Debugging Details:

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

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8257b868

Unable to read MiSystemVaType memory at 8255b420

00000004

CURRENT_IRQL: 2

FAULTING_IP:

dxgkrnl+198ce

8e66f8ce ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: dwm.exe

TRAP_FRAME: 9766a6ec -- (.trap 0xffffffff9766a6ec)

ErrCode = 00000002

eax=00000000 ebx=919c18b8 ecx=b3121850 edx=8553f334 esi=00000000 edi=84d42008

eip=8e66f8ce esp=9766a760 ebp=9766a770 iopl=0 nv up ei ng nz na pe cy

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010287

dxgkrnl+0x198ce:

8e66f8ce ?? ???

Resetting default scope

LAST_CONTROL_TRANSFER: from 8e66f8ce to 82491fb9

STACK_TEXT:

9766a6ec 8e66f8ce badb0d00 8553f334 919c1800 nt!KiTrap0E+0x2e1

WARNING: Stack unwind information not available. Following frames may be wrong.

9766a75c b31216d0 00000000 919c1c66 919c1b00 dxgkrnl+0x198ce

9766a770 8e6e8a9f 919c1c64 b3121850 b3121858 0xb31216d0

9766a7f0 8e6e629a 919c1c64 00000001 c4725210 dxgkrnl+0x92a9f

9766a818 8e699059 b31216d0 9766aa30 c4725210 dxgkrnl+0x9029a

9766a9b0 8e69b088 00000000 c000ff40 00000000 dxgkrnl+0x43059

9766aba4 8e69bbf9 ac06ec58 00000000 1901efcb dxgkrnl+0x45088

9766ad58 8248ec7a 004d0027 01b3f5d0 775e5e74 dxgkrnl+0x45bf9

9766ad58 775e5e74 004d0027 01b3f5d0 775e5e74 nt!KiFastCallEntry+0x12a

01b3f5d0 00000000 00000000 00000000 00000000 0x775e5e74

STACK_COMMAND: kb

FOLLOWUP_IP:

dxgkrnl+198ce

8e66f8ce ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: dxgkrnl+198ce

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4abc1c72

FAILURE_BUCKET_ID: 0xD1_dxgkrnl+198ce

BUCKET_ID: 0xD1_dxgkrnl+198ce

Followup: MachineOwner

---------

[jv9090]

Ik denk dat het iets te maken heeft met de drivers van je videokaart. Welke videokaart heb je en heb je de laatste drivers?

[sofianmaster]

Ik heb een Intel GM965 Express Chipset Family. En de videokaart is up-to-date.

[jv9090]

DRIVER_IRQL_NOT_LESS_OR_EQUAL

Dit wijst volgens mij toch op een verkeerde driver.

Of je geheugen? Dit kunnen we nakijken door memtest te laten draaien.

[sofianmaster]

Ik begrijp niet helemaal hoe je die memtest moet runnen. Ook heb ik sinds vandaag een andere BSOD.

Microsoft ® Windows Debugger Version 6.11.0001.404 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini122409-02.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*DownstreamStore*Symbol information

Executable search path is:

Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6002.18082.x86fre.vistasp2_gdr.090803-2339

Machine Name:

Kernel base = 0x8244e000 PsLoadedModuleList = 0x82565c70

Debug session time: Thu Dec 24 11:13:55.704 2009 (GMT+1)

System Uptime: 0 days 0:09:29.465

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

......

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8a3e2c50, ff, 0, c4845167}

Unable to load image \??\C:\Windows\system32\XDva317.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for XDva317.sys

*** ERROR: Module load completed but symbols could not be loaded for XDva317.sys

Probably caused by : XDva317.sys ( XDva317+8167 )

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: 8a3e2c50, memory referenced

Arg2: 000000ff, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: c4845167, address which referenced memory

Debugging Details:

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

READ_ADDRESS: GetPointerFromAddress: unable to read from 82585868

Unable to read MiSystemVaType memory at 82565420

8a3e2c50

CURRENT_IRQL: 0

FAULTING_IP:

XDva317+8167

c4845167 ?? ???

ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.

BUGCHECK_STR: DISABLED_INTERRUPT_FAULT

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: crossfire.exe

TRAP_FRAME: b5692620 -- (.trap 0xffffffffb5692620)

ErrCode = 00000000

eax=85801f50 ebx=c4848790 ecx=8a3e2c50 edx=8a3e2c50 esi=00000050 edi=b5692714

eip=c4845167 esp=b5692694 ebp=b56926d0 iopl=0 nv up di pl zr na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046

XDva317+0x8167:

c4845167 ?? ???

Resetting default scope

LAST_CONTROL_TRANSFER: from c4845167 to 8249bfb9

STACK_TEXT:

b5692620 c4845167 badb0d00 8a3e2c50 00000060 nt!KiTrap0E+0x2e1

WARNING: Stack unwind information not available. Following frames may be wrong.

b5692690 b5692714 c484a00c 9625c000 b5692cf0 XDva317+0x8167

b56926d0 c4843ed1 82585b00 82585b40 c484a00c 0xb5692714

b56926f8 c484564d b5692738 b5692714 d8492e58 XDva317+0x6ed1

b56928e4 c483e075 d8492e58 000001a8 d8492e58 XDva317+0x864d

b5692bd0 c484011a d8076f68 c77e9358 00000001 XDva317+0x1075

b5692c0c 827306be d5846448 d8076f68 c77e9358 XDva317+0x311a

b5692c30 8249292d d8076fd8 d8076f68 d5846448 nt!IovCallDriver+0x23f

b5692c44 826946a1 c77e9358 d8076f68 d8076fd8 nt!IofCallDriver+0x1b

b5692c64 82694e46 d5846448 c77e9358 0012cb00 nt!IopSynchronousServiceTail+0x1d9

b5692d00 82695f10 d5846448 d8076f68 00000000 nt!IopXxxControlFile+0x6b7

b5692d34 82498c7a 000005a0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a

b5692d34 773d5e74 000005a0 00000000 00000000 nt!KiFastCallEntry+0x12a

0012cb7c 00000000 00000000 00000000 00000000 0x773d5e74

STACK_COMMAND: kb

FOLLOWUP_IP:

XDva317+8167

c4845167 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: XDva317+8167

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: XDva317

IMAGE_NAME: XDva317.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4b18ac6d

FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_VRF_XDva317+8167

BUCKET_ID: DISABLED_INTERRUPT_FAULT_VRF_XDva317+8167

Followup: MachineOwner

---------- Post toegevoegd om 11:26 ---------- Vorige post was om 11:25 ----------

Wat ik nog vergeten te melden ben is dat deze 2 BSOD's maar in één spel voorkomen nl. Crossfire

[jv9090]

Wat ik nog vergeten te melden ben is dat deze 2 BSOD's maar in één spel voorkomen nl. Crossfire

Kan toeval zijn natuurlijk. Kan je het spel eens testen op een andere pc?

Wat meer info over die stopfout:

Stop 0x D1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

[sofianmaster]

Mijn vriend speelt dit spel al heel lang zonder problemen. En zoals je me nu vertelt is het wel degelijk de videokaart. Het kan aan de update liggen. Weet je misschien hoe ik de update van de videokaart kan verwijderen?

[jv9090]

Voor xp kon je dit doen via apparaatbeheer. Vista gebruik ik niet. Zal het vragen aan een andere medewerker.

[sofianmaster]

Bij apparaatbeheer zie ik niet wat ik zou moeten verwijderen. Ik heb hier nog een afbeelding. Misschien zie je wat ik moet verwijderen

[stegisoft]

Je kan eveneens bij Vista bij apparaatbeheer uw drivers verwijderen.

Maar bij videokaart moet je ook de software verwijderen.

Dus

Klik op deze computer met de rechtermuisknop op eigenschappen

Dan klik je op apparaatbeheer

Software

Start / configuratiescherm / programma

Klik op de nvidia en boven op verwijderen klikken.

Die chipset driver is verkeerd want die hoort daar niet.

Daarom die conflict.

Welke videokaart hebt je?

Ofwel Merk / type en eventueel serie nummer van laptop of computer.

24 december 2009 aangepast door stegisoft