Random BSOD at random moments on Toshiba L500 laptop; graphics card?

[luciflash]

My GF has had a Toshiba L500 laptop for 4 years now. It's a great model and it worked well...till now.

It started about two weeks ago, with 1 blue screen every 1-2 days. I haven't reinstalled her windows for about a year, so i figured that was the problem.

Four days ago it started blue screening randomly (from just after the welcome screen, clicking on start button to opening a new tab in a browser). Sometimes it dies instantly, other times it keeps on going for an hour.

I tried:
- fresh install of windows (x64) (it bsod just after the input of computer name)
- another install (bsod just after welcome screen); i figured it was the video card, so i downloaded the latest driver, but it didn't help. I ran a check disk, everything was ok.
- tried the driver posted by toshiba and the newest posted by intel; i didn't get to installing anything else, because it kept crashing
- another install, this time Win 7 x32 Home, and let it update everything, didn't install anything else; still nothing.
- ran memtest x86, 2 passes once, 7 passes the second time, no errors.
- removed ram cards one at a time, still nothing
- heavy load, stressed every component, no crashes, everything was ok.
- checked out some settings in bios, nothing there
- tried driver verifier (it froze at windows logo the first time, restart 2 minutes after log on with no blue screen, froze at the windows logo the third; the I put it out of it's misery and disabled the verifier)

Safe mode works just fine.
I can't shake the feeling that the motherboard is dying
I'm all out of ideas and I could really really use your help.

View attachment 306990

 

[Arc]

Hi luciflash.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.x86fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Also update Realtek RTL8187B Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter from Realtek

Let us know the results.

 

[luciflash]

So...no luck.

I installed Windows XP last night just after posting. It worked well, no blue screens what so ever, until I ran an app Video Card Stability Test which caused a BSOD (this also caused bs on Windows 7).

In the morning I reinstalled Windows 7 x32, and installed all the updates possible, including the one for Realtek Wireless card. It worked until I plugged in an external drive. It froze. I had to force shutdown. It restarted, i click on start, it BSOD. It restarted, BSOD just after welcome screen. It restarted I plugged in an usb, it BSOD after a few seconds. Then i managed to run SFDebug, and here I am...

View attachment 307143

 

[Arc]

So...no luck.

I installed Windows XP last night just after posting. It worked well, no blue screens what so ever, until I ran an app Video Card Stability Test which caused a BSOD (this also caused bs on Windows 7).

In the morning I reinstalled Windows 7 x32, and installed all the updates possible, including the one for Realtek Wireless card.

If you dont swing the OSs back and forth, it may help you to concentrate on troubleshooting.

until I ran an app Video Card Stability Test which caused a BSOD (this also caused bs on Windows 7).

What I see in the latest zip is all Mobile Intel(R) 4 Series Express Chipset Family Graphics, no video card.

It worked until I plugged in an external drive. It froze. I had to force shutdown. It restarted, i click on start, it BSOD. It restarted, BSOD just after welcome screen. It restarted I plugged in an usb, it BSOD after a few seconds. Then i managed to run SFDebug, and here I am...

View attachment 307143

Mostly the BSODs are

[COLOR=Red]BugCheck 1000008E[/COLOR], {c0000005, 0, 8c975bf4, 0}

Probably caused by : ntkrpamp.exe ( nt!ObpRemoveObjectRoutine+59 )

Followup: MachineOwner
---------

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory.

There is another one.....

[COLOR=Red]BugCheck A[/COLOR], {4e710646, 2, 1, 828f0e2e}

Probably caused by : [COLOR=Red]hardware[/COLOR] ( nt!MiResolveTransitionFault+51c )

Followup: MachineOwner
---------

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

One thing is common, that is the BIOS.

BiosVendor = TOSHIBA
BiosVersion = V1.80
[COLOR=Red]BiosReleaseDate = 10/28/2009[/COLOR]

Search for any possible updates.

Taking the age of the computer in mind, One question is very important. Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

About the HDD, it is a 320 GB Western Digital. But the C drive is of 64 GB, and no other information is available. Test is using Data Lifeguard Diagnostic for Windows.

If any hardware is attached there recently, remove it; at least on a test basis.

Stress test the CPU.
Hardware - Stress Test With Prime95

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the results.

 

[luciflash]

Partial update:

Results from Prime95:
[Thu Feb 20 15:35:50 2014]
Self-test 24K passed!
Self-test 24K passed!
[Thu Feb 20 16:06:30 2014]
Self-test 24K passed!
Self-test 24K passed!
[Thu Feb 20 16:21:32 2014]
Self-test 8K passed!
Self-test 8K passed!
[Thu Feb 20 16:37:54 2014]
Self-test 32K passed!
Self-test 32K passed!
[Thu Feb 20 16:52:58 2014]
Self-test 12K passed!
Self-test 12K passed!
[Thu Feb 20 17:08:53 2014]
Self-test 20K passed!
[Thu Feb 20 17:17:54 2014]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Thu Feb 20 17:40:04 2014]
Self-test 480K passed!
Self-test 480K passed!
[Thu Feb 20 17:56:00 2014]
Self-test 128K passed!
Self-test 128K passed!
[Thu Feb 20 18:11:46 2014]
Self-test 576K passed!
Self-test 576K passed!
[Thu Feb 20 18:28:21 2014]
Self-test 160K passed!
Self-test 160K passed!
[Thu Feb 20 18:34:29 2014]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.

