Problem z grami!

BugCheck 1000008E, {c0000005, bfa69083, ba5d19f8, 0}

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

*** ***

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

Unable to load image ndisuio.sys, Win32 error 2

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

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

Probably caused by : nv4_disp.dll ( nv4_disp+96083 )

Followup: MachineOwner


i jeszcze inna sprawa:

Czy po tych BSOD-ach są błędy w Podglądzie zdarzeń?

Start> Panel sterowania>Wydajność i konserwacja>Narzędzia administracyjne lub Start>>Uruchom>>eventvwr

W zakładce System lub Aplikacje szukasz wpisów zaznaczonych czerwonym znaczkiem. Następnie PPM i wybieramy Właściwości.Jak coś będzie ale mniej więcej z tego dnia i godziny co był błąd, wklejasz tutaj :slight_smile:

BugCheck 1A, {41284, 8dfd001, 5d8b, c0883000}

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


Tak jak myślałem problem ze sterownikami nVidia pobierz te stery co ci pisałem czyli 91.47

BugCheck 10000050, {c48b8da0, 0, bf9c3fd8, 0}

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

*** ***

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

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

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

Probably caused by : dxg.sys ( dxg+2fd8 )

Złączono Posta : 20.02.2007 (Wto) 21:33

BugCheck 24, {1902fe, f7a47960, f7a4765c, 8054a51a}

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

Unable to load image aswMon2.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for aswMon2.SYS

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

*** ***

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

Probably caused by : Ntfs.sys ( Ntfs+637f )

Złączono Posta : 20.02.2007 (Wto) 21:34

BugCheck 4E, {2, 33a81, 3ff9f, 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 ***

*** ***

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

Unable to load image Ntfs.sys, Win32 error 2

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

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

Unable to load image aswMon2.SYS, Win32 error 2

*** WARNING: Unable to verify timestamp for aswMon2.SYS

*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS

Probably caused by : aswMon2.SYS ( aswMon2+83c )

tu masz link do sterów

http://www.nvidia.pl/object/winxp_2k_91.47_pl.html

chyba że masz gdzieś na płytce to odinstaluj stare i zainstaluj nowe

to jest wszystko ale jest mały problem bo miałem te stery i przy graniu w most wanted było troszke lepiej bo chwilke dłuzej mogłem pograc ale po jakims czasie i tak działo sie to samo ;/

A to to jest od avasta jak masz to odinstaluj i sprawdz efekt

a w podgladzie zdarzen sa jakies błedy tylko nie jestem do konca pewien czy to te od gier ale chyba tak

A to to może oznaczać problem z kością DDR

Trochę tych błędów masz :mrgreen:

Złączono Posta : 20.02.2007 (Wto) 21:45

ale tego na 100% nie jestem pewny

Złączono Posta : 20.02.2007 (Wto) 21:46

wrzuć zobaczymy

ja radze ustawic plik stronicowania na ostatniej partycji najlepiej staly czyli 1500mb a na partycji z windowsem 2mb tylko mi to pomoglo bo mialem uszkodzony dysk. rowniez moze to byc wina zasilacza. jaka moc i firma

A to to chyba jest problem z directx

no błedów troche mam ;/ a swiezy system ;/ a teraz ta gra mi sie znowu zacieła i wyłaczyła z tym niebieskim oknem a w podgladzie zdarzen nic o tym nie ma

Trochę mi to wszystko podpada.Albo masz w kompie zamotane że tyle wywala błędów albo coś nie działa tak jak powinno.Spróbuj jeszcze to wszystko sprawdzić czyli stery,directxa,avasta,jak dalej będzie broić to nic innego nie pozostanie jak złożyć reklamację jak jest nowym komputerem.

Złączono Posta : 20.02.2007 (Wto) 22:01

to wrzuć tego świeżego minidumpa

BugCheck 1A, {41284, 8dfd001, 5d8b, c0883000}

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


Złączono Posta : 20.02.2007 (Wto) 22:09

no tez mnie denerwuje ten komp sam z siebie jakies dziwactwa se wymysla nie rozumiem tego mój stary poprzedni przez 7 lat nigdy mi niczego takiego nie wykazywał i chyba na tym sie skonczy ze bede musiał sie wybrac na reklamacje;/

w tym ostatnim dumpie tylko to było??

a jakies inne sterowniki moze jeszcze by dało rade czy nie ?? i sciagam nowego directx’a i jeszcze popróbuje ale raczej z tego nic nie bedzie ;/ a nie chce mi sie leciec z tym kompem do sklepu ale nie bede miał wyjscia bo tak dalej byc nie moze :slight_smile:

Złączono Posta : 20.02.2007 (Wto) 22:20

Microsoft ® Windows Debugger Version 6.4.0007.2

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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Mon Feb 20 19:59:02.140 2006 (GMT+1)

System Uptime: 0 days 1:05:06.723

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

* 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 unloaded module list

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 8dfd001, 5d8b, c0883000}

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


to jest cały ostatni dump

oczywiście że można tylko muszą być zgodne z twoją kartą :mrgreen: w sterownikach jest tak że trzeba wypróbować przetestować i powiedzieć czy się sprawdzają jak nie będą odpowiednie to wymienić na inne aż się znajdze te odpowiednie :slight_smile:

aha a skad mam je wziasc??

ja korzystam z wersji 91.47 i nie narzekam :roll: :slight_smile:

Złączono Posta : 20.02.2007 (Wto) 22:28

ze strony producenta

http://www.nvidia.pl/page/drivers.html

Złączono Posta : 20.02.2007 (Wto) 22:32

http://heil.pl/index.php?mode=download&id=188