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

[All Things Mopar]

New PC, Win XP Pro SP2, all updates. Lite On CD/DVD reader and
Lite On CD/DVD burner.

*Old* CD-Rs burned on an SP1 PC with EZ CD Creator 5 using UDF
crash imediately upon AutoPlay attempting to scan them Blue
Screen of Death. The message coming back from MS is that it is a
driver error and to contact the manufacturer. Except that the
manufacturer is MS itself.

DVD-Rs burned on the SP2 box using Easy Media Creator 8 and UDF
102 load OK and can be scanned using My Computer, but eventually
one or more files are encountered that cause the same crash.

In *all* cases the *only* file types on these discs are JPEGs.
No multi-media, nothing else.

I can find nothing in the MS KB nor by Googling and there is
nothing on Lite On's web site that suggests I need a firmware
upgrade.

Anybody got any ideas? Please don't suggest I use Joliet. These
very same CD and DVD discs read 100% correctly on my old SP1
box, so the problem can only be specific to Lite On or a bug in
SP2 (or both).

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

New PC, Win XP Pro SP2, all updates. Lite On CD/DVD reader and
Lite On CD/DVD burner.

*Old* CD-Rs burned on an SP1 PC with EZ CD Creator 5 using UDF
crash imediately upon AutoPlay attempting to scan them Blue
Screen of Death. The message coming back from MS is that it is a
driver error and to contact the manufacturer. Except that the
manufacturer is MS itself.

DVD-Rs burned on the SP2 box using Easy Media Creator 8 and UDF
102 load OK and can be scanned using My Computer, but eventually
one or more files are encountered that cause the same crash.

In *all* cases the *only* file types on these discs are JPEGs.
No multi-media, nothing else.

I can find nothing in the MS KB nor by Googling and there is
nothing on Lite On's web site that suggests I need a firmware
upgrade.

Anybody got any ideas? Please don't suggest I use Joliet. These
very same CD and DVD discs read 100% correctly on my old SP1
box, so the problem can only be specific to Lite On or a bug in
SP2 (or both).

Have you considered that Easy Media Creator 8 may be the problem? That or a
defective drive or a bad IDE driver, or a bad cable, etc. etc. SP2 is
unlikely to be the cause of the problem.

To start troubleshooting: Make sure you have the latest chipset drivers
installed. Try the burner on a new cable with no other drives on the same
cable. Uninstall Easy Media Creator 8 and install a different program. If it
still fails then try a different drive. If it still fails it is starting to
look like a motherboard problem.

Kerry

 

[Gerry Cornell]

Please provide copies of the exact text of the error messages.


--


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Using invalid email address

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.



~~~~~~~~~~~~~~~~~~~~~~~~

 

[All Things Mopar]

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

Have you considered that Easy Media Creator 8 may be the
problem? That or a defective drive or a bad IDE driver, or
a bad cable, etc. etc. SP2 is unlikely to be the cause of
the problem.

Please re-read my post. *OLD* CD-Rs are the problem, not just
new ones, so no it is not Roxio 8.

When I send the crash report to MS, I get back a link to an MS
KB article that says what crashed was a device driver. Now,
the *only* driver that could possibly have failed is one of my
2 CD/DVD drives (one is a reader-only and the other is a
burner). Lite On does *not* provide drivers, they come from
MS. And, I've checked for new drivers (there are none) and
I've killed the DVD/CD's in Device Manager and let Win XP Pro
SP2 re-install them. Same problem.

To start troubleshooting: Make sure you have the latest
chipset drivers installed. Try the burner on a new cable
with no other drives on the same cable. Uninstall Easy
Media Creator 8 and install a different program. If it
still fails then try a different drive. If it still fails
it is starting to look like a motherboard problem.

The only chipset that could be out-of-date is on the Lite On
drives, but there isn't anything on their web site to support
that theory. I have the latest mobo chipset stuff installed.
Ditto for the BIOS.

