BSOD playing Ragnarok 2, error 1000008e

Apparently it is avast! Virtualization Driver that is causing the BSOD there.

Code:

addcd22c  94412a95Unable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
 aswSnx+0x8a95]

Description here: Driver Reference Table - aswSnx.SYS

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know the results.

____________________________________________________________________
BSOD ANALYSIS:

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Arch\Desktop\SF_08-06-2013\060813-31418-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.x86fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0x82e09000 PsLoadedModuleList = 0x82f524d0
Debug session time: Sat Jun  8 20:41:34.775 2013 (UTC + 5:30)
System Uptime: 0 days 0:25:08.508
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {c06063a0, 0, 0, 82e6c8e1}

Probably caused by : memory_corruption ( nt!MiIsWsleHashValid+33 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: c06063a0, memory referenced
Arg2: 00000000, IRQL
Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82e6c8e1, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82f7284c
Unable to read MiSystemVaType memory at 82f51e20
 c06063a0 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiIsWsleHashValid+33
82e6c8e1 8b81000000c0    mov     eax,dword ptr [ecx-40000000h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  WinSAT.exe

TRAP_FRAME:  addcdbe8 -- (.trap 0xffffffffaddcdbe8)
ErrCode = 00000009
eax=00000000 ebx=00007eab ecx=006063a0 edx=c0802000 esi=c0802d08 edi=1cd3f001
eip=82e6c8e1 esp=addcdc5c ebp=addcdc64 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!MiIsWsleHashValid+0x33:
82e6c8e1 8b81000000c0    mov     eax,dword ptr [ecx-40000000h] ds:0023:c06063a0=00000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e6c8e1 to 82e49c9b

STACK_TEXT:  
addcdbe8 82e6c8e1 badb0d00 c0802000 85346978 nt!KiTrap0E+0x2cf
addcdc64 82e70012 840f9b70 85f9dd48 c0600730 nt!MiIsWsleHashValid+0x33
addcdc78 82e2e47e c0c744fc 899eaf76 ffffffff nt!MiLocateWsle+0x89
addcdd1c 82e468ba ffffffff 069af898 069af89c nt!NtLockVirtualMemory+0x2bc
addcdd1c 774e7094 ffffffff 069af898 069af89c nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
069af890 00000000 00000000 00000000 00000000 0x774e7094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIsWsleHashValid+33
82e6c8e1 8b81000000c0    mov     eax,dword ptr [ecx-40000000h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiIsWsleHashValid+33

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5147d331

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0xA_nt!MiIsWsleHashValid+33

BUCKET_ID:  0xA_nt!MiIsWsleHashValid+33

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

Please follow the Windows Update Posting Instructions and post the requested data - there appear to be unresolved errors in Windows update, which may be affecting things.

PsychoticBiotic said:

So, I came around to buying a bigger case (No cable management/cramped in old case) and a better power supply. (Previous one was only 400w. New one is 750w). I was attempting to run a benchmark test, just a regular one and it was going through the 3D arts and then it BSd with "MEMORY MANAGEMENT" in caps. Any help with this is much appreciated!

Here are my files!

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.

Also, the Linksys Wireless-G PCI Adapter Driver has some bearing in your BSODs.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {4ff696, 2, 1, 94a3297b}

Unable to load image \SystemRoot\system32\DRIVERS\WMP54Gv41x86.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WMP54Gv41x86.sys
*** ERROR: Module load completed but symbols could not be loaded for WMP54Gv41x86.sys
Probably caused by : hardware ( WMP54Gv41x86+397b )

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

And the driver is very old.

Code:

94a2f000 94a90000   WMP54Gv41x86 T (no symbols)           
    Loaded symbol image file: WMP54Gv41x86.sys
    Image path: \SystemRoot\system32\DRIVERS\WMP54Gv41x86.sys
    Image name: WMP54Gv41x86.sys
    Timestamp:        Wed Apr 07 17:37:15 2010 (4BBC7573)
    CheckSum:         0005CC03
    ImageSize:        00061000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from WMP54G Support | Wireless-G PCI Adapter

Congrats on the new rig
If there is any issue (wish it is not) let us know.