I did a search here and someone in the past checked their bootlog and the first driver 
that did not load was NDProxy.SYS but not solution was given.  My computer boots 
past the logon screen, loads the time, volume, modem, then reboots before loading 
COMODO and avast.  Sometimes it doesn't reboot and sometimes it reboots up to 5 times. 
 Mostly 1 or 2.  It all appeared to happen when I removed McAfee and loaded Avast 
antivirus and COMODO Firewall Pro (free) although I've been messing with this so 
long I am not sure.  I still have remnants of Iolo left I can't get rid of and see 
a McAfee file there also.  I downloaded some registry cleaner I can't remember and 
things were working good after I deleted all kinds of things I knew I didn't have 
on here anymore.  Then I got brave and started deleting things it said I needed to 
delete.  Before I realized that I think I deleted something I needed, I had also 
downloaded their defrag program and defraged my hard drive.  Now when I do a restore 
for a time before I did all this I don't think it is restoring what I need.  Anyway, 
here is my bootlog (ntbtlog.txt).  Does anyone have any idea what my problem is? 
 And please speak real slow step by step English as I am no computer whiz.
Service Pack 2 7 22 2008 15:59:11.500
Loaded driver \WINDOWS\system32\ntkrnlpa.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\System32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver pciide.sys
Loaded driver \WINDOWS\System32\DRIVERS\PCIIDEX.SYS
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver PartMgr.sys
Loaded driver nvraid.sys
Loaded driver \WINDOWS\System32\DRIVERS\CLASSPNP.SYS
Loaded driver VolSnap.sys
Loaded driver atapi.sys
Loaded driver nvatabus.sys
Loaded driver disk.sys
Loaded driver fltmgr.sys
Loaded driver sr.sys
Loaded driver PxHelp20.sys
Loaded driver KSecDD.sys
Loaded driver Ntfs.sys
Loaded driver inspect.sys
Loaded driver \WINDOWS\System32\DRIVERS\NDIS.SYS
Loaded driver \WINDOWS\System32\DRIVERS\TDI.SYS
Loaded driver nv_agp.sys
Loaded driver Mup.sys
Loaded driver \SystemRoot\System32\DRIVERS\fdc.sys
Loaded driver \SystemRoot\System32\DRIVERS\parport.sys
Loaded driver \SystemRoot\System32\DRIVERS\gameenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\i8042prt.sys
Loaded driver \SystemRoot\System32\DRIVERS\kbdclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\serial.sys
Loaded driver \SystemRoot\System32\DRIVERS\serenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbohci.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbehci.sys
Loaded driver \SystemRoot\System32\DRIVERS\nvnetbus.sys
Loaded driver \SystemRoot\system32\drivers\ALCXWDM.SYS
Loaded driver \SystemRoot\System32\DRIVERS\imapi.sys
Loaded driver \SystemRoot\System32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\System32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\System32\Drivers\GEARAspiWDM.sys
Loaded driver \SystemRoot\System32\DRIVERS\Xgiv3m.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbuhci.sys
Loaded driver \SystemRoot\System32\DRIVERS\smserial.sys
Loaded driver \SystemRoot\System32\Drivers\Modem.SYS
Loaded driver \SystemRoot\System32\DRIVERS\AmdK8.sys
Loaded driver \SystemRoot\System32\DRIVERS\audstub.sys
Loaded driver \SystemRoot\System32\DRIVERS\rasl2tp.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndistapi.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndiswan.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspppoe.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspptp.sys
Loaded driver \SystemRoot\System32\DRIVERS\msgpc.sys
Loaded driver \SystemRoot\System32\DRIVERS\psched.sys
Loaded driver \SystemRoot\System32\DRIVERS\ptilink.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspti.sys
Loaded driver \SystemRoot\System32\DRIVERS\termdd.sys
Loaded driver \SystemRoot\System32\DRIVERS\swenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\update.sys
Loaded driver \SystemRoot\System32\DRIVERS\mssmbios.sys
Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\System32\DRIVERS\usbhub.sys
Loaded driver \SystemRoot\system32\drivers\MODEMCSA.sys
Loaded driver \SystemRoot\System32\DRIVERS\NVENETFD.sys
Loaded driver \SystemRoot\System32\DRIVERS\flpydisk.sys
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\i2omgmt.SYS
Loaded driver \SystemRoot\System32\DRIVERS\cmdguard.sys
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Loaded driver \SystemRoot\System32\Drivers\Null.SYS
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\mnmdd.SYS
Loaded driver \SystemRoot\System32\DRIVERS\RDPCDD.sys
Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver \SystemRoot\System32\DRIVERS\rasacd.sys
Loaded driver \SystemRoot\System32\DRIVERS\ipsec.sys
Loaded driver \SystemRoot\System32\DRIVERS\tcpip.sys
Loaded driver \SystemRoot\system32\DRIVERS\USBSTOR.SYS
Loaded driver \SystemRoot\System32\DRIVERS\cmdhlp.sys
Loaded driver \SystemRoot\System32\DRIVERS\ipnat.sys
Loaded driver \SystemRoot\System32\DRIVERS\wanarp.sys
Loaded driver \SystemRoot\System32\Drivers\aswTdi.SYS
Loaded driver \SystemRoot\System32\DRIVERS\netbt.sys
Loaded driver \SystemRoot\System32\drivers\afd.sys
Loaded driver \SystemRoot\System32\DRIVERS\netbios.sys
Did not load driver \SystemRoot\System32\DRIVERS\processr.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Loaded driver \SystemRoot\System32\DRIVERS\rdbss.sys
Loaded driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\System32\Drivers\Fips.SYS
Loaded driver \SystemRoot\System32\Drivers\aswSP.SYS
Loaded driver \SystemRoot\System32\Drivers\Aavmker4.SYS
Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS
Loaded driver \SystemRoot\system32\DRIVERS\aswFsBlk.sys
Loaded driver \SystemRoot\System32\Drivers\aswMon2.SYS
Did not load driver \SystemRoot\System32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\system32\drivers\wdmaud.sys
Loaded driver \SystemRoot\system32\drivers\sysaudio.sys
Loaded driver \SystemRoot\system32\drivers\splitter.sys
Loaded driver \SystemRoot\system32\drivers\aec.sys
Loaded driver \SystemRoot\system32\drivers\swmidi.sys
Loaded driver \SystemRoot\system32\drivers\DMusic.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys
Loaded driver \SystemRoot\system32\drivers\drmkaud.sys
Loaded driver \SystemRoot\System32\Drivers\ParVdm.SYS
Loaded driver \SystemRoot\System32\Drivers\Fastfat.SYS
Loaded driver \SystemRoot\system32\DRIVERS\css-dvp.sys
Loaded driver \SystemRoot\System32\Drivers\HTTP.sys
Loaded driver \SystemRoot\System32\DRIVERS\srv.sys
 
Thanks so much for your attention.  Michele

[Reply or follow-up to this message]

I think you have a bad device driver loading there - it's css-dpv.sys which is known to cause problems. Preventing it loading might bring enough stability back to get the machine to boot, if you are lucky. This driver is listed as "supicious" and known to send out emails. That classes it as a rootkit in my book and you need some clever strokes to get rid of it. Can you connect the disk up as a slave drive on another PC, or do you have access to a BartPE bootable CD? Cheers. Spexx.

[Reply or follow-up to this message]

I searched the internet for css-dvp.sys and there are a number of references of it being from Iolo System Mechanic which I once had. It will never let me delete a few things related to Iolo because it said it was being used. But that was a long time ago that I uninstalled that program and this problem is new. And everyone that had a problem with css-dvp.sys had a blue screen and it said Page Fault in Non Paged Area and I don't get that. Of all the threads I read through, none ever solved the problem of how to get rid of css-dvp.sys. Other people mentioned what it said in their *.dmp (can't remember the actual name). Does anyone know how I can read my dump file (*.dmp)? I clicked on it the other day and it wanted to know what program to use to read it. I think that is where it will tell me what my problem is.

[Reply or follow-up to this message]

Michele,

Start up in Safe Mode and see if you can remove the listed file/files.

Use the search function to find the file. Right click the file & delete from search 
results. Search also for any files known o be associated with the program.

You may also have to turn of System Restore to clear all the previous Restore points, 
then create a new Restore Point when you are sure the file has been deleted.

BW



__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Tuesday, July 22, 2008 at 9:43 pm, michele2007 wrote:

>I searched the internet for css-dvp.sys and there are a number of references of 
it 

>being from Iolo System Mechanic which I once had.  It will never let me delete a 

>few things related to Iolo because it said it was being used.  But that was a long 

>time ago that I uninstalled that program and this problem is new.  And everyone 
that 

>had a problem with css-dvp.sys had a blue screen and it said Page Fault in Non Paged 

>Area and I don't get that.  Of all the threads I read through, none ever solved 
the 

>problem of how to get rid of css-dvp.sys.  

>

