Page 1 of 2

blue screens

Posted: Sun Feb 01, 2015 2:35 am
by mjnelson99
I have a 3 year old laptop that has had 3 blue screens in about 3 weeks.
I was not doing anything very intensive at any time it crashed.


I did feel and the computer did not feel very hot the last time (this
morning).

Any suggestions?
Mary

Re: blue screens

Posted: Sun Feb 01, 2015 6:56 am
by TeraByte Support(PP)
Get the BSOD code and look it up (can usually help pinpoint the cause). Check the RAM and disk(s) for errors. Check if any programs or drivers have been installed recently. Check the Event Log for any error messages.

Re: blue screens

Posted: Sun Feb 01, 2015 1:23 pm
by DrTeeth
On Sat, 31 Jan 2015 18:35:01 PST, just as I was about to take a herb,
MJNelson disturbed my reverie and wrote:

>I have a 3 year old laptop that has had 3 blue screens in about 3 weeks.
Try system restore if you have a restore point that predates the
issue. You have nothing to loose and it quicker and easier that a
restore of a backup, plus no personal data lost.
--
Cheers,

DrT

** You've never known happiness until you're married;
** but by then it is too late.

Re: blue screens

Posted: Sun Feb 01, 2015 5:58 pm
by mjnelson99
I only use IFL/IFW, not Windows so there isn't one I can use.

On 2/1/2015 7:23 AM, DrTeeth wrote:
> On Sat, 31 Jan 2015 18:35:01 PST, just as I was about to take a herb,
> MJNelson
>
> disturbed my reverie and wrote:
>
>> I have a 3 year old laptop that has had 3 blue screens in about 3 weeks.
> Try system restore if you have a restore point that predates the
> issue. You have nothing to loose and it quicker and easier that a
> restore of a backup, plus no personal data lost.
>

Re: blue screens

Posted: Sun Feb 01, 2015 6:01 pm
by mjnelson99
Is the BSOD error code near the top?
The display is not on very long before it reboots.

I did add a couple of new USB 3 (4 port) hubs, 2 diff mfgrs.
Might be worth disconnecting?
Mary

On 2/1/2015 12:56 AM, PP wrote:
> Get the BSOD code and look it up (can usually help pinpoint the cause).

Check the RAM and disk(s) for errors. Check if any programs or drivers have
been installed recently. Check the Event Log for any error messages.
>
>

Re: blue screens

Posted: Sun Feb 01, 2015 6:05 pm
by mjnelson99
I only started to use this computer when a 2nd laptop had a bad screen
so not sure how old I would need to get a restored version that might work.

Hopefully the other laptop will find itself back from Acer in the near
future.
Mary

On 2/1/2015 11:58 AM, MJNelson wrote:
> I only use IFL/IFW, not Windows so there isn't one I can use.
>
> On 2/1/2015 7:23 AM, DrTeeth wrote:
>> On Sat, 31 Jan 2015 18:35:01 PST, just as I was about to take a herb,
>> MJNelson
>>
>> disturbed my reverie and wrote:
>>
>>> I have a 3 year old laptop that has had 3 blue screens in about 3 weeks.
>> Try system restore if you have a restore point that predates the
>> issue. You have nothing to loose and it quicker and easier that a
>> restore of a backup, plus no personal data lost.
>>
>
>

Re: blue screens

Posted: Sun Feb 01, 2015 6:56 pm
by rich071
Mary,

The link below, will show you how to disable the Auto Restart, so you can get the required information from the monitor, when the Blue Screen happens again. It has the info to do it manually or create a REG file, which ever makes you feel more comfortable. When installing Windows the first time, I always disable the Auto Restart for the very reason you are experiencing.

http://www.bleepingcomputer.com/forums/ ... s-crashes/

Where are the fan(s) on the laptop? A friend of mine had the blue screens as well and his fan was blowing down, not out the sides or out the back but down when setting on a hard surface. He uses his laptop as a desktop, so it never moves. He had blown out the vents and propped it up so the laptop had about an inch of space between the table and the laptop. His Blues Sceens have not returned.

Good luck,

Re: blue screens

Posted: Sun Feb 01, 2015 8:20 pm
by mjnelson99
I ran a program within windows (part of Win7) that looked for problems
with 2 of the blue screens. However, it was right after I had just
turned the computer on. It found nothing.

May run it again later.
Mary

On 1/31/2015 8:35 PM, MJNelson wrote:
> I have a 3 year old laptop that has had 3 blue screens in about 3 weeks.
> I was not doing anything very intensive at any time it crashed.
>
>
> I did feel and the computer did not feel very hot the last time (this
> morning).
>
> Any suggestions?
> Mary
>
>

Re: blue screens

Posted: Mon Feb 02, 2015 1:32 am
by TeraByte Support
tap f8 just after the post, before starting windows comes up and then choose
the option to disable automatic reboot. then you can see what the bsod is.

"MJNelson" wrote in message news:9312@public.tech.misc...

Is the BSOD error code near the top?
The display is not on very long before it reboots.

I did add a couple of new USB 3 (4 port) hubs, 2 diff mfgrs.
Might be worth disconnecting?
Mary

On 2/1/2015 12:56 AM, PP wrote:
> Get the BSOD code and look it up (can usually help pinpoint the cause).

Check the RAM and disk(s) for errors. Check if any programs or drivers have
been installed recently. Check the Event Log for any error messages.
>
>


Re: blue screens

Posted: Mon Feb 02, 2015 3:25 pm
by Walter B
Mary,

I just worked on a friend's notebook that was BSODing frequently. I used
MemTest+ and found that one of the memory modules was shot. I replaced it,
and that took care of it. The version of MemTest+ that I used is 4.20;
there may be newer versions.

Checking memory is always a good place to start for me, in addition to video
drivers.

"MJNelson" wrote in message
news:9312@public.tech.misc...
> Is the BSOD error code near the top?
> The display is not on very long before it reboots.
>
> I did add a couple of new USB 3 (4 port) hubs, 2 diff mfgrs.
> Might be worth disconnecting?
> Mary
>
> On 2/1/2015 12:56 AM, PP wrote:
>> Get the BSOD code and look it up (can usually help pinpoint the cause).
>
> Check the RAM and disk(s) for errors. Check if any programs or drivers
> have
> been installed recently. Check the Event Log for any error messages.
>>
>>
>
>