Hi Nobus, yes here are a few:
*** ERROR: Module load completed but symbols could not be loaded for ino_fltr.sys
Probably caused by : memory_corruption ( nt!MiFlushSectionInternal+
Followup: MachineOwner
---------
0: kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 00000007, A driver has unlocked a page more times than it locked it
Arg2: 000c84a4, page frame number
Arg3: 00088e5d, current share count
Arg4: 00000000, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_7
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 80522d13 to 804f9f43
STACK_TEXT:
ba4ff790 80522d13 0000004e 00000007 000c84a4 nt!KeBugCheckEx+0x1b
ba4ff7b0 8050f165 8a826188 8a8ab640 8a8561d8 nt!MiDecrementReferenceCou
ba4ff884 8050faa4 e4898fb0 e4899010 e4899010 nt!MiFlushSectionInternal+
ba4ff8c0 804e4554 8a8561d8 00000000 0000c000 nt!MmFlushSection+0x1f2
ba4ff948 b9d3f007 0000c000 ba4ff9e8 0000c000 nt!CcFlushCache+0x3a0
ba4ffa10 b9d3f089 e150a2a8 e3cfb960 e150a2a8 Ntfs!LfsFlushLfcb+0x227
ba4ffa34 b9d493db e150a2a8 e3cfb960 e14d8040 Ntfs!LfsFlushLbcb+0x81
ba4ffa5c b9d3dc60 e150a2a8 ffffffff 7fffffff Ntfs!LfsFlushToLsnPriv+0xf
ba4ffa9c b9d5cfe4 e14d8040 ffffffff 7fffffff Ntfs!LfsFlushToLsn+0x8e
ba4ffb08 b9d5d160 89ae5268 8a70a008 8a70a008 Ntfs!NtfsCommonFlushBuffer
ba4ffb6c 804ef19f 8a826770 8a70a008 8a81e858 Ntfs!NtfsFsdFlushBuffers+0
ba4ffb7c b9dc1459 ba4ffbc8 804ef19f 8a890c08 nt!IopfCallDriver+0x31
ba4ffb84 804ef19f 8a890c08 8a70a008 89dc6590 sr!SrPassThrough+0x31
ba4ffb94 b68f5544 8a0db360 8a39b030 8a70a008 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4ffbc8 80576eb1 89dc64d8 8a70a008 8a0db360 ino_fltr+0x7544
ba4ffc40 8054162c 80000464 ba4ffcd4 ba4ffcdc nt!NtFlushBuffersFile+0x1b
ba4ffc40 80500351 80000464 ba4ffcd4 ba4ffcdc nt!KiFastCallEntry+0xfc
ba4ffcc0 8063c233 80000464 ba4ffcd4 e10de000 nt!ZwFlushBuffersFile+0x11
ba4ffcdc 8063b56b e10ddb60 00000001 00000000 nt!CmpFileFlush+0x55
ba4ffd30 8063b8b7 fffffe00 e10ddb60 8067d3b0 nt!HvpWriteLog+0xe9
ba4ffd44 806320d4 e10ddb01 80559534 8055a220 nt!HvSyncHive+0x71
ba4ffd60 8062af25 00000000 8056485c 8a8ab640 nt!CmpDoFlushAll+0x6c
ba4ffd7c 8053877d 00000000 00000000 8a8ab640 nt!CmpLazyFlushWorker+0x53
ba4ffdac 805cff70 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
ba4ffddc 805460ee 8053868e 00000001 00000000 nt!PspSystemThreadStartup+
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiFlushSectionInternal+
8050f165 8b45ec mov eax,dword ptr [ebp-14h]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!MiFlushSectionInternal+
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x4E_7_nt!MiFlushSectionIn
BUCKET_ID: 0x4E_7_nt!MiFlushSectionIn
Followup: MachineOwner
__________________________
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\duwaynem\Desktop\
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl
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.080814-1
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jan 14 10:57:55.571 2009 (GMT+10)
System Uptime: 0 days 2:38:37.286
Loading Kernel Symbols
..........................
..........................
Loading User Symbols
Loading unloaded module list
...................
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1902fe, b622a160, b6229e5c, 8051afe6}
*** WARNING: Unable to verify timestamp for ino_fltr.sys
*** ERROR: Module load completed but symbols could not be loaded for ino_fltr.sys
Probably caused by : Ntfs.sys ( Ntfs!LfsGetLbcb+5b )
Followup: MachineOwner
---------
1: kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 001902fe
Arg2: b622a160
Arg3: b6229e5c
Arg4: 8051afe6
Debugging Details:
------------------
EXCEPTION_RECORD: b622a160 -- (.exr 0xffffffffb622a160)
ExceptionAddress: 8051afe6 (nt!MmCheckCachedPageState
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000024
Attempt to read from address 00000024
CONTEXT: b6229e5c -- (.cxr 0xffffffffb6229e5c)
eax=00000000 ebx=00000400 ecx=00000000 edx=00000001 esi=8a8260b8 edi=c0617d28
eip=8051afe6 esp=b622a228 ebp=b622a274 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!MmCheckCachedPageState+
8051afe6 8b7824 mov edi,dword ptr [eax+24h] ds:0023:00000024=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: InoRT.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 00000024
READ_ADDRESS: 00000024
FOLLOWUP_IP:
Ntfs!LfsGetLbcb+5b
b9d3ebc3 8b45dc mov eax,dword ptr [ebp-24h]
BUGCHECK_STR: 0x24
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from 804e2480 to 8051afe6
STACK_TEXT:
b622a274 804e2480 c2fa5000 00000000 b622a3a0 nt!MmCheckCachedPageState+
b622a2bc 804e3f0a 8a8cb650 b622a2fc 00001000 nt!CcMapAndRead+0x86
b622a350 8056a5ab 8a8c1230 b622a390 00001000 nt!CcPinFileData+0x204
b622a3c4 b9d3ebc3 8a8c1230 b622a404 00001000 nt!CcPreparePinWrite+0x93
b622a444 b9d3ed21 e14d6b28 e1507298 000000d8 Ntfs!LfsGetLbcb+0x5b
b622a458 b9d3e9a2 e14d6b28 000000d0 e1507298 Ntfs!LfsPrepareLfcbForLogR
b622a488 b9d3e6d6 e14d6b28 e1507298 00000002 Ntfs!LfsWriteLogRecordInto
b622a564 b9d3e1ff e1507298 00000002 b622a624 Ntfs!LfsWrite+0x2f7
b622a6e8 b9d59c37 b622aa6c e14d2588 89371128 Ntfs!NtfsWriteLog+0x6a2
b622a7b4 b9d9b576 b622aa6c e14d2588 16294370 Ntfs!NtOfsPutData+0x2fa
b622a848 b9d712bd b622aa6c 00000000 b622ab7c Ntfs!NtfsWriteUsnJournalCh
b622aa50 b9d42d4d b622aa6c 89979008 8a8cbcc0 Ntfs!NtfsCommonCleanup+0x2
b622abc8 804ef19f 8a826770 89979008 8a81e858 Ntfs!NtfsFsdCleanup+0xcf
b622abd8 b9dc5bbf 00000000 89f3d9a0 b622ac60 nt!IopfCallDriver+0x31
b622abe8 804ef19f 8a8cbc08 89979008 89979198 sr!SrCleanup+0xb3
b622abf8 b699aacd 89c8e5a0 8a176a18 89979018 nt!IopfCallDriver+0x31
WARNING: Stack unwind information not available. Following frames may be wrong.
b622ac60 804ef19f 8a137ea8 89979008 89979008 ino_fltr+0xcacd
b622ac70 80583953 89c8e588 00000038 8a8d0900 nt!IopfCallDriver+0x31
b622aca0 805bca16 89d8eda0 8a137ea8 00100100 nt!IopCloseFile+0x26b
b622acd4 805bc33f 89d8eda0 00000001 8a8d0900 nt!ObpDecrementHandleCount
b622acfc 805bc3dd e237e5c8 89c8e5a0 00000154 nt!ObpCloseHandleTableEntr
b622ad44 805bc515 00000154 00000001 00000000 nt!ObpCloseHandle+0x87
b622ad58 8054162c 00000154 024eef88 7c90e4f4 nt!NtClose+0x1d
b622ad58 7c90e4f4 00000154 024eef88 7c90e4f4 nt!KiFastCallEntry+0xfc
024eef88 00000000 00000000 00000000 00000000 0x7c90e4f4
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: Ntfs!LfsGetLbcb+5b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP:
STACK_COMMAND: .cxr 0xffffffffb6229e5c ; kb
FAILURE_BUCKET_ID: 0x24_Ntfs!LfsGetLbcb+5b
BUCKET_ID: 0x24_Ntfs!LfsGetLbcb+5b
Followup: MachineOwner
---------
__________________________
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\duwaynem\Desktop\
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl
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.080814-1
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jan 15 09:37:51.293 2009 (GMT+10)
System Uptime: 0 days 1:44:23.256
Loading Kernel Symbols
..........................
..........................
Loading User Symbols
Loading unloaded module list
.....................
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {f78001b7, 2, 1, 80522770}
Probably caused by : memory_corruption ( nt!MiRemovePageByColor+de )
Followup: MachineOwner
---------
0: kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: f78001b7, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80522770, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: f78001b7
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+de
80522770 ff4808 dec dword ptr [eax+8]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: svchost.exe
LAST_CONTROL_TRANSFER: from 80522a90 to 80522770
STACK_TEXT:
b5a53cb4 80522a90 00000001 00000024 c0047bd8 nt!MiRemovePageByColor+0xd
b5a53cd0 80514b0f c0600238 c0047bd8 00000000 nt!MiRemoveZeroPage+0x8a
b5a53ce8 805205bd 08f7b000 c0047bd8 89e399f0 nt!MiResolveDemandZeroFaul
b5a53d4c 80544588 00000001 08f7b000 00000001 nt!MmAccessFault+0xbeb
b5a53d4c 7c910741 00000001 08f7b000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
00b1f170 00000000 00000000 00000000 00000000 0x7c910741
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiRemovePageByColor+de
80522770 ff4808 dec dword ptr [eax+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiRemovePageByColor+de
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor
BUCKET_ID: 0xA_nt!MiRemovePageByColor
Followup: MachineOwner
---------
__________________________
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\duwaynem\Desktop\
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl
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.080814-1
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jan 15 09:44:14.407 2009 (GMT+10)
System Uptime: 0 days 0:06:09.125
Loading Kernel Symbols
..........................
..........................
Loading User Symbols
Loading unloaded module list
...........
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000000A, {0, 2, 1, 805226f8}
Probably caused by : memory_corruption ( nt!MiRemovePageByColor+66 )
Followup: MachineOwner
---------
0: kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 805226f8, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!MiRemovePageByColor+66
805226f8 ff08 dec dword ptr [eax]
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: VB6.EXE
LAST_CONTROL_TRANSFER: from 80522a90 to 805226f8
STACK_TEXT:
b5effcb4 80522a90 00000001 0000002f c00205c8 nt!MiRemovePageByColor+0x6
b5effcd0 80514b0f c0600100 c00205c8 00000000 nt!MiRemoveZeroPage+0x8a
b5effce8 805205bd 040b9000 c00205c8 89869810 nt!MiResolveDemandZeroFaul
b5effd4c 80544588 00000001 040b9000 00000001 nt!MmAccessFault+0xbeb
b5effd4c 7c910741 00000001 040b9000 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013fb64 00000000 00000000 00000000 00000000 0x7c910741
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiRemovePageByColor+66
805226f8 ff08 dec dword ptr [eax]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiRemovePageByColor+66
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0xA_nt!MiRemovePageByColor
BUCKET_ID: 0xA_nt!MiRemovePageByColor
Followup: MachineOwner
---------
__________________________
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\duwaynem\Desktop\
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl
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.080814-1
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Wed Jan 7 10:16:55.905 2009 (GMT+10)
System Uptime: 0 days 22:41:03.023
Loading Kernel Symbols
..........................
..........................
Loading User Symbols
Loading unloaded module list
..........................
**************************
* *
* Bugcheck Analysis *
* *
**************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 805ded8e, b6426b6c, 0}
Probably caused by : win32k.sys ( win32k!Win32HeapFree+13 )
Followup: MachineOwner
---------
0: kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
KERNEL_MODE_EXCEPTION_NOT_
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: 805ded8e, The address that the exception occurred at
Arg3: b6426b6c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!RtlpCoalesceFreeBlocks+
805ded8e 8b12 mov edx,dword ptr [edx]
TRAP_FRAME: b6426b6c -- (.trap 0xffffffffb6426b6c)
ErrCode = 00000000
eax=00050712 ebx=bbee0000 ecx=bbf76cf8 edx=00000003 esi=bbf76cf0 edi=bbf76da0
eip=805ded8e esp=b6426be0 ebp=b6426bec iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlpCoalesceFreeBlocks+
805ded8e 8b12 mov edx,dword ptr [edx] ds:0023:00000003=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iexplore.exe
LAST_CONTROL_TRANSFER: from 805e1639 to 805ded8e
STACK_TEXT:
b6426bec 805e1639 bbee0000 00000003 b6426c54 nt!RtlpCoalesceFreeBlocks+
b6426c74 bf80ca54 bbee0000 00000000 bbf76da8 nt!RtlFreeHeap+0xa1
b6426c88 bf8283b3 bbee0000 bbf76da8 0000c031 win32k!Win32HeapFree+0x13
b6426ca4 bf828346 bc027438 00000000 e2067b80 win32k!CreateProp+0x7b
b6426cb8 bf8785ac bbf9e500 0000c031 e2067b80 win32k!InternalSetProp+0x3
b6426cdc bf87864e bbf9e500 d4052a1c 00000000 win32k!SetRedirectionBitma
b6426cf4 bf878d84 bbf9e500 bbf9e500 b6426d30 win32k!CreateRedirectionBi
b6426d04 bf84d1af bbf9e500 00000001 b6426d64 win32k!SetRedirectedWindow
b6426d30 bf84d1fb bbf9e500 00000000 00000000 win32k!_SetLayeredWindowAt
b6426d4c 8054162c 00020f16 00000000 00000000 win32k!NtUserSetLayeredWin
b6426d4c 7c90e4f4 00020f16 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
03b2fce8 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!Win32HeapFree+13
bf80ca54 0fb6c0 movzx eax,al
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: win32k!Win32HeapFree+13
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP:
FAILURE_BUCKET_ID: 0x8E_win32k!Win32HeapFree+
BUCKET_ID: 0x8E_win32k!Win32HeapFree+
Followup: MachineOwner
---------
Main Topics
Browse All Topics
by: nobusPosted on 2009-01-14 at 01:42:49ID: 23371076
can you post a couple of minidumps?