DPM 2010 RC and Stop Code 0x50

Discussion:

(too old to reply)

MarkT

2010-04-13 13:03:03 UTC

We're using DPM 2010 RC to protect SQL workloads. Our DPM server is an HP
ProLiant BL460c G6 running Windows Server 2008 R2. It's twice bugchecked
with 0x50 (PAGE_FAULT_IN_NONPAGED_AREA). The stack trace from the memory
dump is below. Has anyone else seen this?

AGE_FAULT_IN_NONPAGED_AREA (50)
Arguments:
Arg1: fffffa8014cba000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800018c0113, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

WRITE_ADDRESS: fffffa8014cba000

FAULTING_IP:
nt!memset+93
fffff800`018c0113 488951e0 mov qword ptr [rcx-20h],rdx

STACK_TEXT:
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'+0x42907
nt!KiPageFault+0x16e
nt!memset+0x93
nt!RtlClearBits+0xaf
volsnap!VspQueryNtfsFreeSpaceBitmap+0x2a2
volsnap!VspMarkFreeSpaceInBitmap+0x178
volsnap!VspOptimizeDiffAreaFileLocation+0x2a0
volsnap!VspOpenDiffAreaFile+0x481
volsnap!VspCreateInitialDiffAreaFile+0x1ed
volsnap!VspTryPrepareForSnapshot+0x710
volsnap!VspPrepareForSnapshot+0x116
volsnap!VspPostWorker+0x2c
nt!IopProcessWorkItem+0x23
nt!ExpWorkerThread+0x111
nt!PspSystemThreadStartup+0x5a
nt!KxStartSystemThread+0x16

FOLLOWUP_IP:
volsnap!VspQueryNtfsFreeSpaceBitmap+2a2
fffff880`00c33fc2 eb68 jmp
volsnap!VspQueryNtfsFreeSpaceBitmap+0x30c (fffff880`00c3402c)

Thanks,
Mark

Seshagiri K V [MSFT]

2010-04-14 10:34:34 UTC

Permalink

This looks like http://support.microsoft.com/kb/977001 . Though the Stop
Code that is mentioned in the kb is different, the bugcheck that you see
might be a manifestation of that issue.

Thanks,
Seshagiri [MSFT].
This posting is provided "AS IS" with no warranties, and confers no rights.

Post by MarkT
We're using DPM 2010 RC to protect SQL workloads. Our DPM server is an HP
ProLiant BL460c G6 running Windows Server 2008 R2. It's twice bugchecked
with 0x50 (PAGE_FAULT_IN_NONPAGED_AREA). The stack trace from the memory
dump is below. Has anyone else seen this?
AGE_FAULT_IN_NONPAGED_AREA (50)
Arg1: fffffa8014cba000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800018c0113, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
------------------
WRITE_ADDRESS: fffffa8014cba000
nt!memset+93
fffff800`018c0113 488951e0 mov qword ptr [rcx-20h],rdx
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'+0x42907
nt!KiPageFault+0x16e
nt!memset+0x93
nt!RtlClearBits+0xaf
volsnap!VspQueryNtfsFreeSpaceBitmap+0x2a2
volsnap!VspMarkFreeSpaceInBitmap+0x178
volsnap!VspOptimizeDiffAreaFileLocation+0x2a0
volsnap!VspOpenDiffAreaFile+0x481
volsnap!VspCreateInitialDiffAreaFile+0x1ed
volsnap!VspTryPrepareForSnapshot+0x710
volsnap!VspPrepareForSnapshot+0x116
volsnap!VspPostWorker+0x2c
nt!IopProcessWorkItem+0x23
nt!ExpWorkerThread+0x111
nt!PspSystemThreadStartup+0x5a
nt!KxStartSystemThread+0x16
volsnap!VspQueryNtfsFreeSpaceBitmap+2a2
fffff880`00c33fc2 eb68 jmp
volsnap!VspQueryNtfsFreeSpaceBitmap+0x30c (fffff880`00c3402c)
Thanks,
Mark

