Witam,
Nie wiem czy to jakiś problem sprzętowy, czy sterowniki czy coś innego.
Komputer już z lekka wiekowy-
płyta główna- Asus p4p800 deluxe
procesor p4 2,4 GHz HT
pamięć - dwa duale w sumie 4 kości = 1,50GB RAM
grafika- ATI Radeon 9600
Jednym słowem świetny komputer sprzed około siedmiu lat i do tej pory
sprawujący się wyśmienicie.
Jakiś czas temu padł jeden dysk (na szczęście nie systemowy i wszystko
odzyskałam).
Kupiłam nowy dysk pasujący do tego sprzętu, zainstalowałam na nim Windowsa
XP professional (sp3 i wszystkie najnowsze poprawki są).
Programów mam teraz niewiele.
Komputer sprawował się cały czas bardzo dobrze.
Pięć dni temu nagle wyskoczył błąd MOM.exe (po raz pierwszy i jedyny jak do
tej pory), kliknęłam OK sprawdziłam, ze to związane z ATI.
Byłam wtedy z dala od komputera, żaden program poza zwykłymi, które pracują
w tle nie był odpalony.
Jednorazowy błąd.
Następnego dnia, też byłam z dala od kompa i też nie był niczym przeciążony-
wyskoczył niebieski ekran.
Kolejnego dnia parę minut po uruchomieniu komputera- niebieski ekran.
Kolejny dzień bezproblemowy.
Następnego dnia - niebieski ekran.
Kolejny dzień - spokój.
Dzisiaj znowu niebieski ekran.
W sumie cztery razy w ostatnich kilku dniach.
Przeważnie skarga na win3k.sys
Ściągnęłam WinDbg i -
-----------
--------------------------------------
16.02.2011
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini021611-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is:
SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Feb 16 14:09:43.656 2011 (GMT+1)
System Uptime: 0 days 4:29:20.219
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {f9836641, 1, bf80e7bc, 0}
Could not read faulting driver name
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: f9836641, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf80e7bc, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: f9836641
FAULTING_IP:
win32k!HMFreeObject+a9
bf80e7bc ff0f dec dword ptr [edi]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x50
PROCESS_NAME: Maxthon.exe
LAST_CONTROL_TRANSFER: from bf80e902 to bf80e7bc
STACK_TEXT:
ada5bcf8 bf80e902 e112b9a0 09d9fc34 ada5bd14 win32k!HMFreeObject+0xa9
ada5bd08 bf802d3f e112b9a0 ada5bd2c bf80e8a6 win32k!FreeTimer+0x53
ada5bd14 bf80e8a6 bc0a9c10 000210c1 00000000 win32k!FindTimer+0x3c
ada5bd2c bf80e926 bc0a9c10 000210c1 00000000 win32k!KillTimer2+0x1d
ada5bd40 bf80e957 bc0a9c10 000210c1 09d9fc34 win32k!_KillTimer+0x12
ada5bd54 804dd99f 000607d8 000210c1 09d9fc40 win32k!NtUserKillTimer+0x2a
ada5bd54 7c90e514 000607d8 000210c1 09d9fc40 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
09d9fc40 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -db !win32k
4 errors : !win32k (bf80e787-bf80e7b7)
bf80e780 85 d8 1a 99 bf f6 c3 *75 75 83 f6 c3 01 75 bd 33
.......uu....u.3
bf80e790 c0 85 c0 75 7c f6 46 *8b 20 0f 85 73 ff ff ff f6
...u|.F. ..s....
bf80e7a0 c3 10 57 75 74 f6 c3 *bf 0f 85 73 ff ff ff e8 c0
..Wut.....s.....
bf80e7b0 42 ff ff 66 8b 4e 0a *bf 41 66 83 f9 ff 0f 84 68
B..f.N..Af.....h
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: STRIDE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE
BUCKET_ID: MEMORY_CORRUPTION_STRIDE
Followup: memory_corruption
---------
0: kd> lmvm memory_corruption
start end module name
------------------------------------------------
------------------------------------------------------------
17.02.2011
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini021711-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is:
SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Thu Feb 17 12:05:54.281 2011 (GMT+1)
System Uptime: 0 days 3:46:34.861
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {ff08050f, 0, bf814766, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!CreateXlateObject+de )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: ff08050f, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf814766, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: ff08050f
FAULTING_IP:
win32k!CreateXlateObject+de
bf814766 85c8 test eax,ecx
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: Maxthon.exe
LAST_CONTROL_TRANSFER: from bf809f84 to bf814766
STACK_TEXT:
ad812738 bf809f84 00000000 00000000 e4ee1d18 win32k!CreateXlateObject+0xde
ad812774 bf831aff 00000000 00000000 00000001
win32k!EXLATEOBJ::bInitXlateObj+0xe3
ad8128c0 bf847717 d00125c7 00000000 00000000
win32k!GreStretchBltInternal+0x473
ad8128fc 804dd99f d00125c7 00000000 00000000 win32k!GreStretchBlt+0x30
ad8128fc 7c90e514 d00125c7 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
11e89d94 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!CreateXlateObject+de
bf814766 85c8 test eax,ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!CreateXlateObject+de
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d1dd63f
FAILURE_BUCKET_ID: 0x50_win32k!CreateXlateObject+de
BUCKET_ID: 0x50_win32k!CreateXlateObject+de
Followup: MachineOwner
-------------------------------------------------
---------------------------------------------------------
19.02.2011
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini021911-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is:
SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Sat Feb 19 08:28:47.828 2011 (GMT+1)
System Uptime: 0 days 0:06:08.545
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10000050, {ff08050f, 0, bf814766, 0}
Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!CreateXlateObject+de )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: ff08050f, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf814766, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: ff08050f
FAULTING_IP:
win32k!CreateXlateObject+de
bf814766 85c8 test eax,ecx
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: gg.exe
LAST_CONTROL_TRANSFER: from bf809f84 to bf814766
STACK_TEXT:
ae118c50 bf809f84 00000000 00000000 e40bda60 win32k!CreateXlateObject+0xde
ae118c8c bf809c9d 00000000 00000000 00000001
win32k!EXLATEOBJ::bInitXlateObj+0xe3
ae118d30 804dd99f e3f9d700 00000000 e40bda60 win32k!NtGdiBitBlt+0x451
ae118d30 7c90e514 e3f9d700 00000000 e40bda60 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
01a2c310 00000000 00000000 00000000 00000000 0x7c90e514
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!CreateXlateObject+de
bf814766 85c8 test eax,ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!CreateXlateObject+de
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d1dd63f
FAILURE_BUCKET_ID: 0x50_win32k!CreateXlateObject+de
BUCKET_ID: 0x50_win32k!CreateXlateObject+de
Followup: MachineOwner
------------------------------------------------------------
21.02.2011
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini022111-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is:
SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Mon Feb 21 19:08:09.781 2011 (GMT+1)
System Uptime: 0 days 10:45:07.483
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {5d89badb, ff, 1, 896876ca}
Probably caused by : win32k.sys ( win32k!HANDLELOCK::vUnlock+20 )
Followup: MachineOwner
---------
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: 5d89badb, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 896876ca, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 5d89badb
CURRENT_IRQL: ff
FAULTING_IP:
+fc
896876ca 000ddbba895d add byte ptr ds:[5D89BADBh],cl
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: gg.exe
LAST_CONTROL_TRANSFER: from 00000000 to 896876ca
SYMBOL_ON_RAW_STACK: 1
STACK_ADDR_RAW_STACK_SYMBOL: ffffffffae667c50
STACK_COMMAND: dds AE667C50-0x20 ; kb
STACK_TEXT:
ae667c30 1dccd000
ae667c34 00000000
ae667c38 ae667c3c
ae667c3c ae667cb8
ae667c40 8056e8d8 nt!ProbeForWrite+0x39
ae667c44 badb0d00
ae667c48 fffff000
ae667c4c bf8054ee win32k!HANDLELOCK::vUnlock+0x20
ae667c50 ae667c64
ae667c54 bf805490 win32k!HANDLELOCK::vLockHandle+0x75
ae667c58 00000000
ae667c5c 00000000
ae667c60 e157b9c8
ae667c64 00000000
ae667c68 00000001
ae667c6c 00000000
ae667c70 00000023
ae667c74 00000023
ae667c78 fffff000
ae667c7c 00001000
ae667c80 1dcf5000
ae667c84 00000001
ae667c88 ae667d28
ae667c8c bf800030 win32k!CheckPwndFilter <PERF> (win32k+0x30)
ae667c90 1dcf5000
ae667c94 1dccd000
ae667c98 e2b90af0
ae667c9c ae667cb8
ae667ca0 00000000
ae667ca4 8056e8d8 nt!ProbeForWrite+0x39
ae667ca8 00000008
ae667cac 00010287
FOLLOWUP_IP:
win32k!HANDLELOCK::vUnlock+20
bf8054ee 83660400 and dword ptr [esi+4],0
SYMBOL_NAME: win32k!HANDLELOCK::vUnlock+20
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d1dd63f
FAILURE_BUCKET_ID: 0xD1_win32k!HANDLELOCK::vUnlock+20
BUCKET_ID: 0xD1_win32k!HANDLELOCK::vUnlock+20
Followup: MachineOwner
---------
1: kd> lmvm win32k
start end module name
bf800000 bf9c4f00 win32k # (pdb symbols)
downstreamstore\win32k.pdb\FA73BD4EB15C4AA793F12403BBB5C32C2\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file:
DownstreamStore\win32k.sys\4D1DD63F1c4f00\win32k.sys
Image path: win32k.sys
Image name: win32k.sys
Timestamp: Fri Dec 31 14:10:23 2010 (4D1DD63F)
CheckSum: 001C9AD2
ImageSize: 001C4F00
File version: 5.1.2600.6064
Product version: 5.1.2600.6064
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0408.04b0
CompanyName: Microsoft Corporation
ProductName: ??????????? ??????? MicrosoftR WindowsR
InternalName: win32k.sys
OriginalFilename: win32k.sys
ProductVersion: 5.1.2600.6064
FileVersion: 5.1.2600.6064 (xpsp_sp3_gdr.101231-1614)
FileDescription: ????????? ???????? Multi-User Win32
LegalCopyright: C Microsoft Corporation. ?? ????????? ???? ???????
???????????.
------------------
Czy na podstawie tego czegoś powyżej można choć mniej więcej rozgryźć co się
dzieje?
Pamięć? System? Sterowniki? Chęć zrobienia na złość?
Będę wdzięczna jeśli ktoś znający się na rzeczy rzuci okiem i choć podpowie
czego szukać.
Z góry dziękuję za wszelkie rady.
Pozdrawiam, Anna
Received on Mon Feb 21 19:50:02 2011
To archiwum zostało wygenerowane przez hypermail 2.1.8 : Mon 21 Feb 2011 - 19:51:03 MET