BleepingComputer.com: Windows Vista Backup

Hello everyone!
I was recently backing up the data on our new Windows Vista emachines W3611 computer with the Windows Backup Tool. When it required Disc 3 to be inserted, it simply locked up, displayed a blue screen of death for about 2 seconds, and rebooted by itself.
How do I solve this problem? Thanks.
-Glen

What message does the Blue Screen display? You may be able to locate it in the Event Viewer also.

I couldn't find the actual message in the Events Viewer, and it was too fast to see it when it actually happened. BUT I did use some problem log and extracted this information about the incident:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.768.2
Locale ID: 1033


Files that help describe the problem:
Mini040807-01.dmp
Sysdata.xml
version.txt


Extra Info:
BCCode e3
BCP1: 837BC594
BCP2: 827DED78
BCP3: 00000000
BCP4: 00000002
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

I haven't seen an e3 error before - but here's a link to it: http://aumha.org/a/stop.php#0xe3

Since it's a file system error, the first step would be to run chkdsk /f /r from the Run dialog - it'll ask you if it's OK to run it on the next boot, tell it yes.

Also, you may want to download a free diagnostic utility from the manufacturer of your hard drive to test your hard drive.

Once that's done, we can move on with further troubleshooting.

If you can find the Mini040807-01.dmp file on your hard drive (typically in C:\Windows\minidump), you can analyze it by following the directions at this link: http://forums.majorgeeks.com/showthread.php?t=35246 Then copy and paste the results here for us to have a look at (it may tell us more about what caused the error). Don't forget to use the !analyze -v command (in the empty space at the bottom of the debugger window) to get the verbose readout.

Sorry I haven't responded forever - I almost forgot about this post! My dad's computer wasn't hooked up to the Internet at the time, and so these instructions were pretty much impossible to follow. But we're on the 'net, now, so I did um. The results:


Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini040807-01.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 Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Sun Apr 8 12:07:31.927 2007 (GMT-6)
System Uptime: 0 days 1:51:00.677
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E3, {837bc594, 827ded78, 0, 2}

Probably caused by : udfs.sys ( udfs!UdfMarkVolumeClean+3eb )

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

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

RESOURCE_NOT_OWNED (e3)
A thread tried to release a resource it did not own.
Arguments:
Arg1: 837bc594, Address of resource
Arg2: 827ded78, Address of thread
Arg3: 00000000, Address of owner table if there is one
Arg4: 00000002

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_RC

BUGCHECK_STR: 0xE3

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 81877594 to 818d85c9

STACK_TEXT:
845e7c34 81877594 000000e3 837bc594 827ded78 nt!KeBugCheckEx+0x1e
845e7c64 81876daa 00000001 837bc0f0 a56379ad nt!ExpReleaseResourceForThreadLite+0xd8
845e7c70 a56379ad a5637961 84f9c793 818fde00 nt!ExReleaseResourceLite+0xf
845e7c74 a5637961 84f9c793 818fde00 837bc0f0 udfs!UdfMarkVolumeClean+0x3eb
845e7cb0 a563957a 845e7cd8 837bc0f0 00000000 udfs!UdfMarkVolumeClean+0x39f
845e7d44 81878e18 837bc0f0 00000000 827ded78 udfs!UdfCleanVolumeWorker+0x7c
845e7d7c 81a254a8 837bc0f0 845ec680 00000000 nt!ExpWorkerThread+0xfd
845e7dc0 8189145e 81878d1b 00000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
udfs!UdfMarkVolumeClean+3eb
a56379ad 8b4ddc mov ecx,dword ptr [ebp-24h]

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: udfs

IMAGE_NAME: udfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4549acc1

SYMBOL_NAME: udfs!UdfMarkVolumeClean+3eb

FAILURE_BUCKET_ID: 0xE3_udfs!UdfMarkVolumeClean+3eb

BUCKET_ID: 0xE3_udfs!UdfMarkVolumeClean+3eb

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

It's likely a bug with the file system used for CD/DVD's in Vista - here's a link to the KB article about it (with a link to the hotfix): http://support.microsoft.com/kb/930917

FYI-

Quote

If this doesn't fix the BSOD's, try some of the other tips in the article (different CD/DVD media, different speeds, etc). If that still doesn't fix it, then we'll work on other fixes for the OS.