| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 100374 | 2009-06-05 04:30:00 | Computer slowed to a crawl. | B.M. (505) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 779840 | 2009-06-05 06:37:00 | If there's nothing hogging the CPU in safe mode, but runs slow, as noted above by Wainuitech -could be a driver problem. You might want to read this (blogs.technet.com) about using process explorer (technet.microsoft.com) to digg into driver issues, since you have done many of the standard procedures... | kahawai chaser (3545) | ||
| 779841 | 2009-06-05 07:24:00 | Maybe IDE ATA in device manager in PIO mode rather than DMA, look in properties. Look at this: support.microsoft.com |
zqwerty (97) | ||
| 779842 | 2009-06-05 07:26:00 | If there's nothing hogging the CPU in safe mode, but runs slow, as noted above by Wainuitech -could be a driver problem. But then again a lot of drivers aren't running in safe mode. How old is the Windows install? 3 years+? Probably bloat then in which case a fresh install might be the answer. As for not reading NFO files, you have to associate that with something like Notepad first. |
pctek (84) | ||
| 779843 | 2009-06-06 08:31:00 | Thanks everyone for your input. :thumbs: Without dealing with every post individually I can advise I have followed all the suggestions and links but have failed to remedy the situation. :( On the driver front there are no noted conflicts and device manager says everything is working fine. I hadn’t Defragged, but I have read somewhere that defragging a NTFS file system is unlikely to make any noticeable difference. However, I did do it even though the Defragg Report said it was unnecessary. Unfortunately, no improvement. :( I ran sfc /scannow and it found a dozen or so files that it replaced but to no avail. As a matter of interest can anyone explain how a XP SP1 Disk can successfully replace files that have been updated to SP3? :confused: However, I have stumbled across a strange phenomenon in that the FSB is set to 100MHz. I’ve tracked this back to the BIOS but CMOS Setup won’t allow me to change it. This is despite the CPU having a FSB speed of 400 MHz and the Motherboard being capable of 533MHz and the RAM having a DDR 333MHz clock speed. So, that’s where I’m up to and any further suggestions would be appreciated. (Especially about the BIOS being locked to 100MHz Bus speed. :thanks |
B.M. (505) | ||
| 779844 | 2009-06-06 08:51:00 | I hadn’t Defragged, but I have read somewhere that defragging a NTFS file system is unlikely to make any noticeable difference . As a matter of interest can anyone explain how a XP SP1 Disk can successfully replace files that have been updated to SP3? :confused: However, I have stumbled across a strange phenomenon in that the FSB is set to 100MHz . It won't touch the MFT in an NTFS system . It removes and replaces them . So they're not SP3 files anymore . Because its 100 x 4, making 400mhz . |
pctek (84) | ||
| 779845 | 2009-06-08 00:45:00 | Well this has got me licked . :confused: Having given up on the Software approach, I decided to check the Hardware (Bulging, leaking Capacitors etc) . They looked fine . Anyway, I pulled out the RAM to see if there might be a mismatch or something (clutching at straws) and there are two sticks . That’s fine, they will be two 256 Meg sticks to make up the 512 Meg registering . Not so, one turns out to be 256 and the other 512 . What the???? Naturally by this stage they were lying on the table so I couldn’t check to see what was registering in what slot . Therefore I cleaned up their terminals and reinstalled them and now I have 768 Meg of Memory and the problem solved . The Computer runs good as gold again . There is still one thing that concerns me though and that is I get the traditional one beep before the initial Splash Screen and another single beep after the Splash Screen, before Windows starts loading . Can’t say I’ve struck this before . Who’d be a Computer Technician? How the devil would you ever charge your time out for an event of this nature? However, I still can’t fathom why the BIOS didn’t pick up the 256 stick that wasn’t registering, or the half of the 512 stick that wasn’t registering, which ever it was . I suppose it did struggle on without complaint . Anyway, :thanks everyone for your input . :thumbs: |
B.M. (505) | ||
| 779846 | 2009-06-15 10:34:00 | I imagine there are so many programs that you need that there is not enough RAM to supply.Try upgrading or buying new RAM, if that dosent do use a external HDD(hard drive) and move some programs on to it.or else, it could be the very well knowen virius or worm in your PC........ | TechProX (14940) | ||
| 779847 | 2009-06-15 10:42:00 | Who’d be a Computer Technician? How the devil would you ever charge your time out for an event of this nature? However, I still can’t fathom why the BIOS didn’t pick up the 256 stick that wasn’t registering Me. Well that's what makes it fun, sometimes you pick it quick and sometimes you stuff around for ages, of course stuffing around can't really be entirely charged for. Thats also why sometimes it's better to come back to the workshop and have a look. The BIOS did, it just didn't like it for whatever reason. If its not seated right then you should get BIOS beeps but not if it is seated OK, but RAM can be funny, sometimes swapping the order round fixes weirdness like that. I had one of those nasty little HPs today - 10 years old with a dead PSU. Had a little 400w handy but of course this thing had one of those small 150ws. But aha, there was room. I just had to dismantle the entire PC and insert it and then put everything else back. WHile that took ages longer than it should to swap out a PSU, I just charged the usual PSU price. AFter all it was fun making it accept a proper PSU. |
pctek (84) | ||
| 1 2 | |||||