Overclock.net › Forums › Intel › Intel - General › Memory Management BSOD
New Posts  All Forums:Forum Nav:

Memory Management BSOD

post #1 of 6
Thread Starter 
Minidump File 35k .zip file Hey guys, I'm getting a memory management BSOD. The specs are in my signature. It seems to happen at random times. Overclocked memory at 1600MHz.

Here are the minidumps:
1: http://www.filefactory.com/file/3n2zd6p8v4gf/n/040512-9984-01.zip

2: http://www.filefactory.com/file/2swx3n60y6xb/n/minidump.zip
Edited by Avian - 4/4/12 at 5:38pm
post #2 of 6
I'm not going to bother with Filefactory, can you please zip the dumps up and attach them using the OCN attachment system? Thanks.
post #3 of 6
Thread Starter 
Okay, I have done that. Thank you for taking your time to read my post, hope you find out the problem!
post #4 of 6
Hi smile.gif

The dumps are pointing to the culprit aswSP.SYS, which is the avast! Self Protection Driver. Avast is sometimes known to cause issues in the Windows environment, specifically Windows 7, so for diagnostic purposes, please fully uninstall !avast from your system. I would also recommend fully removing the Gigabyte EasyTune6 software as this is a gigantic causer of crashes and freezes in Windows 7. If you'd like, you can remove Gigabyte EasyTune6 before seeing if it's not just Gigabyte EasyTune6 forcing !avast to crash, and if you're still crashing after removing the Gigabyte EasyTune6 software, you can then remove !avast as well.

A few drivers that need to be updated:
Quote:
GVTDrv64.sys - Tue Sep 05 03:10:02 2006 (Gigabyte EasyTune6 driver (known issues w/Win7). The driver is from 2006, we're removing this, so no relevance in updating it.

Lycosa.sys - Update here.
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040412-12168-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03250000 PsLoadedModuleList = 0xfffff800`03494650
Debug session time: Wed Apr  4 07:25:14.047 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:25.843
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 1020, 0, 0}

Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswSP.SYS ( aswSP+39953 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000001020
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dllhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b987290 -- (.trap 0xfffff8800b987290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000002f58 rbx=0000000000000000 rcx=0000000000110158
rdx=0000058000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003144953 rsp=fffff8800b987420 rbp=fffffa8012aaee58
 r8=0000007ffffffff8  r9=0000098000000000 r10=0000000000000000
r11=fffff8800b987380 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
aswSP+0x39953:
fffff880`03144953 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032610be to fffff800032ccd40

STACK_TEXT:  
fffff880`0b986c78 fffff800`032610be : 00000000`0000001a 00000000`00041287 00000000`00001020 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b986c80 fffff800`032cae6e : 00000000`00000000 00000000`00001020 00000000`00000000 00000000`00001000 : nt! ?? ::FNODOBFM::`string'+0x45a35
fffff880`0b986de0 fffff800`033cd6b3 : 00000000`00000000 fffffa80`0808b180 fffff680`00000400 fffff700`01080000 : nt!KiPageFault+0x16e
fffff880`0b986f70 fffff800`0333aec1 : 00000003`00000000 00000000`002ad91d fffff880`0b987000 80d00003`4f6f6225 : nt!MiLogPageAccess+0x33
fffff880`0b986fc0 fffff800`032d9c9d : 00000000`00110158 fffff680`00000880 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34e51
fffff880`0b987130 fffff800`032cae6e : 00000000`00000001 00000000`00110158 fffffa80`135ce700 00000000`00000000 : nt!MmAccessFault+0xc6d
fffff880`0b987290 fffff880`03144953 : 00000000`00112f48 00000000`00000000 fffff880`0b987500 00000000`00000031 : nt!KiPageFault+0x16e
fffff880`0b987420 00000000`00112f48 : 00000000`00000000 fffff880`0b987500 00000000`00000031 00000000`00070024 : aswSP+0x39953
fffff880`0b987428 00000000`00000000 : fffff880`0b987500 00000000`00000031 00000000`00070024 00000000`00000000 : 0x112f48


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSP+39953
fffff880`03144953 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  aswSP+39953

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4f56a5f3

FAILURE_BUCKET_ID:  X64_0x1a_41287_aswSP+39953

BUCKET_ID:  X64_0x1a_41287_aswSP+39953

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

4: kd> !thread
GetPointerFromAddress: unable to read from fffff800034fe000
THREAD fffffa80135ce740  Cid 0974.05e8  Teb: 000000007efdb000 Win32Thread: 0000000000000000 RUNNING on processor 4
Not impersonating
GetUlongFromAddress: unable to read from fffff8000343dba4
Owning Process            fffffa80135a3060       Image:         dllhost.exe
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      5502         
Context Switch Count      2             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address 0x0000000000111609
Stack Init fffff8800b987c70 Current fffff8800b987440
Base fffff8800b988000 Limit fffff8800b982000 Call 0
Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0b986c78 fffff800`032610be : 00000000`0000001a 00000000`00041287 00000000`00001020 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b986c80 fffff800`032cae6e : 00000000`00000000 00000000`00001020 00000000`00000000 00000000`00001000 : nt! ?? ::FNODOBFM::`string'+0x45a35
fffff880`0b986de0 fffff800`033cd6b3 : 00000000`00000000 fffffa80`0808b180 fffff680`00000400 fffff700`01080000 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0b986de0)
fffff880`0b986f70 fffff800`0333aec1 : 00000003`00000000 00000000`002ad91d fffff880`0b987000 80d00003`4f6f6225 : nt!MiLogPageAccess+0x33
fffff880`0b986fc0 fffff800`032d9c9d : 00000000`00110158 fffff680`00000880 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34e51
fffff880`0b987130 fffff800`032cae6e : 00000000`00000001 00000000`00110158 fffffa80`135ce700 00000000`00000000 : nt!MmAccessFault+0xc6d
fffff880`0b987290 fffff880`03144953 : 00000000`00112f48 00000000`00000000 fffff880`0b987500 00000000`00000031 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0b987290)
fffff880`0b987420 00000000`00112f48 : 00000000`00000000 fffff880`0b987500 00000000`00000031 00000000`00070024 : aswSP+0x39953
fffff880`0b987428 00000000`00000000 : fffff880`0b987500 00000000`00000031 00000000`00070024 00000000`00000000 : 0x112f48

post #5 of 6
Thread Starter 
Hmm, so would I have to remove avast! Antivirus permanently? Could I reinstall it perhaps? I'll try these steps tommorow, thanks a bunch for your help!
post #6 of 6
No, I would not reinstall it if it's causing issues as I have said it's known to sometimes unfortunately causes issues with the Windows 7 environment. There are many alternatives to !avast, anyway.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › Memory Management BSOD