It is *not* a burner issue. I can "prove" that by reading the
CD-Rs that crash my new SP2 box on my old SP1 box and my
wife's Win 98 SE box. Both not only read all the files, but
also show the full 32 character long volume name allowed by
UDF. When I can get SP2 to read a UDF CD at all, it truncates
the volume name to 15.

The problem is either SP2 or Lite On or both. It is *not* the
CDs nor is it what I used to burn them. My nephew who built my
PC is coming over one night this week to put in my older CD
drives into my new PC. If the problem goes away, then I'll
know it is a Lite On issue. If not, it is an SP2 issue, at
which time I'll call MS tech support. I can do that for free
since I have a retail license.

What I'm trying to find out here is if anyone else has seen
this. It is a very tough problem to debug as most people don't
even know about UDF on CD-Rs, hence they've not burned any,
which may explain why no one else is experiencing this.

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

 

[All Things Mopar]

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

Please provide copies of the exact text of the error messages.

I can't! It is a classic Blue Screen of Death. All I can see
before my PC restarts is one of two messages:
Page_Fault_In_Non_Paged_Area (which is an oxymoron to me) or
Bad_Pool_Header.

When my PC restarts, I get the standard Windows dialog box
asking if I want to send the error report to MS. When I do, it
comes back and says no such problem could be found in their KB
and simply says that a driver crashed. That'd help, except that
it is a Win XP Pro SP2 driver, and there is no update. And, I've
removed both devices and let XP reinstall its drivers, no joy.

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

See comments inline.

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


Please re-read my post. *OLD* CD-Rs are the problem, not just
new ones, so no it is not Roxio 8.

Roxio installs software that acts like a driver. It could easily be Roxio
conflicting with another driver or software.

When I send the crash report to MS, I get back a link to an MS
KB article that says what crashed was a device driver. Now,
the *only* driver that could possibly have failed is one of my
2 CD/DVD drives (one is a reader-only and the other is a
burner). Lite On does *not* provide drivers, they come from
MS. And, I've checked for new drivers (there are none) and
I've killed the DVD/CD's in Device Manager and let Win XP Pro
SP2 re-install them. Same problem.


The only chipset that could be out-of-date is on the Lite On
drives, but there isn't anything on their web site to support
that theory. I have the latest mobo chipset stuff installed.
Ditto for the BIOS.

What chipset are you using? Some like Intel also require you to install IDE
controller drivers in some cases.

It is *not* a burner issue. I can "prove" that by reading the
CD-Rs that crash my new SP2 box on my old SP1 box and my
wife's Win 98 SE box. Both not only read all the files, but
also show the full 32 character long volume name allowed by
UDF. When I can get SP2 to read a UDF CD at all, it truncates
the volume name to 15.

The problem is either SP2 or Lite On or both. It is *not* the
CDs nor is it what I used to burn them. My nephew who built my
PC is coming over one night this week to put in my older CD
drives into my new PC. If the problem goes away, then I'll
know it is a Lite On issue. If not, it is an SP2 issue, at
which time I'll call MS tech support. I can do that for free
since I have a retail license.

You are jumping to conclusions about SP2. It could definately be a defective
burner though. I build computers and use LiteOn as well as LG drives. I have
experienced defective drives with both brands. I don't know of any issues
with non-defective drives with either brand. I have been using both brands
with SP2 since it came out.

What I'm trying to find out here is if anyone else has seen
this. It is a very tough problem to debug as most people don't
even know about UDF on CD-Rs, hence they've not burned any,
which may explain why no one else is experiencing this.

I set up many computers with Nero or Roxio using UDF and CDRW disks for
backup. Some drives are very sensitive to the brand of disk used. Memorex in
particular seems to cause a lot of problems. It is also quite common for UDF
formatted disks to be unreadable in drives other than the one they were
formatted in. It is also common with Roxio to have problems with disks
formatted with an older version. Nero InCD seems to work a little better
especially the newer versions but it also has some problems. UDF is not the
most reliable file system. I always tell my clients to supplement using CDRW
disks with CDRs at least once a week. I also build in error checking to the
CDRW backups to verify a good backup. My clients generally have to change
out the CDRW disks after a few uses as they fail on the verification
process. Some disks last several months, some fail after two or three uses.
I would not recommend CDRW and UDF for long term storage.

