Performance problem

  • Thread starter Thread starter Matthew
  • Start date Start date
M

Matthew

I have a dell dimension 8200 computer running win xp home
edition, and it is less than a year old. Until recently
it has been working fine. What has occured in the past
week is that the page file usage has gone through the
roof. When working fine its at 180mb but then it spikes
up to 780 all the way up to 818mb and my computer stops
working. It goes up and down between 180 to 790mb. The
kernel memory as of right now is this total:38068, paged
28460, nonpaged 9608. The physical memory is 261100,
available 148536, system cache 47628. I have tried
everything to fix it from defragmenting, to deleting
programs, all the way to restoring the system to a
previous date before this started to happen. Will I need
to reinstall the whole system again. I have checked and
there are no viruses, or any potential ports open that a
hacker could get in. Any help would be much appreciated.

Thanks,

Matt
 
Matthew said:
I have a dell dimension 8200 computer running win xp home
edition, and it is less than a year old. Until recently
it has been working fine. What has occured in the past
week is that the page file usage has gone through the
roof. When working fine its at 180mb but then it spikes
up to 780 all the way up to 818mb and my computer stops
working. It goes up and down between 180 to 790mb. The
kernel memory as of right now is this total:38068, paged
28460, nonpaged 9608. The physical memory is 261100,
available 148536, system cache 47628. I have tried
everything to fix it from defragmenting, to deleting
programs, all the way to restoring the system to a
previous date before this started to happen. Will I need
to reinstall the whole system again. I have checked and
there are no viruses, or any potential ports open that a
hacker could get in. Any help would be much appreciated.

Thanks,

Matt

Try turning off virtual memory. Immediately reboot and delete
pagefile.sys. Delete the contents only of Windows\Prefetch (it will be
rebuilt). Immediately reboot and turn virtual memory back on again with
the windows default management.

Q
 
Back
Top