Problem z Bioshockiem i Crisisem

Sebastian010686 [ Junior ]

Bioshock to orginał a Crysis grałem w demo z gazety i robiło się to samo co z Bioshockiem.

DJ Pinata [ Red Bull Racing ]

W innych grach się tak robi? Sprawdź.

Sebastian010686 [ Junior ]

Grałem tylko w jedną starszą gre na tym kompie i nic się nie robiło ale grałem krótko.Czemu tak się dzieje? Chce normalnie pograć w Bioshocka.

24.12.2007

21:50

[6]

Arxel [ Legend ]

Stery najnowsze? DX także?

Ściągnij ten program:

(na dole wybierasz system, który posiadasz)

Następnie za jego pomocą otwórz plik
C:\WINDOWS\Minidump\Mini122207-01.dmp
(powinien tam być, jeśli go nie ma to ten do którego wcześniej podałeś ściezkę)

Aby otworzyć plik kliknij File -> Open Crash dump file... (czy jakoś tak).
Później będzie jakiś komunikat - naciśnij nie.

Po chwili powinieneś dostać loga odnośnie błędu... Skopiuj go tutaj... Nie pamiętam dokładnie gdzie jest napisane, który dokładnie plik jest odpowiedzialny za dany błąd.

fresherty [ Jimi Hendrix Rules! ]

Majstrowałeś coś w BIOSie, bawiłeś się w OC? Jaki >dokładnie< masz model karty?

Ściągnij też Everesta, odpal w tle i ustaw zapisywanie logów temperatur.

Sebastian010686 [ Junior ]

Tak stery i DX najnowsze. Karta to NVidia Geforce 8600GTS.

fresherty [ Jimi Hendrix Rules! ]

Ponawiam pytanie - bawiłeś się w podkręcanie procesora/karty graficznej?
Jaki KONKRETNIE model Gf8600GTS masz? (producent mile widziany)

Takie objawy jak Ty miałem po ustawieniu zbyt małego napięcia na CPU...

Sebastian010686 [ Junior ]

Nic nie robiłem.To nowy komputer ma z miesiąc. Karta Gigabyte GeForce 8600GTS 256MB

Conath [ Generaďż˝ ]

sprawdz temperatury karty graficznej (np. programem riva tuner, chociaz w opcjach sterownika tez bedzie)

fresherty [ Jimi Hendrix Rules! ]

Ściągnij program Everest, włącz, przejdź do Plik -> Ustawienia -> Logging (na samym dole listy po lewej stronie okienka, ustawień) -> zaznacz "Log sensor readings to HTML log file:" -> Kliknij [...] po prawej stronie, zaznacz pulpit i w nazwie jakąś nazwe dla pliku, np. "test".

Włącz grę i poczekaj aż się zawiesi, zrestartuj komputer i zobacz najnowszy plik z tych, które pojawią Ci się na pulpicie. Wrzuć go na rapidshare'a albo gdziekolwiek tam chcesz i daj link tutaj... W tym pliku zapisane będą dane Twojego komputera sprzed awarii - temperatury CPU, GPU, chipsetu plyty głównej, dysku twardego, napięcia i inne takie cuda.

Byłoby dobrze gdybyś z tego samego programu raport także tutaj wrzucił (po uruchomieniu klikasz na przycisk 'Raport', 3 razy na dalej, zapisz do pliku, zapisujesz, wrzucasz ten pliczek na serwer).

To powinno dać nam jako taki obraz sytuacji.

Conath -> Riva Tuner z tego co pamiętam nie pozwala zapisać loga sekunda po sekundzie, a nam potrzebna raczej temperatura GPU w stresie. Bioshock i Crisis to wymagające tytuły więc... ;)

Sebastian010686 [ Junior ]

Tak pisze debuger o tym pliku C:\WINDOWS\Minidump\Mini122207-01


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


