Windows 7: BSODS on new system

ryanmcrae · 24 Aug 2010

Hi, I'm getting pretty random BSODs, usually anything between 1 hour and 12 after booting.

I've attached the zip file requested on the sticky.

I'm using:

OS Windows 7 Ultimate 32 Bit OEM
System = 1 week old
OS Install = 1 week old

Can anyone advise?

Thanks in advance,

Ryan

ttran · 25 Aug 2010

Hi there,

I suspect the graphic card since directX was blamed in the DMP a lot with stop code 7E and 8E, which is usually graphic driver related. First thing to try is to re-install the graphic card driver, When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

When it is removed then download and install the fresh copy.

After doing that, update directX as well:
Download details: DirectX End-User Runtime

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.

Please remove Avast: avast! Uninstall Utility
Replace by MSE: http://www.microsoft.com/security_essentials

BUGCHECK SUMMARY:

Code:

BugCheck 19, {3, cb40d058, c340d058, cb40d058}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+312 )

Followup: Pool_corruption
---------
BugCheck 50, {839b4950, 0, 8fe7e707, 0}


Could not read faulting driver name
Probably caused by : fastfat.SYS ( fastfat!FatFindFcb+17 )

Followup: MachineOwner
---------
BugCheck 19, {3, 8af054b0, 82f054b0, 8af054b0}

*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+312 )

Followup: Pool_corruption
---------
BugCheck 1000008E, {c0000005, 828b6117, aa16d86c, 0}

Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+61 )

Followup: MachineOwner
---------
BugCheck 1000007E, {c0000005, 905fc3d0, 8ddc7ea0, 8ddc7a80}

Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------
BugCheck 7F, {d, 0, 0, 0}

Probably caused by : RDPDD.dll ( RDPDD!SSECBCHash::AddToHash_SSE+35 )

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

Run system file check please:
SFC /SCANNOW Command - System File Checker

I want to ask you few question:
-Are you overclocking anything?
-Have you done anything such as changing registry etc?

Let us know if you need help

Tuan

zigzag3143 · 25 Aug 2010

Also of note the aswsp.sys file was loaded at the time. That is an Avast driver and AV apps can be the cause. I would also remove avast and replace it with MSE.

Jonathan_King · 25 Aug 2010

Here is the Avast removal tool: http://files.avast.com/files/eng/aswclear5.exe

MSE: http://www.microsoft.com/security_essentials

Windows 7: BSODS on new system

BSODS on new system problems?