Special_pool_detected_memory_corruption

  • Thread starter Thread starter Jacques
  • Start date Start date
J

Jacques

I have Windows Vista Home Premium. Since 2 weeks, I have blue screen that
appear once a day in average with SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.
I'm beginner in debugging blue screens.
I used windbg on the same PC and below is the result. I called Dell and they
advised me to reinstall all the operating system and Dell programs. I prefer
to come here and try to pinpoint the problem.
I had 2 sticks of 512 MB and 2 slots. I had the blue screen problem. I
bought 2 sticks of 2 GB each and installed them. I had the same blue screen.

I hope you can help me.

Here is the log:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Feb 26 13:40:45.916 2008 (GMT+1)
System Uptime: 0 days 2:40:49.015
Loading Kernel Symbols
............................................................................
............................................................................
....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
***************************************************************************
****
* *
* Bugcheck Analysis *
* *
***************************************************************************
****

Use !analyze -v to get detailed debugging information.

BugCheck C1, {b4134f68, 0, 98, 22}


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+69 )

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

0: 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: b4134f68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE: 22

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

IRP_ADDRESS: 00134f68

LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

STACK_TEXT:
c2e49ac4 81ce1ca5 000000c1 b4134f68 00000000 nt!KeBugCheckEx+0x1e
c2e49b3c 81ce7c54 b4134f68 c2e49bec 87a1f330 nt!MmFreeSpecialPool+0x69
c2e49ba4 81ed5995 b4134f68 00000000 c2e49bcc nt!ExFreePoolWithTag+0xeb
c2e49bb4 81ed5b9b b4134f68 b4134f68 8634f038 nt!VfIrpFree+0x15
c2e49bcc 81ece111 81cb1217 8634f09c b4134f68 nt!VerifierIoFreeIrp+0x11d
c2e49be4 81cb1217 b4134f68 c2e42774 002c49a8 nt!IovFreeIrpPrivate+0x4c
c2e49c34 81ccc1a7 00134fa8 c2e49c64 c2e49c60 nt!IopCompleteRequest+0x862
c2e49c80 81d8ba01 c2e49c9c c2e42784 00000001 nt!IopPostProcessIrp+0xdc
c2e49cc4 81d8b705 00000001 c2e49cfc c2e49d14 nt!IoRemoveIoCompletion+0xa2
c2e49d48 81c8caaa 000000b4 011bfb48 011bfb38 nt!NtRemoveIoCompletion+0x106
c2e49d48 776a0f34 000000b4 011bfb48 011bfb38 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
011bfb20 00000000 00000000 00000000 00000000 0x776a0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+69
81ce1ca5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmFreeSpecialPool+69

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

Followup: MachineOwner
 
Hi,

Have you run the memory diagnostic tool on this system yet?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jacques said:
I have Windows Vista Home Premium. Since 2 weeks, I have blue screen that
appear once a day in average with SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.
I'm beginner in debugging blue screens.
I used windbg on the same PC and below is the result. I called Dell and
they
advised me to reinstall all the operating system and Dell programs. I
prefer
to come here and try to pinpoint the problem.
I had 2 sticks of 512 MB and 2 slots. I had the blue screen problem. I
bought 2 sticks of 2 GB each and installed them. I had the same blue
screen.

I hope you can help me.

Here is the log:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Feb 26 13:40:45.916 2008 (GMT+1)
System Uptime: 0 days 2:40:49.015
Loading Kernel Symbols
...........................................................................
...........................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
....
***************************************************************************
****
* *
* Bugcheck Analysis *
* *
***************************************************************************
****

Use !analyze -v to get detailed debugging information.

BugCheck C1, {b4134f68, 0, 98, 22}


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+69 )

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

0: 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: b4134f68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE: 22

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

IRP_ADDRESS: 00134f68

LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

STACK_TEXT:
c2e49ac4 81ce1ca5 000000c1 b4134f68 00000000 nt!KeBugCheckEx+0x1e
c2e49b3c 81ce7c54 b4134f68 c2e49bec 87a1f330 nt!MmFreeSpecialPool+0x69
c2e49ba4 81ed5995 b4134f68 00000000 c2e49bcc nt!ExFreePoolWithTag+0xeb
c2e49bb4 81ed5b9b b4134f68 b4134f68 8634f038 nt!VfIrpFree+0x15
c2e49bcc 81ece111 81cb1217 8634f09c b4134f68 nt!VerifierIoFreeIrp+0x11d
c2e49be4 81cb1217 b4134f68 c2e42774 002c49a8 nt!IovFreeIrpPrivate+0x4c
c2e49c34 81ccc1a7 00134fa8 c2e49c64 c2e49c60 nt!IopCompleteRequest+0x862
c2e49c80 81d8ba01 c2e49c9c c2e42784 00000001 nt!IopPostProcessIrp+0xdc
c2e49cc4 81d8b705 00000001 c2e49cfc c2e49d14 nt!IoRemoveIoCompletion+0xa2
c2e49d48 81c8caaa 000000b4 011bfb48 011bfb38 nt!NtRemoveIoCompletion+0x106
c2e49d48 776a0f34 000000b4 011bfb48 011bfb38 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
011bfb20 00000000 00000000 00000000 00000000 0x776a0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+69
81ce1ca5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmFreeSpecialPool+69

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