>Other people mentioned what it said in their *.dmp (can't remember the actual name). 

> Does anyone know how I can read my dump file (*.dmp)?  I clicked on it the other 

>day and it wanted to know what program to use to read it.  I think that is where 

>it will tell me what my problem is.   

[Reply or follow-up to this message]

That is interesting. My searches did not turn up any reference to Iolo System Mechanic. All the references pointed to Command Software Anti-virus, but also that known malware may disguise itself by this file name. Even if it is the real deal from Command Software, this link shows what Microsoft think of it. Prevx had a listing for it too here. Cheers. Spexx.

[Reply or follow-up to this message]

PROBLEM SOLVED, I HOPE: I deleted css-dvp.sys in Safe Mode. There were two of them. One in Windows\System 32 and one in c:\Program Files\Common Files\Authentium\AntiVirus. This must have gotten there with one of my many free registry scan downloads. I wonder if it would be okay to delete this whole Authentium folder? Anyway, it didn't fix the problem of my computer rebooting a few times each time I turn it on. So I did what the Microsoft response to sending my error report said. I went to Add or Remove Programs, sorted it by Date Last Used, selected Show updates and looked at the Last Used On dates to see recent installations. There was a program called Ask Toolbar so I deleted that. I have booted my computer up three times and my problem appears to be gone! Thanks for the help.

[Reply or follow-up to this message]

This is all very odd. Ask toolbar isn't even loaded at boot time - only when you open the internet browser - so I can't see why that should have anything to do with it. The PC should not be rebooting sometimes and not all the time. That particular behaviour sounds more like a hardware fault such as bad RAM (memory) or the CPU overheating or something like that. Further, you say that you found the file in two locations, but not where you should have looked for it straightaway, namely the c:\windows\system32\drivers folder as it appears in the boot log. It may be a hidden file there in that folder. Please post up a new ntbtlog.txt. Thanks. Spexx.

[Reply or follow-up to this message]

That is strange. I have my hidden files turned on so I can see them. css-dvp.sys is not there. You may have something with the overheating. I recently moved my computer from one room to another and there was a circular burn mark under the cpu on the rug. This time I put it up off the rug but still gets hot in here sometimes. I'll do another boot log and send.

[Reply or follow-up to this message]

Oops. Laptops should never be laid on a rug or carpet. The bright spark who designed the laptop probably decided that putting crucial air vents on the bottom was the right place for them. It is vital that air vents are kept clear, free of dust and fluff etc. Laptop overheating is very common. Cheers. Spexx.

[Reply or follow-up to this message]

css-dvp.sys is still in ntbtlog.txt!  I wonder why.  I did a search of the c and 
d drives and it only shows as being in c:\RECYCLER in each twice.

 Service Pack 2 7 23 2008 15:59:32.500
Loaded driver \WINDOWS\system32\ntkrnlpa.exe
Loaded driver \WINDOWS\system32\hal.dll
Loaded driver \WINDOWS\system32\KDCOM.DLL
Loaded driver \WINDOWS\system32\BOOTVID.dll
Loaded driver ACPI.sys
Loaded driver \WINDOWS\System32\DRIVERS\WMILIB.SYS
Loaded driver pci.sys
Loaded driver isapnp.sys
Loaded driver pciide.sys
Loaded driver \WINDOWS\System32\DRIVERS\PCIIDEX.SYS
Loaded driver MountMgr.sys
Loaded driver ftdisk.sys
Loaded driver PartMgr.sys
Loaded driver nvraid.sys
Loaded driver \WINDOWS\System32\DRIVERS\CLASSPNP.SYS
Loaded driver VolSnap.sys
Loaded driver atapi.sys
Loaded driver nvatabus.sys
Loaded driver disk.sys
Loaded driver fltmgr.sys
Loaded driver sr.sys
Loaded driver PxHelp20.sys
Loaded driver KSecDD.sys
Loaded driver Ntfs.sys
Loaded driver inspect.sys
Loaded driver \WINDOWS\System32\DRIVERS\NDIS.SYS
Loaded driver \WINDOWS\System32\DRIVERS\TDI.SYS
Loaded driver nv_agp.sys
Loaded driver Mup.sys
Loaded driver \SystemRoot\System32\DRIVERS\fdc.sys
Loaded driver \SystemRoot\System32\DRIVERS\parport.sys
Loaded driver \SystemRoot\System32\DRIVERS\gameenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\i8042prt.sys
Loaded driver \SystemRoot\System32\DRIVERS\kbdclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\mouclass.sys
Loaded driver \SystemRoot\System32\DRIVERS\serial.sys
Loaded driver \SystemRoot\System32\DRIVERS\serenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbohci.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbehci.sys
Loaded driver \SystemRoot\System32\DRIVERS\nvnetbus.sys
Loaded driver \SystemRoot\system32\drivers\ALCXWDM.SYS
Loaded driver \SystemRoot\System32\DRIVERS\imapi.sys
Loaded driver \SystemRoot\System32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\System32\DRIVERS\redbook.sys
Loaded driver \SystemRoot\System32\Drivers\GEARAspiWDM.sys
Loaded driver \SystemRoot\System32\DRIVERS\Xgiv3m.sys
Loaded driver \SystemRoot\System32\DRIVERS\usbuhci.sys
Loaded driver \SystemRoot\System32\DRIVERS\smserial.sys
Loaded driver \SystemRoot\System32\Drivers\Modem.SYS
Loaded driver \SystemRoot\System32\DRIVERS\AmdK8.sys
Loaded driver \SystemRoot\System32\DRIVERS\audstub.sys
Loaded driver \SystemRoot\System32\DRIVERS\rasl2tp.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndistapi.sys
Loaded driver \SystemRoot\System32\DRIVERS\ndiswan.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspppoe.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspptp.sys
Loaded driver \SystemRoot\System32\DRIVERS\msgpc.sys
Loaded driver \SystemRoot\System32\DRIVERS\psched.sys
Loaded driver \SystemRoot\System32\DRIVERS\ptilink.sys
Loaded driver \SystemRoot\System32\DRIVERS\raspti.sys
Loaded driver \SystemRoot\System32\DRIVERS\termdd.sys
Loaded driver \SystemRoot\System32\DRIVERS\swenum.sys
Loaded driver \SystemRoot\System32\DRIVERS\update.sys
Loaded driver \SystemRoot\System32\DRIVERS\mssmbios.sys
Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS
Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS
Loaded driver \SystemRoot\System32\DRIVERS\usbhub.sys
Loaded driver \SystemRoot\system32\drivers\MODEMCSA.sys
Loaded driver \SystemRoot\System32\DRIVERS\NVENETFD.sys
Loaded driver \SystemRoot\System32\DRIVERS\flpydisk.sys
Did not load driver \SystemRoot\System32\Drivers\lbrtfdc.SYS
Did not load driver \SystemRoot\System32\Drivers\Sfloppy.SYS
Did not load driver \SystemRoot\System32\Drivers\i2omgmt.SYS
Loaded driver \SystemRoot\System32\DRIVERS\cmdguard.sys
Did not load driver \SystemRoot\System32\Drivers\Changer.SYS
Did not load driver \SystemRoot\System32\Drivers\Cdaudio.SYS
Loaded driver \SystemRoot\System32\Drivers\Fs_Rec.SYS
Loaded driver \SystemRoot\System32\Drivers\Null.SYS
Loaded driver \SystemRoot\System32\drivers\vga.sys
Loaded driver \SystemRoot\System32\Drivers\mnmdd.SYS
Loaded driver \SystemRoot\System32\DRIVERS\RDPCDD.sys
Loaded driver \SystemRoot\System32\Drivers\Msfs.SYS
Loaded driver \SystemRoot\System32\Drivers\Npfs.SYS
Loaded driver \SystemRoot\System32\DRIVERS\rasacd.sys
Loaded driver \SystemRoot\System32\DRIVERS\ipsec.sys
Loaded driver \SystemRoot\System32\DRIVERS\tcpip.sys
Loaded driver \SystemRoot\system32\DRIVERS\USBSTOR.SYS
Loaded driver \SystemRoot\System32\DRIVERS\cmdhlp.sys
Loaded driver \SystemRoot\System32\DRIVERS\ipnat.sys
Loaded driver \SystemRoot\System32\Drivers\aswTdi.SYS
Loaded driver \SystemRoot\System32\DRIVERS\netbt.sys
Loaded driver \SystemRoot\System32\drivers\afd.sys
Loaded driver \SystemRoot\System32\DRIVERS\netbios.sys
Did not load driver \SystemRoot\System32\DRIVERS\processr.sys
Did not load driver \SystemRoot\System32\Drivers\PCIDump.SYS
Loaded driver \SystemRoot\System32\DRIVERS\rdbss.sys
Loaded driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\System32\DRIVERS\wanarp.sys
Loaded driver \SystemRoot\System32\Drivers\Fips.SYS
Loaded driver \SystemRoot\System32\Drivers\aswSP.SYS
Loaded driver \SystemRoot\System32\Drivers\Aavmker4.SYS
Loaded driver \SystemRoot\System32\Drivers\Cdfs.SYS
Loaded driver \SystemRoot\system32\DRIVERS\aswFsBlk.sys
Loaded driver \SystemRoot\System32\Drivers\aswMon2.SYS
Did not load driver \SystemRoot\System32\DRIVERS\rdbss.sys
Did not load driver \SystemRoot\System32\DRIVERS\mrxsmb.sys
Loaded driver \SystemRoot\system32\drivers\wdmaud.sys
Loaded driver \SystemRoot\system32\drivers\sysaudio.sys
Loaded driver \SystemRoot\system32\drivers\splitter.sys
Loaded driver \SystemRoot\system32\drivers\aec.sys
Loaded driver \SystemRoot\system32\drivers\swmidi.sys
Loaded driver \SystemRoot\system32\drivers\DMusic.sys
Loaded driver \SystemRoot\system32\drivers\kmixer.sys
Loaded driver \SystemRoot\system32\drivers\drmkaud.sys
Loaded driver \SystemRoot\System32\Drivers\ParVdm.SYS
Did not load driver \SystemRoot\system32\DRIVERS\css-dvp.sys
Loaded driver \SystemRoot\System32\Drivers\HTTP.sys
Loaded driver \SystemRoot\System32\DRIVERS\srv.sys
Did not load driver \SystemRoot\System32\DRIVERS\ipnat.sys
Loaded driver \SystemRoot\System32\Drivers\aswRdr.SYS
Loaded driver \SystemRoot\system32\drivers\kmixer.sys

[Reply or follow-up to this message]

This is not a laptop. It's in a big case.

[Reply or follow-up to this message]

Yep I figured it would be! We need to know which drive c: or d: is the systemdrive urgently. I explained a little bit more about the "set" command on the other thread. Let's keep it all on here from now on though. Cheers. Spexx.

[Reply or follow-up to this message]

Oh right - there was me leaping to conclusions again :-) I suspect the "burn mark" may just be a collection of dust, but it does indicate that the machine has been there a while and may have collected a lot of dust and fluff inside - it is an unpleasant task cleaning out a PC and a paint brush + vacuum cleaner are the tools needed for the job. If the cooling fan on the CPU in particular is clogged up, this will cause overheating and odd behaviour from the PC. Cheers. Spexx.

