Hi
I have carried out memtests and prime95 tests for days but didnt find any hardware problems. however these bsods keep comming with new errors.
this time its due to csrss & also due to my firewall but i have just bought the new version Outpost Firewall Pro ver. 4.0.1007.7323 (591) and it still giving me the error,
I have carried out memtests and prime95 tests for days but didnt find any hardware problems. however these bsods keep comming with new errors.
this time its due to csrss & also due to my firewall but i have just bought the new version Outpost Firewall Pro ver. 4.0.1007.7323 (591) and it still giving me the error,
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini020507-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: c:\foo: SRV*c:\foo*Symbol information
Executable search path is: c:\windows\system32; c:\windows\system\system32; Index of /SymServe
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.061030-0020
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Mon Feb 5 03:23:15.390 2007 (GMT+13)
System Uptime: 1 days 2:06:12.108
Loading Kernel Symbols
.........................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, 86c17a78, 86c17bec, 805d1370}
Unable to load image Sandbox.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for Sandbox.SYS
*** ERROR: Module load completed but symbols could not be loaded for Sandbox.SYS
*** WARNING: Unable to verify timestamp for guard.sys
*** ERROR: Module load completed but symbols could not be loaded for guard.sys
*** WARNING: Unable to verify timestamp for FILTNT.SYS
*** ERROR: Module load completed but symbols could not be loaded for FILTNT.SYS
Probably caused by : csrss.exe
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 86c17a78, Terminating object
Arg3: 86c17bec, Process image file name
Arg4: 805d1370, Explanatory message (ascii)
Debugging Details:
------------------
PROCESS_OBJECT: 86c17a78
IMAGE_NAME: csrss.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: csrss
FAULTING_MODULE: 00000000
PROCESS_NAME: csrss.exe
EXCEPTION_RECORD: aa9e49d8 -- (.exr ffffffffaa9e49d8)
ExceptionAddress: 75b7af1d
ExceptionCode: c0000006 (In-page I/O error)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000008
Parameter[1]: 75b7af1d
Parameter[2]: c000009a
Inpage operation failed at 75b7af1d, due to I/O error c000009a
EXCEPTION_CODE: (NTSTATUS) 0xc000009a - Insufficient system resources exist to complete the API.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".
IO_ERROR: (NTSTATUS) 0xc000009a - Insufficient system resources exist to complete the API.
EXCEPTION_STR: 0xc0000006_c000009a
FAULTING_IP:
+75b7af1d
75b7af1d ?? ???
BUGCHECK_STR: 0xF4_IOERR_C000009A
STACK_TEXT:
aa9e43e4 805d0517 000000f4 00000003 86c17a78 nt!KeBugCheckEx+0x1b
aa9e4408 805d141b 805d1370 86c17a78 86c17bec nt!PspCatchCriticalBreak+0x75
aa9e4438 aa9400f8 86c17cc0 c0000006 aa9e4584 nt!NtTerminateProcess+0x7d
WARNING: Stack unwind information not available. Following frames may be wrong.
aa9e450c f7c6e89f ffffffff c0000006 aa9e4584 Sandbox+0x140f8
aa9e454c aaac1ad1 ffffffff c0000006 aa9e4584 guard+0x89f
aa9e4574 805409dc ffffffff c0000006 aa9e49b0 FILTNT+0x13ad1
aa9e4574 805007a1 ffffffff c0000006 aa9e49b0 nt!KiFastCallEntry+0xfc
aa9e45f4 804fe7d2 ffffffff c0000006 aa9e49f8 nt!ZwTerminateProcess+0x11
aa9e49b0 80501edf aa9e49d8 00000000 aa9e4d64 nt!KiDispatchException+0x3a0
aa9e4d34 805442a7 00c8fbd4 00c8fbf4 00000000 nt!KiRaiseException+0x175
aa9e4d50 805409dc 00c8fbd4 00c8fbf4 00000000 nt!NtRaiseException+0x33
aa9e4d50 75b7af1d 00c8fbd4 00c8fbf4 00000000 nt!KiFastCallEntry+0xfc
00c8fed0 00000000 00000000 00000000 00000000 0x75b7af1d
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: 0xF4_IOERR_C000009A_IMAGE_csrss.exe
BUCKET_ID: 0xF4_IOERR_C000009A_IMAGE_csrss.exe
Followup: MachineOwner
---------