I ran the test three times. Once it bs during, the second it gave an error, and also the third time.
Also, I ran Intel Processor Diagnostic Tool, and it passed the tests.
I ran WD Data Lifeguard, and it passed the extended test.
I ran Speccy during the tests, and the maximum was 75 C.

I tried to update the bios (there is a newer version), but no such luck .
The laptop's battery is dead, so the normal bios approach didn't work.
I tried:
- removing the battery, and leaving it only on AC
- adding force it
- opening it with cmd, and adding force it
- making a bootable usb stick: "this file cannot run in dos mode"
I don't know what else to try.
One of my friends has the same laptop but his battery is dead also, and I don't really what to buy a new one.

I'll rerun memtest86 this night for 8 or more passes.
I'll also dismantle it and clean it. Also, the CD drive gets power, but it can't read. I think a cable is unplugged.

*Sorry about changing the OS.

Thank you.

 

[luciflash]

OK, so, i ran Memtest86 for 18 hours, 16 passes, no errors.

I set default settings on BIOS, and after this the PC kept super fast blue screening just after the windows logo.
I had to change the SATA Controller Mode from AHCI to Compatibility and the laptop started.

I attached some recent minidumps, maybe you can see something new there.

Please, help!

View attachment 308118

 

[Arc]

Nothing new. Two BSODs today, and just as previous.

