Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Admin\My documents\Mini032510-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp 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: Thu Mar 25 12:40:58.203 2010 (UTC + 2:00)
System Uptime: 0 days 3:43:04.920
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
..............................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image ati2cqag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2cqag.dll
******************
* *
* Bugcheck Analysis *
* *
******************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ec695854, 0, bf084c36, 1}


Could not read faulting driver name
Probably caused by : ati2cqag.dll ( ati2cqag!__safe_se_handler_table+376 )

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: ec695854, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf084c36, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

Debugging Details:
--------


Could not read faulting driver name

READ_ADDRESS: ec695854

FAULTING_IP:
ati2cqag!__safe_se_handler_table+376
bf084c36 394a54 cmp dword ptr [edx+54h],ecx

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: Bully.exe

LAST_CONTROL_TRANSFER: from bf090a89 to bf084c36

STACK_TEXT:
a97f0828 bf090a89 e22579a0 a97f08ec e2256280 ati2cqag!__safe_se_handler_table+0x376
a97f082c e22579a0 a97f08ec e2256280 e21f5540 ati2cqag!aPM4_RT_Microcode_R400+0x3bc1
WARNING: Frame IP not in any known module. Following frames may be wrong.
a97f0830 a97f08ec e2256280 e21f5540 e20009a0 0xe22579a0
a97f0834 e2256280 e21f5540 e20009a0 e20009a0 0xa97f08ec
a97f08ec 00000000 0000002b 00000663 0155bf0c 0xe2256280


STACK_COMMAND: kb

FOLLOWUP_IP:
ati2cqag!__safe_se_handler_table+376
bf084c36 394a54 cmp dword ptr [edx+54h],ecx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ati2cqag!__safe_se_handler_table+376

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ati2cqag

IMAGE_NAME: ati2cqag.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4b68e81f

FAILURE_BUCKET_ID: 0x50_ati2cqag!__safe_se_handler_table+376

BUCKET_ID: 0x50_ati2cqag!__safe_se_handler_table+376

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

KLUCHICK, а мышь юсб, которая отвалилась? Или 1 раз может быть и случайность?

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Admin\My documents\Новая папка (2)\Mini032110-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp 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: Sun Mar 21 12:05:41.375 2010 (UTC + 2:00)
System Uptime: 0 days 0:15:21.939
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
..............
******************
* *
* Bugcheck Analysis *
* *
******************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {0, 0, 0, 0}

Unable to load image ati2mtag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
Probably caused by : ntoskrnl.exe ( nt!_woutput+3ef )

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

0: kd> !analyze -v
******************
* *
* Bugcheck Analysis *
* *
******************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
--------


BUGCHECK_STR: 0x7f_0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: metro2033.exe

LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)

Resource @ nt!PiEngineLock (0x805591e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 805a270d to 804f9f1e

STACK_TEXT:
a8e1db80 805a270d 0000007f b949c62e a8e1dc70 nt!_woutput+0x3ef
a8e1dbd8 80542244 a8e1dbe4 a8e1dcbc b949c62e nt!PipConcatenateUnicodeStrings+0x7d
a8e1dbe4 b949c62e badb0d00 00000000 b902b000 nt!RtlpExtendStackTraceDataBase+0x9d
a8e1dcbc b939a586 a8e1dcd4 00000027 8a1ccc50 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x22e62e)
a8e1dce4 b9398433 8a1ccc50 a8e1dd08 a8e1dd70 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x12c586)
a8e1dd18 b93b9626 8a1c3350 a8e1dd30 8a0f8188 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x12a433)
a8e1dd70 b93c2180 8a1e7e14 0000003f a8e1dd84 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x14b626)
a8e1dd90 b93db21a 8a33eb74 00011170 0001c138 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x154180)
a8e1dd94 8a33eb74 00011170 0001c138 fff0001f ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x16d21a)
WARNING: Frame IP not in any known module. Following frames may be wrong.
a8e1dd98 00011170 0001c138 fff0001f 8a0f8188 0x8a33eb74
a8e1dd9c 0001c138 fff0001f 8a0f8188 fff0001f 0x11170
a8e1dda0 fff0001f 8a0f8188 fff0001f 8a33eb74 0x1c138
a8e1dda4 8a0f8188 fff0001f 8a33eb74 ffffffff 0xfff0001f
a8e1dda8 fff0001f 8a33eb74 ffffffff ffffffff 0x8a0f8188
a8e1ddac 8a33eb74 ffffffff ffffffff b93c4a58 0xfff0001f
a8e1ddb0 ffffffff ffffffff b93c4a58 8a33eb74 0x8a33eb74
a8e1ddb4 ffffffff b93c4a58 8a33eb74 8a0f8188 0xffffffff
a8e1ddb8 b93c4a58 8a33eb74 8a0f8188 8a33ec5c 0xffffffff
a8e1ddbc 8a33eb74 8a0f8188 8a33ec5c 8a1f1e88 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x156a58)
a8e1ddc0 8a0f8188 8a33ec5c 8a1f1e88 a8e1de18 0x8a33eb74
a8e1ddc4 8a33ec5c 8a1f1e88 a8e1de18 00000002 0x8a0f8188
a8e1ddc8 8a1f1e88 a8e1de18 00000002 b93c0ee9 0x8a33ec5c
a8e1ddcc a8e1de18 00000002 b93c0ee9 8a33eb74 0x8a1f1e88
a8e1ddd0 00000000 b93c0ee9 8a33eb74 a8e1de30 0xa8e1de18


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_woutput+3ef
804f9f1e 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!_woutput+3ef

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1e8f8a

FAILURE_BUCKET_ID: 0x7f_0_nt!_woutput+3ef

BUCKET_ID: 0x7f_0_nt!_woutput+3ef

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

Microsoft ® Windows Debugger Version 6.12.0002.633 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Admin\My documents\Новая папка (2)\Mini032110-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp 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: Sun Mar 21 14:56:37.296 2010 (UTC + 2:00)
System Uptime: 0 days 2:37:28.994
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols
Loading unloaded module list
.........................
******************
* *
* Bugcheck Analysis *
* *
******************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {0, 0, 0, 0}

Unable to load image ati2mtag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati2mtag.sys
Probably caused by : ntoskrnl.exe ( nt!_woutput+3ef )

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

0: kd> !analyze -v
******************
* *
* Bugcheck Analysis *
* *
******************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
--------


BUGCHECK_STR: 0x7f_0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: metro2033.exe

LOCK_ADDRESS: 805591e0 -- (!locks 805591e0)

Resource @ nt!PiEngineLock (0x805591e0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0x805591e0
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from 805a270d to 804f9f1e

STACK_TEXT:
a9720b80 805a270d 0000007f b949c62e a9720c70 nt!_woutput+0x3ef
a9720bd8 80542244 a9720be4 a9720cbc b949c62e nt!PipConcatenateUnicodeStrings+0x7d
a9720be4 b949c62e badb0d00 00000000 b902b000 nt!RtlpExtendStackTraceDataBase+0x9d
a9720cbc b939a586 a9720cd4 00000027 8a2a8c50 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x22e62e)
a9720ce4 b9398433 8a2a8c50 a9720d08 a9720d70 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x12c586)
a9720d18 b93b9626 8a29f350 a9720d30 8a2865e8 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x12a433)
a9720d70 b93c2180 8a2c3e14 0000003f a9720d84 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x14b626)
a9720d90 b93db21a 89a94d2c 00011170 0001c138 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x154180)
a9720d94 89a94d2c 00011170 0001c138 fff0001f ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x16d21a)
WARNING: Frame IP not in any known module. Following frames may be wrong.
a9720d98 00011170 0001c138 fff0001f 8a2865e8 0x89a94d2c
a9720d9c 0001c138 fff0001f 8a2865e8 fff0001f 0x11170
a9720da0 fff0001f 8a2865e8 fff0001f 89a94d2c 0x1c138
a9720da4 8a2865e8 fff0001f 89a94d2c ffffffff 0xfff0001f
a9720da8 fff0001f 89a94d2c ffffffff ffffffff 0x8a2865e8
a9720dac 89a94d2c ffffffff ffffffff b93c4a58 0xfff0001f
a9720db0 ffffffff ffffffff b93c4a58 89a94d2c 0x89a94d2c
a9720db4 ffffffff b93c4a58 89a94d2c 8a2865e8 0xffffffff
a9720db8 b93c4a58 89a94d2c 8a2865e8 89a94e14 0xffffffff
a9720dbc 89a94d2c 8a2865e8 89a94e14 8a346a60 ati2mtag!_NULL_IMPORT_DESCRIPTOR (ati2mtag+0x156a58)
a9720dc0 8a2865e8 89a94e14 8a346a60 a9720e18 0x89a94d2c
a9720dc4 89a94e14 8a346a60 a9720e18 00000002 0x8a2865e8
a9720dc8 8a346a60 a9720e18 00000002 b93c0ee9 0x89a94e14
a9720dcc a9720e18 00000002 b93c0ee9 89a94d2c 0x8a346a60
a9720dd0 00000000 b93c0ee9 89a94d2c a9720e30 0xa9720e18


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!_woutput+3ef
804f9f1e 5d pop ebp

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!_woutput+3ef

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b1e8f8a

FAILURE_BUCKET_ID: 0x7f_0_nt!_woutput+3ef

BUCKET_ID: 0x7f_0_nt!_woutput+3ef

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

Сегодня при включении компа, начиная с логотипа материнки и вплоть до загрузки виндовс изображение было искажённое, как мне обьяснили в полосах, логотип виндовс с бегущими полосками был по всему экрану в небольших экземплярах.