My computer keeps getting very sluggish

Sorry, FDD + floppy disc.
You download the file, to your computer, and extract it to A: DRIVE----The floppy disc drive.

 

I don't use a download accelerator,but usually if you right click the program icon, it has an option to exit/close. But ,if it has not I would try uninstalling it, and reinstalling after the driver update.

 

FDD . . . I'm losing it in my old age.

I don't know if I have a Download Accelerator. I wanted to download the Nvidia driver update and a tip said that it should be turned off before I downloaded the driver. Where would I look for it if I have it? It's not listed in Add/Remove Programs nor in Services. A search showed that I have no program named Download Accelerator or accelerator. Would that more than likely say that I don't have one? I never know what Microsoft downloads in its updates. I do know what I download and install and I never installed it unless it was part of a program.

 

I have Download acccelerator v4.2 ...I download Nvid files all the time...
You shouldnt have any probs...

 

Thanks

 

Denise, is Damion still giving your problems? Have you tried leaning a sledgehammer on the computer? The hammer lets it know you are serious.

Sorry you are still having problems.

E

 

Ah, Fred . . . if you only knew. It's giving me a devil of a time!

Denise

 

On the mobo driver updates, it says that they're for GeForce 6100-M9. I have a TFORCE 6100-939. I backtracked from where the GeForce page and downloaded the TForce drivers:

- On-Board Audio
- Chipset
- On-Board VGA

Are they all that I need?

I downloaded the BIOS but I haven't installed it yet because I don't have a FDD (I catch on quick )

Can I install the drivers without first updating the BIOS?

Denise

 

Also, you listed

I found no driver updates for the TForce, only for the GeForce.


Denise

 

This thread is getting long . . .

For the processor update at the AMD Athlon™ 64/FX Processor Utilities and Updates site

http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html

I chose

Again, I downloaded it but I didn't install it.

Is this the right one and can this update also be installed before I update the BIOS too?

Denise

 

I found this page through a Google search

http://www.nvidia.com/object/winxp64_160.02.html

I couldn't find anything else for the XP Pro X64 version except for the Beta release.

Wadda ya think?

Denise

 

Sorry Denise, your drivers are on this page, for chipset etc;
If they are the ones you downloaded - o.k you can install them, before the Bios update.

http://www.biostar.com.tw/app/en-us/t-series/driver.php?S_ID=188

 

Again, your Bios update for the 939 is this one- if this is the one you downloade, that is good.

http://www.biostar.com.tw/app/en-us/t-series/bios.php?S_ID=188

 

Denise, not the Nvidia quodro driver, but this one
It's firmware for your system
http://www.nvidia.com/object/winxp64_93.71.html

If you cannot remember having a download accelerator, and cannot find it, you should forget it, as you probably have not got one.
Cadal says found no problems with it, but it is always best to follow instructions when installing any drivers.
I also recommend disabling antivirus, and firewalls, and shutting all running programs down when updating drivers, to avoid a corrupted install.
I would set a restore point before each driver update, - only install one at a time, and restart if /when directed - then you can recover easily if a problem occurs, and you should know which driver probably caused it.
Leave the Bios update until last, and read the instructions- write them down, as you will not be able to see the instructions, when booting with the floppy - it is possible that it will show some instructions as it flashes the Bios, but, it will not hurt to have it in writing, next to you.
As you know, or, by now are becoming aware, Updating your Bios is to be done strictly as the manufacturer instructs , to avoid the possibility of a failed installation.Generally, it will go like clockwork.
Thanks for popping in Fred - feel free to interpose, if you want to.

 

Denise, once you have installed the new chipset drivers, and nvidia drivers, you can go and get another free scan to check if there are any missing.:foolish

If not then :celebrate

 

That problem finding seagate tools..............
http://www.seagate.com/www/en-us/support/
Click on downloads,all the tools appear,In the most popular downloads, click the seatools (under disc wizard- which is also a good tool)

The seatools for dos might help you get over the problems you had with the windows version.
SeaTools for DOS
http://www.seagate.com/ww/v/index.j...toid=51e092db8a13d010VgnVCM100000dd04090aRCRD

 

Last night, I installed the same drivers as you just specified, but my computer crashed big time last night. When I woke up this afternoon, my computer was off except for a dark blue screen that said

None of the names of the drivers that I installed were named Driver_IRQL_NOT_LESS_OR-EQUAL


I installed

1. Nvidia - 160.02_quadro_winxp64

2. AMD Athlon 64/FX Processor Driver for Windows XP and Windows Server 2003 Version (x86 and X64 exe) 1.3.2.16

3. Biostar TForce 6100-939 Chipset, On-Board Audio, On-Board VGA

There was nothing at SeaTools at http://www.seagate.com/ww/v/index.js...00dd04090aRCRD that I could use except, maybe, SeaTools for DOS. I downloaded it and installed one version last week or the week before and it couldn't work. It needed JIT Debugger. I downloaded and installed JIT Debugger but it still wouldn't work so I uninstalled the two programs and did a System Restore point that I had made prior to installing the programs (a double whammy). Is SeaTools for DOS the same as the other one?


Before I installed the new drivers, I made a System Restore point.

The computer was running fast and seemed to have no problems, no hangups, no error messages. I was transferring a number of large files from one 500Gb ext hdd to another one when I went to bed and it was going very well. I noticed no unusal behavior and was I watching for it very closely because I installed the new drivers.


If I get the blue screen with the message again, can I do a System Restore to the restore point that I created prior to installing the new drivers or do I have to follow the directions that the blue screen showed?

Denise

 

Thanks backlogic . . . as always, you're terrific.

It was nice seeing Fred here again

I just went to the SeaTools for DOS website and downloaded the two files. I can't run them yet as I haven't received the FDD cable in the mail. As soon as it comes in, I'll install the floppy drive (hoping that the IDE port didn't get damaged when the previous one went up in smoke), and follow the instructions. Hopefully, I won't blow it up again either.

BTW, I was in a car accident yesterday. I'm fine but my car was damaged. If I were a superstitious person, I'd be waiting for the third bomb to hit.

Denise

 

Just to be on the safe side, I did a system restore to a restore point that I created on Saturday.

I downloaded the Nvidia Forceware file at the link you just gave me but I haven't installed it yet.

According to what you said

Do you think by installing the Nvidia - 160.02_quadro_winxp64 driver that this could have caused my computer to crash and give me the message that I mentioned earlier?

I just checked some of my components again. My mobo is TForce but my Display Adapters are GeForce 6100.

Denise

 

These are the ones that I installed.

This is the one that I downloaded, but haven't installed yet.




For the processor update at the AMD Athlon™ 64/FX Processor Utilities and Updates site

http://www.amd.com/us-en/Processors/...1_9706,00.html

I chose AMD Athlon™ 64/FX Processor Driver for Windows XP and Windows Server 2003 Version (x86 and x64 exe) 1.3.2.16


Since you didn't mention that the AMD Athlon 64/FX Processor Driver for Windows XP and Windows Server 2003 Version (x86 and X64 exe) 1.3.2.16 was the wrong one, I'm assuming that it's the right one.


So the only wrong one was the Nvidia . . . Am I correct?

Denise

 

I just installed

Nvidia - 93.71_forceware_winxp64_english_whql dated 112006.

Thanks so much for giving me the right one.

I'm going to give it a very good workout for a day and if all goes well, tomorrow I'll install one of the others. Which one would you suggest?

Patience is not one of my virtues so the waiting is gonna kill me.

 

I think the general consensus is to install the graphics, first, then chipset,and then any others.
A GOOD TIP- IF IT THEN RUNS NICELY, LEAVE THE BIOS UPDATE- SAVE IT FOR LATER.

Yes, Denise, I hoped to catch you before that nvidia quodro driver, sorry I was a bit late, - that wouldhave been the trouble, I am sure.I am up to my neck in a trojan, and virus locked up system(locked through Norton's inability to cope),:crap that has taken me three days to get working to get the information off, and still not perfectly clean- then I could not get it to format (hidden partition- and page file on hidden partition- that was a nasty), and finished up connecting it as a usb, though my handy little usb to IDE adaptor, and it still had a trojan!- but as soon as it connected my computer kicked that into eternity.Anyway, I have now formatted it, and am free again, for a little while.:celebrate
Just for your records
Sometimes, a driver tries sharing an IRQ, THAT wINDOWS DOES NOT LIKE IT TO, AND May have that one permanently assigned to a specific item.
There was a problem with a Microsoft update , too.
More explanation at
http://support.microsoft.com/kb/293077:D

This site is a very instructive, if you ever have the problem, again.rolleyes
http://www.vladd44.com/other/irq_error.php

 

You said " I chose AMD Athlon™ 64/FX Processor Driver for Windows XP and Windows Server 2003 Version (x86 and x64 exe) 1.3.2.16


Since you didn't mention that the AMD Athlon 64/FX Processor Driver for Windows XP and Windows Server 2003 Version (x86 and X64 exe) 1.3.2.16 was the wrong one, I'm assuming that it's the right one.


So the only wrong one was the Nvidia . . . Am I correct?" :wine

Yes, Denise, you chose right, And system Restore ! except the nvidia. (You could have uninstalled the nvidia driver, but , as you did not know, system restore was the best way to go.:dancer
I was hoping Fred might have been about, as I was tied up, - nice to bump into each other, as we go.:drink

 

The new Nvidia Forceware did very well overnight. I had several processes going, just to give it a good run and it's still running strong.

When I got up a few hours ago, I tried to install

AMD Athlon 64/FX Processor Driver for Windows XP and Windows Server 2003 Version (x86 and X64 exe) 1.3.2.16

I received a message to first uninstall the existing file "Athlon 64 Processor Driver". I went into Control Panel, Add/Remove Programs, and tried to uninstall it but it wouldn't uninstall. I received the attached message. I didn't have a problem uninstalling it the first time, when I installed the wrong driver, so maybe the System Restore wasn't such a great idea afterall.

 

Try - right click, My Computer, click manage, click devices double click the plus sign next to 'Computer', and it should show your processor- , click driver tab, click roll back driver.

 

I believe the roll back worked but I received no message either way. When I tried to install the new driver, I received the Microsoft messages that says "setup has encountered a problem and needs to close."

I rebooted and tried again and received the same message when I tried to uninstall the CPU driver.

Have I ever mentioned that I have a lot of problems with this computer? :cry

 

I just updated the driver using Microsoft's update, hoping that it would give the driver something it needs so that I could remove it. I rebooted and tried to remove it again, but I received the same error message, that "setup has encountered a problem and needs to close".

 

If what you are installing is the correct version and the executable itself is not corrupted, then there is a good chance that a leftover file or registry key could be causing the installation to bomb out.

I'd start with cleaning up all the temp folders the installer could be using, perhaps there are some leftovers in there that is causing the problem. Use either CCleaner or ATF-Cleaner to empty out all standard temp folders. Then if there was ever a folder created by the previous installation, delete it as well but generall drivers of this kind would probably drop a few .sys, .dll and .inf files in the Windows\System32 or Windows\System32\Drivers folder but for now I say skip on that. You would have to scan your system for the date of the original driver installation to spot all files created within Windows (and sub folders) then filter out the possible file types abd search for the ones that are related.

I would say you should download and install Autoruns, this is a great utility that not only helps you with the startup entries but also lets you see the installed 3rd party services and drivers (click on Options then check the 'Hide Microsoft entries' option then click refresh). If you see any any entries under HKLM\CurrentControlSet\Services that reads 'file doesn't exist' or 'File not found' delete those entries and reboot.
Also run a reputable registry cleaner like RegScrubXP which is effective yet not too aggressive, more something more aggresive you might want to try RegSeeker but make sure they create a new backup each time you run them.

Last but not least, I would kill all background services and processes that might conflict with the installation, such as AV scanners, Firewall, Printer monitoring software. If you also o/c'ed your system in anyway, it might be wise to reset things to default.

 

Hi Turcoloco,

Thanks for your help.

Since I have X64, I can't use CCleaner, PC onPoint or RegSeeker. Each program removes files that are needed by X64. I did that when I first installed X64 and had to reformat it 3 times for each of the 3 programs.
But I can run NewFiles to see which files were created recently and post the results here. Maybe someone can see what the culprit might be.



I few days ago, I installed

Nvidia - 93.71_forceware_winxp64_english_whql dated 112006.

My computer liked the update a lot. It didn't crash once in 3 days of constant processing.



This evening, I created a restore point and installed these 3 updates:

NFref_826_XP64 (Chipset)
Setup (On-Board Audio)
VGA_8440_XP64 (On-Board VGA)

and I received the message again:

I went into Safe Mode and did a System Restore to the Restore Point that I created and it works fine now.


I'll try installing one of the updates one at a time soon to see which one caused the problem, or maybe someone will know because it sticks out like a sore thumb. The first one I'll try is Chipset.

I'll try this also. If a report is generated, I'll post it here.

Denise

 

I downloaded AutoRuns from Microsoft. The name of the program is

It was the only one I could find. It doesn't say whether it will work for X64 but I'll give it a try along with NewFiles, post them here, and see what they come up with.

Denise

 

I ran ShowNew but it didn't work because it isn't compatible with X64.

I ran AutoRuns for Windows v8.70. I clicked on the Options tab, hide Microsoft entries. Under HKLM\CurrentControlSet\Services, there was one file that said "file doesn't exist" and I deleted it, rebooted and tried to uninstall the CPU driver but I received the same message that said that "Setup has encountered a problem and needs to close"

Does it look like I won't be able to update the driver without reformatting the drive?

 

I just installed "NFref_826_XP64" (Chipset driver) and didn't receive an error message. I'll wait a day or so before I install one of the other 2 so that I can see how this one interacts with my pc.

If anyone has any ideas, speak up and don't hold you peace.

 

I attached 2 pictures and a report from AutoRuns tht you might be interested in seeing . . . also an attached report.

 

Hi Denise, I see you have had some help fiding odd files- It looks like the first three are cpu related (one obvious, and two more same category.
Te dll files could have been your problem - When you finish installing the other drivers, then try updating the cpu again, as it could have solved the uninstall problem.

 

I deleted one file in HKLM\CurrentControlSet\Services but there were also these files in LSA Providers.

HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\SESSION MANAGER\KNOWNDLLS

C:\WINDOWS\SYSWOW64\WOW64.DLL
C:\WINDOWS\SYSWOW64\WOW64cpu.DLL
C:\WINDOWS\SYSWOW64\WOW64WIN.DLL




HKLM\SYSTEM\CURRENT\CONTROLSET\CONTROL\PRINT\MONITORS

msapsscpc.dll
msnsspc.dll



Should I delete these 5 also?

Denise

 

I also found a Shadow Copy Backup - Regedit, MSConfig, Task Manager that I made on 061007. Do you think that it might help if I used it?

Denise

 

Your registry backup could well be needed, if you delete the wrong files.
Generally I have found that 'file not found' needs to be treated carefully.
I would see if the program has a backup to any you delete, and if so, backup, in case they are needed.I use a different regisryrepairpro, and I can see what mine are related to, and am given two, or, three choices- delete, reconfiger in registry, or, leave alone, and I can also set a backup, automatically.- Does autoruns have those choices.

 

I wish that I understood this more.

The "file not found" files for WOW are

HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\SESSION MANAGER\KNOWNDLLS

C:\WINDOWS\SYSWOW64\WOW64.DLL
C:\WINDOWS\SYSWOW64\WOW64cpu.DLL
C:\WINDOWS\SYSWOW64\WOW64WIN.DLL

I Googles WOW and it came up with this Microsoft page:

http://msdn.microsoft.com/library/d.../win64/win64/wow64_implementation_details.asp

in case the address doesn't work, here's a part of it. It seems relavant to the 32-bit processes that are needed for X64 (if I'm not mistaken). Since the WOW files aren't there, it may be the cause of the problem, but that's just pure guessing/clutching at straws on my part.

When I Googled msapsspc.dll and msnsspc.dll, I found that they're both Internet Explorer 5.X Repair Tools.

Denise

 

"Shadow Copy Backup - Regedit, MSConfig, Task Manager" is an all-in-one copy. If I use it, it will install everything that was in them on June 10th, when I created it.

Denise

 

Denise, you have done right to check them out. Now, as I see it, these files help your compatability to your older 32 bit programs, and I cannot see it wise to delete them, as it may be that they need another file to compliment them to be complete .
I suggest that , at this point you do a start, run, sfc /scannow, or run CHKDSK /R, to ensure system files are repaired.
The backup you have is still very valuable, and might save you a lot of work, if the problem persists.

 

Great minds think alike

Right now, I'm running AdAware, SpyBot, and BitDefender just to see if they find something, but they probably won't as my pc is usually clean.

My next step is to run scannow. The tool is also on Dial-a-Fix, a program that I love. When I tried to run scannow in my old pc, scannow wanted me to insert SP2 disk. Since I didn't have it, it was downloaded a few years after I installed Windows XP Pro, it wouldn't work. I'm concerned that the same thing might happen with my X64 disc. It didn't come with SP2, or maybe even SP1, but I'll be doing the scannnow in about an hour, and I'll let you know how it worked out.

Also, Dial-A-Fix has a number of tools. I used to use them on my old pc but the only ones I use now, because I have x64, is flush dns, purge sfc and process idle tasks. I'm concerned that if I used other tools, such as "Flush Software Distribution," "Fix Windows Installer," "Fix SSl/HTTPS/Cryptsvc," etc, I may do more harm than good, but it helped my old 32-bit pc a lot.

It also has the options to "Reinstall BITS" but I have no idean what BITS are, "Repair Permissions," again, no idea, and a few other tools. I used them with my 32-bit pc but never with the 64-bit pc.

Boy, I can gab sometimes, can't I?

Ok, my next operations will be to run ChkDsk and sfc scannow.

Denise

 

I have to go off-line for now, others may come in to help, and I will look back in tommorrow- it's 23.37 in UK, now.
Post back your progress.

 

No malware/adware/viruses were found in my pc when I ran the scans.

I ran chkdsk and all was fine.

I ran scannow and I received no message or report. I don't know if it fixed anything but I can't uninstall the existing CPU file.

Denise

 

I know this is not the place for this, but you are booting into safemode before all the malware/virus scans right?

E

 

Sometimes I do and sometimes I don't. I disconnect from the internet by pulling the plug out of wall, turn off Firewall and Avast and shut down all running programs, i.e., Webshots desktop.

 

Since nothing else was working, I decided to use the Shadow Copy but made everything look as if I was in Safe Mode but even more grainier. I didn't check anything else. I created a Restore Point prior to using the Shadow Copy and restored it to that point.

It doesn't look like any process will allow me to uninstall the CPU Processor driver. I'm copying and moving files from my hdd to an external hdd and tomorrow I'm going to do a reformat.

baklogic, you helped an more than anyone could ask for and I appreciated it very much. This is just one of those unexplanable and unfixable things that calls for drastic measures. I prefer starting from scratch because it eliminates every little thing that could cause a problem.

I tried to install the new FDD this evening but the CPU 4-pin power connector wouldn't fit in the FDD power port. I tried to install the system fan but the fan has a female connector and the PSU has 2 female connectors that are available. I've looked for adapters for both of them but haven't found any yet. I'll look more again tomorrow.

X64 has too many bugs that need to be worked out and I seem to be running into all of them so I'm thinking about installing 32-bit Windows XP Pro 2000, the version that I had in my old computer, but I'm going to sleep on it and see how I feel about it tomorrow.

Besides have a SATA hdd, no other hardware is made exclusively for a 64-bit os, so it should be ok. If worse comes to worst, I'll do another reformat and install the dreaded X64.

Denise

 

Hi Denise,

Sorry I was not able to follow up as I had a very busy weekend.
Ok, I didn't know you had a x64 system but for how Autoruns work, it doesn't matter. It compares the related registry entries to the files at the locations they point at so if the program is telling you that the file a certain registry key is pointing at didn't exist, then the file shuld be missing.
If you are cautious, that is fine, simply browse to the location and check for yourself if the file is there or indeed missing.
Also, to be on the safe side, first try disabling that entry instead of deleting it by simply unchecking the box next to it, then reboot and see if everything works fine. If disabling didn't help you with your problem then deleting would be the next logical step.
For Registry backup (since autoruns doesn't provide it), I suggest using ERUNT or any other reputable program you prefer before deleting the entries.

As far as installing other stuff you mentioned, I won't be able to comment on them but good luck to you and I hope this helps.

~TL :cool

 

Good reminder, Fred.
And as Turcoloco
If you are cautious, that is fine, simply browse to the location and check for yourself if the file is there or indeed missing.
Also, to be on the safe side, first try disabling that entry instead of deleting it by simply unchecking the box next to it, then reboot and see if everything works fine. If disabling didn't help you with your problem then deleting would be the next logical step.
For Registry backup (since autoruns doesn't provide it), I suggest using ERUNT or any other reputable program you prefer before deleting the entries.

Denise
The only thing you will have to remember, if you decide to go x32, is that you will need all x32 drivers.

If the error does not appear, and it runs o.k with the present cpu driver, -then I would forget the last cpu update, and try it for a while, as you said it was running a lot quicker.

At least , you have tried all ways, and if you are not 100% happy with the result, then by all means, save, and reformat.-save those driver downloads, for x32, and x64, in case you reconsider- it will be a lot quicker to do , then.
As for the help, that is what I understand majorgeeks to be about- to try to help you save your hard earned cash, and fix it yourself, because you have, all the way through.All at majorgeeks, like those I see helping-like FedG-and,Turcoloco, here are all here to try to help you fix it, and if all goes well, we get the pleasure of any success.

Keep us posted.:duck

 

Well, I slept but I haven't decided what I want to do yet.

As I mentioned in my last post, I have 2 female PSU adapters and I need 2 male adapters plus a PSU 4-pin plug that's not a molex. It took me most of the day (I get up late) in another thread to find the cables and adapters that I need. Bidiot helped me with those. I didn't know it but it seems that my name has become famous here, synanimous with Run For Your Life, or it's infamous, lol.

Anyway, I also backed up everything that I need from my C drive onto an ext hdd to prepare to do a reformat since nothing else works to uninstall the PSU driver. My computer runs faster with Nvidia but only about 1/2 as fast as when the PSU driver was installed, albeit the wrong one, so I think the PSU really needs the updated driver.

I just came to this thread and read the posts. (I sometimes don't get emails that someone has posted something)

Hi Turcoloco . . . I understand how AutoRuns work. I deleted one entry from the path that you gave me. I'll follow the other ones to see if it's there. If not, I'll delete it in AutoRuns. Thanks for your help.

Hi baklogic . . . you've held my hand, you nursed my wounds, you put up with my constant questions and re-questioning of things. If I hadn't leaped before I waited and looked at what you had to say about the CPU driver, the correct update would be installed, so it's a self-made problem and that's what's bothering me most.

I looked into the PSU update and it has to do with Nvidia.

I wish you hadn't said

I thought the software that came with the mobo and with Windows supplied all the drivers. I've never had to download drivers before except for my printer because it's X32, not X64. How will I know what drivers aren't X32? I thought that the only thing that was X64 is my hard drive. Do you want to see a grown woman go out of her mind :foolish :heliroflmao :crybaby :tas

Denise

 

No need to worry.
The basic x32 drivers will be there, on the motherboard CD, and Windows.
It is just that when you update, you will have to be sure the updated drivers are x32.
We can lead you through, if you decide to go to x32 - but I think you were almost there, until you used the wrong (quod ) update for your system.