[Reply or follow-up to this message]

Okay, here's what I put on the other thread: What am I supposed to be looking for in cmd set? I'll keep it open. Everything in there refers to c: and I don't see d: at all. Something bothering though...it says OS-Windows_NT. I have the unopened Windows XP Home I bought that the guy said he used his disk but my registration number. What is Windows NT?

[Reply or follow-up to this message]

It's got a glass side where I can see in the whole thing. It looked okay to me. The front circular part where air is expelled I think is cleaned off but inside the screen it does look dusty. I'll have to figure out how to get in there and clean it. Also I smoke. One thing it was doing before I moved it here was the start button wouldn't work. I kept unplugging the computer from the wall and trying again and again until it would start. In here I don't have that problem so figured it was a loose cord that got fixed when I moved it.

[Reply or follow-up to this message]

michele,

Did you remember to disable System Restore? If not, this problem will return if you 
try to Restore the System.
 
When all is fixed you can turn System Restore back on and create a restore Point 
for future use.

If you are no longer using anything in the Authentium/Antivirus folder you have three 
choices. Rename the folder/Move the folder to another Directory or Delete the Folder 
and leave it sit in the Recycle Bin for at least a week.

If it proves you need something in the folder you can restore the Name, move the 
folder back to it's current location or restore it from the Recycle bin.

Which ever you choose, if there is no usage of the files or problems associated with 
changing name or location, within the week, go ahead and delete the folder.

I would empty the Recycle Bin now to get rid of the file you deleted, and based on 
the Link below I would also delete css-dvp.sys from C:windows\System32. On second 
thought delete the Authentium\Antivirus folder as well.

http://www.file.net/process/css-dvp.sys.html

Thr Start/Restart is most likely a temperature problem, loose connection or maybe 
a faulty Power Supply.

I'd start with cleaning the inside of the case, make sure all wire connections are 
secure and Pull, clean and reseat the RAM modules.

Post back here if problems. 

BW



__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Wednesday, July 23, 2008 at 12:15 pm, michele2007 wrote:

>PROBLEM SOLVED, I HOPE:  I deleted css-dvp.sys in Safe Mode.  There were two of 
them. 

> One in Windows\System 32 and one in c:\Program Files\Common Files\Authentium\AntiVirus. 

> This must have gotten there with one of my many free registry scan downloads.  
I 

>wonder if it would be okay to delete this whole Authentium folder?  Anyway, it didn't 

>fix the problem of my computer rebooting a few times each time I turn it on.  So 

>I did what the Microsoft response to sending my error report said.  I went to Add 

>or Remove Programs, sorted it by Date Last Used, selected Show updates and looked 

>at the Last Used On dates to see recent installations.  There was a program called 

>Ask Toolbar so I deleted that.  I have booted my computer up three times and my 
problem 

>appears to be gone!  Thanks for the help.
 

[Reply or follow-up to this message]

You said a lot here I had to research. I had already deleted the two locations of css-dvp.sys but after running boot logging in safe mode it still shows up as not loading. I found the two in my recycle bin and emptied it. Then I created a new restore point because I had not previously disabled restore before I deleted this file. I shouldn't have to go back to go back to a more previous restore point. I renamed the Authentium folder and will watch to see if that creates any new problems. I cleaned out the inside of the computer, checked connections as much as I could tell what to check and relocated the computer where it had more air circulation. Two times now and no boot problem. As for pull, clean and reset the RAM modules, I have no idea what that is and will wait and see if problem returns. Thanks for your help.

[Reply or follow-up to this message]

Michele,

You're welcome.Good to hear you're making progress.

Maybe I wasn't clear about System restore. You MUST disable System Restore to rid 
the Computer of any and ALL existing Restore Points. 

System Restore contains copies of the C:\ windows\System32 folder, as it was, before 
you deleted anything. 

Leave System Restore disabled untill you are no longer having problems and all the 
files/Folders associated with this problem have been deleted, and the Recycle Bin 
is empty.

Then, and only then, Re-enable System Restore and create a new Restore Point.

The Driver Not Loaded in Bootlog simply indicates there is a left over Registry entry 
for css-dvp.sys. The Driver could not load because you deleted it from Windows\ System\32. 
Not worth worrying about, at this point.

Sounds like it's time to sit back and see if the problems are resolved.

BW



__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Wednesday, July 23, 2008 at 10:47 pm, michele2007 wrote:

>You said a lot here I had to research.  I had already deleted the two locations 
of 

>css-dvp.sys but after running boot logging in safe mode it still shows up as not 

>loading.  I found the two in my recycle bin and emptied it.  Then I created a new 

>restore point because I had not previously disabled restore before I deleted this 

>file.  I shouldn't have to go back to go back to a more previous restore point. 
 

>

>I renamed the Authentium folder and will watch to see if that creates any new problems.

>

>I cleaned out the inside of the computer, checked connections as much as I could 

>tell what to check and relocated the computer where it had more air circulation. 

> Two times now and no boot problem.

>

>As for pull, clean and reset the RAM modules, I have no idea what that is and will 

>wait and see if problem returns.  

>

>Thanks for your help. 

[Reply or follow-up to this message]

Well I had so many restore points, up to 3 a day and I have never cleared any for the life of the computer, and after reading that windows creates one about every day and they hog space, I cleared them because my computer was booting up nice the last 5 times. I disabled restore points, enabled restore points, gained 2 gigs disk space, and created a new restore point. Then I restarted computer and it was shaky whether it would boot up completely, flickering, flickering, restarted twice and here I am. So I'm back to square one. Any ideas? I wonder if memory may have something to do with it. I know when this problem first started something I read directed me to change my virtual memory settings and then it worked better right away for a while. BTW, I have restore points disabled now.

[Reply or follow-up to this message]

Just to recap on what stage we are at. Does that pesky css-dvp.sys file still show up as being loaded in the bootlog, or has that been eliminated now? I have a concern about possible long-term hardware damage due to prolonged overheating too. Cheers. Spexx.

[Reply or follow-up to this message]

Yes css-dvp.sys is still there not loading. However, just ran a new boot log and this is the only difference: Loaded driver \SystemRoot\System32\Drivers\NDProxy.SYS Did not load driver \SystemRoot\System32\Drivers\NDProxy.SYS Before it just showed it as Did not load. I have seen this problem all over the place with people who get a blue error screen but haven't found any answers yet.

[Reply or follow-up to this message]

Never mind. my bootlog has always shown NDProxy.sys as loading then not loading. I'm going to reboot now to get out of boot logging. Hope I'll be back.

[Reply or follow-up to this message]

michele,

How long has it been since you've run Chekdsk or Defrag? After removing 2GB of files, 
it might be to your advantage to Defrag the HDD and run Chekdsk.

Also will give you a break while the processes run.

Virtual Memory is just HDD space used to augment the Ram. VM is best handled by the 
operating System, suggest you undo changes made. 

Deleting the Restore points should not have caused any instability. The files are 
basically static unless you elect to Restore the System via System Restore.

If you are getting any error messages when your computer restarts please post them 
here exactly as seen on screen.

