Pining Kerry Brown: new info on my UDF CD-R Win XP Pro SP2 crashes

[All Things Mopar]

Hi, Kerry.

I just burned a brand new CD-R using Roxio's Easy Media Creator
8 on my new SP2 box. The CD-R was burned with UDF 102 with a
Joliet bridge (whatever that is!).

I gave the CD the volume name of "UDF CD-R Test Burn 2005-11-
09". It showed up for a brief minute in my burner showing a
truncated volume name of "UDF CD-R Test B", which is the same 15
characters a HD or Joliet volume can be named, but UDF allows up
to 32.

I tested this CD on my old SP1 box. It correctly showed the
entire volume name, and correctly showed the 2,673 total JPEG
files in 7 folders. A text file was placed in each folder to ID
the number of files in that folder for easy verification.

This time, when I attempted to read the just-burned CD in my
reader, I got the following, from the Blue Screen of Death as
well as Event Viewer:

BAD_POOL_HEADER <--- this is the 2nd of two errors I see, the
other being PAGE_FAULT et al

STOP: 0x00000010 (0x00000020,0xE5076810,0xE5076838,0x0C50203)

Event Viewer log:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 11/9/2005
Time: 11:25:06 AM
User: N/A
Computer: EVERYWHERE
Description:
Error code 00000019, parameter1 00000020, parameter2 e5076810,
parameter3

e5076838, parameter4 0c050203.

For more information, see Help and Support

Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 65 35 30 37 36 38 31 30 e5076810
0040: 2c 20 65 35 30 37 36 38 , e50768
0048: 33 38 2c 20 30 63 30 35 38, 0c05
0050: 30 32 30 33 0203

If this helps you to help me, great. If not, please advise what
else you want to know.

--
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]

You need to follow the advice in the other thread you started about turning
on the driver verifier. The errors you are experiencing point to a bad
driver and/or bad hardware. I am still betting that one of the optical
drives is defective.

It would be best to keep the topic in one thread. I put any more comments in
that thread. I have a very busy day ahead so I won't get a chance to get
back to you until later today.

Kerry

 

[All Things Mopar]

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

You need to follow the advice in the other thread you
started about turning on the driver verifier. The errors
you are experiencing point to a bad driver and/or bad
hardware. I am still betting that one of the optical drives
is defective.

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.

Now, if I could only get Bill the Gates to admit he *may* have
a problem...

It would be best to keep the topic in one thread. I put any
more comments in that thread. I have a very busy day ahead
so I won't get a chance to get back to you until later
today.

I started this new thread because the other was was getting
clogged by old, obsolete info and I wanted you specifically to
see this message.

If/when you have any other ideas, please post them to either
thread. I'm still like a fish out of water, just flopping on
the dock gasping for air.

--
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]

Answered in the first thread.

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.

Now, if I could only get Bill the Gates to admit he *may* have
a problem...


I started this new thread because the other was was getting
clogged by old, obsolete info and I wanted you specifically to
see this message.

If/when you have any other ideas, please post them to either
thread. I'm still like a fish out of water, just flopping on
the dock gasping for air.

--
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"