The error messages you indicate in another post can also be caused by bad
ram. I know you won't believe me but bad ram could be the cause of your
problem. You seem set on blaming SP2 for some reason. If all other
troubleshooting fails try running memtest86+ for a few hours.
www.memtest.org

Kerry

 

[All Things Mopar]

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

See comments inline.

Roxio installs software that acts like a driver. It could
easily be Roxio conflicting with another driver or
software.

Yes, Kerry, I know. That is why I uninstalled not only my old
Roxio EZ CD Creator 5 and the Nero Express that came with my
CD/DVD burner. I then did an exhaustive search for orphaned
Registry entries via JV16 Powertools, and removed several
thousand that Roxio and Nero had put there.

Then, with everything cleared out, I turned Windoze own CD
burning off and tried again. Same problem - I've got a large
number of CD-Rs burned originally with EZ CD Creator 5 that
100% crash Win XP Pro SP2 on my new box, yet load and read
completely correctly on my old SP1 box and my wife's Win 98 SE
box.

So, while I am still flumoxxed as to what the root cause of
this is, I can categorically say that it is *not* the CD-Rs
themselves. The mystery that remains is whether there's a
firmware bug in both my Lite On drives or an SP2 issue, or
both.

What chipset are you using? Some like Intel also require
you to install IDE controller drivers in some cases.

The motherboard is Asus and has the latest chipset on it, to
the best of my knowledge. The CPU is an AMD 3700 64/32,
running in 32-bit mode, as my XP is not the newer 64-bit
version.

You are jumping to conclusions about SP2. It could
definately be a defective burner though. I build computers
and use LiteOn as well as LG drives. I have experienced
defective drives with both brands. I don't know of any
issues with non-defective drives with either brand. I have
been using both brands with SP2 since it came out.

I may be jumping to conclusions about SP2, and I may not be.
All I can say is that the crashes are *NOT* burner related.
One more time: the very same CDs work 100% correctly on SP1
and 98.

I set up many computers with Nero or Roxio using UDF and
CDRW disks for backup. Some drives are very sensitive to
the brand of disk used. Memorex in particular seems to
cause a lot of problems. It is also quite common for UDF
formatted disks to be unreadable in drives other than the
one they were formatted in. It is also common with Roxio to
have problems with disks formatted with an older version.
Nero InCD seems to work a little better especially the
newer versions but it also has some problems. UDF is not
the most reliable file system. I always tell my clients to
supplement using CDRW disks with CDRs at least once a week.
I also build in error checking to the CDRW backups to
verify a good backup. My clients generally have to change
out the CDRW disks after a few uses as they fail on the
verification process. Some disks last several months, some
fail after two or three uses. I would not recommend CDRW
and UDF for long term storage.

Please, please, please re-read what I've been saying. What you
say is true, but please comprehend that these are *old* CDs as
well as some new ones I burned under SP2 before I discovered
the problem.

The CD-Rs that crash include Memorex, Verbatim, TDK, and
several others, so it is not, not, not the media.

The error messages you indicate in another post can also be
caused by bad ram. I know you won't believe me but bad ram
could be the cause of your problem. You seem set on blaming
SP2 for some reason. If all other troubleshooting fails try
running memtest86+ for a few hours. www.memtest.org

I didn't say anything about my system because the last time I
did, I was flamed for being too verbose. But, I have run
exhaustive tests using Hot CPU Tester 4.22 for 2, 4, 6, and 11
hours - with no, repeat no problems. That doesn't mean there
aren't any, just that a very good diagnostic program has
failed to find them so far.

As soon as I can, I'm going to swap known good CD drives from
my SP1 box with the Lite On drives. I'll then be able to see
if the problem goes away under SP2 and appears under SP1,
which would point to Lite On. Next, is a call to M$ tech
support.

BTW, I've Googled until I'm blind, and I can assure you that I
am *not* the only person seeing this kind of crash on SP2.
Some didn't get it until they upgraded from SP1 to SP2, while
others didn't say. And, the bulk of the problems seem to be
Lite On, but that could be coincidence since Lite On is a very
popular brand.

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

