[Rollin' Rog]

No, but try following the more rigorous test procedure -- if nothing turns up after a couple of boots, run verifier /reset to turn it off.

In reviewing the last BSOD you posted -- I checked the "trap frame" of the error -- and you appear to have a scanner attached -- I would remove that device physically and see if the error returns.

Also if it is common enough you should try "clean boot" troubleshooting.

[Zenoxio]

I unplugged the scanner. A bit later, I got a BSOD. I've now uninstalled the software too, see what happens.

How do I run more rigorous driver verifies?

[Rollin' Rog]

That is available under the "custom" settings properties -- check "rigorous" but possibly "spurious or excessive" tests.

Don't bother rebooting more than twice in this configuration -- the only time verifier runs is during the reboot process -- and if it doesn't catch anything, it's just going to be in the way. To disable verifier, run verifier /reset

Let me see the minidump created after physically removing the scanner. I don't know if the drivers would still be found in the trap frame after that.

[Zenoxio]

I've attached the dump. The most recent one was the one after removing the scanner, I believe.

[Rollin' Rog]

There are no more scanner drivers in the trap frame. My next suspect, other than hardware (possibly overheating or ram faults) -- would be Avast.

This is also my personal AV choice on XP and I have had no problems with it, but you might consider removing and reinstalling it -- or trying another.

[Zenoxio]

avast is installed, but hasn't been running for a while. Or at least it doesn't show up as running (taskbar etc). It expired and I haven't renewed the free license. Was it showing up in the trap frame?

[Rollin' Rog]

Here's your "trap frame" from the last; you can google the driver names to see what they belong to. The "asw*" ones are all Avast

kd> .trap (display trap frame)
*** WARNING: Unable to verify timestamp for OMCI.SYS
*** ERROR: Module load completed but symbols could not be loaded for OMCI.SYS
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*** WARNING: Unable to verify timestamp for ATMFD.DLL
*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
*** WARNING: Unable to verify timestamp for ppsio2.SYS
*** ERROR: Module load completed but symbols could not be loaded for ppsio2.SYS
*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*** WARNING: Unable to verify timestamp for e100b325.sys
*** ERROR: Module load completed but symbols could not be loaded for e100b325.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** WARNING: Unable to verify timestamp for Aavmker4.SYS
*** ERROR: Module load completed but symbols could not be loaded for Aavmker4.SYS
*** WARNING: Unable to verify timestamp for aswFsBlk.sys
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.sys
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for aeaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for aeaudio.sys
Couldn't resolve error at 'display trap frame)'

There is a "Free" version of Avast -- technically it expires -- but you need only follow the prompt when you get that message to to get the registration number for it.

I would just remove it and reinstall it from a fresh download.

[Zenoxio]

Okay, 2 crashes within the hour. After the first crash, I uninstalled Avast (but didn't restart). Another BSOD 30min later. I was doing a search on a network drive both times, hmm.

I've attached a dump from the latest crash, can you tell me if Avast is in there? I didn't restart after uninstalling, so I don't know if it was still in memory.

[Rollin' Rog]

Debug session time: Thu Oct 8 09:49:22.906 2009 (GMT-7)

BugCheck 10000050, {cb81acc6, 1, 8054bbb4, 0}



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
Probably caused by : aswSP.SYS ( aswSP+867a )

Nope -- it's still there, lol

And this time it's flagged specifically as the cause.

[Zenoxio]

Left the computer on overnight, came back to it and found it had crashed.

Attached the dump.

[Rollin' Rog]

This is about all I can get out of that one, not much in the backtrace -- but perhaps audio drivers. Can't get the "trap frame". Don't see Avast.

Loading Dump File [C:\Documents and Settings\Rollin' Rog\Desktop\Mini100809-03\Mini100809-03.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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Oct 8 15:49:53.312 2009 (GMT-7)
System Uptime: 0 days 6:00:14.920
Loading Kernel Symbols
...............................................................
...............................................
Loading User Symbols
Loading unloaded module list
...................
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck C1, {87704f68, 877047ba, bb0094, 23}

Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+29b )

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

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

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: 87704f68, address trying to free
Arg2: 877047ba, address where bits are corrupted
Arg3: 00bb0094, (reserved)
Arg4: 00000023, caller is freeing an address where nearby bytes within the same page have been corrupted

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


BUGCHECK_STR: 0xC1_23

SPECIAL_POOL_CORRUPTION_TYPE: 23

CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: lsass.exe

LAST_CONTROL_TRANSFER: from 806813ae to 80533806

STACK_TEXT:
f2badc10 806813ae 000000c1 87704f68 877047ba nt!KeBugCheckEx+0x1b
f2badc50 8054c32a 87704f68 f2badcd3 86958a20 nt!MmFreeSpecialPool+0x29b
f2badc90 80673269 87704f68 00000000 80673410 nt!ExFreePoolWithTag+0x4a
f2badc9c 80673410 ffff0000 87704f68 00000000 nt!VfIrpFree+0xc
f2badcb8 8066be08 000e6b10 00000000 f2badd48 nt!VerifierIoFreeIrp+0x129
f2badcc8 805670d3 87704f68 f2badd64 0096fec8 nt!IovFreeIrpPrivate+0x41
f2badd48 804de7ec 00000280 0096ff00 0096fef0 nt!NtRemoveIoCompletion+0x14a
f2badd48 7c90e514 00000280 0096ff00 0096fef0 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0096fed8 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+29b
806813ae 8b4108 mov eax,dword ptr [ecx+8]

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmFreeSpecialPool+29b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 498c1a18

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_23_nt!MmFreeSpecialPool+29b

BUCKET_ID: 0xC1_23_nt!MmFreeSpecialPool+29b

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

kd> kv (Display Stack Backtrace)
*** WARNING: Unable to verify timestamp for OMCI.SYS
*** ERROR: Module load completed but symbols could not be loaded for OMCI.SYS
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
*** WARNING: Unable to verify timestamp for ATMFD.DLL
*** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
*** WARNING: Unable to verify timestamp for smwdm.sys
*** ERROR: Module load completed but symbols could not be loaded for smwdm.sys
*** WARNING: Unable to verify timestamp for e100b325.sys
*** ERROR: Module load completed but symbols could not be loaded for e100b325.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for drmk.sys -
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for aeaudio.sys
*** ERROR: Module load completed but symbols could not be loaded for aeaudio.sys
Couldn't resolve error at 'Display Stack Backtrace) '
kd> .trap (display trap frame)
Couldn't resolve error at 'display trap frame)'

Also have you tried resetting the paging file? You should be able to follow these directions >>

http://support.microsoft.com/Default...810093&sd=RMVP

[Zenoxio]

Yeah, I reset the page file a while back after I first started noticing BSODs.

I just had the computer freeze on me for some reason, I restarted and found this:

---------------------------
svchost.exe - Application Error
---------------------------
The instruction at "0x6c417746" referenced memory at "0x6c417746". The memory could not be "read".


Click on OK to terminate the program
---------------------------
OK
---------------------------

[Zenoxio]

Another BSOD just now, hopefully this dump is more useful.

[Rollin' Rog]

Exactly the same as the last.

I don't see that we've done any testing for heat issues.

Has the case been cleaned out and the fan verified to be working?

Will Speedfan read and log temps for you on this motherboard >>

http://www.majorgeeks.com/download337.html

Dell's often do not support temperature logging.

[Zenoxio]

When I run that program, my second monitor goes berserk. Don't know why.

But I don't see any readings in the program, unless I'm not looking at the right place.