I have been getting the blue screen and memory dump .. I always get the same Bugcheck Analysis .. Any Suggetsions? .. here's the debug results:
Note: That always happens when refreshing IE while working on some .net application using MS VS.NET .. I'm using Kaspersky KIS and Zone Alarm at the same time.
================================================== ======
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Sep 1 20:49:16.203 2009 (GMT+2)
System Uptime: 1 days 5:38:00.937
Loading Kernel Symbols
.................................................. .............
.................................................. .......
Loading User Symbols
Loading unloaded module list
................................
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000BE, {7c90eb98, ec1d025, bacdbc10, a}
Probably caused by : ntkrpamp.exe ( nt!CcFlushCache+bf )
Followup: MachineOwner
---------
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: 7c90eb98, Virtual address for the attempted write.
Arg2: 0ec1d025, PTE contents.
Arg3: bacdbc10, (reserved)
Arg4: 0000000a, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xBE
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from 804e482b to 804e41ed
STACK_TEXT:
bacdbcf0 804e482b b5e3ad64 00000000 00000001 nt!CcFlushCache+0xbf
bacdbd34 804e7041 89e81038 80563720 89e3e998 nt!CcWriteBehind+0x119
bacdbd7c 80537757 89e81038 00000000 89e3e998 nt!CcWorkerThread+0x12f
bacdbdac 805ce794 89e81038 00000000 00000000 nt!ExpWorkerThread+0xef
bacdbddc 805450ce 80537668 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!CcFlushCache+bf
804e41ed ff4604 inc dword ptr [esi+4]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!CcFlushCache+bf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 41107b0d
FAILURE_BUCKET_ID: 0xBE_nt!CcFlushCache+bf
BUCKET_ID: 0xBE_nt!CcFlushCache+bf
Followup: MachineOwner
---------
Thank you In Advance
Bookmarks