znowu blue screen :/
15 Lis 2008, 18:38
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini111508-02.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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Sat Nov 15 17:09:53.656 2008 (GMT+1)
System Uptime: 0 days 4:20:23.236
*********************************************************************
* 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 nv4_disp.dll, Win32 error 0n2
*** 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, {8839cb61, 1, bfa69eb9, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : nv4_disp.dll ( nv4_disp+94eb9 )
Followup: MachineOwner
---------
powie mi ktos czemu znowu mi screena wywalilo?? ostatnio to byla zapora nvidi a teraz jak gralem w san andreas i wychodzilem z gry to mnie znowu wywalilo, i tak 2 razy z rzedu
odczyta ktos ten blad??
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini111508-02.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 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
Debug session time: Sat Nov 15 17:09:53.656 2008 (GMT+1)
System Uptime: 0 days 4:20:23.236
*********************************************************************
* 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 nv4_disp.dll, Win32 error 0n2
*** 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, {8839cb61, 1, bfa69eb9, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : nv4_disp.dll ( nv4_disp+94eb9 )
Followup: MachineOwner
---------
powie mi ktos czemu znowu mi screena wywalilo?? ostatnio to byla zapora nvidi a teraz jak gralem w san andreas i wychodzilem z gry to mnie znowu wywalilo, i tak 2 razy z rzedu
odczyta ktos ten blad??
Re: znowu blue screen :/
15 Lis 2008, 20:07
[quote]Probably caused by : nv4_disp.dll[/url]
System uwalił sterownik NVIDII od karty graficznej.
System uwalił sterownik NVIDII od karty graficznej.
Re: znowu blue screen :/
15 Lis 2008, 20:36
cosik_ktosik napisał(a):Probably caused by : nv4_disp.dll[/url]
System uwalił sterownik NVIDII od karty graficznej.
czyli jeszcze raz zainstalowac sterownik??
Re: znowu blue screen :/
15 Lis 2008, 20:54
Albo jakiś inny. Jaką posiadasz kartę graficzną oraz jaką wersję sterowników do niej?
Po raporcie widzę, że chodzi o system WinXP SP3, zgadza się?
Po raporcie widzę, że chodzi o system WinXP SP3, zgadza się?
Re: znowu blue screen :/
15 Lis 2008, 22:58
cosik_ktosik napisał(a):Albo jakiś inny. Jaką posiadasz kartę graficzną oraz jaką wersję sterowników do niej?
Po raporcie widzę, że chodzi o system WinXP SP3, zgadza się?
tak jest mam neta na starym kompie a ten nowy sluzy tylko i wylacznie do gier i filmow, moja grafa na tym kompie to gf 6600le 128mb, w mendrzeze urzadzen pisze ze wersja sterownika to 7.7.7.4, jest stary bo ma date 07.08.2005
wiec co z tym zrobic?? sciagnac owy z nvidii?
Re: znowu blue screen :/
16 Lis 2008, 00:16
Tak, dajmy na to wersję 93.71: http://www.nvidia.pl/object/winxp_2k_93.71_pl.html
Re: znowu blue screen :/
16 Lis 2008, 11:42
zainstalowalem ten nowy sterownik i narazie jest ok 
a jak wczesniej odinstalowalem ta zapore nvidii to powinienem jakas inna zainstalowac??
w tym nowym steroniku nie widze zadnej zapory wiec widocznie jej nie ma to raczej nie trzeba znowu odinstalowywac
a jak wczesniej odinstalowalem ta zapore nvidii to powinienem jakas inna zainstalowac??w tym nowym steroniku nie widze zadnej zapory wiec widocznie jej nie ma to raczej nie trzeba znowu odinstalowywac
Re: znowu blue screen :/
16 Lis 2008, 13:27
Jakąś inną zaporę zainstaluj. Ja np polecam Comodo Firewall.