Windows 7 Crashing... Please Help!

So I'm normally a tomshardware.com user, but the *******s there were not very helpful and quite irritating, so I was told to try seven forums by a friend.

Here's my situation:
I have just upgraded from Windows 7 RC to Win 7 32 bit Enterprise Edition with no problems. Did a fresh install and had it formatted.

Just got my first BSOD/crash, and I had been having regular crashes (about once every 4-5 days) I don't think it's hardware related, probably driver, so I was hoping people could help narrow it down and kill this problem for good.

Here's the text of the BSOD:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 828D1082
BCP3: 8C28D920
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020910-24320-01.dmp
C:\Users\Jivan\AppData\Local\Temp\WER-74646-0.sysdata.xml


Here's a megaupload link for the .dmp file
MEGAUPLOAD - The leading online storage and file delivery service

I'm hopeful!

Thanks

-J

jachreja said:

So I'm normally a tomshardware.com user, but the *******s there were not very helpful and quite irritating, so I was told to try seven forums by a friend.

Here's my situation:
I have just upgraded from Windows 7 RC to Win 7 32 bit Enterprise Edition with no problems. Did a fresh install and had it formatted.

Just got my first BSOD/crash, and I had been having regular crashes (about once every 4-5 days) I don't think it's hardware related, probably driver, so I was hoping people could help narrow it down and kill this problem for good.

Here's the text of the BSOD:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 828D1082
BCP3: 8C28D920
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\020910-24320-01.dmp
C:\Users\Jivan\AppData\Local\Temp\WER-74646-0.sysdata.xml


Here's a megaupload link for the .dmp file
MEGAUPLOAD - The leading online storage and file delivery service

I'm hopeful!

Thanks

-J

Hi J

this one was caused by fltmgr.sys which is part of the MS OS

I would
run a system file check
type cmd in search>right click and run as admin>sfc /scannow

If you are over clocking stop

Let us know the results


Ken


[code]

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


Loading Dump File [C:\Users\K\Desktop\020910-24320-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8281e000 PsLoadedModuleList = 0x82966810
Debug session time: Tue Feb 9 03:06:39.799 2010 (GMT-5)
System Uptime: 0 days 0:28:22.953
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 828d1082, 8c28d920, 0}

Probably caused by : fltmgr.sys ( fltmgr!FltpCompleteRequest+2d )

Followup: MachineOwner
---------

0: 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: c0000005, The exception code that was not handled
Arg2: 828d1082, The address that the exception occurred at
Arg3: 8c28d920, 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.

FAULTING_IP:
nt!IoGetRelatedDeviceObject+28
828d1082 8b4924 mov ecx,dword ptr [ecx+24h]

TRAP_FRAME: 8c28d920 -- (.trap 0xffffffff8c28d920)
ErrCode = 00000000
eax=8520d280 ebx=00000000 ecx=00000000 edx=0000000e esi=84fea600 edi=84fea847
eip=828d1082 esp=8c28d994 ebp=8c28d99c 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!IoGetRelatedDeviceObject+0x28:
828d1082 8b4924 mov ecx,dword ptr [ecx+24h] ds:0023:00000024=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82886c2d to 828d1082

STACK_TEXT:
8c28d99c 82886c2d 8520d280 00000000 84fea600 nt!IoGetRelatedDeviceObject+0x28
8c28d9dc 8a7259a7 8c28d9fc 8a725aa1 84fea600 nt!IopfCompleteRequest+0x222
8c28d9e4 8a725aa1 84fea600 00000000 84fea600 fltmgr!FltpCompleteRequest+0x2d
8c28d9fc 8a7262e9 8519d9c0 84fea600 00000000 fltmgr!FltpSynchronizeIoCleanup+0x4f
8c28da24 8a7398c9 8c28da44 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x387
8c28da70 8285a4bc 850816c0 851f8008 8520d2dc fltmgr!FltpCreate+0x2db
8c28da88 82a5e62d a7183f9c 8c28dc30 00000000 nt!IofCallDriver+0x63
8c28db60 82a3f1d7 86f5bb38 85ee4a00 8522c008 nt!IopParseDevice+0xed7
8c28dbdc 82a6524d 00000000 8c28dc30 00000040 nt!ObpLookupObjectName+0x4fa
8c28dc38 82a5d5ab 046ae694 84ee4a00 82889301 nt!ObOpenObjectByName+0x159
8c28dcb4 82a68eb6 046ae6f0 00100081 046ae694 nt!IopCreateFile+0x673
8c28dd00 8286142a 046ae6f0 00100081 046ae694 nt!NtCreateFile+0x34
8c28dd00 779264f4 046ae6f0 00100081 046ae694 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
046ae6f8 00000000 00000000 00000000 00000000 0x779264f4


STACK_COMMAND: kb

FOLLOWUP_IP:
fltmgr!FltpCompleteRequest+2d
8a7259a7 5d pop ebp

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: fltmgr!FltpCompleteRequest+2d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: fltmgr

IMAGE_NAME: fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf11

FAILURE_BUCKET_ID: 0x8E_fltmgr!FltpCompleteRequest+2d

BUCKET_ID: 0x8E_fltmgr!FltpCompleteRequest+2d

Followup: MachineOwner
---------

Thanks for the advice guys! Running both tests now, i'll post the results as soon as possible.
I'm running Avast! Antivirus, fully updated, and i did a full clean install when I installed the Enterprise edition. If it's simple malaware, my life is going to be so nice.

Fingers crossed!

jachreja

The Windows Resource Protection through the cmd as the previous poster suggested, just finished and found no errors or integrity violations.

Malaware scan just finished, also no problems
Next steps?

Any updates ladies and gentlemen?