Vollständige Version anzeigen : [Grafikkarte] ATi Treiber macht probs bei CSS und HL²
share the pain
04.01.2005, 19:05
Hi Leute.
Hab en Prob und find keine Lösung. Wenn ich Counterstrike Source zocke oder Half-life ², verreckt nach Mapwechsel bzw. Ladebildschrim mein Pc. Habe mir mal die dmp Dateien angeschaut und gesehen, dass es an dem Treiber von ATi liegt. Da ich nun aber schon 2 mal Formatiert habe und alle Treiber durchgetestet habe, weiß ich netmehr weiter. Versteh das mit dem Symbols net.
Hier Noch mein System und drunter die dmp Datei:
AMD Athlon XP 3200
Asus A7N8X-E Deluxe
1024 mb DDR Ram von Corsair
ATi X800 SE @ Mad-Moxx 550/550
Creative Audigy 2 zs
240 GB Seagate ( 2 Platten mit jeweils 120 Gb)
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini122304-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543fb0
Debug session time: Thu Dec 23 14:59:47 2004
System Uptime: 0 days 0:19:42.898
************************************************** *******************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
************************************************** *******************
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .................................................. ..............
Loading unloaded module list
...............
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {e12b5000, 2, 0, bf9c5e66}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Unable to load image ati2dvag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2dvag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2dvag.dll
Probably caused by : ati2dvag.dll ( ati2dvag+ee66 )
Followup: MachineOwner
---------
thx schonmal an @lle :)
StillPad
04.01.2005, 19:16
Was issn Mad Moxx?
Ich glaube das liegt an dein übertakten, takte das ding runter und schau obs noch immer abschmiert.
Off-topic:
Wieder ein grund warum ich keine ati habe :D
share the pain
04.01.2005, 19:20
Hi.
Mad-Moxx ist der Vertreiber dieser Karte. Das ist der normale Takt der Karte wie er im Bios steht. Auch mit den normalen 430/430 Mhz einer X800 SE stürzt mein PC ab....
Denke deshalb nicht, dass es am Übertakten liegt.
Thx trotzdem :)
Auch wenn sie bei Standardtakt noch abstürzt, kann es trotzdem am OC liegen. Schließlich wird Mad-Moxx die Karte mit mehr Spannung versehen, um höhere Taktraten stabil zu erriechen. Evtl. schlägt der Überhitzungsschutz hier einfach zu früh an.
Wie warm ist es denn ansonsten in deinem Gehäuse?
Wenn es lediglich bei diesen zwei Spielen zu Problemen kommt, heißt es auf Patches warten. ;)
Bis denne!
share the pain
04.01.2005, 19:36
Also im Gehäuse hab ich so um die 34 °C und die Graka hat beim zockken bisher max. 55 °C gehabt. Aber stürzt nur beim Spielen ab. Und bisher auch nur bei HL² oder CSS.
Wenn sich das net bessert, tausch ich die Karte wieder um. Schade um das Teil....
Thx
Dennis
Ist ne schwierige Frage. Beide Spiele sind relativ neu und basieren auf der gleichen Engine (falls nicht, bitte berichtigen). Von daher würde ich schon erstmal andere Spiele testen, bevor man von nem Defekt ausgeht. Aber trotzdem ist die Karte ja für dich nicht viel wert, wenn sie deine Lieblingsspiele nicht richtig verarbeitet.
Oder du kontaktierst mal Mad-Moxx. Vielleicht kennen die das Problem schon.
Bis denne!
StillPad
04.01.2005, 20:10
Ist ne schwierige Frage. Beide Spiele sind relativ neu und basieren auf der gleichen Engine (falls nicht, bitte berichtigen). Von daher würde ich schon erstmal andere Spiele testen, bevor man von nem Defekt ausgeht. Aber trotzdem ist die Karte ja für dich nicht viel wert, wenn sie deine Lieblingsspiele nicht richtig verarbeitet.
Oder du kontaktierst mal Mad-Moxx. Vielleicht kennen die das Problem schon.
Bis denne!
CSCZ bassiert meines wissen auf einer modifizierten HL1 Engine und HL² auf HL² Engine :D
Kann mir aber sehr gut vorstellen das es bei beiden zu problemen kommt, da die engines fast gleich sind von der programierung.
Warten auf neue Teiber ;)
share the pain
04.01.2005, 20:14
Is zzt. der Catalyst 4.12 drauf :)
Hab im Netz mal das Packet mit diesen Symbolen gefunden aus der Fehlermeldung. Werd das nachher mal installieren und schauen, was sich tut. Also Farcry, X² und UT2004 sin bisher net abgestürzt. Werd gleich auch mal an Mad-Moxx schreiben.
Thx nochmal
Dennis
share the pain
04.01.2005, 20:35
Hab wie gesagt das Packet installiert und den Debugger gestartet. Und mir gefällt irgendwie net, was da so steht:
Microsoft (R) Windows Debugger Version 6.3.0017.0
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini122304-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543fb0
Debug session time: Thu Dec 23 14:59:47 2004
System Uptime: 0 days 0:19:42.898
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .................................................. ..............
Loading unloaded module list
...............
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {e12b5000, 2, 0, bf9c5e66}
Unable to load image ati2dvag.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ati2dvag.dll
Probably caused by : ati2dvag.dll ( ati2dvag!DrvEnableDirectDraw+64 )
Followup: MachineOwner
---------
kd> analyze -v
*** WARNING: Unable to verify timestamp for hal.dll
*** WARNING: Unable to verify timestamp for kmixer.sys
*** WARNING: Unable to verify timestamp for wdmaud.sys
*** WARNING: Unable to verify timestamp for srv.sys
*** WARNING: Unable to verify timestamp for mrxdav.sys
*** WARNING: Unable to verify timestamp for afd.sys
*** WARNING: Unable to verify timestamp for dump_nvatabus.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_nvatabus.sys
*** WARNING: Unable to verify timestamp for Fastfat.SYS
*** WARNING: Unable to verify timestamp for dxgthk.sys
*** WARNING: Unable to verify timestamp for Cdfs.SYS
*** WARNING: Unable to verify timestamp for Dxapi.sys
*** WARNING: Unable to verify timestamp for watchdog.sys
*** WARNING: Unable to verify timestamp for secdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for secdrv.sys
*** WARNING: Unable to verify timestamp for DCR.sys
*** ERROR: Module load completed but symbols could not be loaded for DCR.sys
*** WARNING: Unable to verify timestamp for mrxsmb.sys
*** WARNING: Unable to verify timestamp for rdbss.sys
*** WARNING: Unable to verify timestamp for netbt.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
*** WARNING: Unable to verify timestamp for ipsec.sys
*** WARNING: Unable to verify timestamp for ctac32k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctac32k.sys
*** WARNING: Unable to verify timestamp for ctsfm2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctsfm2k.sys
*** WARNING: Unable to verify timestamp for emupia2k.sys
*** ERROR: Module load completed but symbols could not be loaded for emupia2k.sys
*** WARNING: Unable to verify timestamp for ha10kx2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha10kx2k.sys
*** WARNING: Unable to verify timestamp for hap16v2k.sys
*** ERROR: Module load completed but symbols could not be loaded for hap16v2k.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** WARNING: Unable to verify timestamp for ati2cqag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati2cqag.dll
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*** WARNING: Unable to verify timestamp for ativvaxx.dll
*** ERROR: Module load completed but symbols could not be loaded for ativvaxx.dll
*** WARNING: Unable to verify timestamp for dxg.sys
*** WARNING: Unable to verify timestamp for imapi.sys
*** WARNING: Unable to verify timestamp for PfModNT.sys
*** ERROR: Module load completed but symbols could not be loaded for PfModNT.sys
*** WARNING: Unable to verify timestamp for arp1394.sys
*** WARNING: Unable to verify timestamp for wanarp.sys
*** WARNING: Unable to verify timestamp for Null.SYS
*** WARNING: Unable to verify timestamp for Fips.SYS
*** WARNING: Unable to verify timestamp for netbios.sys
*** WARNING: Unable to verify timestamp for USBSTOR.SYS
*** WARNING: Unable to verify timestamp for Npfs.SYS
*** WARNING: Unable to verify timestamp for Msfs.SYS
*** WARNING: Unable to verify timestamp for rasacd.sys
*** WARNING: Unable to verify timestamp for update.sys
*** WARNING: Unable to verify timestamp for ndisuio.sys
*** WARNING: Unable to verify timestamp for rdpdr.sys
*** WARNING: Unable to verify timestamp for psched.sys
*** WARNING: Unable to verify timestamp for ndiswan.sys
*** WARNING: Unable to verify timestamp for VIDEOPRT.SYS
*** WARNING: Unable to verify timestamp for ati2mtag.sys
*** WARNING: Unable to verify timestamp for ctoss2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctoss2k.sys
*** WARNING: Unable to verify timestamp for ks.sys
*** WARNING: Unable to verify timestamp for portcls.sys
*** WARNING: Unable to verify timestamp for ctaud2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
*** WARNING: Unable to verify timestamp for yukonx86.sys
*** ERROR: Module load completed but symbols could not be loaded for yukonx86.sys
*** WARNING: Unable to verify timestamp for USBPORT.SYS
*** WARNING: Unable to verify timestamp for termdd.sys
*** WARNING: Unable to verify timestamp for msgpc.sys
*** WARNING: Unable to verify timestamp for Mup.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** WARNING: Unable to verify timestamp for KSecDD.sys
*** WARNING: Unable to verify timestamp for sr.sys
*** WARNING: Unable to verify timestamp for nvatabus.sys
*** ERROR: Module load completed but symbols could not be loaded for nvatabus.sys
*** WARNING: Unable to verify timestamp for atapi.sys
*** WARNING: Unable to verify timestamp for dmio.sys
*** WARNING: Unable to verify timestamp for ftdisk.sys
*** WARNING: Unable to verify timestamp for ACPI.sys
*** WARNING: Unable to verify timestamp for pci.sys
*** WARNING: Unable to verify timestamp for isapnp.sys
*** WARNING: Unable to verify timestamp for ohci1394.sys
*** WARNING: Unable to verify timestamp for 1394BUS.SYS
*** WARNING: Unable to verify timestamp for MountMgr.sys
*** WARNING: Unable to verify timestamp for VolSnap.sys
*** WARNING: Unable to verify timestamp for disk.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** WARNING: Unable to verify timestamp for nic1394.sys
*** WARNING: Unable to verify timestamp for redbook.sys
*** WARNING: Unable to verify timestamp for i8042prt.sys
*** WARNING: Unable to verify timestamp for rasl2tp.sys
*** WARNING: Unable to verify timestamp for raspppoe.sys
*** WARNING: Unable to verify timestamp for raspptp.sys
*** WARNING: Unable to verify timestamp for NDProxy.SYS
*** WARNING: Unable to verify timestamp for usbhub.sys
*** WARNING: Unable to verify timestamp for sysaudio.sys
*** WARNING: Unable to verify timestamp for processr.sys
*** WARNING: Unable to verify timestamp for drmk.sys
*** ERROR: Module load completed but symbols could not be loaded for drmk.sys
*** WARNING: Unable to verify timestamp for cdrom.sys
*** WARNING: Unable to verify timestamp for PCIIDEX.SYS
*** WARNING: Unable to verify timestamp for PartMgr.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for nv_agp.sys
*** ERROR: Module load completed but symbols could not be loaded for nv_agp.sys
*** WARNING: Unable to verify timestamp for vga.sys
*** WARNING: Unable to verify timestamp for usbehci.sys
*** WARNING: Unable to verify timestamp for mouclass.sys
*** WARNING: Unable to verify timestamp for kbdclass.sys
*** WARNING: Unable to verify timestamp for ptilink.sys
*** WARNING: Unable to verify timestamp for raspti.sys
*** WARNING: Unable to verify timestamp for BOOTVID.dll
*** WARNING: Unable to verify timestamp for usbohci.sys
*** WARNING: Unable to verify timestamp for gameenum.sys
*** WARNING: Unable to verify timestamp for ndistapi.sys
*** WARNING: Unable to verify timestamp for TDI.SYS
*** WARNING: Unable to verify timestamp for kdcom.dll
*** WARNING: Unable to verify timestamp for WMILIB.SYS
*** WARNING: Unable to verify timestamp for dmload.sys
*** WARNING: Unable to verify timestamp for ctprxy2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ctprxy2k.sys
*** WARNING: Unable to verify timestamp for USBD.SYS
*** WARNING: Unable to verify timestamp for dump_WMILIB.SYS
*** ERROR: Module load completed but symbols could not be loaded for dump_WMILIB.SYS
*** WARNING: Unable to verify timestamp for Fs_Rec.SYS
*** WARNING: Unable to verify timestamp for Beep.SYS
*** WARNING: Unable to verify timestamp for mnmdd.SYS
*** WARNING: Unable to verify timestamp for RDPCDD.sys
*** WARNING: Unable to verify timestamp for pciide.sys
*** WARNING: Unable to verify timestamp for audstub.sys
*** WARNING: Unable to verify timestamp for swenum.sys
Couldn't resolve error at 'nalyze -v'
share the pain
04.01.2005, 20:48
Problem ist gefunden denke ich. Habe jetzt ne komplette auswertung und muss feststellen, dass irgendwass mit dem Arbeitsspeicher net stimmt. Hatte zwar schonmal nen Test gemacht mit Memtest und war nach 35 Durchläufen fehlerfrei, werde mir jetzt aber mal die besch****** Auslagerungsdatei vornehmen.
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: e12b5000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: bf9c5e66, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: e12b5000
CURRENT_IRQL: 2
FAULTING_IP:
ati2dvag!DrvEnableDirectDraw+64
bf9c5e66 8b5e04 mov ebx,[esi+0x4]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 80530cf5 to 804f40ed
STACK_TEXT:
afbc637c 80530cf5 0000000a e12b5000 00000002 nt!CcSetValidData+0x8d
afbc6398 00000000 afbc6664 851557d8 f76c65e5 nt!ViFreeToContiguousMemory+0x51
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
ati2dvag!DrvEnableDirectDraw+64
bf9c5e66 8b5e04 mov ebx,[esi+0x4]
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: ati2dvag!DrvEnableDirectDraw+64
MODULE_NAME: ati2dvag
IMAGE_NAME: ati2dvag.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 417efb7d
BUCKET_ID: 0xD1_ati2dvag!DrvEnableDirectDraw+64
Followup: MachineOwner
Danke für eure Mühe.
StillPad
06.01.2005, 15:31
Ich würde einfach mal SP 2 installieren.
Einige Spiele wie Riddick brauchen das z.b.
Frage an share the pain
Funktioniert es nun bei dir? Wenn ja was hast du denn unternommen??
Ich habe eine Lösung für dieses Problem in einem anderen Forum gefunden. Schaut euch das mal an:
http://www.winfuture-forum.de/index.php?showtopic=29313&st=30
Mir hat es geholfen. Mein Rechner läuft jetzt.
vBulletin v3.5.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.