MarkT

2010-04-14 12:16:01 UTC

Permalink

Thanks for the suggestion, Seshagiri, but I don't think KB977001 is
applicable in my case; I'm running Windows Server 2008 R2, and that hotfix
appears to apply only to Windows Server 2008. [And our storage pool is only
6TB -- nowhere close to 64TB.]

Thanks,
Mark

Post by Seshagiri K V [MSFT]
This looks like http://support.microsoft.com/kb/977001 . Though the Stop
Code that is mentioned in the kb is different, the bugcheck that you see
might be a manifestation of that issue.
Thanks,
Seshagiri [MSFT].
This posting is provided "AS IS" with no warranties, and confers no rights.

Praveen D [MSFT]

2010-04-20 10:19:03 UTC

Permalink

This looks like a volsnap bug in windows. Can you please mail me
praveend-at-microsoft-dot-com. we might need the full crash dump to file the
bug with Windows team.

Thanks,
Praveen D [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Michelvk

2010-12-07 08:07:13 UTC

Permalink

Hi Mark,

Since the last few week i am having the same issues as you mentioned. Server is crashing with 0x50 (PAGE_FAULT_IN_NONPAGED_AREA).

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: System
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: volsnap!VspQueryNtfsFreeSpaceBitmap+2a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: volsnap
IMAGE_NAME: volsnap.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc128

Were you able to find a solution for this?

Only thing what i can remember myself is that we increased the server from 12GB to 24GB of memory.

Michel

Post by MarkT
We're using DPM 2010 RC to protect SQL workloads. Our DPM server is an HP
ProLiant BL460c G6 running Windows Server 2008 R2. it is twice bugchecked
with 0x50 (PAGE_FAULT_IN_NONPAGED_AREA). The stack trace from the memory
dump is below. Has anyone else seen this?
AGE_FAULT_IN_NONPAGED_AREA (50)
Arg1: fffffa8014cba000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800018c0113, If non-zero, the instruction address which
referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
------------------
WRITE_ADDRESS: fffffa8014cba000
nt!memset+93
fffff800`018c0113 488951e0 mov qword ptr [rcx-20h],rdx
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'+0x42907
nt!KiPageFault+0x16e
nt!memset+0x93
nt!RtlClearBits+0xaf
volsnap!VspQueryNtfsFreeSpaceBitmap+0x2a2
volsnap!VspMarkFreeSpaceInBitmap+0x178
volsnap!VspOptimizeDiffAreaFileLocation+0x2a0
volsnap!VspOpenDiffAreaFile+0x481
volsnap!VspCreateInitialDiffAreaFile+0x1ed
volsnap!VspTryPrepareForSnapshot+0x710
volsnap!VspPrepareForSnapshot+0x116
volsnap!VspPostWorker+0x2c
nt!IopProcessWorkItem+0x23
nt!ExpWorkerThread+0x111
nt!PspSystemThreadStartup+0x5a
nt!KxStartSystemThread+0x16
volsnap!VspQueryNtfsFreeSpaceBitmap+2a2
fffff880`00c33fc2 eb68 jmp
volsnap!VspQueryNtfsFreeSpaceBitmap+0x30c (fffff880`00c3402c)
Thanks,
Mark

Thanks for the suggestion, Seshagiri, but I do not think KB977001 is
applicable in my case; I am running Windows Server 2008 R2, and that hotfix
appears to apply only to Windows Server 2008. [And our storage pool is only
6TB -- nowhere close to 64TB.]
Thanks,
Mark

Post by Praveen D [MSFT]
This looks like a volsnap bug in windows. Can you please mail me
praveend-at-microsoft-dot-com. we might need the full crash dump to file the
bug with Windows team.
Thanks,
Praveen D [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Submitted via EggHeadCafe
Microsoft LINQ Query Samples For Beginners
http://www.eggheadcafe.com/training-topic-area/LINQ-Standard-Query-Operators/33/LINQ-Standard-Query-Operators.aspx