Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


windows vista constantly taking a dump

  • Please log in to reply
No replies to this topic

#1 pstee


  • Members
  • 1 posts
  • Local time:01:16 AM

Posted 23 April 2009 - 11:40 PM

can someone please tell me what is causing my laptop to dump, it is a dell 1520 intel core 2 duo t7500 2.2GHz, windows vista home premium 32bit, nvidia geforce 8600M GT.

It has been happening alot lately and most of the time when i am playing a website flash game (mybrute.com)

Below is my dump information. Thank you.

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini042309-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:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x81e36000 PsLoadedModuleList = 0x81f4dc70
Debug session time: Thu Apr 23 18:06:00.569 2009 (GMT-7)
System Uptime: 0 days 0:39:58.634
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81ea1051, a96a988c, 0}

Probably caused by : memory_corruption ( nt!MiCheckControlArea+246 )

Followup: MachineOwner

0: kd> !analyze -v
* *
* Bugcheck Analysis *
* *

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
Arg1: c0000005, The exception code that was not handled
Arg2: 81ea1051, The address that the exception occurred at
Arg3: a96a988c, 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.

81ea1051 8b33 mov esi,dword ptr [ebx]

TRAP_FRAME: a96a988c -- (.trap 0xffffffffa96a988c)
ErrCode = 00000000
eax=00000000 ebx=00000015 ecx=81f6ed00 edx=00000000 esi=00000000 edi=874a25d0
eip=81ea1051 esp=a96a9900 ebp=a96a9910 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
81ea1051 8b33 mov esi,dword ptr [ebx] ds:0023:00000015=????????
Resetting default scope




PROCESS_NAME: svchost.exe


LAST_CONTROL_TRANSFER: from 81ea0950 to 81ea1051

a96a9910 81ea0950 874a25d0 00000000 00000000 nt!MiCheckControlArea+0x246
a96a9928 8207a898 874a25d0 00000001 00000000 nt!MiDereferenceControlAreaBySection+0x2d
a96a994c 8207a5e7 874a25d0 81e0a110 abe96378 nt!MiSectionDelete+0x101
a96a9968 81e878c9 abe96390 00000000 8461dcd0 nt!ObpRemoveObjectRoutine+0x13d
a96a9990 820534ca 88802fc8 8461dcd0 00002dd4 nt!ObfDereferenceObject+0xa1
a96a99d0 820536c0 88802fc8 a5fedba8 83c3ec10 nt!ObpCloseHandleTableEntry+0x24e
a96a9a00 820538e5 83c3ec10 577a0000 577a0000 nt!ObpCloseHandle+0x73
a96a9a14 81fd5019 80002dd4 aeaf4d88 a96a9aac nt!NtClose+0x20
a96a9a24 81fd4c3e 87113358 00000000 c0000240 nt!PfpReadSupportCleanup+0x15
a96a9aac 81fd52d7 006a9aec a96a9be4 00000001 nt!PfpPrefetchFilesTrickle+0x1e8
a96a9b00 81fd5574 aeaf4000 b24a88c5 a96a9bf8 nt!PfpPrefetchRequestPerform+0x295
a96a9b54 820144b2 a96a9be4 81f2e801 b24a8f89 nt!PfpPrefetchRequest+0x16e
a96a9c18 8202dcf3 05faf748 00000014 81f2e801 nt!PfSetSuperfetchInformation+0x182
a96a9d50 81e8da1a 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x908
a96a9d50 77c39a94 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
05faf760 00000000 00000000 00000000 00000000 0x77c39a94


81ea1051 8b33 mov esi,dword ptr [ebx]


SYMBOL_NAME: nt!MiCheckControlArea+246




IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x8E_nt!MiCheckControlArea+246

BUCKET_ID: 0x8E_nt!MiCheckControlArea+246

Followup: MachineOwner

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users