I don't think you are back to square one at all. You obviously had more than one 
problem. One obviously software related, now it seems like the hardware is the focus.

BTW, could you post some info on your System? Make, model #,Processor type and Speed, 
RAM in mb (128-256?) Size of HDD in GB?. Also, is your OS on a M$ WindowsXP CD or 
a Manufacturer's Restore CD/CD's?

Don't give up, doing this Via a Forum is never easy unless the problems are easy. 

BW





__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Thursday, July 24, 2008 at 9:11 am, michele2007 wrote:

>Well I had so many restore points, up to 3 a day and I have never cleared any for 

>the life of the computer, and after reading that windows creates one about every 

>day and they hog space, I cleared them because my computer was booting up nice the 

>last 5 times.  I disabled restore points, enabled restore points, gained 2 gigs 
disk 

>space, and created a new restore point. Then I restarted computer and it was shaky 

>whether it would boot up completely, flickering, flickering, restarted twice and 

>here I am.  So I'm back to square one.  Any ideas?  I wonder if memory may have 
something 

>to do with it.  I know when this problem first started something I read directed 

>me to change my virtual memory settings and then it worked better right away for 

>a while.  BTW, I have restore points disabled now. 

[Reply or follow-up to this message]

Yep. It is a "poisson rouge". That pesky file has gone thank goodness so it is no longer an issue. I still think we have a hardware fault lurking, judging by the symptoms. A good clean-up was a good thing to do but maybe something is still amiss. I would try running a memory diagnostic on the system - this one from Microsoft is just the ticket. Read the instructions on how to create a bootable disk and give it a go. If you don't mind opening up the machine, re-seating the memory modules can often work wonders too. Cheers. Spexx.

[Reply or follow-up to this message]

My disk drive is giving me trouble. When I was recording to it, it would fail half way through the disk. Then I accidentally deleted Nero and couldn't get it back and tried using some Windows way to write to a disk and that worked even less. So I don't think I can make a disk. Also, once I tried to make a boot disk CD but that didn't work for some reason and that was when the CD was working properly. All I have is 6 a: drive 1.44 disks I made once that may or may not work. Do you have any howto link on reseating memory modules? I don't even know what they look like.

[Reply or follow-up to this message]

A floppy diskette will do nicely. The memory modules are easy to spot. They are like long thin slices that stick out at right angles to the main board. They are located in long thin sockets with little levers at each end. Operating the levers by pushing out and down will release the memory module, while pressing the module firmly back into the socket will automatically close the levers too. Be careful about static electricity while handling memory modules - always keep one hand holding bare metal on the computer chassis to ensure that your body is grounded. If you are not confident about doing that, see if you can find someone good with electronics to do it for you! It should only take a second or two. Cheers. Spexx.

[Reply or follow-up to this message]

I looked inside the computer thru the glass side and reseating the memory modules, 
whichever board they are on, would be something I don't want to attempt.  I'm going 
to have to take computer to a shop when I can afford it.  Meanwhile, the other day 
I ran this advanced system information - error log and it was 44 pages and started 
with July 14, 2008 and there are 3 errors listed over and over.  See if any of these 
3 will shed any light:

Source: nvatabus   Device slot returned an invalid status value.  See data for detailed 
information.

Source: nvatabus  The computer is configured as a member of a workshop, not as a 
member of a domain.  The Netlogon service does not need to run in this configuration.

and this is the one that keeps getting the error screen to send to Microsoft:
Source:  nvatabus  Error code 1000000a, parameter1 00004016, parameter2 00000002, 
parameter 3 00000000, parameter4 8050055c.

Also, I have a printout of My Computer Information - status and it says Memory (RAM) 
Detected 384 MB

I've also have a printout of my System Information report System Summary of 7/22/08 
that goes on and on.  Tells the status of everything. I stopped printing at page 
23 which is drivers.  It probably tells you in here, if a person knew what they are 
looking at, why the driver doesn't load.  And this is interesting about the css-dvp.sys 
file before I deleted it:  Name-css-dvp; Description-Dynamic Virus Protection; File-c:\Windows\System32\drivers\css-dvp.sys; 
Type-Kernel Driver; Started-Yes; Start Mode-Auto; State-Running; Status-OK; Error 
Control-Normal; Accept Pause-No; Accept Stop-Yes.   According to this it was running 
on 7-22.  Now it shows up as not running even though I deleted it.  But probably 
because of registry. 

[Reply or follow-up to this message]

I looked at pictures on the internet and mine looks different. Can't locate these modules. There is a fan blowing on what I think is the motherboard and in the way of touching anything in my opinion. I can't mess with it. I really need this computer to be working even the way it is. I moved to a very small town with only one computer repair place and don't know anyone that knows anything about computers.

[Reply or follow-up to this message]

I won't be giving up!

I did defrag the other day.  I could defrag again with the extra 2 gig but here's 
what I have left on my partitioned hard drive:  c:  used 14.9 GB  free 7.71 GB; d: 
used 59.5 GB free 12.7 GB.

I did a bunch of stuff with CCleaner and believe that's where a lot of my problems 
began.  One problem was things weren't loading right.  I roamed the internet and 
it was suggested to change Virtual Memory.  I think CCleaner changed what I originally 
had.  I went in there and it was set to recommended 574 MB.  I checked System Managed 
Size for both c and d drives and things worked okay.  Both drives now say:

Minimum allowed 2 MB
Recommended 574 MB
Currently allocated 1149 MB

So I'll leave it at that because things are loading properly.  Maybe that's a problem. 
 Maybe it has to use so much virtual memory because my memory is not working properly. 
??

Do you mean start, run, chkdsk?  If so I just did it and it said:

The type of file system is NTFS
Warning!  F parameter not specified
Running CHKDSK in read-only mode
File verification completed, so did indexes, so did security descriptors.  100% completed.

What can I type to find out what this computer has?

Thank you.

[Reply or follow-up to this message]

We were discussing my operating system a few posts back on this thread. I originally had Windows XP Professional which may or may not have been on my d drive. USP damaged my computer. Things on d were salvageable but not on c according to computer repair guy (now out of business). I bought Windows Home Edition and took it to him. When I got the computer back my disk is unopened. He said he used his and used my registration number. So I have the unopened Windows Home Edition Verson 2002 disk. The other day it said my operating system was NT??? I have a Windows directory in c and d. Also have an NT directory in c. ??????????

[Reply or follow-up to this message]

Here is the error message exactly that I get when the computer restarts at startup: Error signature BCCode: 1000000a BCP1: 00000016 BCP2: 00000002 BCP3: 00000000 BCP4: 8050055C OSVer: 5-1-2600 SP:2_0 Product 768:1 I also have automatic updates turned off permanently because it kept re-downloading Microsoft Software Distribution Service 3.0. (All this is discussed in a previous thread). I had gone back and downloaded a few more files numerous months ago but just the other day I went there to see and it would not work. (another problem amongst the many)

[Reply or follow-up to this message]

MY COMPUTER: start, help and support, My comuter, View general system information about this computer: Operating System: System Model: K8Upgrade-NF3; BIOS Version: American Megatrends Inc L1.21; Version 5.1.2600; Service Pack: 2.0; Location: c:\Windows; PID: long number-ask if needed; Hot Fix: KB946026; Memory (RAM): 384MB; PROCESSOR: AMD Sempron (tm) Processor 2800+; Version: x86 Family 15 Model 44 Steppping 2; Speed 1607 MHZ; GENERAL: Connection: workstation (standalone); Local Disk: 74.52 GB Used 54.04 Free 20.48 (some on c: and some on d:); System Software: MS Windows XP Home Edition created 1-25-06; BIOS created 9-26-05. I use Avast browser because was getting viruses using Internet Explorer and kept getting hijacked (changing my default screen).

[Reply or follow-up to this message]

michele,

I just realized that you are working two threads on This forum, as well as searching 
for solutions on the Net.

I my humble opinion you are going in too many directions, at the same time, to ever 
get you problems resolved.

I'm trying to approach this from your skill level, but the other suggestions your 
being given are more Tech level. Consequently, the answers you are giving  me do 
not fit with my approach to the problems you've described.

Therefore, I'm going to stop responding to this thread, as I believe the conflicting 
approaches are more confusing you rather than helping you.

I suggest you go with one approach and cease using the Internet while accepting support 
from any Forum Volunteer.

Too many Cooks spoil the Broth.

Good luck with your project. Gotta say, you ARE persistent, which is a GOOD thing. 
:)

Sincerely,

BW



__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Thursday, July 24, 2008 at 12:56 pm, michele2007 wrote:

>MY COMPUTER:  start, help and support, My comuter, View general system information 

>about this computer:

>Operating System:  System Model: K8Upgrade-NF3; BIOS Version: American Megatrends 

>Inc L1.21; Version 5.1.2600; Service Pack: 2.0; Location: c:\Windows; PID: long 
number-ask 

>if needed; Hot Fix: KB946026; Memory (RAM): 384MB; PROCESSOR: AMD Sempron (tm) Processor 

>2800+; Version: x86 Family 15 Model 44 Steppping 2; Speed 1607 MHZ; GENERAL: Connection: 