More info always helps. With all the new info I still suspect a hardware
problem. I'm not clear if the old CDRs cause a crash in both drives. In any
case with all the new info you have posted I would suspect a controller
problem or a problem with one of the drives if they are both on the same
cable. Try hooking up one drive at a time, uninstall any UDF or burning
software, install the UDF reader software available from Roxio and see what
happens. You don't mention what model your motherboard is. I have had some
problems with optical disks on the IDE interface and SATA hard disks in a
RAID configuration with nForce chipsets. I spent hours trying to set this up
for a client and eventually gave up. I disabled RAID and set the SATA
controller to show up as a regular IDE controller. The optical drives worked
fine after that. Good luck. If you solve the problem let us know.

Kerry

 

[Gerry Cornell]

Jerry

You do often get error messages when the fault is a classic Blue Screen
of Death but you are only giving us part of the message.

Easy CD Creator 5.0 Does Not Function In Windows XP
http://support.microsoft.com/?kbid=310628&sd=RMVP

However, I cannot say whether the above Article relates to your problem
because of the incompleteness of the information you have provided.

I suggest you Disable automatic restart on system failure. This should
help by allowing time to write down the STOP code properly. Right click
on the My Computer icon on the Desktop and select Properties, Advanced,
StartUp and Recovery, System Failure and uncheck box before
Automatically Restart.

There will also be Error Reports in Event Viewer. Please post copies.

You can access Event Viewer by selecting Start, Administrative Tools,
Event Viewer.
When researching the meaning of the error, information regarding Event
ID, Source
and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the
error you want to copy. In the window, which appears is a button
resembling two
pages. Double click the button and close Event Viewer. Now start your
message
(email) and do a paste into the body of the message. This will paste the
info from the
Event Viewer Error Report complete with links into the message. Make
sure this is
the first paste after exiting from Event Viewer.

Just because you do not know what they mean doesn't mean others cannot
interpret the.

BTW have you tried a CD disc drive cleaner?

--


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Using invalid email address

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.



~~~~~~~~~~~~~~~~~~~~~~~~

 

[All Things Mopar]

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

More info always helps. With all the new info I
still suspect a hardware problem. I'm not clear if
the old CDRs cause a crash in both drives.

Yes, both drives cause the crashes with CD-Rs burned a couple
years ago with Roxio's EZ CD Creator 5.35 (updated to support
both XP SP1 and SP2). One of my Lite On drives is just a CD/DVD
reader and the other a burner, so 2 different models. Can't
ffind anything definitive on Lite On's web site. Groan!

In any case with all the new info you have posted
I would suspect a controller problem or a problem
with one of the drives if they are both on the same
cable. Try hooking up one drive at a time, uninstall
any UDF or burning software, install the UDF reader
software available from Roxio and see what happens.

Could be a cable thingy, hadn't thought of that. But if the
cable is defective or at least intermittant, wouldn't Joliet CD-
Rs fail at least some of the time? None do, nor do any
commercially mastered "real" CDs, such as software comes on.

You don't mention what model your motherboard is. I have
had some problems with optical disks on the IDE interface
and SATA hard disks in a RAID configuration with nForce
chipsets.

nForce is a nVidia video card right? I've got an ATI Radeon.

I spent hours trying to set this up for a client
and eventually gave up. I disabled RAID and set the
SATA controller to show up as a regular IDE controller.
The optical drives worked fine after that. Good luck.
If you solve the problem let us know.

Roxio's UDF reader got installed with V8, but I'd uninstalled
both EZ CD Creator 5 and Nero Express (and cleaned out my
Registry manually) before installing the newer Roxio software.
Still crashed.

I have also verified that the Windoze sys files for UDF,
including udfs.sys, Cdudf_xp.sys, IviUdf.sys, and undffsrec.sys
are all in the right places. I have researched this thoroughly
and UDF, all versions including the newer 102 variety, *are*
supported across all Windoze O/S's since 98. I will swap the
drives, as I said.

