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



Jynx,

> I selected picture files and hit properties.
> Everything that way seems to be working okay now without looking at links.

Read on, there are some NVidia items that can cause problems with your right
click menu.

> Timeout (30000 milliseconds) waiting for a transaction response from the
> NVSvc service.

NVSvc service is the NVIDIA Driver Helper Service. This does *NOT* need to
be running. I have mine disabled.

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

[[User Action
No user action is required.]]
ID: 1003
Source: System Error
http://www.microsoft.com/technet/support/ee/result.aspx?EvtSrc=System+Error&EvtID=1003&ProdName=Windows+Operating+System&LCID=1033&ProdVer=5.2

> The device, \Device\CdRom0, has a bad block.

This means that part of the data on that CD that was in the CD drive is
toast. Consider it scrambled. Think of a scratched up phonograph record.
The way that record would sound is how the data is on part of your CD. Or a
partially mangled cassette tape if you've ever heard one of those play. ;-)

> Would this be bad ram?

No. RAM is Random Access Memory also known as main memory or system memory
is a term commonly used to describe the memory within a computer. This is
hardware. Different hardware than the Hard drive. Hard drive is used to
store programs, data, etc on your machine. RAM is a temporary storage area
utilized by the CPU. Before a program can run the program is loaded into
memory which allows the CPU direct access to the program.

RAM info and pictures here...
http://www.computerhope.com/help/memory.htm

Hard drive looks like this...
http://www.computerhope.com/jargon/h/harddriv.htm

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

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:435C8C66-E79A-41F8-9920-818FFD23CF7E@xxxxxxxxxxxxx,
Jynx o.t.T.Leaves <vernonaemonteith@xxxxxxxxxxxx(donotspam)> hunted and
pecked:
> "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

.



Relevant Pages

  • hang on startx with nvidia / also with emu10kx
    ... avail memory = 2082811904 ... ACPI APIC Table: <Nvidia ASUSACPI> ... bdftopcf-1.0.1 Convert X font from BDF to PCF ... compat4x-i386-5.3_9 A convenience package to install the compat4x libraries ...
    (freebsd-current)
  • LD internal error while compiling 2.6.15 kernel
    ... cpufreq_stats freq_table cpufreq_powersave cpufreq_ondemand cpufreq_conservative nvidia video container button battery ac ipv6 nfs lockd sunrpc af_packet ide_cd analog gameport snd_mpu401 snd_mpu401_uart snd_rawmidi snd_seq_device floppy pcspkr tsdev sk98lin skge ohci1394 shpchp pci_hotplug forcedeth amd74xx generic ide_core usbhid ... 0000:00:00.0 Memory controller: nVidia Corporation: Unknown device 005e ... Subsystem: Asustek Computer, Inc.: Unknown device 815a ... # ACPI Support ...
    (Linux-Kernel)
  • Re: Video Cards
    ... If you are buying for gaming I suggest you ask this question on the forums for the games you like to play. ... Chipset Manufacturer NVIDIA ... Memory Interface 128-bit ... OpenGL OpenGL 2.0 ...
    (microsoft.public.windowsxp.general)
  • Re: Video Cards
    ... Chipset Manufacturer NVIDIA ... Memory Interface 128-bit ... DirectX DirectX 9 ... OpenGL OpenGL 2.0 ...
    (microsoft.public.windowsxp.general)
  • Re: Video Cards
    ... Chipset Manufacturer NVIDIA ... Memory Interface 128-bit ... DirectX DirectX 9 ... OpenGL OpenGL 2.0 ...
    (microsoft.public.windowsxp.general)