troubleshooting Question

Blue Screen Crash

Avatar of LLC0706
LLC0706 asked on
Windows 7
29 Comments4 Solutions711 ViewsLast Modified:
Hi

I keep getting Blue Screen Crashes on my Windows 7 computer.  Iiniyially  though it may have been a faulty hard drive, so I brought another one and installed it.  However I 'm still getting the same problem.

I've ran windows memory diagnostic, which didn't report any errors. I've also ran windows verifier, setting it to all drivers.  This picked up a driver error.  I installed and ran Driver Genius, which located 20+ out of date drivers.

I thought this would solve my problem, but it crashed again.

I have 2 500mb internal hard drives installed, one with 2 operating systems installed on it and the other is the data drive.

I've opened the minidump file and attached it, this one and several of the others state memmory corruption.  I have 4 x 1GB sticks of memory installed on a Windows 7 Ultimate 32bit os.

Please can anyone help me solve this problem.


Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\My Documents\Blue Screen Crash\New folder\080811-28360-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.x86fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0x82a15000 PsLoadedModuleList = 0x82b5e4d0
Debug session time: Mon Aug  8 20:30:45.977 2011 (UTC + 1:00)
System Uptime: 0 days 0:09:54.460
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 8ba53ac6, 9724ba9c, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 8ba53ac6, The address that the exception occurred at
Arg3: 9724ba9c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
fltmgr!FltpRemoveAllStreamHandleContextsForFileObject+18
8ba53ac6 ff              ???

TRAP_FRAME:  9724ba9c -- (.trap 0xffffffff9724ba9c)
ErrCode = 00000000
eax=8665f138 ebx=8664d790 ecx=00000000 edx=00000000 esi=00000000 edi=85c7f080
eip=8ba53ac6 esp=9724bb10 ebp=9724bb20 iopl=0         nv up di ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010082
fltmgr!FltpRemoveAllStreamHandleContextsForFileObject+0x18:
8ba53ac6 ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8ba48eac to 8ba53ac6

FAILED_INSTRUCTION_ADDRESS: 
fltmgr!FltpRemoveAllStreamHandleContextsForFileObject+18
8ba53ac6 ff              ???

STACK_TEXT:  
9724bb20 8ba48eac 860098b8 8665f108 9724bb9c fltmgr!FltpRemoveAllStreamHandleContextsForFileObject+0x18
9724bb30 8ba41cd8 86eb8008 860098b8 8665f108 fltmgr!FltpCleanupStreamListCtrlForFileObjectCloseWithStreamListCtrl+0x10
9724bb9c 8ba449f0 9724bbf0 85f05bd0 85f05da8 fltmgr!FltpPerformPreCallbacks+0x53a
9724bbb4 8ba44f01 9724bbf0 00000000 86f0dcd0 fltmgr!FltpPassThroughInternal+0x40
9724bbd8 8ba453ba 0224bbf0 86f0dcd0 860098b8 fltmgr!FltpPassThrough+0x203
9724bc08 82a4c593 86f0dcd0 85f05bd0 86f0e024 fltmgr!FltpDispatch+0xb4
9724bc20 82c46965 85397900 860098a0 00000000 nt!IofCallDriver+0x63
9724bc64 82c37581 860098b8 860098b8 860098a0 nt!IopDeleteFile+0x10c
9724bc7c 82a8dd60 00000000 8568d030 860098a0 nt!ObpRemoveObjectRoutine+0x59
9724bc90 82a8dcd0 860098b8 82c5a30c ba2d0ce8 nt!ObfDereferenceObjectWithTag+0x88
9724bc98 82c5a30c ba2d0ce8 8568d030 00000390 nt!ObfDereferenceObject+0xd
9724bcdc 82c5a032 ba2d0ce8 bf46a720 8559b490 nt!ObpCloseHandleTableEntry+0x21d
9724bd0c 82c5a3cc 8559b490 8568d001 00c5fb70 nt!ObpCloseHandle+0x7f
9724bd28 82a531ea 00000390 00c5fbb0 77b170b4 nt!NtClose+0x4e
9724bd28 77b170b4 00000390 00c5fbb0 77b170b4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c5fbb0 00000000 00000000 00000000 00000000 0x77b170b4


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !fltmgr
    8ba53ac3 - fltmgr!FltpRemoveAllStreamHandleContextsForFileObject+15
	[ e8:e0 ]
1 error : !fltmgr (8ba53ac3)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
ASKER CERTIFIED SOLUTION
LLC0706

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 4 Answers and 29 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 4 Answers and 29 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros