Re: Wielki Problem z Blue Screenem


(Mazurek10) #1

Witam. Posiadam Windows XP Home Edition oczywiście oryginalny i mam problem z Blue Screenami. Oto plik mindup

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

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

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620

Debug session time: Sun Jun 1 19:37:29.578 2008 (GMT+2)

System Uptime: 0 days 0:08:18.150

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

* 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

............

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {ffffff22, 2, 0, f6c54926}

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

*** WARNING: Unable to verify timestamp for hal.dll

*** ERROR: Module load completed but symbols could not be loaded for hal.dll

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

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

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

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

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

Wydaje mi sie że jest to problem z zasilaczem. Komputer ma 5 lat i ani razu nie był wymieniany. Zasilacz ma 300W. Proszę o pomoc.

W dniu 01.06.2008 , o godzinie 21:21 został dopisany post przez bartekzmc

Naprawdę bardzo proszę o pomoc, bo nie wiem co mam robić :(:frowning:


(Cosik Ktosik) #2

Jaki to zasilacz tj producent/model?

Plik torususb.sys pochodzi od modemu neostrady. Zapoznaj się może z tym wątkiem: viewtopic.php?t=203678

Błąd 0x000000D1 wskazuje na problem ze sterownikiem.


(Mazurek10) #3

Temp Płyta Główna 45 stopni

Samsung SV0401H 30 stopni

Wartość Napięć

Napięcie rdzenia procesora 1.49 V

  • 2,5 V 2.54 V

+3.3 V 2.54 V

  • 5 V 3.01 V

  • 12 V wacha się od 8 V do 4 V

V Bat baterii CMOS 3.34 V

W dniu 01.06.2008 , o godzinie 21:40 został dopisany post przez bartekzmc

Firam Codegen 300W Model 250XA1. Chodzi o sterowniki z karty graficznej czy z modemu ??


(Cosik Ktosik) #4

Napięcia sprawdź everestem ultimate: http://dobreprogramy.pl/index.php?dz=2& ... +4.50.1330

Zasilacz nadaje się zapewne do wymiany, więc zmieniłbym go.

Z tego co wiem (neostrady nie mam) to plik torususb.sys pochodzi właśnie od neo, a co za tym idzie modemu. Być może to przez zasilacz problem Masz z USB i urządzeniami do niego podłączonymi.


(Mazurek10) #5

No własnie sprawdzałem i go wysłałem tym programem. I jak moge usunąć bądź zmienić tenm plik torususb.sys???


(Cosik Ktosik) #6

Jeżeli to są napięcia z everesta ultimate, to sprawdź jeszcze w Biosie lub miernikiem (jeśli posiadasz). Jeżeli tam napięcia będą podawane takie same, to najpierw zmień zasilacz.

Potem, jeżeli nadal będzie kicha, odinstaluj modem, przeczyść programem ccleaner i zainstaluj najnowsze stery do tego modemu.


(Asterisk) #7

Zapoznaj się proszę z tą stroną i zmień tytuł na

konkretny. Inaczej temat poleci do śmietnika.