Book now with code EOY2025
gateway wrote: » Reimaging is too easy I would boot it via USB to something like WINPE, and do a virusscan, and whilst that is running, copy the bsod minidump files and analyse them to see what has gone wrong. If you decide its not worth fixing and you only have a recovery cd, you will need to (depending on manufacturer) copy the contents of the recovery cd to an external hdd or file server and run the recovery from there - may/may not be possible depending on how recovery environment is set up.
demonfurbie wrote: » i just reimaged it with an external dvd
demonfurbie wrote: » to me it sounds like the page file
Devilsbane wrote: » How could you be thinking this based on the little knowledge that we know?
earweed wrote: » It goes through several files on the safemode boot. The one it stops on ends in mup.sys I'm assuming it's a driver of some kind.
earweed wrote: » Found this about hanging at the mup.sys and I'm not sure if the battery being kind of bad (only holds charge for about 1 hr. may be part of problem The main reasons for this Windows XP or Win 2000 boot hang or alleged mup.sys issue are:Hard disk failure or corruption A corrupted registry or registry hive New hardware has been installed but not did not completely "Register or re-Register" correctly New hardware has been installed but it is faulty or failing The new hardware's driver or windows itself has been compromised (Disk data corruption or by a virus) or (rare) needs to be updated The power supply is marginal in output or failing (Common per user feedback) BIOS\ESCD\Motherboard chipset driver conflict with a component, its driver, or its registry data Existing hardware including the motherboard may have failed in a specific way but not catastrophically. I ran chkdsk and it looks good.
earweed wrote: » Apparently it got infected while she was on facebook so don't think you're safe there.
earweed wrote: » Where do I find the BSOD minidump files?
Use code EOY2025 to receive $250 off your 2025 certification boot camp!