Random BSOD on cold boot

[GizmoTheMogwai]

Just booted this morning, opened up windows media player, played a track for a few seconds, then bang, BSOD.

First BSOD i've had with this hardware.

ATI 5750
E5200
4GB RAM
Gigabyte mobo


If someone could point me in the right direction as to what is causing this, I would be greatly appreciative.

 

[zigzag3143]

Just booted this morning, opened up windows media player, played a track for a few seconds, then bang, BSOD.

First BSOD i've had with this hardware.

ATI 5750
E5200
4GB RAM
Gigabyte mobo


If someone could point me in the right direction as to what is causing this, I would be greatly appreciative.

This crash was probably caused by your Avastsvc.sys (part of your avast anti virus). If it doesnt happen again I would simply forget about it

If it does I would find a different AV app.

Since the actual errrors were memory related I would also download memtestx86 and run it for 5 passes to test .

Ken

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


Loading Dump File [C:\Users\K\Desktop\040610-15802-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`0281f000 PsLoadedModuleList = 0xfffff800`02a5ce50
Debug session time: Tue Apr  6 09:46:01.602 2010 (GMT-4)
System Uptime: 0 days 0:00:38.303
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck DE, {2, fffff8a002b593d0, fffff80002b593d1, ab5ee8c0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2d2e0 )

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

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

POOL_CORRUPTION_IN_FILE_AREA (de)
A driver corrupted pool memory used for holding pages destined for disk.
This was discovered by the memory manager when dereferencing the file.
Arguments:
Arg1: 0000000000000002
Arg2: fffff8a002b593d0
Arg3: fffff80002b593d1
Arg4: 00000000ab5ee8c0

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xDE

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800028343d3 to fffff80002890f00

STACK_TEXT:  
fffff880`06103d18 fffff800`028343d3 : 00000000`000000de 00000000`00000002 fffff8a0`02b593d0 fffff800`02b593d1 : nt!KeBugCheckEx
fffff880`06103d20 fffff800`028763ce : 00000000`00000000 fffffa80`05ed7000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2d2e0
fffff880`06103e10 fffff880`012df447 : fffffa80`05f56768 00000000`00000000 fffff8a0`00000000 00000000`00000000 : nt!CcPurgeCacheSection+0x172
fffff880`06103e80 fffff880`012f8c0a : fffff880`061046f0 fffff8a0`029eeb40 fffff8a0`01fba140 fffff880`0610417c : Ntfs!NtfsDeleteFile+0x57b
fffff880`06104100 fffff880`01266aa9 : 00000000`00000000 fffff880`010f078c fffff880`06104650 fffff880`060f3000 : Ntfs!NtfsCommonCleanup+0x15da
fffff880`06104510 fffff800`028a064a : fffff880`06104650 00000000`00000040 00000000`00000000 fffff800`029c445c : Ntfs!NtfsCommonCleanupCallout+0x19
fffff880`06104540 fffff880`01266662 : fffff880`01266a90 fffff880`06104650 fffff880`06104900 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xda
fffff880`06104620 fffff880`01308244 : fffff880`061046f0 fffff880`061046f0 fffff880`061046f0 00000000`00000000 : Ntfs!NtfsCommonCleanupOnNewStack+0x42
fffff880`06104690 fffff880`010a623f : fffff880`061046f0 fffffa80`06359010 fffffa80`063593b0 fffffa80`0624a870 : Ntfs!NtfsFsdCleanup+0x144
fffff880`06104900 fffff880`010a46df : fffffa80`0498c620 00000000`00000000 fffffa80`044bc700 fffffa80`06359010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`06104990 fffff800`02ba468f : fffffa80`06359010 fffffa80`0563bb30 00000000`00000000 fffffa80`0606fdd0 : fltmgr!FltpDispatch+0xcf
fffff880`061049f0 fffff800`02b8a304 : 00000000`00000000 fffffa80`0563bb30 fffffa80`06410100 fffffa80`0606fdd0 : nt!IopCloseFile+0x11f
fffff880`06104a80 fffff800`02ba4181 : fffffa80`0563bb30 fffffa80`00000001 fffff8a0`01b70f00 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`06104b00 fffff800`02ba4094 : 00000000`000005f4 fffffa80`0563bb30 fffff8a0`01b70f00 00000000`000005f4 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`06104b90 fffff800`02890153 : fffffa80`057fc840 fffff880`06104c60 00000000`fff53000 fffffa80`05900740 : nt!ObpCloseHandle+0x94
fffff880`06104be0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2d2e0
fffff800`028343d3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2d2e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d2e0

BUCKET_ID:  X64_0xDE_nt!_??_::FNODOBFM::_string_+2d2e0

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