BSOD 4.8.1335 Home Ed WinXpPro SP3 (PAGE_FAULT_IN_NONPAGED_AREA)

[jeffthewop]

I experienced a BSOD (Blue Screen of Death) today. down from the Blue screen "PAGE_FAULT_IN_NONPAGED_AREA" Probably caused by aswsp.sys.

The minidump refers to asesp.sys as the possible cause as well. I am running Avast 4.8.1335 Home Ed on WinXpPro SP3. I lost the stuff I was working on!

Is there a fix for this?

I love Avast and do pay license fee for a few other business workstations, this is my home machine. I don't want this to happen again and am very concerned that it may without a patch.

Below is the minidump:

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


Loading Dump File [c:\windows\minidump\Mini072609-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: c:\i386
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Sun Jul 26 12:10:14.187 2009 (GMT-6)
System Uptime: 0 days 0:08:29.981
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
........................
Unable to load image 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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {ba4d0044, 0, b66ac4df, 0}


Could not read faulting driver name
Probably caused by : aswSP.SYS ( aswSP+44df )

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

[polonus]

Hi jeffthewop,

A proposed solution:
STEP 1
->Start->Settings->Control Panel->System->Advanced->Performance->Settings->Advanced->Change
Then check "No paging file" and click "Set" for each HD you got.

REBOOT

STEP 2
Then use Pagefileconfig.vbs delete command.
pagefileconfig.vbs /delete [/s Computer [/u Domain\User [/p Password]]] /vo {VolumeLetter | *} [/vo {VolumeLetter2 | *} [...]]

Parameters
/s Computer
Specifies the name or IP address of a remote computer (do not use backslashes). The default is the local computer.
/u Domain\User
Runs the script with the account permissions of the user specified by User or Domain\User. The default is the permissions of the current logged on user on the computer issuing the command.
/p Password
Specifies the password of the user account that is specified in the /u parameter.
/vo {VolumeLetter | *}
Specifies the volume or volumes of the paging file settings to be deleted. The volume is specified by a letter followed by a colon (for example, "C:").
/?
Displays help at the command prompt.
Examples
The following examples show how you can use the pagefileconfig /delete command:

pagefileconfig.vbs /delete /vo d:
pagefileconfig.vbs /delete /s srvmain /u maindom\hiropln /vo d:
pagefileconfig.vbs /delete /s srvmain /u maindom\hiropln /p p@ssW23 /vo d: /vo e: /vo f:

REBOOT

STEP 3

Either you use again Pagefileconfig.vbs create command.

pagefileconfig.vbs /create [/s Computer [/u Domain\User [/p Password]]] /i InitialPageFileSize /m MaximumPageFileSize /vo {VolumeLetter | *} [/vo {VolumeLetter2 | *} [...]]

Parameters
/s Computer
Specifies the name or IP address of a remote computer (do not use backslashes). The default is the local computer.
/u Domain\User
Runs the script with the account permissions of the user specified by User or Domain\User. The default is the permissions of the current logged on user on the computer issuing the command.
/p Password
Specifies the password of the user account that is specified in the /u parameter.
/i InitialPageFileSize
Specifies the new initial size (in MB) to use for the paging file specified.
/m MaximumPageFileSize
Specifies the new maximum size (in MB) to use for the paging file specified.
/vo {VolumeLetter | *}
Specifies the volume or volumes of the paging file settings to be created. The volume is specified by a letter followed by a colon (for example, "C:").
/?
Displays help at the command prompt.
Examples
The following examples show how you can use the pagefileconfig /create command:

pagefileconfig.vbs /create /i 140 /m 300 /vo d:
pagefileconfig.vbs /create /s srvmain /u maindom\hiropln /i 150 /m 300 /vo d:
pagefileconfig.vbs /create /s srvmain /u maindom\hiropln /i 50 /m 200 /vo *
pagefileconfig.vbs /create /s srvmain /u maindom\hiropln /p p@ssW23 /i 100 /m 600 /vo d: /vo e: /vo f:

OR

->Start->Settings->Control Panel->System->Advanced->Performance->Settings->Advanced->Change
Then check "Custom File" and set up the size of the paging file w

PS1: Please refer to MS Site for more information for each paging file command

It could also be an issue caused by your firewall. What firewall are you running, not Outpost by the way, it has been known for these issues?

polonus