Followup: MachineOwner
Click to expand...
 
I ran it when I had the 2 memory sticks of 512 MB and it passed successfully.

Rick Rogers said:
Hi,

Have you run the memory diagnostic tool on this system yet?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jacques said:
I have Windows Vista Home Premium. Since 2 weeks, I have blue screen that
appear once a day in average with SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.
I'm beginner in debugging blue screens.
I used windbg on the same PC and below is the result. I called Dell and
they
advised me to reinstall all the operating system and Dell programs. I
prefer
to come here and try to pinpoint the problem.
I had 2 sticks of 512 MB and 2 slots. I had the blue screen problem. I
bought 2 sticks of 2 GB each and installed them. I had the same blue
screen.

I hope you can help me.

Here is the log:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Feb 26 13:40:45.916 2008 (GMT+1)
System Uptime: 0 days 2:40:49.015
Loading Kernel Symbols
...........................................................................
...........................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
....
***************************************************************************
****
* *
* Bugcheck Analysis *
* *
***************************************************************************
****

Use !analyze -v to get detailed debugging information.

BugCheck C1, {b4134f68, 0, 98, 22}


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+69 )

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

0: 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: b4134f68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE: 22

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

IRP_ADDRESS: 00134f68

LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

STACK_TEXT:
c2e49ac4 81ce1ca5 000000c1 b4134f68 00000000 nt!KeBugCheckEx+0x1e
c2e49b3c 81ce7c54 b4134f68 c2e49bec 87a1f330 nt!MmFreeSpecialPool+0x69
c2e49ba4 81ed5995 b4134f68 00000000 c2e49bcc nt!ExFreePoolWithTag+0xeb
c2e49bb4 81ed5b9b b4134f68 b4134f68 8634f038 nt!VfIrpFree+0x15
c2e49bcc 81ece111 81cb1217 8634f09c b4134f68 nt!VerifierIoFreeIrp+0x11d
c2e49be4 81cb1217 b4134f68 c2e42774 002c49a8 nt!IovFreeIrpPrivate+0x4c
c2e49c34 81ccc1a7 00134fa8 c2e49c64 c2e49c60 nt!IopCompleteRequest+0x862
c2e49c80 81d8ba01 c2e49c9c c2e42784 00000001 nt!IopPostProcessIrp+0xdc
c2e49cc4 81d8b705 00000001 c2e49cfc c2e49d14 nt!IoRemoveIoCompletion+0xa2
c2e49d48 81c8caaa 000000b4 011bfb48 011bfb38 nt!NtRemoveIoCompletion+0x106
c2e49d48 776a0f34 000000b4 011bfb48 011bfb38 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
011bfb20 00000000 00000000 00000000 00000000 0x776a0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+69
81ce1ca5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmFreeSpecialPool+69

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

Followup: MachineOwner
Click to expand...
Click to expand...
 
Hi Jacques,

Well, the dump file isn't indicating a specific process other than the local
security authentication (lsass.exe), and that is rarely the actual problem.
Are all the dump files reading the same? Do they happen while running
specific software? How about in diagnostic mode, does it still dump then?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jacques said:
I ran it when I had the 2 memory sticks of 512 MB and it passed
successfully.

Rick Rogers said:
Hi,

Have you run the memory diagnostic tool on this system yet?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jacques said:
I have Windows Vista Home Premium. Since 2 weeks, I have blue screen
that
appear once a day in average with
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.
I'm beginner in debugging blue screens.
I used windbg on the same PC and below is the result. I called Dell and
they
advised me to reinstall all the operating system and Dell programs. I
prefer
to come here and try to pinpoint the problem.
I had 2 sticks of 512 MB and 2 slots. I had the blue screen problem. I
bought 2 sticks of 2 GB each and installed them. I had the same blue
screen.

I hope you can help me.

Here is the log:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Feb 26 13:40:45.916 2008 (GMT+1)
System Uptime: 0 days 2:40:49.015
Loading Kernel Symbols
...........................................................................
...........................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
....
***************************************************************************
****
* *
* Bugcheck Analysis *
* *
***************************************************************************
****

Use !analyze -v to get detailed debugging information.

BugCheck C1, {b4134f68, 0, 98, 22}


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+69 )

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

0: 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: b4134f68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE: 22

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

IRP_ADDRESS: 00134f68

LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

STACK_TEXT:
c2e49ac4 81ce1ca5 000000c1 b4134f68 00000000 nt!KeBugCheckEx+0x1e
c2e49b3c 81ce7c54 b4134f68 c2e49bec 87a1f330 nt!MmFreeSpecialPool+0x69
c2e49ba4 81ed5995 b4134f68 00000000 c2e49bcc nt!ExFreePoolWithTag+0xeb
c2e49bb4 81ed5b9b b4134f68 b4134f68 8634f038 nt!VfIrpFree+0x15
c2e49bcc 81ece111 81cb1217 8634f09c b4134f68 nt!VerifierIoFreeIrp+0x11d
c2e49be4 81cb1217 b4134f68 c2e42774 002c49a8 nt!IovFreeIrpPrivate+0x4c
c2e49c34 81ccc1a7 00134fa8 c2e49c64 c2e49c60
nt!IopCompleteRequest+0x862
c2e49c80 81d8ba01 c2e49c9c c2e42784 00000001 nt!IopPostProcessIrp+0xdc
c2e49cc4 81d8b705 00000001 c2e49cfc c2e49d14
nt!IoRemoveIoCompletion+0xa2
c2e49d48 81c8caaa 000000b4 011bfb48 011bfb38
nt!NtRemoveIoCompletion+0x106
c2e49d48 776a0f34 000000b4 011bfb48 011bfb38 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be
wrong.
011bfb20 00000000 00000000 00000000 00000000 0x776a0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+69
81ce1ca5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmFreeSpecialPool+69

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

Followup: MachineOwner
Click to expand...
Click to expand...
Click to expand...
 
All the dump files don't read the same.
They happen randomly.
When I ran the memory diagnostic tool, there was no dump happening.


Rick Rogers said:
Hi Jacques,

Well, the dump file isn't indicating a specific process other than the local
security authentication (lsass.exe), and that is rarely the actual problem.
Are all the dump files reading the same? Do they happen while running
specific software? How about in diagnostic mode, does it still dump then?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jacques said:
I ran it when I had the 2 memory sticks of 512 MB and it passed
successfully.

Rick Rogers said:
Hi,

Have you run the memory diagnostic tool on this system yet?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

I have Windows Vista Home Premium. Since 2 weeks, I have blue screen
that
appear once a day in average with
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.
I'm beginner in debugging blue screens.
I used windbg on the same PC and below is the result. I called Dell and
they
advised me to reinstall all the operating system and Dell programs. I
prefer
to come here and try to pinpoint the problem.
I had 2 sticks of 512 MB and 2 slots. I had the blue screen problem. I
bought 2 sticks of 2 GB each and installed them. I had the same blue
screen.

I hope you can help me.

Here is the log:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Feb 26 13:40:45.916 2008 (GMT+1)
System Uptime: 0 days 2:40:49.015
Loading Kernel Symbols
...........................................................................
...........................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
....
***************************************************************************
****
* *
* Bugcheck Analysis *
* *
***************************************************************************
****

Use !analyze -v to get detailed debugging information.

BugCheck C1, {b4134f68, 0, 98, 22}


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+69 )

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

0: 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: b4134f68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details

BUGCHECK_STR: 0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE: 22

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

IRP_ADDRESS: 00134f68

LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

STACK_TEXT:
c2e49ac4 81ce1ca5 000000c1 b4134f68 00000000 nt!KeBugCheckEx+0x1e
c2e49b3c 81ce7c54 b4134f68 c2e49bec 87a1f330 nt!MmFreeSpecialPool+0x69
c2e49ba4 81ed5995 b4134f68 00000000 c2e49bcc nt!ExFreePoolWithTag+0xeb
c2e49bb4 81ed5b9b b4134f68 b4134f68 8634f038 nt!VfIrpFree+0x15
c2e49bcc 81ece111 81cb1217 8634f09c b4134f68 nt!VerifierIoFreeIrp+0x11d
c2e49be4 81cb1217 b4134f68 c2e42774 002c49a8 nt!IovFreeIrpPrivate+0x4c
c2e49c34 81ccc1a7 00134fa8 c2e49c64 c2e49c60
nt!IopCompleteRequest+0x862
c2e49c80 81d8ba01 c2e49c9c c2e42784 00000001 nt!IopPostProcessIrp+0xdc
c2e49cc4 81d8b705 00000001 c2e49cfc c2e49d14
nt!IoRemoveIoCompletion+0xa2
c2e49d48 81c8caaa 000000b4 011bfb48 011bfb38
nt!NtRemoveIoCompletion+0x106
c2e49d48 776a0f34 000000b4 011bfb48 011bfb38 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be
wrong.
011bfb20 00000000 00000000 00000000 00000000 0x776a0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+69
81ce1ca5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmFreeSpecialPool+69

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

