BlueScreen na Viscie podczas grania

[IAmDarkElf]

Co jakis czas (srednio raz na dzien) zdaza sie ze gra nagle sie zacina i wyskakuje bluescreen, potem komp sie restartuje i wyswietla sie komunikat windowsowy:

Podpis problemu:

Nazwa zdarzenia problemu: BlueScreen

Wersja systemu operacyjnego: 6.0.6002.2.2.0.768.3

Identyfikator ustawień regionalnych: 1045

Dodatkowe informacje o problemie:

BCCode: d1

BCP1: 00000004

BCP2: 00000002

BCP3: 00000001

BCP4: 8FD30BF4

OS Version: 6_0_6002

Service Pack: 2_0

Product: 768_1

Pliki pomagające opisać problem:

C:\Windows\Minidump\Mini110110-02.dmp

C:\Users\Kamil\AppData\Local\Temp\WER-42572-0.sysdata.xml

C:\Users\Kamil\AppData\Local\Temp\WERF3B0.tmp.version.txt

Przeczytaj nasze zasady zachowania poufności informacji:

http://go.microsoft.com/fwlink/?linkid=501...mp;clcid=0x0415

prosze o pomoc mozliwie szybka, co z tym zrobic?

[yojc]

Podaj pełną konfigurację komputera (w tym markę, model i moc zasilacza).

[IAmDarkElf]

Core2Duo 2,33 GHz

3 GB RAM

Vista

ATI Radeon HD 4670

zasilacz- nie mam pojecia

marka? - kupowany w Vobisie jezeli o to chodzi

[Murezor]

Zatem powinieneś rozkręcić obudowę i sprawdzić specyfikę swojego zasilacza - niewykluczone, że to właśnie wadliwy lub posiadający zbyt małą moc zasilacz jest przyczyną tego problemu. A ''marka'' w tym wypadku oznacza producenta zasilacza (i jest ona dość istotna, gdyż można po niej rozpoznać ''jakość'' danego sprzętu). Do zdiagnozowania problemu możesz także wykorzystać program Debbuger Windows, którego instrukcję (w wersji polskojęzycznej) znajdziesz tutaj.

[IAmDarkElf]

a co grozi jesli zbagatelizuje problem?

[Murezor]

Jeśli przyczyną problemu jest faktycznie zasilacz, to konsekwencje mogą być poważne - zasilacz może się spalić, a ponadto spowodować uszkodzenie innych podzespołów komputerowych (karta graficzna, płyta główna etc.). Bagatelizacja jest w tym wypadku bardzo niewskazana...

[IAmDarkElf]

ale ja zasilacz mam ten sam od poczatku kupna komputera, jedyne co w nim zmienialem to karta graficzna i dokupowalem ram

@EDIT!!

nie moge otworzyc pliku dump bo pisze ze nie mam do tego uprawnien ... co mam robic, pomocy!!

@EDIT2!!!

juz moge otworzyc, wystarczylo wlaczyc jako administrator, a teraz wyskoczyl mi taki plik:

Microsoft ® Windows Debugger Version 6.12.0002.633 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini110110-02.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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0x8261a000 PsLoadedModuleList = 0x82731c70

Debug session time: Mon Nov 1 09:54:18.980 2010 (UTC + 1:00)

System Uptime: 0 days 1:16:04.107

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

* 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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

.....

Unable to load image \SystemRoot\system32\DRIVERS\inspect.sys, Win32 error 0n2

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

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

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4, 2, 1, 8fd30bf4}

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

*** ***

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

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

*** ***

*** ***

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

*** ***

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

Probably caused by : inspect.sys ( inspect+1bf4 )

Followup: MachineOwner

---------

i teraz byloby fajnie jakby ktos mi to przetlumaczyl o co chodzi

[Murezor]

Ale nie zmienia to faktu, że zasilacz mógł ulec jakiemuś uszkodzeniu (przecież to tylko sprzęt...); ponadto zasilacze mogą psuć się po pewnym czasie użytkowania - nie musi to nastąpić od razu po zakupie.

Różnice w poborze energii pomiędzy kartami graficznymi mogą być znaczne - wprawdzie Radeon HD 4670 ma relatywnie niski pobór prądu, ale podanie dokładnej specyfiki zasilacza jest w tym wypadku bardzo wskazane...

[IAmDarkElf]

a moglbys mi wytlumaczyc ten jakze dlugi komunikat z debuggera?

dodatkowo jak wcisnalem analyze-v czy cos takiego to mi wyskoczylo takie cos:

Microsoft ® Windows Debugger Version 6.12.0002.633 X86

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini110110-02.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458

Machine Name:

Kernel base = 0x8261a000 PsLoadedModuleList = 0x82731c70

Debug session time: Mon Nov 1 09:54:18.980 2010 (UTC + 1:00)

System Uptime: 0 days 1:16:04.107

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

.....

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4, 2, 1, 8fd30bf4}

Unable to load image \SystemRoot\system32\DRIVERS\inspect.sys, Win32 error 0n2

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

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

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

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

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

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

Probably caused by : inspect.sys ( inspect+1bf4 )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 00000004, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000001, value 0 = read operation, 1 = write operation

Arg4: 8fd30bf4, address which referenced memory

Debugging Details:

------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82751868

Unable to read MiSystemVaType memory at 82731420

00000004

CURRENT_IRQL: 2

FAULTING_IP:

inspect+1bf4

8fd30bf4 ?? ???

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: League of Legen

TRAP_FRAME: a3afb180 -- (.trap 0xffffffffa3afb180)

ErrCode = 00000002

eax=00000000 ebx=870de210 ecx=8fd3f9a8 edx=00000000 esi=8fd3f9b0 edi=8551ce10