>workstation (standalone); Local Disk: 74.52 GB  Used 54.04  Free 20.48 (some on 
c: 

>and some on d:); System Software: MS Windows XP Home Edition created 1-25-06; BIOS 

>created 9-26-05.  I use Avast browser because was getting viruses using Internet 

>Explorer and kept getting hijacked (changing my default screen). 

[Reply or follow-up to this message]

Bob, ur right. I think the OP may not be in best state of mind right this minute either - I know that I've been drinking now too and so will check back tomorrow. The problem with the dodgy device driver has been put aside now and it just sems to be a hardware fault left to deal with, which was probably the original fault anyway. Cheers. Spexx.

[Reply or follow-up to this message]

I wish you wouldn't abanadon me. Let me explain. I was all over the net searching my problems and trying to resolve them before I ever started posting here. And a lot of them I straightened out. But when it started rebooting itself at startup, I posted here. I thought the problem was fixed so I posted another question I had on another thread...having windows on both drives...but that worked out okay I guess and I have abandoned that one. The only time I search the net now is like when you ask me something and I don't know how to do it. Like you asked me about chkdsk and what my computer specifications are, reseating the memory, etc. So I went to the net and found out where to find these out and replied to you. All those last posts of mine to you were things you asked me about that I didn't know how to get the information so I went and found out. Would you rather I ask you how to find something out if I don't know how rather than searching the net. Because that would be easier. Please don't leave. I'm stuck with the rebooting problem and have no way of solving it. Please (sad face)...I need your help.

[Reply or follow-up to this message]

I'm going to take a break the rest of today and hope Bob will reconsider. My head is killing me from too much computer screen.

[Reply or follow-up to this message]

Abandon you? No way! I just think we need to sleep on it and have clearer heads in the morning that's all. It wouldn't hurt to have someone else chip in with an idea too, cos we seem to be going round in circles now and my experience tells me that is a good time to leave it for a bit. Notwithstanding, I still think we are looking at a flaky hardware problem, possibly caused by chronic overheating. Cheers. Spexx.

[Reply or follow-up to this message]

I replied to Bob on that one. That he doesn't abandon me. At least I thought it was a reply to him. This is the only forum I have ever been able to figure out to use. I'm going to get off, have some drinks, start fresh tomorrow.

[Reply or follow-up to this message]

Don't know if I'm right or not, just found the double thread and different approaches 
confusing me, and I'm sure michele as well.

Might be different with the system in front of me but that's not possible.

Think she's trying too hard because of too much input. Not a productive situation.





__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Thursday, July 24, 2008 at 2:23 pm, Spexx wrote:

>Bob, ur right. I think the OP may not be in best state of mind right this minute 

>either - I know that I've been drinking now too and so will check back tomorrow. 

>The problem with the dodgy device driver has been put aside now and it just sems 

>to be a hardware fault left to deal with, which was probably the original fault 
anyway. 

>Cheers. Spexx. 

[Reply or follow-up to this message]

Howdy. Just had a long day, got back and came straight to this thread. Has anything been tried? I need to review the thread again I think. Cheers. Spexx.

[Reply or follow-up to this message]

No, nothing new. If anyone else is reading this, I WILL find the answer to this problem and post it here even if I have to take it to a shop (about 2 months). I hate that Spexx when I search the internet and find my problem in a forum and no one answers the person or the person never puts up the answer to the problem. I'm just doing other things and hoping the computer can hang on until I can take it to a repair shop or we find the answer. Hey, I took a lot of digital pictures of the inside of the case. If you could email me I would email you two of them and maybe you could tell me where the memory is and I could reseat.


On Friday, July 25, 2008 at 11:18 am, Spexx wrote:
>Howdy. Just had a long day, got back and came straight to this thread. Has anything
>been tried? I need to review the thread again I think. Cheers. Spexx.

[Reply or follow-up to this message]

Michele,

Still here. 

When I suggested chkdsk,I meant for you to run it from windows. Try this. Open My 
Computer. Right click on the C:\ Drive option, click on properties. Go first to Disk 
Cleanup and click on the Button. Delete anything found. Click cancell if all categories 
are 0kb.

Click on the Tools tab and the first option should be "Error Checking". click the 
Check Now tab. A box will pop up, check both options and click START. You will be 
informed that it can't run till you next restart your Computer. Where it asks if 
your want to schedule Error Checking select yes, click OK, close My Computer, then 
shut down and restart your computer.

Now get ready to take a break, this will take some time. When it's finished write 
down any messages in detail exactly as seen. If it stops for an error, write it down, 
then Proceed. If you get the option to save  a file of the scan select yes and write 
down the file name. you may not get this option.

Enough for now. Post back with results.

I can't supply info on the RAM, I do not know the Manufacturer and Model  of your 
system. Sounds like an HP but that doesn't do me any good.

BW






__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Friday, July 25, 2008 at 3:29 pm, michele2007 wrote:

>No, nothing new.  If anyone else is reading this, I WILL find the answer to this 

>problem and post it here even if I have to take it to a shop (about 2 months).  
I 

>hate that Spexx when I search the internet and find my problem in a forum and no 

>one answers the person or the person never puts up the answer to the problem.  I'm 

>just doing other things and hoping the computer can hang on until I can take it 
to 

>a repair shop or we find the answer.  Hey, I took a lot of digital pictures of the 

>inside of the case.  If you could email me I would email you two of them and maybe 

>you could tell me where the memory is and I could reseat.

>

>

> 

[Reply or follow-up to this message]

Bob, thanks for coming back to me. A couple things before I do the chkdsk and I will wait for your answers. 1) I have the system restore enabled and I should disable it right? 2) Should I do the defrag first since I gained 2 gigs? 3) I don't have it rebooting at the error point anymore because I discovered I could turn off "Automatically restart" at My Computer, Properties, Advanced tab, Settings button under "Startup and Recovery", uncheck "Automatically restart". Should I check that box back? 4) Yesterday the power-on button would not work. I unplugged the computer from the wall and repluged and it worked. This had been happened to me for about a month a week ago but not since I moved it to this new room. 5) Originally my son-in-law built this computer and can't find the sheet saying what I have but when it got damaged a few years ago the shop bill says: Motherboard ASRock NVF3-250, AMD Sempron 64 HT CUP & Fan Kit (new), HP CD-RW (used), AeroCool Case w/Power supply. I also took lots of close-up digital photos of the inside when I was in there cleaning it the other day and on the pictures I see these things: ASRock AGP 8 x SATA ATA 133 USB 2.0; 686 AMIBIOS 1999 TL94 8718; ID=00138F4771E2; Seagate Barracuda ATA IV Model ST380021A 80 GB. I'll wait for you reply on the first two questions and thanks for helping me. I'll just follow what you say to do if I can do it. (It really scares me though to turn off System Restore but if you want me to I will do it.)

[Reply or follow-up to this message]

Michele,

One of the results of turning off the  Restart on Error is, you should get to see 
the error code and have time to write it down. Are you getting an error? What is 
it? exactly. If it's starting up this way, that's good, we need to see the error 
messages.





On Defrag, it might help. If you do run it from the same Tools Tab as Error Check.

Find the Analyze button and if windows returns "You Do not need to defrag tis volume" 
then proceed Error Checking. 

I just ran Error Checker on my XP machine but did not get any report or file to view 
the results. Guess that means "Mines' perfect" YA right! well at least no errors.

I understand being nervous about turning off System Restore, most people are. However 
if you knew how many times S/R failed, causing further problems, or how limited it 
really is, maybe you'd worry less.

There is much better recovery software, FREE on the net. Lets get to that later.

When dealing with unknown problems that may, or may not be malware connected, the 
last thing you need is part of the system saving the exact Malware files you are 
trying to get rid of. 

If it's a virus/trojan in one of the backed up files, you'll just reinfect the system 
while trying to fix it. So it's up to you. The worst that could happen is having 
to reinstall WinXP.

Speaking of Backup. Have you backed up all your important files?

I will have to get back to you on the Ram issue need time to look up the MOBO. Now 
I see why is been so difficult, Custom Case & all, hence no Owners manual or MFG 
Web site to fall back on. GRRR.

So, from what you've told me, the errors are happening only at Start up. The Computer 
is not shutting Down on it's own. Is This Correct? 

A spontaneous shutdown is different than a restart during Boot up.

"Yesterday the power-on button would not work.  I unplugged the computer from the 
wall and repluged and it worked.  This had been happened to me for about a month 
a week ago but not since I moved it to this new room."

I do not follow the above statement, seems contradictory. can you clarify?

Is the Power Button working properly today? You are using a Surge Protector, right?

Do you see the box at the bottom of the Posting screen wher it says "check this box 
to preserve your Spacing". Please, put a check in the box to make it easier for me 
to read your messages. THX

Gotta go for now need to get my Maintenance work done.

Until next time.

BW





__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Saturday, July 26, 2008 at 3:26 pm, michele2007 wrote:

>Bob, thanks for coming back to me.  A couple things before I do the chkdsk and I 

>will wait for your answers.  1)  I have the system restore enabled and I should 
disable 

>it right?  2)  Should I do the defrag first since I gained 2 gigs? 3) I don't have 

>it rebooting at the error point anymore because I discovered I could turn off "Automatically 

>restart" at My Computer, Properties, Advanced tab, Settings button under "Startup 

>and Recovery", uncheck "Automatically restart".  Should I check that box back? 4) 

>Yesterday the power-on button would not work.  I unplugged the computer from the 

>wall and repluged and it worked.  This had been happened to me for about a month 

>a week ago but not since I moved it to this new room.  5) Originally my son-in-law 

>built this computer and can't find the sheet saying what I have but when it got 
damaged 

>a few years ago the shop bill says:  Motherboard ASRock NVF3-250, AMD Sempron 64 

>HT CUP & Fan Kit (new), HP CD-RW (used), AeroCool Case w/Power supply.  I also took 

>lots of close-up digital photos of the inside when I was in there cleaning it the 

>other day and on the pictures I see these things:  ASRock AGP 8 x SATA ATA 133 USB 

>2.0; 686 AMIBIOS 1999 TL94 8718; ID=00138F4771E2; Seagate Barracuda ATA IV Model 

>ST380021A 80 GB.  I'll wait for you reply on the first two questions and thanks 
for 

>helping me.  I'll just follow what you say to do if I can do it.  (It really scares 

>me though to turn off System Restore but if you want me to I will do it.) 

[Reply or follow-up to this message]

Bob, I have been sent the event logs by PM and the machine is bug-checking 1000000a consistently. I'm too tired to do any more stuff right now but will be back. Cheers. Spexx.

[Reply or follow-up to this message]

Bob,

1)   I turned off System Restore.  Thanks for explaining why I should.

2)   I turned back on ‘Automatically restart’.  I have since turned off the computer 
four times and it did not automatically restart and I had no error screen.

3)   My error is always the same:  
Error signature BCCode: 1000000a
BCP1: 00000016 BCP2: 0000002 BCP3: 00000000 BCP4: 805055C
OSVer: 5-1-2600  SP:2_0 Product 768:1

The error screen shows after the computer restarts successfully.  The point where 
it automatically restarts is always after I logon and after the clock, volume, and 
modem icons appear in the tray but before the Avast icon appears in the tray.  (I 
have a logon screen because I had to set up a different account for my second iPod 
and I set up a Guest account.  I am the only one using this computer.)

My computer only restarts at startup and never shuts down on its own.  But I do lately 
get a lot of programs ‘not responding’ and I have to shut them down because they 
lock up.

4)   I did error checking and defrag like you said on c: and d: (which is just one 
partitioned hard drive).  Everything was fine with no errors, but I was unable to 
see the final screen with the totals because it didn’t stay on the screen long enough.

5)   About the power-on button.  I do have a surge protector but I have to start 
the computer using the power-on button on the case.  About 2 months ago my power-on 
button would not turn on the computer.  I would unplug the surge protector from the 
wall and then plug it back in.  Then the power-on button might work.  Sometimes I 
had to do this 4-5 times.  Last week I moved the computer to another room.  I disconnected 
all the cords from the back of the computer and reconnected them when I got to the 
new room.  My power-on switch worked for about 8 days (which was unusual), until 
yesterday when it wouldn’t work just one time.  So I unplugged the surge protector, 
and then plugged it back in the wall, and the power-on button worked.  But this blew 
my theory that the power-button problem was just because there was some loose cord 
in the back of the computer.

6)   Thanks for allowing me to check the box to keep my formatting.  It says "Don't 
use this option unless you really need it".  I always think it is needed in order 
to read these posts.

Thanks for helping, Bob.  What’s next?

[Reply or follow-up to this message]

Michelle,

Well, this is starting to make some sense, at least a few things can be ruled out.

Probably not temperature, at least now. Over Temp is usually random lock-up/shut 
down after the machine has been running for a while. 

If you've unchecked "Automatically restart on error" in the Start-up and Recovery 
settings menu and it still automatically restarts randomly like that, then it's usually 
a PSU going bad. If the Power Good signal (+5V to mobo) drops at all the effect is 
an immediate reset of the CPU.

The error message you posted looks like a memory problem, but based on the timing, 
during Boot-up, I'm beginning to suspect the  Video Card, which, not only has its 
own RAM but also uses  part of System Ram.

Also possible it's it's a bad Video Driver. I wasn't able to find much on you MotherBoard, 
was hoping for a picture, but that won't answer the Video Card issue. You could have 
Video built into the Motherboard or it could be an add-in Card. One of several different 
kinds.

I suspect you have an add-in Video Card because you said there was a Fan blocking 
you view of the RAM.

If you have either "EVEREST HOME EDITION or "SIW" installed, please run one of them 
to help Identify your Video Card.

You can download Everest Home edition, ver 2.0 here.

http://www.oldversion.com/download.php?idlong=b0e1140fe6e5a7bda6688b67229e3da2

Down load, install and Run Everest to see if we can ID your Video Card. You may also 
find links in Everest for updating Video Drivers.

I'll send my eMail address, could you send the pictures you took?

It' late, I'm whipped & this should keep you busy for a while. :)

BW



__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Saturday, July 26, 2008 at 9:40 pm, michele2007 wrote:

>Bob,

>

>1)   I turned off System Restore.  Thanks for explaining why I should.

>

>2)   I turned back on ‘Automatically restart’.  I have since turned off the computer 

>four times and it did not automatically restart and I had no error screen.

>

>3)   My error is always the same:  

>Error signature BCCode: 1000000a

>BCP1: 00000016 BCP2: 0000002 BCP3: 00000000 BCP4: 805055C

>OSVer: 5-1-2600  SP:2_0 Product 768:1

>

>The error screen shows after the computer restarts successfully.  The point where 

>it automatically restarts is always after I logon and after the clock, volume, and 

>modem icons appear in the tray but before the Avast icon appears in the tray.  (I 

>have a logon screen because I had to set up a different account for my second iPod 

>and I set up a Guest account.  I am the only one using this computer.)

>

>My computer only restarts at startup and never shuts down on its own.  But I do 
lately 

>get a lot of programs ‘not responding’ and I have to shut them down because they 

>lock up.

>

>4)   I did error checking and defrag like you said on c: and d: (which is just one 

>partitioned hard drive).  Everything was fine with no errors, but I was unable to 

>see the final screen with the totals because it didn’t stay on the screen long enough.

>

>5)   About the power-on button.  I do have a surge protector but I have to start 

>the computer using the power-on button on the case.  About 2 months ago my power-on 

>button would not turn on the computer.  I would unplug the surge protector from 
the 

>wall and then plug it back in.  Then the power-on button might work.  Sometimes 
I 

>had to do this 4-5 times.  Last week I moved the computer to another room.  I disconnected 

>all the cords from the back of the computer and reconnected them when I got to the 

>new room.  My power-on switch worked for about 8 days (which was unusual), until 

>yesterday when it wouldn’t work just one time.  So I unplugged the surge protector, 

>and then plugged it back in the wall, and the power-on button worked.  But this 
blew 

>my theory that the power-button problem was just because there was some loose cord 

>in the back of the computer.

>

>6)   Thanks for allowing me to check the box to keep my formatting.  It says "Don't 

>use this option unless you really need it".  I always think it is needed in order 

>to read these posts.

>

>Thanks for helping, Bob.  What’s next?

 

[Reply or follow-up to this message]

Bob, I have downloaded Everesthome and can email you the report.  Email me with your 
email.  Also can send picture of computer insides (I have about 15 pictures of close-ups 
but will send main overall picture.)

Thanks, Michele

[Reply or follow-up to this message]

Starting a new tree branch here for clarity. To summarize, the css-dvp.sys driver has been eliminated but the system is still crashing. Event logs show 10 errors from nvatabus - device slot returned an invalid status value - being logged at boot time, then after a few minutes the system crashes with a bugcheck 1000000a fairly consistently. This bugcheck is usually caused by a faulty device driver, or something closely related.

I had thought originally that the crashes were due to bad RAM or other hardware, but am no longer convinced of that because the crashing seems rather too consistent. Searching for information regarding the nvatabus errors showed that it is rare but not unknown. Nvatabus is a driver for SATA/IDE devices on Nvidia NForce chipsets. In every case that I found, updating this driver did not effect a cure! There were a number of cases where simply disconnecting the CD/DVD drive made the errors go away, which seems perfectly logical, plus the brand name Plextor kept cropping up. So now I wonder if disconnecting the CD/DVD drive from the IDE cable will have the same result in this case? Also I wonder if the CD/DVD drive is a Plextor? Michele, please try this out and then have another look at the event logs. Report back what you find. Cheers. Spexx.

[Reply or follow-up to this message]

Spexx,
I disconnected the CD ROM with the plug that has all the colored wires (not the wide 
one).  The Ntbtlog.txt shows a new line that was not there before:

Did not load driver \SystemRoot\System32\DRIVERS\cdrom.sys
Michele

[Reply or follow-up to this message]

