Господа! Помогите, пожалуйста с исправлением проблемы синего экрана!
дамп памяти
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081411-34281-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Windows 7 Kernel Version 7601 (Service Pack 1.721) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17105.x86fre.win7sp1_rc.100929-1730
Machine Name:
Kernel base = 0x8180e000 PsLoadedModuleList = 0x8194e5b0
Debug session time: Sun Aug 14 23:53:26.794 2011 (GMT+4)
System Uptime: 7 days 17:27:30.088
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 81a40005, a40dbbdc, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c000001d, The exception code that was not handled
Arg2: 81a40005, The address that the exception occurred at
Arg3: a40dbbdc, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {
FAULTING_IP:
nt!ApphelpCacheLockExclusiveNoWait+0
81a40005 8f ???
TRAP_FRAME: a40dbbdc -- (.trap 0xffffffffa40dbbdc)
ErrCode = 00000000
eax=00000000 ebx=81940640 ecx=83c43d48 edx=00000000 esi=81940600 edi=0119e900
eip=81a40005 esp=a40dbc50 ebp=a40dbcb0 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!ApphelpCacheLockExclusiveNoWait:
81a40005 8f ???
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0x8E
PROCESS_NAME: services.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 81a3ff18 to 81a40005
FAILED_INSTRUCTION_ADDRESS:
nt!ApphelpCacheLockExclusiveNoWait+0
81a40005 8f ???
STACK_TEXT:
a40dbc4c 81a3ff18 81940600 8fa793b1 0119e900 nt!ApphelpCacheLockExclusiveNoWait
a40dbcb0 81a3f9d5 a40dbcf4 80000698 0119e900 nt!ApphelpCacheLookupEntry+0x103
a40dbd24 8184387a 00000000 0119e870 0119e940 nt!NtApphelpCacheControl+0xa6
a40dbd24 779b6b74 00000000 0119e870 0119e940 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0119e940 00000000 00000000 00000000 00000000 0x779b6b74
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
81a40004-81a40006 3 bytes - nt!ApphelpCacheLockSharedNoWait+3b
[ 90 8b ff:ff 8f 7f ]
3 errors : !nt (81a40004-81a40006)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
quit: