PCTuning fórum

pri te chybe,modreho okna mi to pise:

STOP: 0X0000008E (0XC0000005, 0XBF815E0D, 0XA75ECB74, 0X00000000)
WIN32K.SYS - ADRESS BF815E0D BASE AT BF8000000, DATESTAMP 45f013f6
ZAHAJOVANI VYPISU FYZICKE PAMETI RAM
VYPIS FYZICKE PAMETI RAM NA DISK:

posledni tyden se to stava pomerne casto, nevim vubec cim by to mohlo byt?Teploty mam v zatizeni pro jadra kolem 55 stupnu, v klidu 30-38. Coz si myslim neni duvod,aby to delalo. Dela to jak v idle obcas, kdyz prohlizim web a posloucham hudbu, tak dnes mi to udelalo porpve ve hre. Pameti mam 4x512MB DDR2 A-Data klasicke, muze byt spatna pamet?Delal sem taky nedavno flash biosu, ktery ale dopadl bez problemu...
NOD32 mi take nic nenasel, co mi prosim doporucite?
Budu rad za kazdou znalou radu, jak na dany problem

//EDIT: pred chvili jsem mel zase modrou obrazovku v idle:


STOP: 0X0000008E (0XC0000005, 0X8057BEFB, 0XA6F2FC14, 0X00000000)
ZAHAJOVANI VYPISU FYZICKE PAMETI RAM
VYPIS FYZICKE PAMETI RAM

flanker píše: STOP: 0X0000008E (0XC0000005, 0XBF815E0D, 0XA75ECB74, 0X00000000)
WIN32K.SYS - ADRESS BF815E0D BASE AT BF8000000, DATESTAMP 45f013f6

Výjimka způsobená přístupem do chybné paměťi => chyba v ovladači.

Nemáš nainstalovaný nějaký software třetí strany na vzdálenou správu?

Můžes si stáhnout Microsoft Debugging Tools (viz. Google) a pak pomoci WINDBG.EXE otevřít (File/Open Crash Dump...) MEMORY.DMP ve WINDOWS adresáři. A do konzolového (Command) okna napiš "!analyze -v" a výstup dej sem.

nemel bych mit nainstalovanej, alespon o tom osobne nevim.

ten vypis, mozna neni potreba cely, nerozumim tomu, ale vyjelo mi toto:

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8057befb, The address that the exception occurred at
Arg3: a6f2fc14, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

***** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP:
nt!NtWriteFile+205
8057befb 8b5828 mov ebx,dword ptr [eax+28h]

TRAP_FRAME: a6f2fc14 -- (.trap 0xffffffffa6f2fc14)
ErrCode = 10101010
eax=612717f3 ebx=10101010 ecx=612717e9 edx=612717df esi=10100100 edi=61271a96
eip=10101010 esp=a6f2fc88 ebp=10101010 iopl=1 vip nv up di pl nz ac po nc
cs=0302 ss=0010 ds=17d5 es=17cb fs=1811 gs=17c1 efl=10101010
0302:1010 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from 612f5314 to 804f9deb

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a6f2f7dc 612f5314 0002a5e9 52f46800 9be9612f nt!KeBugCheckEx+0x1b
a6f2f7e0 0002a5e9 52f46800 9be9612f 68000002 0x612f5314
a6f2f7e4 52f46800 9be9612f 68000002 612f52d8 0x2a5e9
a6f2f7e8 9be9612f 68000002 612f52d8 000291e9 0x52f46800
a6f2f7ec 68000002 612f52d8 000291e9 52b46800 0x9be9612f
a6f2f7f0 612f52d8 000291e9 52b46800 87e9612f 0x68000002
a6f2f7f4 000291e9 52b46800 87e9612f 68000002 0x612f52d8
a6f2f7f8 52b46800 87e9612f 68000002 612f52a0 0x291e9
a6f2f7fc 87e9612f 68000002 612f52a0 00027de9 0x52b46800
a6f2f800 68000002 612f52a0 00027de9 52806800 0x87e9612f
a6f2f804 612f52a0 00027de9 52806800 73e9612f 0x68000002
a6f2f808 00027de9 52806800 73e9612f 68000002 0x612f52a0
a6f2f80c 52806800 73e9612f 68000002 612f5254 0x27de9
a6f2f810 73e9612f 68000002 612f5254 000269e9 0x52806800
a6f2f814 68000002 612f5254 000269e9 fe690500 0x73e9612f
a6f2f818 612f5254 000269e9 fe690500 f883ffff 0x68000002
a6f2f81c 000269e9 fe690500 f883ffff 63870f5f 0x612f5254
a6f2f820 fe690500 f883ffff 63870f5f 33000002 0x269e9
a6f2f824 f883ffff 63870f5f 33000002 5c888ac9 0xfe690500
a6f2f828 63870f5f 33000002 5c888ac9 ff61271d 0xf883ffff
a6f2f82c 33000002 5c888ac9 ff61271d 1d1c8d24 0x63870f5f
a6f2f830 5c888ac9 ff61271d 1d1c8d24 24686127 0x33000002
a6f2f834 ff61271d 1d1c8d24 24686127 e9612f52 0x5c888ac9
a6f2f838 1d1c8d24 24686127 e9612f52 00000242 0xff61271d
a6f2f83c 24686127 e9612f52 00000242 2f520868 0x1d1c8d24
a6f2f840 e9612f52 00000242 2f520868 0238e961 0x24686127
a6f2f844 00000000 2f520868 0238e961 dc680000 0xe9612f52


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!NtWriteFile+205
8057befb 8b5828 mov ebx,dword ptr [eax+28h]

SYMBOL_NAME: nt!NtWriteFile+205

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrpamp.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------

dnesni vypis:
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini020408-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 \WINDOWS\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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Feb 4 02:03:37.433 2008 (GMT+1)
System Uptime: 0 days 0:12:58.167
*********************************************************************
* 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 \WINDOWS\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
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {40, 2, 1, a9b4c7c7}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for tcpip.sys
*** ERROR: Module load completed but symbols could not be loaded for tcpip.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 : tcpip.sys ( tcpip+37c7 )

Followup: MachineOwner
---------

a detailnejsi analyza mi vybehla:

1: 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: 00000040, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: a9b4c7c7, address which referenced memory

Debugging Details:
------------------

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

MODULE_NAME: tcpip

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41107ecf

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000040

CURRENT_IRQL: 2

FAULTING_IP:
tcpip+37c7
a9b4c7c7 ?? ???

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 00000000 to 80543930

STACK_TEXT:
bacd7e30 00000000 00000040 00000002 00000001 nt+0x6c930


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
tcpip+37c7
a9b4c7c7 ?? ???

SYMBOL_NAME: tcpip+37c7

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: tcpip.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------