VISTA BSOD Help

[aliwoo]

Hi everyone, I'm new to the site so a big hello.

I've recently bought MS Vista and have installed it on a brand HDD i bought for a very clean install. Since the upgrade i have been having blue screens periodically. I have gone through and upgraded all the device drivers to the correct versions but the blue screens continue. It can be several times a day or not for days in occurance and its driving me crazy trying to track down the issues. I'm a hardware expert but not an OS one and have swap tested all coponents, run hardware memory tests during boot up with MS and independant testing software. I'm pretty confident that it isn't hardware related but need an OS BSOD expert to peruse over my dump below to see where you suspect the issues are. I also get machine hangs which implies resorces or drivers are conflicting with neither relinquishing, but i don't think the dump below shows enough information to confirm that. Any help any of you could give would be greatly appreciated.

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


Loading Dump File [C:\Windows\Minidump\Mini020908-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Windows\Symbols;http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d08ad0
Debug session time: Sat Feb 9 14:31:58.452 2008 (GMT+0)
System Uptime: 0 days 4:02:04.123
Loading Kernel Symbols
.................................................. ......................... .................................................. .......................
Loading User Symbols
Loading unloaded module list
......
************************************************** ************************* ****
* *
* Bugcheck Analysis *
* *
************************************************** ************************* ****

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81c68356, a0527738, 0}



Probably caused by : ntkrnlmp.exe ( nt!FsRtlAcquireFileExclusiveCommon+31 )

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: 81c68356, The address that the exception occurred at
Arg3: a0527738, 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+27
81c68356 8b4924 mov ecx,dword ptr [ecx+24h]

TRAP_FRAME: a0527738 -- (.trap 0xffffffffa0527738)
ErrCode = 00000000
eax=8483c5d0 ebx=00000000 ecx=00000040 edx=8483c5d6 esi=00000000 edi=8483c5d0
eip=81c68356 esp=a05277ac ebp=a05277b4 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+0x27:
81c68356 8b4924 mov ecx,dword ptr [ecx+24h] ds:0023:00000064=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 81e18412 to 81c68356

STACK_TEXT:
a05277b4 81e18412 8483c5d0 8483c5d0 847b499c nt!IoGetRelatedDeviceObject+0x27
a0527908 81e18614 8483c5d0 00000000 00000007 nt!FsRtlAcquireFileExclusiveCommon+0x31
a052791c 81c95b67 8483c5d0 847b499c 00000000 nt!FsRtlAcquireFileExclusive+0x12
a0527948 81e035db a052c2dc 00000000 00000000 nt!CcZeroEndOfLastPage+0x40
a052799c 81daa9de a0527a2c 0000000d a05279d0 nt!NtCreateSection+0x194
a0527a18 81d9c87f a0527aec c6102428 00000001 nt!PfpFileBuildReadSupport+0xe4
a0527aac 81d9ebff 00527aec a0527be4 00000001 nt!PfpPrefetchFilesTrickle+0xdf
a0527b00 81d9f17b c60ff000 a052c014 a0527bf8 nt!PfpPrefetchRequestPerform+0x295
a0527b54 81dfa68b a0527be4 81cec701 a052c758 nt!PfpPrefetchRequest+0x16e
a0527c18 81df824a 034df90c 00000014 81cec701 nt!PfSetSuperfetchInformation+0x182
a0527d50 81c460fa 0000004f 00000000 00000014 nt!NtSetSystemInformation+0x90e
a0527d50 77020f34 0000004f 00000000 00000014 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
034df924 00000000 00000000 00000000 00000000 0x77020f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!FsRtlAcquireFileExclusiveCommon+31
81e18412 ff7508 push dword ptr [ebp+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!FsRtlAcquireFileExclusiveCommon+31

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 470c2eb8

FAILURE_BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31

BUCKET_ID: 0x8E_nt!FsRtlAcquireFileExclusiveCommon+31

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

[Rootstonian]

Sounds like you got a buggy device driver or or running some program that's crashing Vista.

Have you recently installed a new piece of hardware and it's associated device drivers?

What programs do you have installed (outside of what the OS installs)?