My mobo is an Asus, don't recall the model number. I you really
need it, I can go find the docs for it.

I have SATA instead of IDE as well. But, at this point in the
neverending saga, I don't want to throw out the baby with the
bathwater and revert to standard IDE, at least not before giving
both Lite On and M$ tech support a chance at debugging this.

Couple other things: I uninstalled RAID support some days ago
for other reasons, and it made no difference. And, I killed
Norton System Works 2003 (don't attack me, OK?), but that made
no difference, either. The only reason my computer builder
nephew didn't see this problem during his build, test, and burn-
in, was that he didn't have any UDF CDs. And, once he found out
about this, he confessed not even knowing anything about the
difference between UDF and Joliet. He personally uses ISO 9660
from Linux for his burns, but I need UDF to get the long file
names I want for my car pictures.

And, let me remind everyone that the volume names of the CDs and
DVDs I *can* read without a crash, are truncated at 15
characters, while on my SP1 and 98 boxes, I can see the entire
up to 32 character volume name defined under the various UDF
packet writing specs.

If I do find a solution, I will certainly post it. There's
plenty I know already, but also plenty I do not.

Thanks for the continuing suggestions, Kerry

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

 

[All Things Mopar]

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

Jerry

You do often get error messages when the fault is a classic
Blue Screen of Death but you are only giving us part of the
message.

I don't have the entire error message because it only shows up
for less than a second.

Easy CD Creator 5.0 Does Not Function In Windows XP
http://support.microsoft.com/?kbid=310628&sd=RMVP

This KB article is dated November, 2003, a year before SP2,
and is the only one in the entire MS KB I can find.

However, I cannot say whether the above Article relates to
your problem because of the incompleteness of the
information you have provided.

I suggest you Disable automatic restart on system failure.
This should help by allowing time to write down the STOP
code properly. Right click on the My Computer icon on the
Desktop and select Properties, Advanced, StartUp and
Recovery, System Failure and uncheck box before
Automatically Restart.

That's a good idea. I'll try it.

There will also be Error Reports in Event Viewer. Please
post copies.

You can access Event Viewer by selecting Start,
Administrative Tools, Event Viewer.
When researching the meaning of the error, information
regarding Event ID, Source
and Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in
Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;3084
27&Product=winxp

A tip for posting copies of Error Reports! Run Event Viewer
and double click on the
error you want to copy. In the window, which appears is a
button resembling two
pages. Double click the button and close Event Viewer. Now
start your message
(email) and do a paste into the body of the message. This
will paste the info from the
Event Viewer Error Report complete with links into the
message. Make sure this is
the first paste after exiting from Event Viewer.

Just because you do not know what they mean doesn't mean
others cannot interpret the.

BTW have you tried a CD disc drive cleaner?

These are brand new drives, and if they're already dirty I'm
in real trouble! Plus, one more time, Joliet CD-Rs are OK and
the UDF CD-Rs that kill SP2 work on SP1.

I'll look into your other error tracking suggestions and post
what I find. Thanks for the help.

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

 

[All Things Mopar]

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

I suggest you Disable automatic restart on system failure.
This should help by allowing time to write down the STOP
code properly. Right click on the My Computer icon on the
Desktop and select Properties, Advanced, StartUp and
Recovery, System Failure and uncheck box before
Automatically Restart.

There will also be Error Reports in Event Viewer. Please
post copies.

OK, Gerry, I did as you suggested, here is what I got:

Blue screen of death said:

PAGE_FAULT_IN_NONPAGED_AREA

STOP 0x00000650 (0xC8A00000,0x00000000,0x8055EFB,0x00000000)

And, here is what Event Viewer captured:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 11/8/2005
Time: 5:15:46 PM
User: N/A
Computer: EVERYWHERE
Description:
Error code 10000050, parameter1 c8a00000, parameter2 00000000,
parameter3 8055e4fb, parameter4 00000000.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 74737953 45206d65 726f7272 72452020
0010: 20726f72 65646f63 30303120 35303030
0020: 50202030 6d617261 72657465 38632073
0030: 30303061 202c3030 30303030 30303030
0040: 3038202c 34653535 202c6266 30303030
0050: 30303030

Hope this makes more sense to you than me! Thanks again for
taking the time and effort to help me.

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

nForce is a motherboard chipset made by nVidia for AMD CPU's. It is reputed
to be very fast. I have setup quite a few motherboards using this chipset.
Most times it works well. When it doesn't many weird intermittent problems
occur. It appears this chipset is not very tolerant of non-conforming
hardware. I usually use it when I build a game system for someone but I
stick to high end brand name hardware in these systems. Even then I run into
the odd problem. For example you say you have a ATI Radeon video card. As an
OEM I can buy several brands of cards using the ATI X800 chipset. The
wholesale price varies by as much as $100.00 for cards with the exact same
specifications. Guess which ones usually work the best Guess which ones
are installed in cheap clones sold to a price point. I'm not saying your
nephew used cheap components. Asus is a top motherboard manufacturer. I'm
just pointing out that many factors come into play when you have strange
problems. I'm still betting one of the drives is defective.

Kerry

 

[Kerry Brown]

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


I don't have the entire error message because it only shows up
for less than a second.


This KB article is dated November, 2003, a year before SP2,
and is the only one in the entire MS KB I can find.


That's a good idea. I'll try it.



These are brand new drives, and if they're already dirty I'm
in real trouble! Plus, one more time, Joliet CD-Rs are OK and
the UDF CD-Rs that kill SP2 work on SP1.

You are comparing apples and oranges. The different hardware is the
significant item not SP1 or SP2. To tell if it is SP2 you would have to
setup the computer with SP1 and confirm it works then install SP2 and
confirm it breaks it.

Kerry

 

[All Things Mopar]

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

You are comparing apples and oranges. The different
hardware is the significant item not SP1 or SP2. To tell if
it is SP2 you would have to setup the computer with SP1 and
confirm it works then install SP2 and confirm it breaks it.

Kerry, I don't want to piss you off, OK? All I can tell you is
that it is not, not, not! the GD CD-Rs, OK?! They work, just not
on my new PC

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

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


Kerry, I don't want to piss you off, OK? All I can tell you is
that it is not, not, not! the GD CD-Rs, OK?! They work, just not
on my new PC

I don't see how from my post that you think I am talking about the CD's. You
are very clear that your new pc cannot read existing CD's that were burned
on your old SP1 computer that can read them. What is not clear is why you
think SP2 is the reason. There are more significant differences between the
pc's than the service pack level. Does the old pc have exactly the same
hardware, programs and drivers installed except for SP2? It may turn out to
be that SP2 is not compatible with something on your new pc. It is unlikely
with new hardware and software. It is far more likely that some hardware is
malfunctioning or some driver has a bug. Concentrating on SP2 at this time
is a red herring.

Kerry

 

[Gerry Cornell]

Whilst trying to track down the meaning of the error messages I found
this posting in Google which is worth a try.

To determine what driver is causing the problem I
need you to enable driver verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit
Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and
select
the safe mode boot option. Follow the same steps above but on step 4
choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.


This will slow the performance of you computer a little while enabled
but
will hopefully catch the driver causing corruption. Next time you
crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my
way.
If you have any questions or I didn't explain something well enough
don't
hesitate to e-mail me (remove "online") back. Good Luck,


Joshua Smith
OpenGL Test Lab
Microsoft
-----



--


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Using invalid email address

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.



~~~~~~~~~~~~~~~~~~~~~~~~

 

[All Things Mopar]

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

I don't see how from my post that you think I am talking
about the CD's. You are very clear that your new pc cannot
read existing CD's that were burned on your old SP1
computer that can read them. What is not clear is why you
think SP2 is the reason. There are more significant
differences between the pc's than the service pack level.
Does the old pc have exactly the same hardware, programs
and drivers installed except for SP2? It may turn out to
be that SP2 is not compatible with something on your new
pc. It is unlikely with new hardware and software. It is
far more likely that some hardware is malfunctioning or
some driver has a bug. Concentrating on SP2 at this time
is a red herring.

Kerry, there can be only two possibilities here: 1) some
combination of hardware on my new PC, including the CD/DVD
drives themselves, the mobo/processor, memory, what have you,
and SP2. Besides the obvious differences in HD type and SATO
vs. IDE, my printer and scanner drivers are identical.

