x-kom hosting

BSOD podczas włączania gier

acess
utworzono
utworzono

Witam

mam problem z BSODEM po uruchomieniu gier:

[code]
Microsoft (R) Windows Debugger Version 6.6.0003.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112410-17331-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 Vista Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`0325c000 PsLoadedModuleList = 0xfffff800`03499e50
Debug session time: Wed Nov 24 00:30:30.390 2010 (GMT+1)
System Uptime: 0 days 0:58:45.200
*********************************************************************
* 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
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004c96028, f60c2000, 135}

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

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

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

Unknown bugcheck code (124)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: fffffa8004c96028
Arg3: 00000000f60c2000
Arg4: 0000000000000135

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

MODULE_NAME: nt

FAULTING_MODULE: fffff8000325c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_BETA2

BUGCHECK_STR: 0x124

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800032cc740

STACK_TEXT:
fffff880`02f6ba88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt+0x70740


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

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


[/code]

moj sprzet to:
AMD X4 955 nie krecony
ram 4gb goodram 1600
zaislacz 500wat modxstream
grafika ATI 5770 hawk

raazor90
komentarz
komentarz

Brak symboli !!! bez tego nie mogę nic odczytać
Wykonaj: [quote][b]UWAGA:[/b] Jeśli na ekranie pojawi się komunikat:

Cytat

[quote]***** Kernel symbols are WRONG. Please fix symbols to do analysis.[/quote]

Oznacza to, że musimy [b]pobrać symbole[/b] do swojego systemu dzięki którym odczytamy [b]w całości[/b] plik minidump - na tym etapie jest on niekompletny i może wskazywać nie ten plik co trzeba.

Zamykamy Debuggera. Po ponownym jego uruchomieniu klikamy [i]File[/i] -> [i]Symbol File Path[/i] -> wpisujemy:
[b]SRV*c:\symbols*http://msdl.microsoft.com/download/symbols[/b]

Następnie wciskamy [ctrl] + [D] i wskazujemy znów nasz plik minidump. Trzeba poczekać aż Debugger ściągnie sobie wszystkie symbole i przeanalizuje cały plik.
Należy pamiętać że ten proces może nieco potrwać - symbole mogą ważyć nawet ponad 10MB, także trzeba uzbroić się w cierpliwość.

6. Wklejamy część [b]minidumpa[/b], o której mowa, na forum.[/quote]

Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!

Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.

×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Strona wykorzystuje pliki cookies w celu prawidłowego świadczenia usług i wygody użytkowników. Warunki przechowywania i dostępu do plików cookies możesz zmienić w ustawieniach przeglądarki.