[COLOR=Red]BugCheck 1000008E[/COLOR], {c0000005, 68a00, 8536c2a4, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

[COLOR=Red]BugCheck 1000008E[/COLOR], {c0000005, 9294c7d7, acbdaa6c, 0}

Probably caused by : win32k.sys ( win32k!PtInRect+3 )

Followup: MachineOwner
---------

According to Carrona.org, this BSOD is usually caused by ...
Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

And your BIOS is:

BiosVendor = TOSHIBA
BiosVersion = V1.80
BiosReleaseDate = [COLOR=Red]10/28/2009[/COLOR]

Unfortunaltey I dont know how this problem can be solved with such an old version of BIOS present. Better I ask for some more help for you.

 

[Slartybart]

Could you provide the part number for the L500? There are a few to choose from on the Toshiba site.

Do not post the serial number, only the part number.

Thanks

 

[luciflash]

Model name: L500-1EU
Part no: PSLJTE-00700YG3

 

[Slartybart]

Thanks

Product Specs: Toshiba Laptop Support homepage - Toshiba
Drivers: Toshiba Laptop Support homepage - Toshiba

Well, this is a bit odd.

There is one BIOS on the Product Drivers page
Time for an update?
and
two BIOS on the Toshiba BIOS page.
Time for an update?

Both have the same version 2.10-WIN, but the last modified date is about one year apart.
Your current BIOS from the dumps:
Bios Version = V1.80
Bios ReleaseDate = 10/28/2009

So.....

Download the BIOS from the product page: Toshiba Laptop Support homepage - Toshiba
Determine the update process using the information on this page (there are 5 possible methods, each method can be identified by the contents of the zip file).
How to update the BIOS on Toshiba notebooks

hope this helps.

What OS are you going to stick with for this exercise. It doesn't matter for BIOS but it will for other things. If you have 3 or less GB of memory, I suggest the 32-bit version.

Bill
.

edit: Great.... Toshiba is one of those OEMs that don't let links properly work - they always take you back to data entry.

I'll see if I can fix the links.

 

[Slartybart]

L500-1eu BIOS [direct download]:
http://support1.toshiba-tro.de/tedd-files2/0/bios-20100629135948.zip
06/29/2010 2.10-WIN

L500 Driver Downloads
This search is for 32 -bit Windows7 but BIOS is OS independent

This search shows both BIOS updates. I suggest the earliest one since that is what is shown on the product page. If that doesn't resolve the BSOD, then you might consider the other BIOS update. I read both descriptions and can't make a determination of the difference other than the L500 Pro is listed 1st on the 05/30/2011 2.10-WIN version.

The how-to update BIOS page is ok: How to update the BIOS on Toshiba notebooks

 

[luciflash]

Thanks for the suggestion, but unfortunately it does not work.
The Winphlash exe gives 144 error (battery below 10%). This happens on both files that you suggested (the second one looks different, but still complains about the battery).

Is there any other way to flash the bios? Can I use another program? (i have the bios.rom file) Can I change some settings on Whinphlash so that it ignores the battery?

Thank you

 

[Slartybart]

I gave you every thing I could re: Toshiba BIOS update. I do apologize, I forgot about the update complaining about the low battery.

I would try removing the battery and run on AC only first. Then try the normal BIOS update.

If you can't run on AC (odd) or the update utility still complains (also odd), then you could try the following.

There's no guarantee that this method won't complain about low battery either.

Be careful, a failed or incomplete BIOS update can 'brick' your system
>> brick = make it unusable until a good BIOS is on the machine.

The low battery condition prevented any updating, so that's a different story.

Since you're going outside 'normal' procedures, follow these instructions knowing the risks.

See if your current BIOS has an update mode
Restart the machine, enter setup
Poke around for the BIOS update option (not all have this feature)

If yours does, run it and select 'update from file'
When prompted - provide the location and name of the .rom file

i.e. C:\Toshiba2-10.rom

After this, I've exhausted what I can offer, other than get a new battery.

 

[luciflash]

Already tried the just AC method...and unfortunately it didn't work. I tried anything I could find online, but no luck.
I looked into the bios, and it doesn't have the update from file setting.

I made some calls and I found a distant relative who has a Toshiba L655 and the internet says that it has the same battery.
So after my next family visit I'll come back with an update and let you know if it solved anything.

It's safe to say that I won't recommend Toshiba laptops any time soon. They use antique parts, antique materials, and antique software

Thank you for all your help.

 

[Slartybart]

Ok, good you found a battery to try - make sure they match though (case and rating)

Too bad about the BIOS not having a 'program' mode to update BIOS - some do, some do not.

I thought I saw that you tried AC only mode, but missed it when I looked back - thanks for the refresher.

If the battery isn't charging, it might be the power brick, not the battery. See if the jack is loose... lightly jiggle the jack and see if a better connection is made to the machine.

Some shops will test your battery for free, others might charge (pardon the pun) you a small fee. Try a few places, who knows... a nice shop might even fully charge the battery if it can hold a charge.

You could also look at the wire contacts on the battery and battery compartment to see if any are bent - carefully straighten them out with a plastic 'spreader' (Bic pen cap with pocket clip or similar object).

:warn: Do NOT use anything metal :warn:

If the contacts are misaligned, and you straightened them - see if the battery will take a charge.

Other than that, we'll wait until you meet with your relative.

Good luck,

Bill
.