DC .net is not cleaning well....

createcoms · Jul 12, 2008, 09:05 AM

Hi,

I just swapped my socket 939 nforce 4 motherboard for a socket AM2+ nforce 750a motherboard and dared to not reinstall windows (lazy me). Whilst I'm now there, I was disappointed to find I didn't have the assistance of DC .net - because despite selecting the Nforce Chipset cleaner it failed to scrub the system of the drivers and thus I was dealing with blue screens and missing files etc the works until I loaded the registry hive onto my laptop and manually combed the registry for "nvgts".

Now I am a registered .net user (createcoms@spamcop.net), and also if you need any more details (windows xp x64 edition here) simply ask and I shall deliver!

**Spike** · Jul 12, 2008, 05:40 PM

Hi,

do you still know what you removed? because with that info i can update my cleaning filter.

I think it is part of the sata raid driver. I have that in a seperate filter, but i removed that from the program, because people used that also and came with a not working windows. In your case you could have used those then. Will see if i can put those online in an installer and add a warning to them.

I hope you can remeber what you did or removed, because then i can check that.

createcoms · Jul 12, 2008, 08:41 PM

Sorry I don't have an exact log......like I said I hunted the registry for the nvgts64.sys file (which is the windows xp x64 SATA driver for nforce chipsets)

There were also some nv***** files in system32 which I deleted and also nvgts64.sys in the drivers folder.

So yes it would be good to put the sata driver in there but if you need to include a warning that's fair enough. It's probably a good idea to nuke all the 10DE entries (pci enumeration code which I often found keys for nvgts64 in)

cheers

-cc

Jul 12, 2008, 09:05 AM	#1
createcoms DriverHeaven Newbie Join Date: Mar 2008 Posts: 2 Rep Power: 0	DC .net is not cleaning well.... Hi, I just swapped my socket 939 nforce 4 motherboard for a socket AM2+ nforce 750a motherboard and dared to not reinstall windows (lazy me). Whilst I'm now there, I was disappointed to find I didn't have the assistance of DC .net - because despite selecting the Nforce Chipset cleaner it failed to scrub the system of the drivers and thus I was dealing with blue screens and missing files etc the works until I loaded the registry hive onto my laptop and manually combed the registry for "nvgts". Now I am a registered .net user (createcoms@spamcop.net), and also if you need any more details (windows xp x64 edition here) simply ask and I shall deliver!

Jul 12, 2008, 05:40 PM	#2
Spike Driver Cleaner Maker Join Date: Jul 2002 Location: Netherlands Posts: 2,085 Rep Power: 69 System Specs	Hi, do you still know what you removed? because with that info i can update my cleaning filter. I think it is part of the sata raid driver. I have that in a seperate filter, but i removed that from the program, because people used that also and came with a not working windows. In your case you could have used those then. Will see if i can put those online in an installer and add a warning to them. I hope you can remeber what you did or removed, because then i can check that. __________________

Jul 12, 2008, 08:41 PM	Thread Starter #3
createcoms DriverHeaven Newbie Join Date: Mar 2008 Posts: 2 Rep Power: 0	Sorry I don't have an exact log......like I said I hunted the registry for the nvgts64.sys file (which is the windows xp x64 SATA driver for nforce chipsets) There were also some nv***** files in system32 which I deleted and also nvgts64.sys in the drivers folder. So yes it would be good to put the sata driver in there but if you need to include a warning that's fair enough. It's probably a good idea to nuke all the 10DE entries (pci enumeration code which I often found keys for nvgts64 in) cheers -cc