Jump to content
Posted 05 January 2009 - 02:23 PM
Posted 05 January 2009 - 02:50 PM
Posted 05 January 2009 - 02:58 PM
Good to back up your data, as it could be your harddrive is failing. Try not to reboot more than you have to.
Then try these things.
First try going back to an earlier restore point:
If you've never done this before, Go to Start / All Programs / Accessories / System Tools / System Restore
check the box to Restore my computer to an earlier time and click on Next. You'll see a calendar with highlighted dates. Choose one of the dates just preceeding these problems and allow your system to return to that date. See if the problem goes away.
If this doesn't work, go back into System Restore as per the above instructions, only this time choose the option to reverse the change you made.
Then if that doesn't help, try to boot into Safe Mode and see if you can get to the Last Known Good Configuration choice and see if that helps. Here's an ariticle on that:
Also for this type of error, there's a link from Microsoft suggesting downloading the most recent service pack. Have you done that already? Look at these two articles:
Posted 05 January 2009 - 11:52 PM
Edited by J-ROCK, 06 January 2009 - 12:44 AM.
Posted 06 January 2009 - 04:15 PM
Posted 07 January 2009 - 06:34 AM
- numerous hardware problems
- STOP 0x8e during memory access (in most cases this is a hardware/driver STOP error)
So, he'll need MemTest to rule out the memory ( http://www.memtest86.com/ )
A hard drive diag wouldn't hurt - but there'd be issues in Safe Mode if the hard drive was failing. Most likely it's something that loads in normal mode, but not in Safe Mode (a driver)
And probably run WinDbg to see what else is revealed in the memory dump ( http://www.bleepingcomputer.com/forums/t/176011/how-to-receive-help-diagnosing-blue-screens-and-windows-crashes/ ) I'll read it if he posts it.
If the dump file doesn't give suggestions, then we'll need a detailed history of what was done to the system recently (hardware and software).
Beyond that, we'll end up replacing all the drivers for all the affected pieces of hardware. Then move onto replacing the motherboard drivers. If all that fails to fix it, then we're looking at it possibly being a motherboard problem (since that's where all the hardware comes together).
Posted 07 January 2009 - 10:30 AM
Posted 07 January 2009 - 10:56 AM
Posted 07 January 2009 - 12:24 PM
Posted 09 January 2009 - 08:59 PM
Posted 12 January 2009 - 11:48 PM
Edited by Orange Blossom, 14 January 2009 - 03:10 PM.
Posted 14 January 2009 - 03:11 PM
An ounce of prevention is worth a pound of cureSpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript
0 members, 0 guests, 0 anonymous users