(Actually Sager 3790, forgot what model, sorry)
I was using my laptop last night for internet surfing and e-mail for a few hours and then I shut it off. I then remembered I did want to check something else, so I turned it on, set it on my bed (might have been my downfall), and then got ready for bed while it loaded up (I was in the bathroom, it in my bedroom). I returned to find my screen had blacked out, though I still could hear sounds when I clicked buttons and what not, so it seemed like a screen issue. I ended up having to power off by holding in the power button. I waited a few moments and tried to power it back on.
It will light up for a second and then turn back off. I tried removing the battery, plugging into wall, tried different outlets.... *sigh*, nothing.
It did get pretty hot, so I let it cool down over night and this morning the problem still persists... I'm wondering what I could have broken, hope not the mb or proc, but it probably is), what steps should I take in locating the issue or tips to try?
I don't have time to take it apart until next weekend, luckily I also have a pc I just built last month, maybe the little guy was envious of the big pc's attention and committed suicide, lol.
Thanks for any help!
Wayne
I was using my laptop last night for internet surfing and e-mail for a few hours and then I shut it off. I then remembered I did want to check something else, so I turned it on, set it on my bed (might have been my downfall), and then got ready for bed while it loaded up (I was in the bathroom, it in my bedroom). I returned to find my screen had blacked out, though I still could hear sounds when I clicked buttons and what not, so it seemed like a screen issue. I ended up having to power off by holding in the power button. I waited a few moments and tried to power it back on.
It will light up for a second and then turn back off. I tried removing the battery, plugging into wall, tried different outlets.... *sigh*, nothing.
It did get pretty hot, so I let it cool down over night and this morning the problem still persists... I'm wondering what I could have broken, hope not the mb or proc, but it probably is), what steps should I take in locating the issue or tips to try?
I don't have time to take it apart until next weekend, luckily I also have a pc I just built last month, maybe the little guy was envious of the big pc's attention and committed suicide, lol.
Thanks for any help!
Wayne
