[vistaSP1] Vista crash na openen games

[Dutch2007]

probleem is als volgt...

ik open elk willekeurig spel (speel voornamelijk eve & NFS:Undercover)

en voordat ik het weet *poof* scherm gaat op zwart, andere monitor zegt, display cable not connected (terwijl de pc toch echt werkt)

ik had dit probleem eerst in xp sp3, dacht misschien is de installatie te zwaar vervuild, en ik dus, eerst op XP verschillende drivers van mijn ati x1600 pro agp 512MB gedownload & geinstalleerd (allen waren de 8.12 drivers) zowel de standaard, de agp-hotfix als de omega drivers voor catalyst 8.12


nu heb ik me gisteren vista ultimate geinstalleerd en ik denk mooi hij werkt...
start ik vandaag eve-online op...

weer een vaag scherm (alsof de video kaart geen stroom meer krijgt lijkt het wel???)

wat opzich vreemd is want heb al 2x 350watt voedingen in de pc zitten...

heb het volgende in mijn pc zitten

AMD64 3800+ @2.3ghz
2GB ram (DDR1, 400Mhz, 4x corsair)
Asus A8V Deluxe (latest bios)
Windows Vista Ultimate Sp1
Saphire ATI Raedon X1600Pro 512MB AGP-edition

nu heb ik moet ik wel toegeven, vorige week?? of de week daarvoor... een soort van sissend? geluid gehoord dat uit me pc kast kwam, maar ik kon het geluid niet localiseren, omdat het niet constand was (het was random)

wat-o-wat kan het probleem zijn? mijn gok is of de video-kaart, of de voeding(en)


verder heb ik gekeken in "problem reports and solutions" van windows vista..

en daar zie ik.. "Problem caused by ATI Graphics Driver" ! New

enige wat daar staat..

Check for ATI Graphics Driver updates

This problem was caused by ATI Graphics Driver, which was created by ATI Technologies, Inc.. There is no solution for this problem at this time.

Troubleshooting

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


A driver update, if available, might prevent this problem from recurring.

Pretty useless, voor me xfi stond er tenminste een download link....

heb ook een mini dump... kan alleen niet zo 1 2 3, een programma vinden om het te openen, en te kijken wat er aan de hand is...

p.s. zal zo ook 2 screenshots gemaakt met me gsm, om te laten zien wat voor beeld ik krijg als (denk de driver???) crasht

[alt-92]

Tja, maar als de driver al eruit vliegt en Error Reporting daar al mee komt, dan kun je dat verifieren met de dumpfile die je al hebt en de Debugging tools (zie de HOWTO sectie).

Ik zie dan niet echt in waar je dit topic dan nog voor wil openen?

[Dutch2007]

alt-92 schreef op maandag 15 december 2008 @ 20:28:
Tja, maar als de driver al eruit vliegt en Error Reporting daar al mee komt, dan kun je dat verifieren met de dumpfile die je al hebt en de Debugging tools (zie de HOWTO sectie).

Ik zie dan niet echt in waar je dit topic dan nog voor wil openen?

http://img201.imageshack.us/my.php?image=foto0023ig5.jpg --> lijnen na een crash...

ik nu dus geen games kan dus

en ik niet morgen ofzo een nieuwe voeding wil gaan halen die mogelijk het probleem niet oplost...

die debuggi tools blijven me...

code:

  Your debugger is not using the correct symbols                 ***

geven....


terwijl ik 1) vista SP1 draai 2)de vista sp1 symols geladen heb

code:

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Grabbit Downloads\Mini121508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols;C:\Windows\
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x81c39000 PsLoadedModuleList = 0x81d50c70
Debug session time: Mon Dec 15 19:46:05.455 2008 (GMT+1)
System Uptime: 0 days 0:33:18.593
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.................
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {9802b280, 0, 0, 0}

*** WARNING: Unable to verify timestamp for atikmdag.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c )

Followup: MachineOwner
---------

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

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 9802b280, Pointer to a stuck thread object.  Do .thread then kb on it to find
    the hung location.
Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 00000000, Pointer to offending driver name.
Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************

MODULE_NAME: dxgkrnl

FAULTING_MODULE: 81c39000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4893b1df

FAULTING_THREAD:  9802b280

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0xEA

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8d518b60 to 81d060e3
[b]
STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8a3b79e8 8d518b60 000000ea 9802b280 00000000 nt+0xcd0e3
8a3b7a2c 8d5106cf 8a3b7a78 00000000 8d51370c dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x2c
8a3b7a54 8ce2a3d6 8a3b7a78 00000000 00000000 dxgkrnl!TdrTimedOperationDelay+0xc9
8a3b7aa4 8ce2812b 8cee9066 8a3b7b3c 00000bb8 atikmdag!DISPATCHER::HandleCWDDECI+0x64
8a3b7ac0 8ceef99b 87761000 8a3b7ad8 9ebd1a78 atikmdag!KMDSystemConfiguration::getDeviceHandle+0x9
8a3b7b18 8ceeb363 9ebd1a78 8cee9066 8a3b7b3c atikmdag!vGetNewHVTimingParams+0xcd
8a3b7b64 8cece094 ffffffff 9803131c 8cebb359 atikmdag!bIsTVConnected_R420+0x252
8a3b7bac 00000000 8a3b7bc8 8ce1c255 98014008 atikmdag!DoCallback+0x194
[/b]

STACK_COMMAND:  .thread 0xffffffff9802b280 ; kb

FOLLOWUP_IP: 
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c
8d518b60 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+2c

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  dxgkrnl.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

0: kd> .reload
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.................
0: kd> .reload
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.................

code:

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
8a3b79e8 8d518b60 000000ea 9802b280 00000000 nt+0xcd0e3
8a3b7a2c 8d5106cf 8a3b7a78 00000000 8d51370c dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x2c
8a3b7a54 8ce2a3d6 8a3b7a78 00000000 00000000 dxgkrnl!TdrTimedOperationDelay+0xc9
8a3b7aa4 8ce2812b 8cee9066 8a3b7b3c 00000bb8 atikmdag!DISPATCHER::HandleCWDDECI+0x64
8a3b7ac0 8ceef99b 87761000 8a3b7ad8 9ebd1a78 atikmdag!KMDSystemConfiguration::getDeviceHandle+0x9
8a3b7b18 8ceeb363 9ebd1a78 8cee9066 8a3b7b3c atikmdag!vGetNewHVTimingParams+0xcd
8a3b7b64 8cece094 ffffffff 9803131c 8cebb359 atikmdag!bIsTVConnected_R420+0x252
8a3b7bac 00000000 8a3b7bc8 8ce1c255 98014008 atikmdag!DoCallback+0x194

bovenstaande zal mijn error dus veroorzaken?? atikmdag ???
*edit*

http://winqual.microsoft....US%20A8V%20Deluxe&oid=327

*edit*

zie ik dat me moederbord XP only is? ofjah alleen maar op de XP HCL list staat? maar ook op/voor XP had ik deze problemen.

[ Voor 139% gewijzigd door Dutch2007 op 16-12-2008 13:48 ]