big graphics issue(beer in it for whoever can help)

shadowcreaper

shadowcreaper

shadowcreaper

Associate
Joined
29 Jul 2008
Posts
692
I got a pretty big graphic issue and theres a beer in it for whoever can help me fix it.

Bassically it started when i was playing a game:company of heroes/tales of valor.

i crash/blackscreen/boxyscreen/bluescreen, when i join a game then while i waiting for game to begin or people to join it happends and i have to manualy reboot.

i have no idea why this is, but i think it graphics card issue.

hopefully somone can help.
or give advise which could help me figue wtf going on as this happends nearly every time i try play.

specs are:

e8400 3.0(no overclocking)watercooled
4gb RAM ddr2
sapphire 4870
vista 64
500 sAMSUNG

i cant post my dxlog or warning log as there a limit on characters for some reson--.--
 
i cant see any need to do so as what will that achieve. as the normal/orginal version worked fine..i would like to find the cause before i do anything or i not going to be fixing anything.
 
do you recon i can just uninstall tales of valor then and leave company of heroes alone?

or do i need to uninstall EVERYTHING......

i say this as the game does have a shiiiiii load of patchs and thus takes agges to patch upto date.

any info on what i should do then if i was going to uninstall would be helpfull
 
i dout it power i got 620 and running other games seem fine.

still not sure why it doing this, maybe files didnt install properly or something looks like a full uninstall reinstall needed.

but to make sure this doesnt happen again can you give some advise:

when i uninstall this game is uninstalling it from "add/remove" enough to clear it out?

or do i need to uninstalll in a special way for company of heroes /tales of valor, sinse i dont want to do a bad uninstall then find when i reinstall i have same issue as before.
 
well the uninstall didnt work but i pretty much relised tht.

i still got this problem and it really bugging me out.

here the exact details maybe you can help:

Problem

When i play company of heroes tales of valor, when i join a game(not the game lobby) and then as i wait for people to join/game to start i then get a blank screen/black screen and the music/sound goes loop,

i then have to manually reboot pc.

i get this now every time i try join a game and are waiting for it to begin.( though sometimes when i first play/start pc i can manage to play 1 game then it all starts)

this ISNT DURING THE ACTUALLY PLAYING OF GAME.


Any ideas then what can i do?

What i know

it ISNT THE TEMP, i checked the CPU+GPU and both are fine.

drivers: i recently updated them to 9.4 from 9.4 and have uninstalled and cleaned them so i dout it them.



so guys.... wtf do i do now i really having a hard time trying to work this out as i get 0 error message or any sign of problems.

what can i do?
 
well it 100% just this game i been on crysis and bf2, project reality empire total war and all fine.

it just seems to be this lobby page which issue with.

I found that with some Sapphire 4870s they had dodgy bios which would cause them to downclock to really odd clock speeds and crash.

Cards with this serial number are known to have the issue.
PN: 188-01E85-001SA // SKU#:11133-00-XXR
Click to expand...

stupid question how do i find out my serial number then....
 
it wied how i cant find my CCC..

but in

C :drive/ATI/Support/9.4_vista 64_win7_64/driver/packages/Apps/CCC

I have a loads of files that seem to relate to CCC:confused: like:

Branding
core-implementation
core-preinstall
core-static
graphics full existing

ect ect

would i be able to find CCC there maybe or something there which could help????

or should i just uninstall 9.4..again then use driver cleaner pro to delte al the ATI related files then reinstall..again and maybe it be better????

4th time lucky or something,

hopefully you can help
 
^^ no way...

i not going to reinstall windos just because 1 game doesnt seem to work properly.and having to reinstall every programme again a real bitch..along with all the drivers and devices..

i 100% sure it 100% games fualt, somone told me also that DOW2 another relic game had simular issues with loading crashes ect and relic didnt fix that untill a good while after release.

i think relic has very poor forum tech support yet they really the only ones who could help in telling you if it the game issue or not, typically they tend not to tell you anything about game being wrong for covering themselfs..... sad really.


i did a windos dias heres the result what you recon any thing sticking out then.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini042009-01.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 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`02215000 PsLoadedModuleList = 0xfffff800`023dadb0
Debug session time: Mon Apr 20 01:59:58.216 2009 (GMT+1)
System Uptime: 0 days 8:45:22.070
************************************************** *******************
* 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 0n2
*** 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 User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image watchdog.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for watchdog.sys
*** ERROR: Module load completed but symbols could not be loaded for watchdog.sys
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8007c494e0, fffffa6002221574, 0, 0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** *******************
* 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+ *
************************************************** *******************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
Unable to load image atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** *******************
* 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+ *
************************************************** *******************
************************************************** *******************
* 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+ *
************************************************** *******************
Probably caused by : atikmdag.sys ( atikmdag+12574 )

Followup: MachineOwner
---------
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom