| Author |
Message |
Andrew
Guest
|
 Posted:
Thu Jul 28, 2005 7:49 am Post subject:
Bluescreen with XP SP2 and VSS when creating shadow copy |
|
|
I have just started working with the VSS SDK for Writers-Requestors v7.1.
Every time I attempt to create a shadow copy, the system bluescreens with
0x1000008e (0xc0000005, 0x80588954, 0xb74ab4d0, 0x00000000).
After some experimentation, I decided to try Backup using a shadow copy on
the same volume and it also bluescreens in the same way.
Does anyone know what is happening and any solutions? |
|
| Back to top |
|
 |
Pat [MSFT]
Guest
|
| Posted:
Thu Jul 28, 2005 4:17 pm Post subject:
Re: Bluescreen with XP SP2 and VSS when creating shadow copy |
|
|
If you open the MEMORY.DMP file in WinDBG (part of the ddk debugging kit)
and type:
1) .symfix <enter>
2) .reload <enter>
3) !analyze -v <enter>
Then post the output we can see what caused the failure.
Pat
"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:D7A5DDDE-56DA-495F-BBBB-9F823D54A570@microsoft.com...
| Quote: | I have just started working with the VSS SDK for Writers-Requestors v7.1.
Every time I attempt to create a shadow copy, the system bluescreens with
0x1000008e (0xc0000005, 0x80588954, 0xb74ab4d0, 0x00000000).
After some experimentation, I decided to try Backup using a shadow copy on
the same volume and it also bluescreens in the same way.
Does anyone know what is happening and any solutions? |
|
|
| Back to top |
|
|
Andrew
Guest
|
| Posted:
Fri Jul 29, 2005 12:17 am Post subject:
Re: Bluescreen with XP SP2 and VSS when creating shadow copy |
|
|
Thanks for the reply - I tried emailing the dump and the WinDBG output to you
directly but the email bounced so here is the WinDBG output.
As you can see, SYMEVENT.SYS is calling ObQueryNameString which is writing
(I think) memory where it can't. I've tried disabling SYMEVENT but the
problem still happens and SYMEVENT is still in the stack trace when I analyze
the memory dump. Looks like I will have to uninstall Norton Anti Virus to
workaround in the meantime.
The NAV details are:
V 10.0.1.13, Part number is 10098807 (from 'About Norton AntiVirus' dialog).
Dump analysis follows:
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini072805-07.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*
e:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Jul 28 16:49:54.578 2005 (GMT+12)
System Uptime: 0 days 0:49:42.288
Loading Kernel Symbols
..........................................................................................................................................
Loading unloaded module list
...................
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 80588954, b762c4d0, 0}
Unable to load image \??\C:\Program Files\Symantec\SYMEVENT.SYS, Win32 error 2
*** WARNING: Unable to verify timestamp for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for
SYMEVENT.SYS
Probably caused by : SYMEVENT.SYS ( SYMEVENT+5e06 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80588954, The address that the exception occurred at
Arg3: b762c4d0, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!ObQueryNameString+9b
80588954 8b88a4000000 mov ecx,[eax+0xa4]
TRAP_FRAME: b762c4d0 -- (.trap ffffffffb762c4d0)
Unable to read trap frame at b762c4d0
CUSTOMER_CRASH_COUNT: 7
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
BUGCHECK_STR: 0x8E
LAST_CONTROL_TRANSFER: from bae9be06 to 80588954
STACK_TEXT:
b762c5f8 bae9be06 82f33b19 b762c624 00000008 nt!ObQueryNameString+0x9b
WARNING: Stack unwind information not available. Following frames may be
wrong.
b762c6e4 804e13d9 82b60be0 82264318 82264318 SYMEVENT+0x5e06
b762c6f4 805db84b 00000000 82f33b18 806ffa4c nt!IopfCallDriver+0x31
b762c744 8050bbf0 c000014f 82b02d01 00000000 nt!IopMountVolume+0x1b9
b762c774 8057c9ca 82b02da0 82f33b18 b762c8a8 nt!IopCheckVpbMounted+0x5e
b762c864 8056c063 82f33b18 00000000 82f2eea8 nt!IopParseDevice+0x3c6
b762c8dc 8056f2a8 00000000 b762c91c 00000040 nt!ObpLookupObjectName+0x53c
b762c930 8057d2d3 00000000 00000000 00000000 nt!ObOpenObjectByName+0xea
b762c9ac 8057d3a2 b762cb84 00120089 b762cb34 nt!IopCreateFile+0x407
b762ca08 8057d550 b762cb84 00120089 b762cb34 nt!IoCreateFile+0x8e
b762ca48 804dd99f b762cb84 00120089 b762cb34 nt!NtOpenFile+0x27
b762ca48 804e3ba3 b762cb84 00120089 b762cb34 nt!KiFastCallEntry+0xfc
b762cad8 f8718d91 b762cb84 00120089 b762cb34 nt!ZwOpenFile+0x11
b762cc60 f8719099 82f33bd0 00000000 00000000
VolSnap!VspMarkFreeSpaceInBitmap+0x1a7
b762cd78 f871e0e4 82f33bd0 82f8a364 82f1d46c
VolSnap!VspSetIgnorableBlocksInBitmap+0x23
b762cd90 f871a180 82f8a360 00000000 82cacda8
VolSnap!VspSetIgnorableBlocksInBitmapWorker+0x14
b762cdac 80574128 82f1d4c0 00000000 00000000 VolSnap!VspWorkerThread+0x76
b762cddc 804efc81 f871a10a 82b2dc08 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
FOLLOWUP_IP:
SYMEVENT+5e06
bae9be06 ?? ???
SYMBOL_STACK_INDEX: 1
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: SYMEVENT+5e06
MODULE_NAME: SYMEVENT
IMAGE_NAME: SYMEVENT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4272844c
STACK_COMMAND: .trap ffffffffb762c4d0 ; kb
FAILURE_BUCKET_ID: 0x8E_SYMEVENT+5e06
BUCKET_ID: 0x8E_SYMEVENT+5e06
Followup: MachineOwner
---------
"Pat [MSFT]" wrote:
| Quote: | If you open the MEMORY.DMP file in WinDBG (part of the ddk debugging kit)
and type:
1) .symfix <enter
2) .reload <enter
3) !analyze -v <enter
Then post the output we can see what caused the failure.
Pat
"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:D7A5DDDE-56DA-495F-BBBB-9F823D54A570@microsoft.com...
I have just started working with the VSS SDK for Writers-Requestors v7.1.
Every time I attempt to create a shadow copy, the system bluescreens with
0x1000008e (0xc0000005, 0x80588954, 0xb74ab4d0, 0x00000000).
After some experimentation, I decided to try Backup using a shadow copy on
the same volume and it also bluescreens in the same way.
Does anyone know what is happening and any solutions?
|
|
|
| Back to top |
|
|
Andrew
Guest
|
| Posted:
Mon Aug 01, 2005 12:16 am Post subject:
Re: Bluescreen with XP SP2 and VSS when creating shadow copy |
|
|
Pat - I have achieved a resolution on this issue by getting a fix from
Symantec.
regards
-Andrew
"Pat [MSFT]" wrote:
| Quote: | If you open the MEMORY.DMP file in WinDBG (part of the ddk debugging kit)
and type:
1) .symfix <enter
2) .reload <enter
3) !analyze -v <enter
Then post the output we can see what caused the failure.
Pat
"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:D7A5DDDE-56DA-495F-BBBB-9F823D54A570@microsoft.com...
I have just started working with the VSS SDK for Writers-Requestors v7.1.
Every time I attempt to create a shadow copy, the system bluescreens with
0x1000008e (0xc0000005, 0x80588954, 0xb74ab4d0, 0x00000000).
After some experimentation, I decided to try Backup using a shadow copy on
the same volume and it also bluescreens in the same way.
Does anyone know what is happening and any solutions?
|
|
|
| Back to top |
|
|
Pat [MSFT]
Guest
|
| Posted:
Mon Aug 01, 2005 10:10 pm Post subject:
Re: Bluescreen with XP SP2 and VSS when creating shadow copy |
|
|
Excellent.
Pat
"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:05402936-2057-4C9A-B363-791605C20901@microsoft.com...
| Quote: | Pat - I have achieved a resolution on this issue by getting a fix from
Symantec.
regards
-Andrew
"Pat [MSFT]" wrote:
If you open the MEMORY.DMP file in WinDBG (part of the ddk debugging kit)
and type:
1) .symfix <enter
2) .reload <enter
3) !analyze -v <enter
Then post the output we can see what caused the failure.
Pat
"Andrew" <Andrew@discussions.microsoft.com> wrote in message
news:D7A5DDDE-56DA-495F-BBBB-9F823D54A570@microsoft.com...
I have just started working with the VSS SDK for Writers-Requestors
v7.1.
Every time I attempt to create a shadow copy, the system bluescreens
with
0x1000008e (0xc0000005, 0x80588954, 0xb74ab4d0, 0x00000000).
After some experimentation, I decided to try Backup using a shadow copy
on
the same volume and it also bluescreens in the same way.
Does anyone know what is happening and any solutions?
|
|
|
| Back to top |
|
|
Guest
|
| Posted:
Sat Aug 06, 2005 11:57 pm Post subject:
Re: Bluescreen with XP SP2 and VSS when creating shadow copy |
|
|
I saw the same blue screen in the morning after the computer was doing
backup after 4:00am. I have norton av ce 10.0.1.1000 installed in the
computer. Could you tell me how or where to get the fix from Symantec?
Thanks a lot.
eric |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in