I have eliminated the ATI Radeon video cardbeing part of this
issue by trying unsuccessfully to read UDF-encoded CD-Rs (new
ones and old ones) in Safe Mode, which takes the video card
out of the picture as well as any other driver such as my
printer, scanner, etc.

I also believe that SP2 is at least an unwitting accomplice in
my problem in that I've read dozens and dozens of chat room
comments from people with the same problem I have, and a few
more that I don't have. Most of these folks have Lite On
drives, but that's because it is a popular brand. If I'm not
mistaken, Mitsushita builds the drives for Lite On.

All this, coupled with the fact that no other computer I own
nor my builder-friend-nephew owns fails, but all are 98 or
SP1. And, none of my older CD-Rs burned with Joliet fail. That
leads me back again and again to SP2. Further, Microcrap's own
return link to me when I "send" in the report with details
about the crash says that they can find nothing in their KB (I
believe it, neither can I!), but they specifically say that it
is a driver problem, and I should contact the driver
manufacturer. Well, Kerry, Microcrap is the "manufacturer", as
Lite On does not provide drivers with their readers or
burners.

I have been working on this for a week now and have plenty of
anecdotal information but no solid facts. I simply cannot
believe, though, that so many people are having crashes with
UDF packet writing CD-Rs and DVD-Rs *only* under SP2 if SP2
does not at least in some way be part of the problem. SP2 is a
virtual rewrite of all of XP Pro, and it would be easy to
create a side-effect bug that maybe alpha and beta testers
missed, or it was found and reported but not yet acknowledged
and fixed. The fact that nothing exists in the KB may only
indicate that M$ hasn't yet recognized the problem or hasn't
yet found a fix or a work-around. I don't like Bill the Gates
particularly, but I have found the MS KB to be invaluable - if
I can find specific references for problems I encounter.

