View Full Version : bad mem accessing
Rusty the dog
December 8th 03, 08:33 PM
this might be a bit of a deep problem for posting here...
just wonder if anyone has had one like this...
ms word constantly causes windows to crash when I scroll
down with mouse..
I'm on win xp/office xp
its been happening since upgrading to a VIA motherboard
was getting stop screens (indicating a bad {illegal} mem
access) but now just restarts the pc!
canna figure it out yet
if you know, or know a man who knows..
cheers
Alex Perez
December 8th 03, 08:33 PM
Sounds like a memory problems, if you happen to have a memory stick around,
try replacing the ones you have. Make sure that your memory is of the same
kind and compatible with your MB.
"Rusty the dog" > wrote in message
...
> this might be a bit of a deep problem for posting here...
> just wonder if anyone has had one like this...
>
> ms word constantly causes windows to crash when I scroll
> down with mouse..
> I'm on win xp/office xp
> its been happening since upgrading to a VIA motherboard
> was getting stop screens (indicating a bad {illegal} mem
> access) but now just restarts the pc!
> canna figure it out yet
> if you know, or know a man who knows..
> cheers
Frank
December 8th 03, 08:41 PM
Rusty the dog wrote:
| this might be a bit of a deep problem for posting here...
| just wonder if anyone has had one like this...
|
| ms word constantly causes windows to crash when I scroll
| down with mouse..
| I'm on win xp/office xp
| its been happening since upgrading to a VIA motherboard
| was getting stop screens (indicating a bad {illegal} mem
| access) but now just restarts the pc!
| canna figure it out yet
| if you know, or know a man who knows..
| cheers
It sounds like bad RAM either mis matched to the motherboard
or to each other. _Usually_ if the RAM fits they will work.
I would download _memtest86_ and run the test with one stick
in the first slot at least 3 passes. Do this with each stick. then
each slot. This is one big process of elimination to find what is
broken. If this checks out OK then I would go to checking the
VIA drivers, and so on. This will be time consuming but at
least you will know what is broken.
good luck
--
Tampa Bay
vBulletin® v3.6.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.