Masowy atak błędów


(Gerrard845) #1

Witam.Musze napisać ten temat ponieważ nie mam juz cierpliwości do mojego nowego komputera.Kupiłem ten nowy komputer i uwolnić się od mojego straego grata gzdie wszystko sie sypało i miałem nadzieje ze na nowym komputerze wszystko bedzie normalnie.Jednak oczywiście znając moje szczęście jeszcze gorzej jest na nowym komputerze.Więc tak.Od ostatnich 2 formatów strasznie zwariował mi komputer.W większości gier wyskakuję mi co chwila Raport o błędach(GTA 4 po misjii lub w trakcie jej,Crysis tez podczas misji,PES podczas meczy występują również BSOD'y).Nawet w MMORPG mam problemy.Ostatnio gdy grałem w grę o nazwie "Maple Story" gdy biłem jednego z bossów dostałem BSOD'a)Oto log:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

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

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Fri Dec 25 11:44:55.984 2009 (GMT+1)

System Uptime: 0 days 0:21:23.746

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

* 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 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 ks.sys, Win32 error 0n2

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

Unable to load image portcls.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 100000D1, {2, 2, 0, b71e5417}


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

******

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

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

******

******

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

******

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

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

******

******

***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 nv4_mini.sys, Win32 error 0n2

*** 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!_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 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 argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Probably caused by : ks.sys ( ks+417 )


Followup: MachineOwner

---------

Od czego to może się wszystko dziać?Co ja moge na to poradzić?Licze na szybkie odpowiedzi


(Piotr24 Power) #2

Przeinstaluj DirectX, jak to nie pomoże usuń sterowniki od karty dźwiękowej, zrestartuj komputer i zainstaluje ponownie...

Wgraj najnowsze aktualizacje do systemu.... Szczególnie Service Pack 1 (w nim Microsoft naprawił ten sterownik), bo widzę, że korzystasz z Visty...

Informacje o pliku:

The file ks.sys is a Microsoft Kernel CSA Library system driver. The primary cause of the BSOD ks.sys was known by Microsoft to have some problems and was apparently corrected in Vista SP1.

(Gerrard845) #3

Nie korzystam z Visty ale z Windows XP