Followup: MachineOwner
Click to expand...
Click to expand...
Click to expand...
 
Hi Jacques,

Download the OCA memory tool and create a disk from the .iso file. Boot the
system with the disk and run the diagnostics:
http://oca.microsoft.com/en/windiag.asp

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jacques said:
All the dump files don't read the same.
They happen randomly.
When I ran the memory diagnostic tool, there was no dump happening.


Rick Rogers said:
Hi Jacques,

Well, the dump file isn't indicating a specific process other than the
local
security authentication (lsass.exe), and that is rarely the actual
problem.
Are all the dump files reading the same? Do they happen while running
specific software? How about in diagnostic mode, does it still dump then?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

Jacques said:
I ran it when I had the 2 memory sticks of 512 MB and it passed
successfully.

:

Hi,

Have you run the memory diagnostic tool on this system yet?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com

I have Windows Vista Home Premium. Since 2 weeks, I have blue screen
that
appear once a day in average with
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION.
I'm beginner in debugging blue screens.
I used windbg on the same PC and below is the result. I called Dell
and
they
advised me to reinstall all the operating system and Dell programs.
I
prefer
to come here and try to pinpoint the problem.
I had 2 sticks of 512 MB and 2 slots. I had the blue screen problem.
I
bought 2 sticks of 2 GB each and installed them. I had the same blue
screen.

I hope you can help me.

Here is the log:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is:
SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Feb 26 13:40:45.916 2008 (GMT+1)
System Uptime: 0 days 2:40:49.015
Loading Kernel Symbols
...........................................................................
...........................................................................
...................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details
Loading unloaded module list
....
***************************************************************************
****
* *
* Bugcheck Analysis *
* *
***************************************************************************
****

Use !analyze -v to get detailed debugging information.

BugCheck C1, {b4134f68, 0, 98, 22}


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details
Probably caused by : memory_corruption ( nt!MmFreeSpecialPool+69 )

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

0: 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: b4134f68, address trying to free
Arg2: 00000000, bytes requested
Arg3: 00000098, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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


PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details

PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for
details

BUGCHECK_STR: 0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE: 22

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: lsass.exe

CURRENT_IRQL: 0

IRP_ADDRESS: 00134f68

LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

STACK_TEXT:
c2e49ac4 81ce1ca5 000000c1 b4134f68 00000000 nt!KeBugCheckEx+0x1e
c2e49b3c 81ce7c54 b4134f68 c2e49bec 87a1f330
nt!MmFreeSpecialPool+0x69
c2e49ba4 81ed5995 b4134f68 00000000 c2e49bcc
nt!ExFreePoolWithTag+0xeb
c2e49bb4 81ed5b9b b4134f68 b4134f68 8634f038 nt!VfIrpFree+0x15
c2e49bcc 81ece111 81cb1217 8634f09c b4134f68
nt!VerifierIoFreeIrp+0x11d
c2e49be4 81cb1217 b4134f68 c2e42774 002c49a8
nt!IovFreeIrpPrivate+0x4c
c2e49c34 81ccc1a7 00134fa8 c2e49c64 c2e49c60
nt!IopCompleteRequest+0x862
c2e49c80 81d8ba01 c2e49c9c c2e42784 00000001
nt!IopPostProcessIrp+0xdc
c2e49cc4 81d8b705 00000001 c2e49cfc c2e49d14
nt!IoRemoveIoCompletion+0xa2
c2e49d48 81c8caaa 000000b4 011bfb48 011bfb38
nt!NtRemoveIoCompletion+0x106
c2e49d48 776a0f34 000000b4 011bfb48 011bfb38
nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be
wrong.
011bfb20 00000000 00000000 00000000 00000000 0x776a0f34


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MmFreeSpecialPool+69
81ce1ca5 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MmFreeSpecialPool+69

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

BUCKET_ID: 0xC1_22_VRF_nt!MmFreeSpecialPool+69

Followup: MachineOwner
Click to expand...
Click to expand...
Click to expand...
 
Finally, I ran the OCA memory tool and I saw an error. So I removed my 2
memory sticks of 2 GB each, and put back the 2 original Dell memory sticks of
512 MB each.
My laptop ran for a while and then I saw again a blue screen!
Can a blue screen come because I have only 1GB of RAM and sometimes memory
comes at 100% ?
Anyway, I did another windbg with this original memory sticks and below is
the log, can you tell me what you think?

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV**http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Wed Mar 5 22:19:49.534 2008 (GMT+1)
System Uptime: 0 days 9:39:19.661
Loading Kernel Symbols
...........................................................................................................................................................................
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck C1, {af5b6f48, 0, b8, 22}

*** ERROR: Module load completed but symbols could not be loaded for
iastor.sys




Probably caused by : CLASSPNP.SYS ( CLASSPNP!DestroyTransferPacket+53 )

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

0: 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: af5b6f48, address trying to free
Arg2: 00000000, bytes requested
Arg3: 000000b8, bytes calculated
Arg4: 00000022, caller is trying to free a bad address

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






BUGCHECK_STR: 0xC1_22

SPECIAL_POOL_CORRUPTION_TYPE: 22

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: Idle

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 81ce1ca5 to 81cd8681

STACK_TEXT:
81cf18e4 81ce1ca5 000000c1 af5b6f48 00000000 nt!KeBugCheckEx+0x1e
81cf195c 81ce7c54 af5b6f48 81cf1a08 8638fb60 nt!MmFreeSpecialPool+0x69
81cf19c0 81ed5995 af5b6f48 00000000 81cf19e8 nt!ExFreePoolWithTag+0xeb
81cf19d0 81ed5b9b af5b6f48 af5b6f48 864b98c0 nt!VfIrpFree+0x15
81cf19e8 81ece111 82a2df59 b70378b8 8b82e620 nt!VerifierIoFreeIrp+0x11d
81cf1a00 82a2df59 af5b6f48 864b97c8 864b986c nt!IovFreeIrpPrivate+0x4c
81cf1a18 82a2da04 8b82e620 00000001 b22d73b0
CLASSPNP!DestroyTransferPacket+0x53
81cf1a34 82a2d4a5 863b6768 022d73b0 b5dc6f48
CLASSPNP!EnqueueFreeTransferPacket+0x116
81cf1a5c 81ecec69 00000000 b5dc6f48 012d73b0
CLASSPNP!TransferPktComplete+0x3d7
81cf1a94 81cacb3b 00000000 b5dc6f48 81cf1b04
nt!IovpLocalCompletionRoutine+0xcc
81cf1acc 81eceb53 00000000 858f3000 b22d745c nt!IopfCompleteRequest+0x13d
81cf1b3c 80648856 00000000 858f5000 b22d745c nt!IovCompleteRequest+0x11c
WARNING: Stack unwind information not available. Following frames may be
wrong.
81cf1ba4 8067d970 858f3000 b22d745c 08000000 iastor+0x5856
81cf1c44 8067e4db 00000001 858f3730 81cf4820 iastor+0x3a970
81cf1cdc 806488a3 858f5000 00000000 81ca93ae iastor+0x3b4db
81cf1d50 81c913ee 00000000 0000000e 00000000 iastor+0x58a3
81cf1d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x46


STACK_COMMAND: kb

FOLLOWUP_IP:
CLASSPNP!DestroyTransferPacket+53
82a2df59 8b1dc891a382 mov ebx,dword ptr [CLASSPNP!_imp__ExFreePoolWithTag
(82a391c8)]

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: CLASSPNP!DestroyTransferPacket+53

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME: CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4549b196

FAILURE_BUCKET_ID: 0xC1_22_VRF_CLASSPNP!DestroyTransferPacket+53

BUCKET_ID: 0xC1_22_VRF_CLASSPNP!DestroyTransferPacket+53

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

0: kd> lmvm CLASSPNP
start end module name
82a28000 82a49000 CLASSPNP (pdb symbols) C:\Program Files\Debugging Tools
for Windows\sym\classpnp.pdb\7A81FB9837764DE48E40D71AD33DEDEE2\classpnp.pdb
Loaded symbol image file: CLASSPNP.SYS
Image path: \SystemRoot\system32\drivers\CLASSPNP.SYS
Image name: CLASSPNP.SYS
Timestamp: Thu Nov 02 09:51:34 2006 (4549B196)
CheckSum: 00028767
ImageSize: 00021000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
 
Back
Top