Major crash & reboot: drag & drop files to CD burner

Archived from groups: microsoft.public.windowsxp.general (More info?)

Recently I retreived a bunch of my pictures off of our church computer. I
burned them to disk with some Roxio program.

I brought them to home computer and put them in the appropriate file with
other pictures from same event. It was my intention to make one CD with all
pictures from same event on it.

I selected pictures, hit properites . . .had quite a bit of hang time.

I selected all pictures for burning. I told the burner what to do using the
Win XP pro directions (wizard?) and walked away. DIdn't work, had a problem.

Low on memory, so I rebooted. Came back and deleted a bunch of pics that
had been archived.

Selected pics again, but during the time it was transferring files to the CD
(before the wizard) it put up a black screen with a bunch of information that
flashed too quickly to read before it rebooted.

After the reboot, the computer sent a message to wherever it sends messages
to about a major system crash with a report. (I could make this happen and
post report too.) The online crash analysis system referred me to a Roxio
site for a file called updatecdr4_53_71. "Roxio CD & DVD creator update
utlity"

I ran it and it told me "The Cdr4 layer has not been detected."

So I still have the problem. I'll post this and then perhaps attach the
report.

thanks for reading this.
Jynx
6 answers Last reply
More about major crash reboot drag drop files burner
  1. Archived from groups: microsoft.public.windowsxp.general (More info?)

    error signature:

    BCCode : 100000d1 BCP1 : 00000060 BCP2 : 00000002 BCP3 : 00000000
    BCP4 : FC575844 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

    The following files will be included n this error report:

    C:\DOCUME~1\Amy\LOCALS~1\Temp\WER9b56.dir00\Mini082005-01.dmp
    C:\DOCUME~1\Amy\LOCALS~1\Temp\WER9b56.dir00\sysdata.xml
  2. Archived from groups: microsoft.public.windowsxp.general (More info?)

    "Wesley Vogel" wrote:

    > > I selected pictures, hit properites . . .had quite a bit of hang time.
    >
    > [[When you right-click on a folder and choose Properties, nothing may
    > happen.]]
    >
    I selected picture files and hit properties.
    Everything that way seems to be working okay now without looking at links.

    >
    > > Low on memory, so I rebooted. Came back and deleted a bunch of pics that
    > > had been archived.
    >
    > How full your hard drive is has nothing to do with memory.

    yeah, yeah, yeah, I did that because not long ago, when trying to archive
    digital pictures onto a cd, the computer told me that the hard drive was too
    full. (sorry, too much information, I'm sure)
    >
    > Look in the Event Viewer and see what errors around the timet hat your
    > machine rebooted.
    >
    > Event ID & the Event Source are very important.
    >
    > > This advice was very helpful. Here's where I'm at right now. (I'm not done working on this.)

    first error:

    Event Type: Error
    Event Source: Service Control Manager
    Event Category: None
    Event ID: 7011
    Date: 8/17/2005
    Time: 4:41:46 PM
    User: N/A
    Computer: MOSSYROC-K11YHD
    Description:
    Timeout (30000 milliseconds) waiting for a transaction response from the
    NVSvc service.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.

    Went to the link and yes, my computer was running low on resources at the
    time, so it explains this.

    error #2:

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 8/17/2005
    Time: 4:41:52 PM
    User: N/A
    Computer: MOSSYROC-K11YHD
    Description:
    Error code 100000d1, parameter1 00000060, parameter2 00000002, parameter3
    00000000, parameter4 fc6e5844.

    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 31 30 30 30 30 30 64 100000d
    0020: 31 20 20 50 61 72 61 6d 1 Param
    0028: 65 74 65 72 73 20 30 30 eters 00
    0030: 30 30 30 30 36 30 2c 20 000060,
    0038: 30 30 30 30 30 30 30 32 00000002
    0040: 2c 20 30 30 30 30 30 30 , 000000
    0048: 30 30 2c 20 66 63 36 65 00, fc6e
    0050: 35 38 34 34 5844

    5 different things that windows xp help suggested:
    article #1, I don't believe it was recovering (I know it wasn't recovering)
    from hibernation.
    #2 the "symptoms" didn't match up,
    #3 was referring to "stop errors". I never saw this, but the computer did
    flash (I want to say shell) a black screen with information on it that was
    too fast to read before it rebooted. << I MAY COME BACK TO THIS RESOLUTION>>
    The solution for this is removal of malware "sdbot" or variant
    #4 referred to spyware kernal driver. The error messages don't line up here
    either and the only thing I found in common is the reboot
    #5 was very specific about the error code and had a solution to the HaxDoor
    virus. I'm ruling this one out, since the error code was pretty different.

    > Read all info | Copy and paste to Notepad | Click the [+] Related Knowledge
    > Base articles | Follow any links that might be useful
    >
    > This may be related to the Roxio software or maybe bad ram.

    This statement of yours caught my attention today because I was looking
    through the event log to see what was going last night with symptoms reported
    to me and found this:
    >
    Event Type: Error
    Event Source: Cdrom
    Event Category: None
    Event ID: 7
    Date: 8/23/2005
    Time: 7:48:43 PM
    User: N/A
    Computer: MOSSYROC-K11YHD
    Description:
    The device, \Device\CdRom0, has a bad block.

    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 03 00 68 00 01 00 b8 00 ..h...¸.
    0008: 00 00 00 00 07 00 04 c0 .......À
    0010: 00 01 00 00 9c 00 00 c0 ....œ..À
    0018: 00 00 00 00 00 00 00 00 ........
    0020: 00 00 07 01 00 00 00 00 ........
    0028: b1 3e 00 00 00 00 00 00 ±>......
    0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ....
    0038: 40 00 00 c4 02 00 00 00 @..Ä....
    0040: 00 20 0a 12 48 02 00 00 . ..H...
    0048: 00 00 00 00 0a 00 00 00 ........
    0050: b0 56 88 00 90 72 98 81 °Vˆ.r˜
    0058: 00 00 00 00 08 70 97 81 .....p—
    0060: 02 00 00 00 e0 20 00 00 ....à ..
    0068: 28 00 00 00 20 e0 00 00 (... à..
    0070: 01 00 00 00 00 00 00 00 ........
    0078: 70 00 03 00 00 00 00 0a p.......
    0080: 00 00 00 00 11 05 00 00 ........
    0088: 00 00 00 00 00 00 00 00 ........

    Would this be bad ram?

    Now today I tried to replicate the problem I described before, but before I
    did, I pulled the cd out of the cd-rom (maybe this isn't related, I don't
    know.)

    I had no problem transferring files to the cd-burner. (I haven't burned
    yet, but it didn't reboot.)

    Again, thanks for your time in reading all of this and helping me make some
    sense out of it.

    Jynx

    > --
    > Hope this helps. Let us know.
    >
    > Wes
    > MS-MVP Windows Shell/User
    >
    >
  3. Archived from groups: microsoft.public.windowsxp.general (More info?)

    Wes,

    Yes, I totally know what a tape is. In fact, as a teenager, I was given my
    parent's old junky stereo for my room. . . which included a 8 track player
    (mighta been broke though.)

    Maybe I wasn't completely clear. (time out information is really helpful,
    I'm going to follow up with that.)

    The CDrom error wasn't reported during the whole reboot problem. (Could
    that be related though?) Would a bad block on a cd cause a reboot?

    Like I said, took cd out and transferred files for a burn and did NOT
    restart computer.

    > > error #2:
    > >
    > > Event Type: Error
    > > Event Source: System Error
    > > Event Category: (102)
    > > Event ID: 1003
    > > Date: 8/17/2005
    > > Time: 4:41:52 PM
    > > User: N/A
    > > Computer: MOSSYROC-K11YHD
    > > Description:
    > > Error code 100000d1, parameter1 00000060, parameter2 00000002, parameter3
    > > 00000000, parameter4 fc6e5844.
    > >
    > > 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 31 30 30 30 30 30 64 100000d
    > > 0020: 31 20 20 50 61 72 61 6d 1 Param
    > > 0028: 65 74 65 72 73 20 30 30 eters 00
    > > 0030: 30 30 30 30 36 30 2c 20 000060,
    > > 0038: 30 30 30 30 30 30 30 32 00000002
    > > 0040: 2c 20 30 30 30 30 30 30 , 000000
    > > 0048: 30 30 2c 20 66 63 36 65 00, fc6e
    > > 0050: 35 38 34 34 5844
    > >
    > > 5 different things that windows xp help suggested:
    > > article #1, I don't believe it was recovering (I know it wasn't
    > > recovering) from hibernation.

    > > #2 the "symptoms" didn't match up,

    > > #3 was referring to "stop errors". I never saw this, but the computer did
    > > flash (I want to say shell) a black screen with information on it that was
    > > too fast to read before it rebooted. << I MAY COME BACK TO THIS
    > > RESOLUTION>> The solution for this is removal of malware "sdbot" or
    > > variant

    #4 referred to spyware kernal driver. The error messages don't
    > > line up here either and the only thing I found in common is the reboot
    > >

    #5 was very specific about the error code and had a solution to the
    > > HaxDoor virus. I'm ruling this one out, since the error code was pretty
    > > different.
    > >
    > >> Read all info | Copy and paste to Notepad | Click the [+] Related
    > >> Knowledge Base articles | Follow any links that might be useful
    > >>
    > >> This may be related to the Roxio software or maybe bad ram.
    > >
    > > This statement of yours caught my attention today because I was looking
    > > through the event log to see what was going last night with symptoms
    > > reported to me and found this:
    > >>
    > > Event Type: Error
    > > Event Source: Cdrom
    > > Event Category: None
    > > Event ID: 7
    > > Date: 8/23/2005
    > > Time: 7:48:43 PM
    > > User: N/A
    > > Computer: MOSSYROC-K11YHD
    > > Description:
    > > The device, \Device\CdRom0, has a bad block.
    > >
    > > For more information, see Help and Support Center at
    > > http://go.microsoft.com/fwlink/events.asp.
    > > Data:
    > > 0000: 03 00 68 00 01 00 b8 00 ..h...¸.
    > > 0008: 00 00 00 00 07 00 04 c0 .......À
    > > 0010: 00 01 00 00 9c 00 00 c0 ....œ..À
    > > 0018: 00 00 00 00 00 00 00 00 ........
    > > 0020: 00 00 07 01 00 00 00 00 ........
    > > 0028: b1 3e 00 00 00 00 00 00 ±>......
    > > 0030: ff ff ff ff 00 00 00 00 ÿÿÿÿ....
    > > 0038: 40 00 00 c4 02 00 00 00 @..Ä....
    > > 0040: 00 20 0a 12 48 02 00 00 . ..H...
    > > 0048: 00 00 00 00 0a 00 00 00 ........
    > > 0050: b0 56 88 00 90 72 98 81 °Vˆ.r˜
    > > 0058: 00 00 00 00 08 70 97 81 .....p—
    > > 0060: 02 00 00 00 e0 20 00 00 ....Ã ..
    > > 0068: 28 00 00 00 20 e0 00 00 (... Ã ..
    > > 0070: 01 00 00 00 00 00 00 00 ........
    > > 0078: 70 00 03 00 00 00 00 0a p.......
    > > 0080: 00 00 00 00 11 05 00 00 ........
    > > 0088: 00 00 00 00 00 00 00 00 ........
    > >
    > > Would this be bad ram?
    > >
    > > Now today I tried to replicate the problem I described before, but before
    > > I did, I pulled the cd out of the cd-rom (maybe this isn't related, I
    > > don't know.)
    > >
    > > I had no problem transferring files to the cd-burner. (I haven't burned
    > > yet, but it didn't reboot.)
    > >
    > > Again, thanks for your time in reading all of this and helping me make
    > > some sense out of it.
    > >
    > > Jynx
    > >
    > >> --
    > >> Hope this helps. Let us know.
    > >>
    > >> Wes
    > >> MS-MVP Windows Shell/User
    >
    >
  4. Archived from groups: microsoft.public.windowsxp.general (More info?)

    could not get this program to run. It told me that there was no
    "services,msc" program and I tried just "services" but nothing happened, not
    even a notification. . ..

    Jynx

    >
    > Disable the NVIDIA Display Driver Service...
    > Start | Run | Type: services,msc | OK |
    > Scroll down to and double click: NVIDIA Display Driver Service |
    > Under Startup type set to Disabled | Apply | Click the Stop button |
    > When it stops click OK | You may have to reboot
    >
    >
  5. Archived from groups: microsoft.public.windowsxp.general (More info?)

    Yeah, I'm really intrested in turning off these programs if they're running.
    (Makes me wonder why anyone thought I needed them in the first place.)

    Jynx

    The following items are probably also running...
    NVIDIA nView Wizard = nwiz.exe
    NVIDIA Display Properties Extension = NvCpl.dll
    NVIDIA nView Control Panel = nvtuicpl.cpl

    If you want to know how to disable them, post back.

    I have also disabled the following NVidia items and this has sped up my
    right click menus...
    NVIDIA Desktop Explore Desktop Explorer Menu
    NVIDIA Display Properties Extension DesktopContext Class
    NVIDIA Display Properties Extension NVIDIA CPL Extension
    NVIDIA Desktop Explorer nView Desktop Context Menu
  6. Archived from groups: microsoft.public.windowsxp.general (More info?)

    > Manually delete these three entries:
    > NvCplDaemon, NvMediaCenter and nwiz.

    I think the NvCplDaemon was already missing. I'll probably never need it,
    but I exported the registry value just in case . . .

    (not that I have trust issues, right?) (a-hem. . .)

    .. . . and I downloaded ShellExView.

    desktop explorer menu and desktop explorer were all that was present out of
    your list.

    I have disabled them, thanks!

    Just as long as this doesn't mess with my AOK - conquerors, I'll be just
    fine. (But as you said, I can just use display properties if needed. . .)

    Thanks so much for your help,
    Jynx
Ask a new question

Read More

Burner CD-Rom Windows XP