So, I am still keeping an open mind about this. There's
precious little else I can do until my nephew has time away
from running his father's machine shop 15-18 hours a day to
come over and swap my drives around to see if an older drive
makes the crashes go away, and the newer drives make my SP1
box fail.

Should it turn out to be a Lite On problem, I imagine he is
going to have a devil of a time finding some other
manufacturer that is *known* to work reliably with the several
versions of UDF. Finally, let me say that I have consulted a
number of books on Windows XP Pro SP2 (specifically) that
*all* say that UDF is fully supported, so I can only report
what I am seeing and hope that something pops up that I can
fix.

Thanks for your contuing help and suggestions.

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

 

[All Things Mopar]

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

Whilst trying to track down the meaning of the error
messages I found this posting in Google which is worth a
try.

To determine what driver is causing the problem I
need you to enable driver verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit
next 4) Click on 'Select all drivers installed on this
computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on
reboot. If this occurs hit F8 when rebooting just before
the windows logo screen and select
the safe mode boot option. Follow the same steps above but
on step 4 choose
'Select driver names from a list'; hit next; check the box
next to any driver where the provider is not Microsoft; hit
Finish; reboot.

How do I turn the verifier back "OFF"? I don't want to try
this and render my PC unusable if there's a remote possibility
it may crash on a re-start.

This will slow the performance of you computer a little
while enabled but
will hopefully catch the driver causing corruption. Next
time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs
please send the corresponding minidump (by default it is at
c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something
well enough don't
hesitate to e-mail me (remove "online") back. Good Luck,

Thanks for offering to help me with this privately. After I
understand what the verifier does and does not do and how to
turn it on and off, I'll give it a go.

Joshua Smith
OpenGL Test Lab
Microsoft

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

 

[Gerry Cornell]

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.

--


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Using invalid email address

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.



~~~~~~~~~~~~~~~~~~~~~~~~