That is exactly what I would have expected to find in the ntbtlog - it didn't load the device driver for the CD drive because it had been effectively disconnected. Pulling out the plug with the four coloured cables (power) was good, but pulling out the grey ribbon cable (data) would have been better, but we got away with it :-) The point is what do we get in the Event log now? Have the nvatabus errors stopped? Did the machine crash again, or stay up? What brand is the CD drive? Cheers. Spexx.

[Reply or follow-up to this message]

michele,

Whew! ( he wipes Brow) That was a lot of data. But I did find something of interest, 
at least worth checking out.

The best solution would be to run a memory Scan to not only ID the existing RAM, 
but also, find the Best memory solution. 

Go to the link below to Run Crucial's on-line Memory Scan. This Scan will assess 
you system and give you the info you need to resolve a slight mis-match in the 2 
RAM modules you are currently running.

http://www.crucial.com/promo/index.aspx?prog=uslp_base

I won't bore you with an explanation, but suffice it to say you have 1 Ram module 
that is not totally compatible with the other.

When the Crucial scan is finished you will have all the info you need to find and 
install Compatible RAM for your System.

I don't know if this will resolve all your problems, but the consensus is it's a 
Hardware problem, and since RAM is Hardware, and affects ALL your hardware, I believe 
you won't resolve all your problems till this is corrected.

From this scan you will get Part # & prices for RAM Modules that are Guaranteed to 
be compatible with your Motherboard. It will also show you how the Dimms needs to 
be installed in the Motherboard slots. Sorry, no, they're not all the same.

I havn't had time to view the Pics. If you've figured out how to acces the RAM, I 
would pull the Module in DIMM slot 1 and see if the problems change or go away.

Dimm slots are numbered 0, 1, 2, 3, on the Motherboard, making slot 1 the 2nd slot 
not the first. When you access the RAM slots, with 4 slots available, it kinda looks 
like this.

[0]---[1]---[2]---[3]
256  128      X       X   (X=no DIMM) 
 mb    mb
2 slots looks like this.

[0]---[1]
256   128
mb     mb

Unplug the Computer if you are going to pull the Modules. 

In either case pull the 128mb module. Don't worry, you may notice the system runs 
faster without the 128mb.

Run the scan & let me know what you find. 

BW




__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Sunday, July 27, 2008 at 12:01 am, michele2007 wrote:

>Bob, I have downloaded Everesthome and can email you the report.  Email me with 
your 

>email.  Also can send picture of computer insides (I have about 15 pictures of close-ups 

>but will send main overall picture.)

>

>Thanks, Michele
 

[Reply or follow-up to this message]

Bob, 
Let me get this right.  Should I go to that website and run the test with both modules 
in.  Then go back and run again after I have pulled the 128 MB one?

Too bad, I just now got done pulling both modules (and I have a picture of them out 
of the computer to prove it!) and cleaning everything with very fine paint brush. 
 Then put them back in and ran Everest and saved a report.  Both working.   I know 
the module on the right is the 128 MB (Rosewill Vdata) and the left is the 256 MB 
pq1.

Did notice fan on outside glass wall wasn't working so took side off and moved wires 
around and now it is working.  Would a short in that affect anything?
Michele

[Reply or follow-up to this message]

Yeah Bob you got it. There is a memory speed mismatch shown in the Everest log. Pulling the 128 Mb module out might make the machine stable, but it will struggle with just the 256 Mb left! I think this might be the root of it though. Cheers. Spexx.

[Reply or follow-up to this message]

Also, I would just like to report that since I turned back on "Automatically restart", 
the computer has never restarted and I turned it all the way off and turned back 
on about 7 times.  The error still shows up in the event log though.  Strange....

[Reply or follow-up to this message]

Michele.

It really doesn't matter, the point of the scan is to get the Part#, Price and guaranteed 
compatibility of replacement DIMMS to  correct the mismatch, and possible upgrade 
for better System performance. 256mb is adequate, barely, for your system.

With 2GB memory capacity you have lots of combinations that will work, 2- 1GB Dimms; 
1- 1GB Dimm; 2- 512GB DIMMs. etc. etc.

In any case you are better off with a matched Pair of Dimms, and NOW seems like a 
good time to solve some problems and Upgrade RAM at the same time

Yes they are both working, but can they work together properly, being somewhat different? 
NO!

The Fan was probably not a "SHORT", more like an "OPEN ", or itermittant circuit. 
If it were a SHORT, there, would be Burn marks on the contacts and probably an instant 
shutdown of the Computer, with possible loss of the Power Supply. 

If it's working now the Power Supply is most likely OK.

SCAN!

BW



__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Sunday, July 27, 2008 at 1:00 pm, michele2007 wrote:

>Bob, 

>Let me get this right.  Should I go to that website and run the test with both modules 

>in.  Then go back and run again after I have pulled the 128 MB one?

>

>Too bad, I just now got done pulling both modules (and I have a picture of them 
out 

>of the computer to prove it!) and cleaning everything with very fine paint brush. 

> Then put them back in and ran Everest and saved a report.  Both working.   I know 

>the module on the right is the 128 MB (Rosewill Vdata) and the left is the 256 MB 

>pq1.

>

>Did notice fan on outside glass wall wasn't working so took side off and moved wires 

>around and now it is working.  Would a short in that affect anything?

>Michele 

[Reply or follow-up to this message]

Michele,

I don't know what error you are refering to, since I have not seen the event Logs. 
And, actually, I'm not much interested in the LOG files, as long as there is an unresolved 
Hardware issue, especially where RAM is involved.

I fully expect to see error events in The Event Logs as long as there is a RAM mis-match. 
Like a Doctor treating the symptoms, not the Disease.

What YOU, The Operator of the System, see, Hear and report, from direct observation, 
is much more important, to me, than anything in any LOG file. Log files are just 
proof that there is a problem. I THINK WE ALREADY KNOW THAT, or you wouldn't be posting 
here.

Perfect example of working on Different levels. 

Let me know what you think after you run the Crucial Scan.

BW





__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Sunday, July 27, 2008 at 1:11 pm, michele2007 wrote:

>Also, I would just like to report that since I turned back on "Automatically restart", 

>the computer has never restarted and I turned it all the way off and turned back 

>on about 7 times.  The error still shows up in the event log though.  Strange.... 

[Reply or follow-up to this message]

Bob,
Wow!  That is a great website.  If I get 1 GB this month can I put it to the right 
of the 256 MB?  Or does the first slot (0) have to be the largest RAM?

I took the 128 MB out but my Word doesn't work so good and everything is slower so 
I'll put that back in until I get 1 gig.  Then maybe next month I'll get the other 
1 gig.  I'm in heaven!  I didn't know it was that easy to upgrade RAM.

I want to thank you for all the time and effort you put in to solving this problem. 
 And just think....you do it all for free! We are all so lucky out here.

Is there a forum for cleaning out the registry?  And is there a forum for startup 
files?

Thanks so much,
Michele

[Reply or follow-up to this message]

Michele.

If it were me, I would install the 1GB Module in slot 0 and leave everything else 
out till you can get a matching 1GB Module. I seriously doubt that either the 256mb, 
or the 128mb DIMMS will be FULLY compatible with the 1GB. (SERIOUSLY)

Don't get greedy Girl, the 1st 1GB DIMM will give you more than twice the current 
Memory. You can always add it later, now that you have the Part# and cost.

AND you may, and probably will, find that the 2nd 1GB DIMM is overkill, unless you 
are running Memory intensive Applications. I didn't see anything installed on your 
System that indicates the need for that much RAM.

Run the 1st 1GB for a while to see if you really need #2. It is not uncommon for 
MORE memory to cause as many problems as not enough. More is NOT always better.

I also need to remind you that the RAM upgrade may not fix all your issues. It just 
gets rid of one obvious problem, but could reveal other issues. Not a Panacea, so 
don't expect too much.

I, personally, don't want to get into the Registry/startup issue at this time. I 
think you'd be better off waiting till you have Replaced the RAM and run you system 
for a while before opening that can of worms. Doing too much, too fast, usually leads 
to problems.

That's not to mention that his thread has become an unmanageable MONSTER.

Rather than focus on start up, I would look at the Programs you have installed to 
see if there are any that you do not use or need. 

If any fit the "do not use" category, get rid of them, probably the same for "do 
not need". I'm only talking about Software that you have installed but don't need/use. 

This alone should clear some of the CRAP in startup.

BTW, You're more than welcome for the assistance. I usually learn more than I give 
by doing this.

Gotta go & get caught up with things here. Let me know how the Memory upgrade goes.

BW.







__________________________________________________________

There's nothing to learn from someone who already agrees with you.




On Sunday, July 27, 2008 at 2:00 pm, michele2007 wrote:

>Bob,

>Wow!  That is a great website.  If I get 1 GB this month can I put it to the right 

>of the 256 MB?  Or does the first slot (0) have to be the largest RAM?

>

>I took the 128 MB out but my Word doesn't work so good and everything is slower 
so 

>I'll put that back in until I get 1 gig.  Then maybe next month I'll get the other 

>1 gig.  I'm in heaven!  I didn't know it was that easy to upgrade RAM.

>

>I want to thank you for all the time and effort you put in to solving this problem. 

