Bsod I Reset Kompa I Netu

[zetor]

Witam,

od pewnego czasu mam regularne BSOD-y lub po prostu zatrzymanie internetu. Mam neostradę na usb SpeedTouch 330.

Moja konfiguracja:

Płyta: Gigabyte GA-M52L-S3; Mikroukład płyty głównej: nVIDIA nForce 6100-4xx, AMD Hammer

Procesor: DualCore AMD Athlon 64 X2, 3800+

RAM: 2 x 1 GB (DDR2-800 DDR2 SDRAM) GoodRAM Dual chanel

 

Płytę z procesorem kupiłem niedawno i od początku mam problemy. Zarówno na XP Sp 2 jak i Sp3. Visty nie chcę instalować, bo nie podoba mi się.

Ram jest nowy, więc to raczej nie to. Gdzieś znalazłem info, że być może to problem sterownika NVidia dla Usb i 2 GB ramu, ale nie znalazłem rozwiązania. Kończą mi się pomysły żeby razwiązać problem. Proszę o pomoc.

A to wydruk zrzutu pamięci:

 

Microsoft ® Windows Debugger Version 6.10.0003.233 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini010309-01.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) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Sat Jan 3 21:59:12.968 2009 (GMT+1)

System Uptime: 0 days 0:09:24.658

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

* 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 USBPORT.SYS, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck FE, {5, 899850e0, 10de03f1, 89376960}

 

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

 

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

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

 

Followup: MachineOwner

---------