BSOD Stop 0x000000D1


(Lordek123) #1

Witam,

3 dni temu kupiłem nowy procesor amd64 4000+ socket 939 i mam taki problem, że

gram sobie w "Counter-strike" daje alt tab i jak chce wrócić z powrotem do gry wyskakuje mi blue screen z jakimś niezrozumiałym dla mnie błędem pliku "nv4_mini.sys"

Wcześniej nie miałem takich problemów na procesorze amd64 3000+.

konfiguracja:

proc - amd64 4000+

płyta glówna - gigabyte ga-k8u

karta graficzna - GALAXY geforce 7600gt AGP

zasilacz - TAGAN 400W

ram - 1gb GOODRAM

temp procesora ~ 20 C

temp karty graficznej ~ 38 C


Stop 0x000000D1 (0xF7B57020, 0x00000002, 0x00000001, 0xF6DBF6E6) to wyskakuje m.in


log:

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

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0

Debug session time: Wed Dec 19 17:15:04.437 2007 (GMT+1)

System Uptime: 0 days 0:28:14.942

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f7a52020, 2, 1, f6db4cc6}

***** 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 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 : nv4_mini.sys ( nv4_mini+86cc6 )

Followup: MachineOwner


Błagam, jeżeli ktoś wie jak pomóc to byłbym bardzo wdzięczny.

Z góry dziękuje i pozdrawiam.


(Pan Ziombl) #2

przeinstaluj sterowniki od karty graficznej


(Lordek123) #3

Próbowałem, nic nie dało :frowning:


(Pan Ziombl) #4

zainstaluj najnowsze sterowniki do mobo, być może update biosu też coś pomoże


(Lordek123) #5

Przepraszam ale nie jestem zbyt kumaty :smiley: co to jest mobo :P? Chodzi Ci o płytę główną? A bios mam najnowszy do mojej płyty F5.


(Pan Ziombl) #6

tak. płyta główna. do karty masz najnowsze stery? może na stronie producenta jest coś nowszego?


(Artos) #7

skoro zmieniłeś tylko CPU... to ja stawiam na płyte główną... w tym wypadku GFX nie powinna mieć nic do rzeczy szczególnie skoro wcześniej było ok

  • nowe stery do MB ew. aktualizacja BIOS

  • ew. sprawdz ustawienia w BIOS dla CPU może coś z napięciami albo coś nie wykrywa CPU jak powinno :wink:


(Lordek123) #8

Wczoraj zrobiłem formata i wszystko instalowałem od nowa, najnowsze stery do mobo i sterowniki do karty 93.71,

niestety to nie pomogło.Dziwne jest tylko jedno, że blue screen wyskakuje tylko w tym momencie kiedy wracam z windowsa do cs'a nie wyskakuje mi w żadnych innych grach ani podczas normalnej pracy.


(Piotr Wik) #9

a jaki systemik?


(Lordek123) #10

problem rozwiązany, winne były sterowniki do proca.


(Piotr Wik) #11

procek ma sterowniki :shock: