XP Power PC is crashing, mini dumps blame memory and drivers.
So many different dumps in one day. SOme say ATI, some say SVCHOST, some say memeory. Trying to run windiag memory checker. WHat is the most serious bugcheck in this output and should be fixed first.? Help, home office PC, needs to be stable and run a whole day.
Loading Dump File [C:\WINDOWS\Minidump\Mini022808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\memory-dump-view
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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Feb 28 08:33:12.781 2008 (GMT-5)
System Uptime: 0 days 0:19:33.358
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
BugCheck 7A, {c03007c0, c0000102, c01f0d08, 78e8a804}
Probably caused by : Unknown_Image ( nt!MiRemoveUnusedSegments+70f )
Followup: MachineOwner
---------
kd> !analyze -v
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c03007c0, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000102, error status (normally i/o status code)
Arg3: c01f0d08, current process (virtual address for lock type 3, or PTE)
Arg4: 78e8a804, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0xc0000102 - {Corrupt File} The file or directory %hs is corrupt and unreadable. Please run the Chkdsk utility.
BUGCHECK_STR: 0x7a_c0000102
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: navigator.exe
IRP_ADDRESS: ffffffc0
FAULTING_IP:
+7c34298e
7c34298e ?? ???
LAST_CONTROL_TRANSFER: from 80526759 to 8053738a
STACK_TEXT:
ac48bc58 80526759 0000007a c03007c0 c0000102 nt!MiRemoveUnusedSegments+0x70f
ac48bc80 804fba39 826d8cf0 c03007c0 c01f0d08 nt!PopSetPerfLevels+0x3ea
ac48bcf8 804f5bec 78e8a804 c01f0d08 c03007c0 nt!MiCheckControlArea+0x1a8
ac48bd4c 804e0944 00000000 7c34298e 00000001 nt!IopCompleteRequest+0x10c
ac48bd64 7c34298e badb0d00 030fdfe8 04085180 nt!KiTrap06+0x387
WARNING: Frame IP not in any known module. Following frames may be wrong.
ac48bd68 badb0d00 030fdfe8 04085180 08000050 0x7c34298e
ac48bd6c 030fdfe8 04085180 08000050 00000000 0xbadb0d00
ac48bd70 04085180 08000050 00000000 00000000 0x30fdfe8
ac48bd74 08000050 00000000 00000000 00000000 0x4085180
ac48bd78 00000000 00000000 00000000 00000000 0x8000050
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiRemoveUnusedSegments+70f
8053738a 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiRemoveUnusedSegments+70f
FOLLOWUP_NAME: MachineOwner
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_NAME: Unknown_Image
BUCKET_ID: INVALID_OPCODE
MODULE_NAME: Unknown_Module
Followup: MachineOwner
---------
Loading Dump File [C:\WINDOWS\Minidump\Mini022708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\memory-dump-view
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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Wed Feb 27 23:27:57.305 2008 (GMT-5)
System Uptime: 0 days 0:34:29.015
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 vsapint.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vsapint.sys
*** ERROR: Module load completed but symbols could not be loaded for vsapint.sys
BugCheck 10000050, {acfce000, 0, ad9f9bc6, 0}
*** WARNING: Unable to verify timestamp for tmxpflt.sys
*** ERROR: Module load completed but symbols could not be loaded for tmxpflt.sys
Probably caused by : vsapint.sys ( vsapint+5dbc6 )
Followup: MachineOwner
kd> !analyze -v
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: acfce000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: ad9f9bc6, 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: acfce000
FAULTING_IP:
vsapint+5dbc6
ad9f9bc6 0fb610 movzx edx,byte ptr [eax]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: SfCtlCom.exe
LAST_CONTROL_TRANSFER: from ffffffff to ad9f9bc6
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
acfcd20c ffffffff 0000b3fc acfcd364 ada0a513 vsapint+0x5dbc6
acfcd218 ada0a513 e31fdc1c e327e81c 00000035 0xffffffff
acfcd364 ada7decc e157931c ad9b5cc8 00000053 vsapint+0x6e513
acfcd440 ad9bff58 e157931c e31fdc1c e327e81c vsapint+0xe1ecc
acfcd478 ad9beae3 e157931c 0035dc1c e31fd890 vsapint+0x23f58
acfcd510 ada8b5e6 acfcd528 acfcd5a0 acfcd714 vsapint+0x22ae3
acfcd574 ad9cd4cc e31fdaa0 e31fb81c e157931c vsapint+0xef5e6
acfcd5f4 ada8b09a e157931c e31fb824 acfcd62c vsapint+0x314cc
acfcd604 ada8a13b acfcd700 ad9cd3c1 acfcd7bc vsapint+0xef09a
acfcd62c ada8a014 acfcd700 acfcd6a8 acfcd700 vsapint+0xee13b
acfcd654 ad9bedaf acfcd700 e821fd7c 00000000 vsapint+0xee014
acfcd6e8 ada8b5e6 acfcd700 acfcd778 acfcd8ec vsapint+0x22daf
acfcd74c ad9cd4cc e30feea1 e30fcc1c e157931c vsapint+0xef5e6
acfcd7cc ada8b09a e157931c e30fcc24 acfcd804 vsapint+0x314cc
acfcd7dc ada8a13b acfcd8d8 ad9cd3c1 acfcd994 vsapint+0xef09a
acfcd804 ada8a014 acfcd8d8 acfcd880 acfcd8d8 vsapint+0xee13b
acfcd82c ad9bedaf acfcd8d8 e821f69c 00000000 vsapint+0xee014
acfcd8c0 ada8b5e6 acfcd8d8 acfcd950 acfcdac4 vsapint+0x22daf
acfcd924 ad9cd4cc e2ffe302 e2ffc01c e157931c vsapint+0xef5e6
acfcd9a4 ada8b09a e157931c e2ffc024 acfcd9dc vsapint+0x314cc
acfcd9b4 ada8a13b acfcdab0 ad9cd3c1 acfcdac8 vsapint+0xef09a
acfcd9dc ada8a014 acfcdab0 acfcda58 acfcdab0 vsapint+0xee13b
acfcda04 ad9bedaf acfcdab0 e15cbefc 00000000 vsapint+0xee014
acfcda98 ada8d639 acfcdab0 ff000003 870b6a9c vsapint+0x22daf
acfcdadc ad971c5c e157931c e246349c 870b6a9c vsapint+0xf1639
acfcdb20 ad972c9d e157931c e246349c 870b6a9c tmxpflt+0x17c5c
acfcdb4c ad973b07 e246341c 870b6a9c 00000000 tmxpflt+0x18c9d
acfcdba4 ad969d2d 00000000 870b6ba4 00000000 tmxpflt+0x19b07
acfcdbcc ad96df3c acfcdc24 ac5143d1 866a5230 tmxpflt+0xfd2d
acfcdc0c ad95d5e0 a028448b 866a5230 88947218 tmxpflt+0x13f3c
acfcdc40 804e13d9 88aad8f8 86ff42d0 806ff410 tmxpflt+0x35e0
acfcdc40 88aad8f8 88aad8f8 86ff42d0 806ff410 nt!KiTrap0B+0x10f
acfcdcd4 00000000 86bdd660 8683c720 acfcdd48 0x88aad8f8
STACK_COMMAND: kb
FOLLOWUP_IP:
vsapint+5dbc6
ad9f9bc6 0fb610 movzx edx,byte ptr [eax]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: vsapint+5dbc6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vsapint
IMAGE_NAME: vsapint.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 466e7a9b
FAILURE_BUCKET_ID: 0x50_vsapint+5dbc6
BUCKET_ID: 0x50_vsapint+5dbc6
Followup: MachineOwner
SfCtlCom.exe is Trend Micro Pro 16.05 1039 Engine 8.500 recent updates and scans all done.
SUMMARY
Memory dumps usually freeze the PC Digital interface screen and no further IO is accepted, PC requires manual hard reset. Upon bootup, Trend micro creates a recovery image, then a normal reboot is done to resolve conflict.
ATI debug - recent ATI driver install and Catalyst sw. However 2 ATI icons appear on program , one is Catalyst control center, operates fine.
Microsoft Bootup diag not working due to IO error upon bootup of floopy and CD.