Loading Dump File [C:\WINDOWS\Minidump\Mini122207-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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sat Dec 22 21:55:48.921 2007 (GMT+1)
System Uptime: 0 days 0:32:43.631
*********************************************************************
* 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
Loading unloaded module list
...........
Unable to load image torususb.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for torususb.sys
*** ERROR: Module load completed but symbols could not be loaded for torususb.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, ‹c0000047, 804fcc24, ba5448b0, ba544900›

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : torususb.sys ( torususb+57d8 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 804fcc24, The address that the exception occurred at
Arg3: ba5448b0, Exception Record Address
Arg4: ba544900, Context Record Address

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

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 447563b2

EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - Podj

FAULTING_IP:
nt+25c24
804fcc24 85db test ebx,ebx

EXCEPTION_RECORD: ba5448b0 -- (.exr 0xffffffffba5448b0)
ExceptionAddress: 804fcc24 (nt+0x00025c24)
ExceptionCode: c0000047
ExceptionFlags: 00000001
NumberParameters: 0

CONTEXT: ba544900 -- (.cxr 0xffffffffba544900)
eax=00000000 ebx=00000002 ecx=00000000 edx=00000000 esi=8914390c edi=00000003
eip=804fcc24 esp=ba544bdc ebp=ba544bf0 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000246
nt+0x25c24:
804fcc24 85db test ebx,ebx
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from b67077d8 to 804fcc24

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ba544bf0 b67077d8 8914390c 00000000 00000001 nt+0x25c24
ba544c28 b671416e 00544c38 891432c0 8910a000 torususb+0x57d8
ba544c48 b6712d33 ba544c68 00000001 00000002 torususb+0x1216e
ba544c94 b6743624 ba544d10 00070005 ba544cc4 torususb+0x10d33
ba544cac b673c2d8 ba544d10 ba544cc4 00000005 torususb+0x41624
ba544d24 b674a893 00000000 890f729c ba544d4c torususb+0x3a2d8
ba544d34 b6747d37 00000000 ba544d68 896dfe84 torususb+0x48893
ba544d4c b6742c83 00000000 890ed010 80562920 torususb+0x45d37
ba544d78 b6742b82 890ed010 ba544da8 b670969d torususb+0x40c83
ba544d84 b670969d 890ed010 00000000 00000000 torususb+0x40b82
ba544da8 b670bfec 805ce794 896c453c 00000000 torususb+0x769d
ba544ddc 805450ce b670bfe0 896c453c 00000000 torususb+0x9fec
00000000 00000000 00000000 00000000 00000000 nt+0x6e0ce


FOLLOWUP_IP:
torususb+57d8
b67077d8 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: torususb+57d8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: torususb

IMAGE_NAME: torususb.sys

STACK_COMMAND: .cxr 0xffffffffba544900 ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

Sebastian010686 [ Junior ]

Taki komunikat wyskakuje po resecie samoistnym kompa podczas grania.

25.12.2007

18:09

[15]

Arxel [ Legend ]

Probably caused by : torususb.sys

Wyszukaj ten plik na dysku i powiedz z czego - jakiego programu - on jest

Na necie pierwsze co wyłapałem to:

Could not read faulting driver name
Probably caused by : torususb.sys ( torususb+5e31 )

this message relates to the adsl modem.

try disconnecting modem, install usb drives(if not installed already), and then drives for modem, check what happens.

If system worked prior to windows reinstallement it should work after. Maybe a driver conflict

Z czego masz neta? Może jakiś konflikt sterowników od modemu... :)

Sebastian010686 [ Junior ]

Plik torususb.sys to jest C:\Program Files\ZTE ZXDSL 852\Disck1
C:\WINDOWS\system32\drivers


Czyli ZTE ZXDSL 852 to jest modem neostrady który używam w domu.
I chyba sterowniki do niej.

Conath [ Generaďż˝ ]

Riva Tuner z tego co pamiętam nie pozwala zapisać loga sekunda po sekundzie

ale maluje fajne wykresiki, moze udaloby mu sie zrobic alt-tab przez zwiecha:)
btw Jimi Hendrix Rules! - slyszales Little Wing w wersji instrumentalnej? 6 minut poezji:)

fresherty [ Jimi Hendrix Rules! ]

Conath -> Mam chyba gdzieś na dysku nawet :)

Co do problemu - odinstaluj modem neo, skasuj sterowniki, sprawdź czy problem występuje nadal. Jak nie to (bijcie jak musicie, ale to cholerstwo często się chowa po kątach i trudno je wywabić) przeinstaluj system i pograj na 'czystej' instalacji ze sterownikami karty graficznej i dx-em (nic zbędnego). Jeśli nadal problem będzie występował - szukamy dalej. Nadal obstawiam że to chłodzenie karty graficznej lub napięcie na procku.