eip=8fd30bf4 esp=a3afb1f4 ebp=a3afb1fc iopl=0 nv up ei ng nz na pe nc

cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286

inspect+0x1bf4:

8fd30bf4 ?? ???

Resetting default scope

LAST_CONTROL_TRANSFER: from 8fd30bf4 to 82667fd9

STACK_TEXT:

a3afb180 8fd30bf4 badb0d00 00000000 829da70c nt!KiTrap0E+0x2e1

WARNING: Stack unwind information not available. Following frames may be wrong.

a3afb1f0 8551ce10 85b563c8 a3afb214 8fd307c8 inspect+0x1bf4

a3afb1fc 8fd307c8 8551ce10 85b56340 86f7d6d0 0x8551ce10

a3afb214 8aa107d7 85b56340 85b56340 00000000 inspect+0x17c8

a3afb234 8aa10720 85b56340 85b56340 00000000 ndis!ndisFilterSendNetBufferLists+0x8b

a3afb24c 8fd1e4a3 86f7d6d0 85b56340 00000000 ndis!NdisFSendNetBufferLists+0x18

a3afb2c8 8aa10869 86f7d340 85b56340 00000000 pacer!PcFilterSendNetBufferLists+0x233

a3afb2e4 8aadb3b5 85b56340 85b56340 00000000 ndis!ndisSendNBLToFilter+0x87

a3afb308 8ac69095 870d99b8 85b56340 00000000 ndis!NdisSendNetBufferLists+0x4f

a3afb350 8ac67f4a 870d9d70 00000000 00000000 tcpip!FlSendPackets+0x399

a3afb390 8ac67992 8accfcd0 00000000 00000000 tcpip!IppFragmentPackets+0x201

a3afb3c8 8ac67734 8accfcd0 a3afb4e4 616c7049 tcpip!IppDispatchSendPacketHelper+0x252

a3afb468 8ac6884c 00afb4e4 00000000 875eb798 tcpip!IppPacketizeDatagrams+0x8fe

a3afb5c8 8ac69e49 00000000 00000004 8accfcd0 tcpip!IppSendDatagramsCommon+0x604

a3afb5e8 8ac5c942 85aa5160 a3afb6e4 a3afb8a8 tcpip!IpNlpSendDatagrams+0x4b

a3afb830 8ac5ca69 85542578 85aa51d8 00000000 tcpip!UdpSendMessages+0xc07

a3afb844 826cceb4 a3afb8a8 a1420d7e a3afb8d0 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x13

a3afb884 8ac5ca3b 8ac5ca56 a3afb8a8 00000000 nt!KeExpandKernelStackAndCalloutEx+0xbd

a3afb8b4 8fc5fd86 87bdd9a8 a3afb8d0 8554fe18 tcpip!UdpTlProviderSendMessages+0x5e

a3afb8fc 8fc67a52 88a873a0 8554fe00 87d14878 tdx!TdxSendDatagramTransportAddress+0x206

a3afb918 8265e9c6 87063c50 8554fe18 8554fe18 tdx!TdxTdiDispatchInternalDeviceControl+0x5c

a3afb930 8fc746f9 87096c48 00000000 870e1fa4 nt!IofCallDriver+0x63

a3afb988 8fc74b31 87096d00 8554fe18 8554feac cmdhlp+0x26f9

a3afb9a4 8265e9c6 87096c48 8554fe18 870e1fa0 cmdhlp+0x2b31

a3afb9bc 8fc7c679 2c67f8dd 00000000 8554fed0 nt!IofCallDriver+0x63

a3afba10 8fc7c9ef 870e1f70 8554fe18 8554fed0 aswTdi+0x679

a3afba58 8265e9c6 87096c48 8554fe18 8554ff80 aswTdi+0x9ef

a3afba70 8fcb9914 2c657c6f 00000005 0709fd30 nt!IofCallDriver+0x63

a3afbad8 8fcae3d0 0709fd86 00000003 8fcae3d0 afd!AfdFastDatagramSend+0x5ba

a3afbc58 82860b4c 8541a701 00000001 0709fcf8 afd!AfdFastIoDeviceControl+0x3c1

a3afbd00 82862012 8705f698 000002a0 00000000 nt!IopXxxControlFile+0x2cf

a3afbd34 82664c7a 00000298 000002a0 00000000 nt!NtDeviceIoControlFile+0x2a

a3afbd34 77995e74 00000298 000002a0 00000000 nt!KiFastCallEntry+0x12a

0709fdb0 00000000 00000000 00000000 00000000 0x77995e74

STACK_COMMAND: kb

FOLLOWUP_IP:

inspect+1bf4

8fd30bf4 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: inspect+1bf4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: inspect

IMAGE_NAME: inspect.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ab12803

FAILURE_BUCKET_ID: 0xD1_inspect+1bf4

BUCKET_ID: 0xD1_inspect+1bf4

Followup: MachineOwner

---------

[adam1415]

Pelna konfiguracja kompa wraz z marka i modelem zasilacza jest nam potrzebna. Jesli masz zasilacz z czarnej listy, to mozliwe, ze on jest winowajca tych problemow. Innymi slowy: niekontrolowane skoki napiecia, brak odpowiedniej mocy dostarczanej do poszczegolnych podzespolow predzej czy pozniej uszkodza sprzet. Dlatego potrzebujemy PELNA konfiguracje komputera. Sciagniecie bocznej scianki i spisanie co pisze na zasilaczu to minuta roboty.

Na poczatek wrzuc S.M.A.R.T dysku (zakladka Health programu HDTune) oraz przeskanuj pamieci Memtest86+.