Poasters Computer Forums

Computer Help Desk => Desktop Help => Topic started by: ingeborgdot on November 04, 2009, 19:05 hrs

Title: What could this be?
Post by: ingeborgdot on November 04, 2009, 19:05 hrs
I know it could be a number of things but does anyone have a suggestion?  It started about 7 days ago that my computer would just restart by itself.  It did this several times in a short period.  Now it has only done it a couple of times in the last several days.  What does it sound like?
Title: Re: What could this be?
Post by: ingeborgdot on November 04, 2009, 19:50 hrs
Thanks, but I am already on one. 
Title: Re: What could this be?
Post by: pat on November 04, 2009, 20:14 hrs
I'd disable auto restart to get a look at the error message. System properties, Advanced tab, Start up and recovery, uncheck automatically restart.

I'd also do a thorough check on the memory.
Title: Re: What could this be?
Post by: ingeborgdot on November 04, 2009, 20:21 hrs
Restart now unchecked.  Thanks.
Title: Re: What could this be?
Post by: Buffalo2102 on November 05, 2009, 07:24 hrs
Could also be temperature.....
Title: Re: What could this be?
Post by: ingeborgdot on November 05, 2009, 07:39 hrs
Temps are only at 30 to 42 for all four cores in idle and it shuts at any of those temps. 
Title: Re: What could this be?
Post by: ingeborgdot on November 05, 2009, 07:39 hrs
I got my first BS this morning after unchecking the the restart box after error. How do I read it?
Title: Re: What could this be?
Post by: ingeborgdot on November 05, 2009, 08:52 hrs
I got this on one STOP 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
Title: Re: What could this be?
Post by: Buffalo2102 on November 05, 2009, 09:06 hrs
That is indicative of a memory problem, although it doesn't necessarily mean that your memory is bad.  If you test the memory with a suitable application and it checks out OK then it is probably caused by a poorly written or incompatible driver or application.

What did you install/update at the time that this started?
Check Windows Update to see if anything was installed.
If you have a suitable restore point prior to the issue, try that.
Try disabling resident applications (firewall, antivirus, etc.) and see if that does the trick.

That error can also be caused by hardware issues but it's unlikely in this case unless you have recently changed something?  Try reseating boards, cables etc.

Buff
Title: Re: What could this be?
Post by: ingeborgdot on November 05, 2009, 10:59 hrs
I installed a new update for my logitech keyboard and mouse, avg 9.0 and another piece of software 2 weeks earlier before this even started.
Title: Re: What could this be?
Post by: ingeborgdot on November 05, 2009, 18:59 hrs
I have run a memtest for 6 hours now and there is 1 error.  With 1 error could that cause a problem?
Title: Re: What could this be?
Post by: scuzzy on November 05, 2009, 20:34 hrs
Zero errors is what you want, although I've never heard of one that low.

Have you tried re-seating the memory?
Title: Re: What could this be?
Post by: Mark H on November 07, 2009, 21:14 hrs
I had the same problem on two different machines. On one, it was bad memory modules that when replaced corrected the problem. On another, it was a bad power supply that when replaced, corrected the problem.

Mark H
Title: Re: What could this be?
Post by: ingeborgdot on November 12, 2009, 20:07 hrs
What is this?
modification of a system code or a critical data structure was detected
Title: Re: What could this be?
Post by: Buffalo2102 on November 13, 2009, 02:33 hrs
That could also be caused by bad memory.  Also poor drivers, OS code, hardware etc. etc.

If I was you, I would start with making sure that the motherboard BIOS is up-to-date as this can affect the way the system reads/writes to the memory.  Then set the other BIOS parameters to safe defaults.  Reseat all your cards, cables etc.

Then make sure that all your chipset and other drivers are up-to-date.  Make sure that there are no outstanding Windows updates.

At this point you should have a solid system that is completely up-to-date.  If you still get a BSOD then run memtest again.  If it fails and you have more than one stick of RAM, take one out and run memtest again.  If it fails again, swap the sticks and run again.  If it fails again, try raising the DIMM voltage in the BIOS a notch.  If it fails again, RMA the RAM.

If the RAM tests out fine, try uninstalling (non-essential) bits of hardware, one at a time.  Disable AV and other non-essential resident programmes.

I'm afraid it is a painful process but this is usually the only way to troubleshoot these things, unless you can point to a particular event when this started happening.

Good luck

Buff
Title: Re: What could this be?
Post by: Mark H on November 17, 2009, 00:06 hrs
In my PC that had bad memory, it ended up being 3 bad sticks out of 4.

Mark H
Title: Re: What could this be?
Post by: ingeborgdot on November 17, 2009, 06:42 hrs
Yeah, memtest showed over 400,000 errors when I ran it the 2nd time after 8 hours.