1 yr old (no physical damage) n450, 2gb ram, Win 7 netbook was stuck in startup repair loop. Would boot to safe mode, and safe mode w/ networking. Now after attempting an F9 factory system resore it gets to loading drivers, then fails, says it has to restart then fails again.
Things I've done...
System restore to several point-all successful, no change in problem
chkdsk- no problems
Windows memory diagnostic- no problems
Tried repairing with a full Win 7 disk in an ext DVD drive. Failed.
I'm thinking a hardware issue...but where do I start?
My wife LOVES this little machine, so any help is much appreciated!!
Hard-drive is a very probable cause, so is RAM. The Windows checkdisk is useless to find hardware issues on the drive. It checks the file system, but is not good at all with finding physical issues.
Try running with 1 gig of RAM if it has two sticks, try both, one at a time.
If that still causes crashing, buy a new hard-drive and install windows on that see if that helps. Although you either need to boot it enough to create a restore DVD set, or use your own Windows disks, or contact ACER and have them send you a disk set, or buy a drive from them directly with the thing setup already.
Try installing Windows 7, run all of the drivers and patches from ASUS, then let Windows do the updates.
I have not seen Windows 7 mess up drivers if it did not know what they were. I ran a few laptops that did not have Windows 7 drives, the hardware Windows 7 could not find it left as Generic VGA and such, but they worked fine.
Could be CPU, could be RAM here. Try a BIOS update also, maybe some CPU instruction is having issues.
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
kb will then show the corrected stack.
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
TRAP_FRAME: 87453590 -- (.trap 0xffffffff87453590)
ErrCode = 00000000
eax=00002710 ebx=00000000 ecx=00000000 edx=00000000 esi=907dea88 edi=6f821738
eip=8bfbf64a esp=87453604 ebp=87453604 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
8bfbf64a f7f1 div eax,ecx
Resetting default scope
LOCK_ADDRESS: 81ba8f60 -- (!locks 81ba8f60)
Resource @ nt!PiEngineLock (0x81ba8f60) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.