Two BSODs within an hour. page_fault_in_nonpaged_area

[Whats in a name]

Just started getting BSODs, first I thought it was a one off as I very rarely if ever receive them.
The second one within an hour spooked me.
I haven't done anything unusual, I was just browsing while listening to music. I had two external drives plugged into my front USB 3.0 ports (Fractal Design Define 4) for the first time in about a week, but I never had issues with this before.
Enclosed are the .dmp files

In Blue-screen-view the first dump has 2 lines in red referencing ntoskrnl.exe and usbehci.sys respectively.
The second dump also has 2 red lines referencing ntoskrnl.exe and aswHwid.sys respectively.

Thanks for reading!

 

[koolkat77]

Welcome.

Please remove Avast! for testing purpose.

[FONT="Lucida Console"]Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\Minidumps\012615-7191-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`02e5e000 PsLoadedModuleList = 0xfffff800`030a1890
Debug session time: Tue Jan 27 03:15:23.244 2015 (UTC + 6:00)
System Uptime: 0 days 0:52:25.430
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff30019b78670, 1, fffff80002ed7140, 7}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys

Could not read faulting driver name
Probably caused by : aswSnx.sys ( aswSnx+27f3d )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff30019b78670, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ed7140, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310b100
GetUlongFromAddress: unable to read from fffff8000310b1c0
 fffff30019b78670 Nonpaged pool

FAULTING_IP: 
nt!memset+b0
fffff800`02ed7140 480fc311        movnti  qword ptr [rcx],rdx

MM_INTERNAL_CODE:  7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

TRAP_FRAME:  fffff8800c518930 -- (.trap 0xfffff8800c518930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff30019b78670 rbx=0000000000000000 rcx=fffff30019b78670
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ed7140 rsp=fffff8800c518ac8 rbp=0000000000000001
 r8=0000000000000010  r9=00000015ffd29326 r10=0000000000000000
r11=0000000000000040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!memset+0xb0:
fffff800`02ed7140 480fc311        movnti  qword ptr [rcx],rdx ds:fffff300`19b78670=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002f5058b to fffff80002ed4e80

STACK_TEXT:  
fffff880`0c5187c8 fffff800`02f5058b : 00000000`00000050 fffff300`19b78670 00000000`00000001 fffff880`0c518930 : nt!KeBugCheckEx
fffff880`0c5187d0 fffff800`02ed2fae : 00000000`00000001 fffff300`19b78670 fffffa80`09587600 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`0c518930 fffff800`02ed7140 : fffff800`03196c03 fffffa80`00000000 fffffa80`0000e5c4 fffffa80`00000000 : nt!KiPageFault+0x16e
fffff880`0c518ac8 fffff800`03196c03 : fffffa80`00000000 fffffa80`0000e5c4 fffffa80`00000000 00000000`00010200 : nt!memset+0xb0
fffff880`0c518ad0 fffff800`031d2226 : fffffa80`0b0ec5c0 00000000`00000000 00000000`00000002 fffff880`0c518d90 : nt!MiCreateImageFileMap+0x847
fffff880`0c518d00 fffff800`031aee4e : fffff880`0c518f50 00000000`00000000 00000000`00000000 fffff880`0c518f48 : nt!MmCreateSection+0x836
fffff880`0c518f00 fffff880`0707df3d : 00000000`00000000 fffff880`0c519088 00000000`00000000 00000000`00000008 : nt!NtCreateSection+0x171
fffff880`0c518f80 00000000`00000000 : fffff880`0c519088 00000000`00000000 00000000`00000008 fffffa80`00000002 : aswSnx+0x27f3d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSnx+27f3d
fffff880`0707df3d ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  aswSnx+27f3d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSnx

IMAGE_NAME:  aswSnx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  546f1f38

FAILURE_BUCKET_ID:  X64_0x50_aswSnx+27f3d

BUCKET_ID:  X64_0x50_aswSnx+27f3d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_aswsnx+27f3d

FAILURE_ID_HASH:  {94ab50d4-4ec8-1418-7562-131bbbd51964}

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

0: kd> lmvm aswSnx
start             end                 module name
fffff880`07056000 fffff880`0715a000   aswSnx   T (no symbols)           
    Loaded symbol image file: aswSnx.sys
    Image path: aswSnx.sys
    Image name: aswSnx.sys
    Timestamp:        Fri Nov 21 17:17:12 2014 (546F1F38)
    CheckSum:         00102CB2
    ImageSize:        00104000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
[/FONT]

Revo Uninstaller:

Use Revo Uninstaller to uninstall stubborn software.

• Download and install the software
• Opt for Advance Mode while uninstalling which allows you to remove leftover registry.
• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

 

[Whats in a name]

thanks. I've followed the advice and will report back if I get any more BSODs