> And just think....you do it all for free! We are all so lucky out here.

>

>Is there a forum for cleaning out the registry?  And is there a forum for startup 

>files?

>

>Thanks so much,

>Michele 

[Reply or follow-up to this message]

Bob,

Well it's worse now.  First it kept restarting 4 times in a row.  Then I got the 
famous BLUE SCREEN!  Mind you I only have the one memory module in the computer. 
 It said "A Problem has been detected and windows has been shut down to prevent damage 
to your computer, etc. etc." And showed the same error I always got with the other 
error screen.

So I started in Safe Mode like it told me.  Then I removed a lot of programs thinking 
I gotta get more memory:  Registry Medic; Everest; CCleaner; Belarc Advisor; Event 
Log Explorer; PdfEdit 995; Avast Antivirus; Comodo Firewall Pro; Comodo Safesurf.

When I rebooted I had no internet connection.  I need that!  So I did a restore that 
I had made after I removed the other memory module and all is back.

My question is this.  Do you see any program I removed that would take away my internet 
connection?

Because I think I'll just remove one program at a time and do a restore each time. 
 And I'll leave the Comodo and Avast.  Then I'll order the 1 gig memory module and 
see what happens after that.

What a day it's been.  

Michele

[Reply or follow-up to this message]

Hi Michele. I think Bob intended that you sort out the memory issue first and foremost, then worry about anything else after that. You may be trying to do too much at once now! It could have been the uninstallation of Comodo Firewall that "broke" your internet connection, but you certainly do not want to remove your firewall and antivirus solutions - they are essential, not surplus to requirements. I agree with Bob that the best way forward is to buy a 1 Gb RAM module and install that on its own, without any of your existing RAM modules alongside. Run with that and see what we have. Cheers. Spexx.

[Reply or follow-up to this message]

Yes, okay thanks.  

[Reply or follow-up to this message]

I'm been sitting here getting rid of all my errors and found your post here in a 
web search.  I unplugged the CD-ROM with the big cord and it got rid of the 10 errors 
NVATABUS.  Now I'm down to only two errors in the event log.  

But what does this mean.  That my CD-ROM is bad or that a driver is bad?  It was 
giving me trouble.

[Reply or follow-up to this message]

Aha! There was so much going on that I had almost forgotten about that. Good - the nvatabus errors have gone as I suspected they might - that CD drive (a HP if I remember rightly) is either bad or incompatible I think, but I will have to go back and re-affirm what I found first time around - I seem to remember something about a firmware flash upgrade. Has doing this stopped the machine from crashing too? There were System Error 1003 showing in the event log (bugcheck 1000000a) when those crashes happened. I'm going offline for a time now so no rush. Cheers. Spexx.

[Reply or follow-up to this message]

No I'm afraid 0x000000a error is still with us.  I'm hoping more memory might solve 
it.  All I have left is the one that is a Windows fix problem:  NETLOGON: This computer 
is configured as a member of a workgroup, not as a member of a domain. The Netlogon 
service does not need to run in this configuration; and 2) The Dynamic Virus Protection 
service failed to start due to the following error: The system cannot find the file 
specified.  And that is the css-dvp deleted file.  Comodo has latched onto it in 
the registry and won't let me delete it in there.  

[Reply or follow-up to this message]

I think one or all of these are the problem:

Loaded driver \SystemRoot\System32\DRIVERS\imapi.sys
Loaded driver \SystemRoot\System32\DRIVERS\cdrom.sys
Loaded driver \SystemRoot\System32\DRIVERS\redbook.sys

They used to be loaded and now they are not loaded.  When I deleted reference to 
Registry Medic (which was not even on my computer anymore) one or all of these quit 
loading.  Registry Medic was associated with imapi.sys.  No restarting errors after 
9 reboots.  I'll give it a few days and then plug back in my CD and see which ones 
load and if I have any blue screen or restarting errors of 0x0000000a.   

(happy) Michele

[Reply or follow-up to this message]

Those three cdrom.sys, imapi,sys and redbook.sys are all to do with the CD drive and will start loading again if/when the CD is reconnected. To stop the Netlogon error appearing in the event log, run services.msc and set the Netlogon service startup type to "Manual" or "Disabled" - it is set to "Automatic" at present but is not required in your configuration. Cheers. Spexx.

[Reply or follow-up to this message]

But doesn't seeing those errors tell you that you have a problem?  Or a leftover 
file or registry error?

[Reply or follow-up to this message]

Well yes and no. Apart from the machine crashes still to be addressed by trying new memory, the only real leftover is the entry for css-dvp, the rest of it I have explained already. None of these things really matter since the system is taking care of itself, just logging these events as errors. You said that the registry entry for css-dvp cannot be deleted so you can either struggle to get rid of it (it is probably a matter of permissions on the key) or just live with it - it has been disabled by deleting the file so it is one of those "don't care" situations. None of these things are doing any harm, they just look untidy in the event log. I have quite a few untidy things in my event log for a number of reasons, but I know why they are there and it doesn't bother me :-) I will do some more research on that HP CD drive for you in due course. Cheers. Spexx.

[Reply or follow-up to this message]

I finally got rid of the css-dvp.sys showing up in the bootlog.  I used Autoruns. 
 That seems to go around Comodo.  Comodo seems to latch on to everything and put 
it in the registry under Legacy and won't let you delete it in the registry.  But 
Autoruns outsmarts Comodo I guess.  I also deleted other Files Not Found in Autoruns 
that showed up as Did Not Load in the bootlog:  lbrtfdc.sys, i2omgmt.sys, changer.sys, 
PCIdump.sys, and ipnat.sys.  (Now this ipnat.sys might have been a mistake because 
I see it mentioned around but I don't have any problems from deleting it.)  I ordered 
my 1 gig memory module.  

[Reply or follow-up to this message]

You found Autoruns! The beauty of that utility is that it does not delete anything - it just disables things one way or another - so if you have made a mistake it can undo the changes easily. I know that ipnat.sys is used by Windows Firewall and as you are using Comodo it should not be an issue. Cheers. Spexx.

[Reply or follow-up to this message]

That's nice to know Autoruns doesn't delete.  I'll have to learn more about Autoruns. 
 Also I was mistaken about Legacy being Comodo because I see from my installed hardware 
list of before I installed Comodo, Legacy is in there (whatever it is).

[Reply or follow-up to this message]

Well installed the new 1 gig memory.  Started up fast.  I haven't had a reboot error 
for a while.  Then I plugged back in the CD-ROM and it just kept rebooting.  Then 
I unpluged the CD-ROM and it only rebooted twice.  Now I'm looking for the file I 
had downloaded that would update CD-ROM driver to an HP driver.  Will let you know. 
 Must be the driver or the CD-ROM that is bad.  Although funny it rebooted twice 
after I unplugged the CD-ROM (with the big plug end).

[Reply or follow-up to this message]

Remember the Microsoft update/hotfix for the memory management issue that we discussed by PM. Has that been applied also? Cheers. Spexx.

[Reply or follow-up to this message]

Okay, I'll go install KB929338 because DriverDetection.exe is not working out.  I'm 
not sure if it did anything.  I don't know if it is looking at drivers I already 
have and replacing them or can't find the CD-ROM because I have it unplugged.

[Reply or follow-up to this message]

I installed memory fix KB929338.  I find it interesting that it said:  "This is a 
reliability update. Install this update to resolve an issue in which you receive 
a stop 0x1a or stop 0x0a error message on a computer running Windows XP Service Pack 
2." 

It does list the error I have been having.  I rebooted and it did not reboot.  

What should I do next, plug back in my CD-ROM?

By the way, when I went to Windows Updates, it wouldn't check my computer until I 
let it install KB892130 Genuine Advantage Validation Tool.  I did a search of my 
computer for verclsid.exe and it is back in there as a hidden file.  That was the 
one I changed the extention to .old so Windows would never install anything I didn't 
want.  I was having a problem with that nasty Software Distribution Service 2 which 
I believe was installed with KB943055 so I removed it.  I'm going to start another 
thread on these 15 high priority updates (and 6 software updates) Windows says I 
need and ask if any of them are problems.  I haven't downloaded any updates for a 
long time.

[Reply or follow-up to this message]

Hi Michele. I think that as soon as you plug that CD drive back in, you are going to start getting those nvatabus errors again and the drive will not work, or behave strangely. I have done a fair bit of research on this and have isolated two causes: 1) if the HP CD drive is connected as a slave on the same IDE cable as a hard drive and 2) if the HP CD drive is connected as master on the same IDE cable as another CD drive. Therefore, my advice would be to connect the HP CD drive back up to the system on its own IDE cable, on the secondary IDE channel and set the drive as a slave device (master/slave jumper on the drive to the middle of the three possible settings). Try this configuration and let me know what you get. Also, has applying the memory management hotfix cured the STOP errors completely now with no repeat problem at all? Cheers. Spexx. PS ref those updates - bypass SP3!

[Reply or follow-up to this message]

This is all foreign to me.  How can I tell how it is set up now?  Would pictures 
help or is there some report or place I can look to see how it is set up?

[Reply or follow-up to this message]