getting errors in Premiere "Delayed Write Failure" please help
 

I started getting this error yesterday. I restart my computer, open Premiere again, and resume doing my video captures, and after about the 4th or 5th capture I will get it again - There are 5 different ones, but they keep popping up, i have to restart every time

this is it:

Windows - Delayed Write Failure
Windows was unable to save all the data for the file \Device\HarddiskVolume2\THIS PART VARIES*. The data has been lost. This error may be caused by a failure of your computer hardware or network connections. Please try to save this file elsewhere.

THIS PART VARIES*
I will have either:
$Mft
$Bitmap
PREM60.PRF
Recycler\NPROTECT
Premiere 6.0
Premiere 6.0\Plug-ins\plugcach.fon


I click ok, and 2 seconds later the next one will pop up. I have to restart whenever I get this error, because it won't go away. It looks like it varies in that one line between all of the errors



this is getting vary frustrating

any ideas?

Bret,

Open Event Viewer (you can open Run and type eventvwr and click OK). In System, are there a bunch of Red stops with the word Disk next to them?

there are many many yellow warnings with "!" and they do say disk out to the side

Read those. That will be the hint on what is going on. It could be a couple of things, but the fact that they are there is not the best news. Post the info. You can also go the Microsoft and search the knowledge base with the message

http://support.microsoft.com/

You can fill the search string in the left and possible get an answer.

everyone looks like this or having a 1 instead of a 0

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 3/27/2004
Time: 5:11:45 PM
User: N/A
Computer: 4²°
Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.
Data:
0000: 04 01 22 00 01 00 72 00 .."...r.
0008: 00 00 00 00 33 00 04 80 ....3..€
0010: 2d 01 00 00 00 00 00 00 -.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 6e aa a9 17 00 00 00 .nª©....
0028: 00 00 00 00 01 00 00 00 ........
0030: 00 00 00 00 2a 00 00 00 ....*...
0038: 02 82 00 00 00 00 0b 00 .‚......
0040: 2a 00 0b d4 d5 37 00 00 *..ÔÕ7..
0048: 08 00 ..

Try this first, Open a Command Prompt (Start, All Programs, Accessories, Command Prompt). Because it says Disk1, it sounds like a D: or E: drive (the other HD). Type, where d: is the drive's actual letter:

CHKDSK d: /R

It will probably say it is locked, do you want to run chkdsk on the next restart? Answer Y. Shutdown and restart. This may take awhile, so don't plan on watching it.

You can check the event viewer after the system comes back up to see what the results are. I forget what the event will be called.

The issue appears to be a failing drive. It may just have some issues and a chkdsk will correct them. Cross your fingers or do some other lucky charm ;)

YOUR HARDDISK IS PROBABLY **DYING**!!!

This has nothing to do with Premiere. It is a Windows error
stating (as you've read) that it cannot write data to your harddisk.

If the part beings with $ you really need to be careful. $MFT is
your master file table which holds all pointers to your files (yes,
there is a backup of that). You don't want anything bad to happen
to that (NTFS can rebuild it partially). $Bitmap holds the freespace
blocks on your harddisk.

As soon as possible copy this data to another harddisk. It doesn't
have to be that your harddisk is dying, it could just be too much
heat inside your case for example (which isn't good for your
harddisk either).

Usually it is the harddisk itself though.

1) backup the data on that harddisk as fast as you can if you don't want to loose it

2) run scandisk and have it check for bad sectors

3) can you monitor your motherboard temperature?

I thought that might be the case, so last night I copied everything onto my 250gig hdd in my xbox (good for storage).

I have a cpu and motherboard monitor program, temp is fine. My motherboard has never reached 90 and my cpu has never reached 95.

I'm going to call maxtor today to see if I can get it replaced.

thanks for all the help

I think Maxtor, Seagate, and Western Digital will cross ship. So, they may be able to get a replacement in the mail today.

In XP, chkdsk replaces scandisk. If you ran it, you can just run chkdsk d: and it will have a current report of what it marked as bad. If chkdsk finds more bad files each time you do it, that is a positive sign that failure is imminent.

To the best of my knowledge chkdsk does not do a full harddisk
scan. Only the structures.

90 what? F or C? If it is C then 90 is way too much. My CPU is
60 (and that's a bit too hot for my taste already) and my mother-
board is 35 C.

Also, a lot of people in the business claim you should use extra
cooling for 7200 RPM drives and up. I never have, but perhaps
that shortens there lifecycle dramatically as well.

Hi Rob,

In both XP and Windows 2000, CHKDSK /R does a full scan, hence why I suggested that something else be found to do. It will mark sectors bad if it finds them.

CHKDSK /F does a structure fix and will repair broken tables, security allocators, etc.

CHKDSK does just a basic test and does not fix anything that is broken. It also gives a quick report of free, used, and sectors that have been marked bad.

Scandisk does not exist in XP.

I forgot about /R indeed. My bad. Thank you for explaining!

"Scandisk" (or error checking with a Windows GUI <g>) can be
found if you right-click on a drive and then go to properties ->
tools -> Check now. It also has a full sector scan option. Under-
water it is probably still running chkdsk, but you don't have to
go through the DOS hassles. I personally prefer chkdsk (as well),
but not everyone feels good doing such "low-level" work is my
experience.

That clears it up Rob. In Win9x, there was a function called scandisk.exe which ran in DOS. It looked a bit like Norton's Speed Disk (from DOS 5/Win3.x days) in that it would give you a progress by sector and show what was free and bad.

BTW, I do not trust the Scan for Bad Sectors... in the Check Now dialog of the drive properties through Explorer. I always use /R when I have my doubts :)