Błąd systemu co jest nie tak?


(Lukasz102) #1

gram np w fear combat i po jakims czasie zamias dzwieku sa trzaski i jak wylacze gre to kom sie hibernuje. to jest kod bledu

BCCode : c2 BCP1 : 00000007 BCP2 : 00000CD4 BCP3 : 00000000

BCP4 : 888857C8 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

Złączono Posty : 04.02.2007 (Nie) 16:15

czy mam podac jakies informacje zeby otrzymac pomoc???


(Mail) #2

http://www.techimo.com/forum/showthread ... nextnewest

http://forum.tweakxp.com/forum/shwmessa ... eid=148740

by Google :wink:.


(Lukasz102) #3

dam cos takiego

Microsoft ® Windows Debugger Version 6.6.0007.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

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 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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20

Debug session time: Sun Feb 4 14:44:09.125 2007 (GMT+1)

System Uptime: 0 days 4:12:24.770

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

* 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 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 C2, {7, cd4, 0, 888857c8}

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for dxg.sys

*** ERROR: Module load completed but symbols could not be loaded for dxg.sys

*** WARNING: Unable to verify timestamp for nv4_mini.sys

*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.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!PVOID ***

*** ***

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

unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

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

*** ***

*** ***

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

*** ***

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

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

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

*** ***

*** ***

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

Cannot get _POOL_TRACKER_BIG_PAGES type size

Probably caused by : nv4_mini.sys ( nv4_mini+2b5d00 )

Followup: MachineOwner


Złączono Posty : 04.02.2007 (Nie) 16:35

nie czaje tego bo z ang jestem slaby :confused:


(Edlib) #4

podobno pomaga - odinstaluj w dodaj/usuń wszystko nvidii

wejdż z F8 i wybierz tryb vga

wyłącz wszystko antywirusa(skanery itd)

zainstaluj nvidię i wejdż normalnie


(Lukasz102) #5

ja teraz nie jestem w domu i nie mam jak sprawdzic :frowning: powiem jeszcze ze jak w grze wylacze dzwieki t omoge grac ile chce i po wylaczeni nie mam problemow...

Złączono Posta : 10.02.2007 (Sob) 9:24

RIXX

Wielkie dzieki juz jest ok nareszcie moge grac w Fear, a mam teraz ferie :slight_smile: