TeraByte Unlimited

I checked on BSOD code 109 online. It looks like bad RAM can be one
pretty common cause. Also present was bad/corrupted coding.

The last BSOD involved when I was trying to make a minor change to
settings in Windows Media Player.

Then I decided to check Minidump dates & restored an image created about
6 weeks before the earliest crash.
So far, no BSOD's since I did that.

WMP seems to be working okay as well now.

Since WMP was involved last time, I wondered if Windows itself got
corrupted at some point???
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
>
>

On Sun, 15 Feb 2015 12:15:50 PST, just as I was about to take a herb,
MJNelson disturbed my reverie and wrote:

>Since WMP was involved last time, I wondered if Windows itself got
>corrupted at some point???

That's why I like system restore. Also very handy when trying to
remove autoloading viruses.
--
Cheers,

DrT

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

I got a 4 GB ram stick and replaced one of my 2 GB sticks that were
there. Not sure if one was defective so chose to keep the stick that
most closely resembled the new one.

Ran Memtest86 last night. No errors.

Now choosing to just use the computer normally. So far, no crashes.
Fixed???

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
>
>