On Jan 20, 2:04*pm, myDingling <gu...@unknown-email.com> wrote:
> Thanks you all for the responsed.
> So I installed Windows 7 hoping this might have remedied the problem
> and...it didnt! 
*So it's likely not an OS issue and has to do with
> the hardware/bios. *
Your post does not suggest a surge existed. That conclusion was
wild speculation and contradicted by details in your post. If a surge
existed, then you also are listing other now damaged appliances.
Those many actions performed with no reason for doing so may have
exponentially complicated the problem. 'Try this and try that' is
wild speculation (shotgunning) that typically creates even more
problems.
Stop trying to fix thing. First get facts. For example, a first
fact is information from the event (system) logs and Device Manager.
Well, instead, you destroyed any useful information by loading Windows
7 - when that was a least likely solution. But again, this is why
shotgunning only makes solutions difficult.
Fortunately, you did not reload perfectly good BIOS. But then you
had zero reasons to suspect a BIOS problem. Again, fixing things that
were not even broken. In this case, reloading the BIOS might have
permanently destroyed hardware.
Swapping a power supply would do nothing. It is a laptop. Any a
power supply problem causes it to automatically switch to batteries.
But again, what was battery power level?
Better computer manufacturers provide comprehensive computer
diagnostics so that a problem is broken down into parts. Analyze those
parts one at a time. Comprehensive diagnostics execute with no
Windows. See how it is done? Testing hardware without Windows breaks
a problem into parts.
Worse, you loaded Windows in a machine with unknown hardware. Now
you may have a defective Windows installation in addition to a
hardware defect. If so, the problem is further complicated.
Does that laptop come with comprehensive diagnostics? If not, it
better have cost significantly less money. If not, download
diagnostics for each relevant component and execute them one at a
time. List of suspects is actually shorter.
Let's go back to your original problem. BIOS setting changed. So
what was the battery state and what is the CMOS battery voltage?
Swapping a battery means the problem gets even more complex. With
CMOS battery still in place, measure its voltage with a multimeter.
Again, before fixing anything, first know what is and is not
defective. Post those numbers so that the better informed can suggest
further facts - no more 'it could be this or could be that' wild
speculation. Those numbers report all kinds of facts you never even
realized.
How much labor have you performed? Well, how long is the list of
things you know are definitively good? Still zero items? IOW you
still have accomplished zero. Just another reason why shotgunning and
wild speculation leave you confused. We don't even know the CMOS
battery voltage.
A critical unknown fact. Did you sleep it or hibernate it for 10
days. What was the battery state (power levels) when you rebooted?
Important facts probably now completely lost since you reloaded
Windows. Relevance not explained assumiing you know the difference
between sleep and hibernate.
Go back from the beginning. Above are some basic facts you should
already have such as Device manager, event logs, battery power level,
and comprehensive hardware diagnostic reports. Are BIOS settings for
hardware wakeup still turned off? Are you sleeping the machine or
hibernating it?
Linear Mode
