Blue Screen przy starcie


(Krychaelk) #1

Witam !

Mam problem od wczoraj niestety wyskakuję mi pewien ten sam blue screen od razu przy starcie. Jedynym sposobem na korzystanie z komputera to odpalenie F8 i wybranie trybu windowsa z ostatnią dobrą konfiguracją. Jest jakiś sposób by to naprawić czy pozostał już tylko format ?

bluescreenxk.th.jpg

Microsoft (R) Windows Debugger Version 6.6.0003.5

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

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040

Debug session time: Fri Nov 4 16:34:36.437 2011 (GMT+1)

System Uptime: 0 days 0:01:30.984

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

* 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

....

Unable to load image ztmepwbumivvs1.sys, Win32 error 2

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

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

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

* *

* Bugcheck Analysis *

* *

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


Use !analyze -v to get detailed debugging information.


BugCheck 24, {1902fe, f8a4f94c, f8a4f648, f4e9d1f2}


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


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

*** ERROR: Module load completed but symbols could not be loaded for Ntfs.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 : ztmepwbumivvs1.sys ( ztmepwbumivvs1+d1f2 )


Followup: MachineOwner

---------

(abrakadabra77) #2

Przejedź dysk za pomocą chkdsk /f a następnie chkdsk /r. Masz coś namieszane z partycją ewentualnie "sypie" ci się dysk .


(Krychaelk) #3

Chyba nie mogę tego zrobić. :?

chdsk.th.png

Ten dysk F to jest u mnie dvd- rom.


(system) #4

Wybierz T (tak) i restart komputera!


(Krychaelk) #5

I nic się nie dzieje,może dlatego że muszę wchodzić do windowsa takim sposobem jak opisałem w 1 poście.