#414 BSOD with v0.6.5-v0.6.6

[lwc]

For months these boots are ruining my life! Only now I finally thought maybe it was Winpooch all along (ever since v0.6.0, I guess).

Please please please fix it.

Here is everything you need to figure this out:

1)
STOP: 0x0000008e (0x80000003, 0x80507f56, 0xb86667f4, 0x00000000)

2)
Source: System Error
Event ID: 1003

Error code 1000008e, parameter1 80000003, parameter2 80507f56, parameter3 aca777f4, parameter4 00000000.

3)
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.

BugCheck 1000008E, {80000003, 80507f56, a18437f4, 0}

Unable to load image Winpooch.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for Winpooch.sys
*** ERROR: Module load completed but symbols could not be loaded for Winpooch.sys
Probably caused by : Winpooch.sys ( Winpooch+ff10 )

4)
Debugging Details:

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 80507f56, The address that the exception occurred at
Arg3: a18437f4, Trap Frame
Arg4: 00000000

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
nt!MiRemoveWorkingSetPages+39
80507f56 cc int 3

TRAP_FRAME: a18437f4 -- (.trap ffffffffa18437f4)
ErrCode = 00000000
eax=00000002 ebx=a18438e4 ecx=80542cbe edx=00000056 esi=80542cbf edi=00000002
eip=80507f57 esp=a1843868 ebp=a184387c iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000216
nt!MiRemoveWorkingSetPages+0x3a:
80507f57 5b pop ebx
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: IEXPLORE.EXE

LAST_CONTROL_TRANSFER: from 80546184 to 80507f57

STACK_TEXT:
a184387c 80546184 00000002 80542cbe 00000056 nt!MiRemoveWorkingSetPages+0x3a
a1843898 8054254f a18438ac a18438b4 80542c61 nt!ExpAddTagForBigPages+0xae
a18438bc 80542bcc 80542cbe a18438e4 00000002 nt!VdmCheckPMCliTimeStamp+0x34
a1843bb8 80542d60 f58f5202 f58f50e1 00000129 nt!VdmpDelayInterrupt+0x16
a1843bd4 f58e5f10 f58f5202 f58f50e1 00000129 nt!VdmpDelayInterrupt+0x1aa
WARNING: Stack unwind information not available. Following frames may be wrong.
a1843c04 f58e20f6 82282a58 00000001 a1843c14 Winpooch+0xff10
a1843c34 8056e797 00000000 82282a40 82282a58 Winpooch+0xc0f6
a1843c4c 804e1f77 82282a58 00000000 a1843d64 nt!NtQueryInformationProcess+0xa01
a1843c4c ffffffff 82282a58 00000000 a1843d64 nt!KiTrap0E+0x52
a1843d04 00000000 00000a20 00000000 00000000 0xffffffff

STACK_COMMAND: kb

FOLLOWUP_IP:
Winpooch+ff10
f58e5f10 ?? ???

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: Winpooch+ff10

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Winpooch

IMAGE_NAME: Winpooch.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45fedccd

FAILURE_BUCKET_ID: 0x8E_Winpooch+ff10

BUCKET_ID: 0x8E_Winpooch+ff10

[lwc]

A mini dump

[lwc]

Logged In: YES
user_id=1520489
Originator: YES

I also have Winpooch in another computer and it was ok there...until I've tried the attached SYS file (2007-04-15 00:42) from bug #1700552. Now the OTHER computer (XP SP2 - no other updates) experiences the aforementioned BSOD bug too (same error)! I've had to re-download the old SYS file.

[Benoît Blanchon]

Logged In: YES
user_id=947438
Originator: NO

Did you tryed with Winpooch 0.6.6 RC1 ?
http://www.winpooch.com/candidate/

[lwc]

Logged In: YES
user_id=1520489
Originator: YES

I've tried the official v0.6.6 and the other computer stopped crashing.

However, the original computer (the one that v0.6.5 ruined) got ruined again so I had to uninstall Winpooch from it.

BUT when it got crash in v0.6.6, it's so sudden that XP SP2 doesn't even log the error! Ihe system just gets stuck and ignores what happened when I boot!

You can now combine this bug with #1706218...