Skocz do zawartości

Zarchiwizowany

Ten temat jest archiwizowany i nie można dodawać nowych odpowiedzi.

KMASBIn

Dragon Age: Początek

Polecane posty

Witam,

Mam problem z grą Dragona age: Początek a mianowicie kiedy próbuje wyjść z gry to następuje ekran śmierci i po tym restart

Mam najnowszego patcha 1.01

Mój komp to :

system operacyjny:

Windows XP Professional Dodatek Service Pack 3

procesor: Intel® Core2 Duo CPU E6550 @ 2.33GHz (2 CPUs)

pamięć RAM: 2046MB RAM

karta graficzna: NVIDIA GeForce 8600 GTS - 512.0 MB

sterowniki grafiki: Najnowsze ze strony Nvidi

karta muzyczna: Realtek HD Audio output

directX: Z płyty Gry

Link do komentarza
Udostępnij na innych stronach

Ekran śmierci?Blue screen(oto Ci chodziło)?

Było coś napisane czy tylko czarny ekran i reset.Najpierw wyłącz w panelu reset kompa podczas błędu krytycznego i zanotuj to tam będzie napisane i daj to na forum ;).

EDIT:Gra oryginał?

Link do komentarza
Udostępnij na innych stronach

Tak gra jest orginalna zamówiona na gram.pl, a co do tego komunikatu to :

Microsoft ? Windows Debugger Version 6.6.0003.5

Copyright ? Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini110709-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 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 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Sat Nov 7 12:15:53.359 2009 (GMT+1)

System Uptime: 0 days 1:40:57.065

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

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

Loading unloaded module list

..........

Unable to load image nv4_disp.dll, Win32 error 2

*** WARNING: Unable to verify timestamp for nv4_disp.dll

*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e5135a48, 0, bd1c4b36, 1}

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

*** ***

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

Probably caused by : nv4_disp.dll ( nv4_disp+1b2b36 )

Followup: MachineOwner

---------

Dodam że jeszcze dziś rano instalowałem od nowa sterowniki do karty graficznej

Link do komentarza
Udostępnij na innych stronach



  • Kto przegląda   0 użytkowników

    • Brak zalogowanych użytkowników przeglądających tę stronę.
×
×
  • Utwórz nowe...