Anyone else seeing crashes with CDs and DVDs burned with UDF?

[All Things Mopar]

Today Gerry Cornell spoke these views with conviction for
everyone's edification:

Please disregard my earlier suggestion concerning using the
Driver Verification Tool. I tested it following the
instructions of Joshua Smith and it caused significant
problems.

Whew! I've heard of some XP utilities that actually wreck the
system even if you just cancel out. Which was why I wanted to
hear back from you.

If/when you get other ideas, I'm all ears. Thanks.

--
ATM, aka Jerry

"You’re gonna get your mind right"
"This the way he wants it, well, he gets it"
"What we got here is failure to communicate"

The Cap'n to Lucas "Luke" Jackson in "Cool Hand Luke"

 

[Kerry Brown]

Post copied from second thread, comments inline.

Today Kerry Brown spoke these views with conviction for
everyone's edification:


Gerry just advised me *not* to use the device verifier. Again,
though, Kerry, it is M$'s driver and is the only one they
have, so if it is kapupt, what can I do about it? And, I'd
believe one of my drives being defective but not both. They're
two different models for two different purposes, with two
different sets of firmware, manufactured to two different
release dates. My study of probability says it is very
unlikely that both are bad. And, please keep in mind that
Windows itself keeps insisting it is a driver that crashed.

Driver verifier will make your system unstable while it is running. Once it
is disabled your system will return to normal. You may have to use safe mode
to turn it off. Sometimes it is helpful troubleshooting driver problems.
Troubleshooting drivers can be very frustrating. They interact with one
another. It could be a seemingly unrelated driver that is causing your
problem.

Have you tried my suggestion of only hooking one drive up at a time? A bad
drive could affect both drives ability to work properly. My advice is to
disconnect all drives except your boot hard drive and one optical drive. Do
not have these two drives connected on the same cable. On the disconnected
drives make sure the power cables and the data cables are disconnected.
Check for the problem. Now disconnect the optical drive and connect the
other optical drive. Check for the problem. Let us know the results. If the
problem exists for both drives we can move onto something else.

Kerry

 

[All Things Mopar]

Today Kerry Brown spoke these views with conviction for
everyone's edification:

Post copied from second thread, comments inline.

Driver verifier will make your system unstable while it is
running. Once it is disabled your system will return to
normal. You may have to use safe mode to turn it off.
Sometimes it is helpful troubleshooting driver problems.
Troubleshooting drivers can be very frustrating. They
interact with one another. It could be a seemingly
unrelated driver that is causing your problem.

Understood. Thank you.

Have you tried my suggestion of only hooking one drive up
at a time?

Not yet. I am a software person, not a hardware person. So,
it'll be days or even weeks until my nephew has the time to
come over and swap things around, as I've described in
previous posts. Meanwhile, I'm not at all dead in the water.
I've got 3 work-arounds that'll last indefinitely. I posted
this thread initially to help my nephew and a friend of his
who is a certified MS XP engineer in several areas to know
enough about the problem and what others may or may not be
seeing to guide them in helping me.

A bad drive could affect both drives ability to
work properly. My advice is to disconnect all drives except
your boot hard drive and one optical drive. Do not have
these two drives connected on the same cable. On the
disconnected drives make sure the power cables and the data
cables are disconnected. Check for the problem. Now
disconnect the optical drive and connect the other optical
drive. Check for the problem. Let us know the results. If
the problem exists for both drives we can move onto
something else.

Understood again, Kerry. But, because I'm not totally down, I
don't want to muck around and ruin something until my nephew
can get over here and do it "by the numbers". So, it is likely
that not much is going to happen at my end until then, unless
I discover something new, which I will post to this thread,
and not to a new one. I apologize for annoying you by doing
that.

Again, my thanks for spending so much time walking me through
the mine field I find myself in. Thanks to you, I have
provided my nephew far more information than he'd have ever
found on his own, as he is a *builder* and not an XP "expert"
per se.

--
ATM, aka Jerry

"You’re gonna get your mind right"
"This the way he wants it, well, he gets it"
"What we got here is failure to communicate"

The Cap'n to Lucas "Luke" Jackson in "Cool Hand Luke"

 

[Kerry Brown]

Good luck. Let us know if you have any problems once your nephew gets there.
Don't worry about annoying me If it's more than a few days then you
would be better off starting a new thread but always give a quick synopsis
of the problem and what you've tried so far.

By a strange coincidence a customer's win98 computer started doing the same
thing today. It's a Lite-On CDRW drive. Loading InCD locks the computer up.
If InCD is uninstalled the drive and computer work fine. If the drive is
removed InCD doesn't lock up the computer when booting up. It worked fine
for over a year with InCD then suddenly quit. I replaced the drive and
everything worked again. UDF is very finicky.

Kerry

 

[Kerry Brown]

Today Kerry Brown spoke these views with conviction for
everyone's edification:


Kerry, I can't find memtest86+. Can you tell me the exact name?
Is it a Win XP utility or buried somewhere in one of the links
below? I'd like to try your memory tester to see if Hot CPU
Tester might have missed a bad byte somewhere in all of that 4
gig of RAM I have.

www.memtest.org

Download a floppy disk image, create the floppy, then boot from it. Let
memtest run for several hours at least. Overnight is best.

Kerry