Thinkpad 600X Crash Problem (con't)

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
(Forgive me if this post appears twice on the group. For some reason my
first attempt yesterday didn't appear.)

I wrote to this group back in July regarding a crashing problem I am
having with a Thinkpad 600X.

First, here are the specs on my machine:
600X (Type 2645-9ZU, PIII 650MHz speedstep)
512MB additional RAM, IBM labled (ie: two 256MB DIMMS)
DVD player, 3Com network card
BIOS has been upgraded to latest version

The problem I am having is that about once a week I experience a
complete crash; the screen turns blue for a half a second with a few
lines of text in the upper left, then the initial boot-up screen
appears with words "IBM" and "Thinkpad" in opposite corners of the
screen. At this point it doesn't actually re-boot, it just stays on
this initial boot-up screen. I have to turn it off off then on again to
initiate a re-boot.

I thought the problem might be bad RAM so I ran Memtest86+ once
overnight (6 complete passes total through the memory). No errors were

One of the people who responded back in July (GomJabbar) suggested that
I press F8 on boot-up and select 'Do not restart on system failure'
(see copied post below). However, I don't see this option when I press
F8. I am running Windows 2000. Here is what I see after pressing F8:

"Windows 2000 Advanced Options Menu
Please select and option.

 Safe Mode
 Safe Mode with Networking
 Safe Mode with Command Prompt
 Enable Boot Logging
 Enable VGA Mode
 Last Known Good Configuration
 Directory Services Restore Mode (Windows 2000 Domain Controllers Only)
 Debugging Mode
 Boot Normally

Which one of these should I select so that I can read the error message
the next time I see the BSOD?

Any suggestions are welcome.


---------- Forwarded message ----------
From: GomJabbar
Date: 12 Jul 2005 10:03:35 -0700
Subject: Re: Thinkpad 600X Crash Problem

I used Windows 2000 on a 600E in the past with excellent results - well
at least for a Microsoft product ;).

You should press F8 at the beginning of the boot sequence, and when you
get to the screen that has the Safe Mode option, select 'Do not restart
on system failure' (worded something like that).  Now the next time
your 600X crashes, you'll get the Blue Screen Of Death (BSOD).  There
should be an error message on the screen that may give you a clue to
what's going on.

An anecdote:
I recently loaded some software, did a Windows update, and a Norton AV
update.  I rebooted to do a virus scan in Safe Mode, and as the OS was
booting up, it suddenly restarted.  I could not get to Safe Mode even
after several tries.  The computer would boot up normally however.  I
was shocked.  I thought if the computer would boot up at all, it would
be in Safe Mode.  Anyway I did the above and got the error message on
the screen.  I Googled the error message, and it gave me a clue that it
was one portion of a software package I had just installed.  I
uninstalled just that one portion, and then I was able to boot up in
Safe Mode again.

Re: Thinkpad 600X Crash Problem (con't)

On 9 Oct 2005 07:37:55 -0700, wrote:

Quoted text here. Click to load it

With Windows 2000 and XP, you can turn off the automatic restart from
the Control Panel. Control Panel -> System -> Advanced -> Startup and
Recovery -> Settings. Uncheck the box to automatically restart. (What
I described is for XP Pro. It may be somewhat different for Window
2000 but I don't have a Windows 2000 system handy to check. But this
is the general idea: hunt around a bit and you will find the box to
uncheck.) You need to reboot for setting to take effect.
- -
  Gary L.
  Reply to the newsgroup only

Re: Thinkpad 600X Crash Problem (con't)

On Sun, 09 Oct 2005 22:48:32 GMT, Gary L. wrote:

Quoted text here. Click to load it

That is correct for W2K as well.

I had the same problem with my 600 X when I first
started using a D-link wifi card. The European model
is labeled DWL-G650+  (D-link has a record of using
the same name for different hardware in US and Europe.)

Their first drivers for that card was really buggy and caused
many crashes, but newer drivers sorted it out for me.

If the O P use any such "external" hardware it may be
a good idea to look for the problem there. The 600 X
may well be the best laptop ever built, and W2K fits
it so perfectly that you would think they were designed
for each other.

Stockholm /

Re: Thinkpad 600X Crash Problem (con't)

Thanks to both of the posters for the advice.

Regarding the ethernet card, mine is an older 3Com wired card
(megahertz 3CXFE575BT), not wireless. I used it for a year and a half
with a 600E also with Win 2000 with no problems. But the 600X has a lot
of hardware differences from the 600E so it could be the root of
problem. I'll keep it in mind.

Personally, I liked the 600E a little better. The screen was brighter
(I think they dimmed it a bit on the 600X to conserve battery life),
the keyboard had a softer feel, and the build quality of the case
seemed better. For example there seems to be a slight difference in
shade in the black color used for the plastic cover doors for the
various connection ports and the black color for the metal case of the
computer. With the 600E the shade of black was more consistant. But I
like the 600X anyhow for the better performance and the same simple
square shape. What a classic design!

-Jonathan wrote:
Quoted text here. Click to load it

Re: Thinkpad 600X Crash Problem (con't)

Gary L. wrote:
Quoted text here. Click to load it

Don't know if you are having the same issue as I had but I also the
same model in similar configuration.  At first I thought I was
experiencing RAM issues but BIOS diagnostics kept turning up okay.
Unlike you I kept getting NTKERNEL exception messages.   I looked up
some of these messages and they seemed to indicte corruption in the
running OS (usually RAM or HD).  I replaced the hard drive (20GB IBM
(Hitachi) Travelstar) with a 10GB IBM and reinstalled.  Things worked
smoothly with the new drive.  Just to be sure I ran Drive Fitness Test
on the old HD ( ).  Turns
out the drive was bad.  Hope this helps.

Re: Thinkpad 600X Crash Problem (con't)

I was having the same problem with my 600X and I initially thought I
was going to need to test all the RAM, especially since it got to the
point where my computer would not turn on.  After opening the case and
reseating the RAM I had in there, I havn't had any problems, though
it's only been a few weeks.  You might pull out your chip(s) and give
that a whirl.

Re: Thinkpad 600X Crash Problem (con't)

I switched around the RAM chips between the two slots about a week ago
and so-far no crashes. However, the problems has been very sporatic,
sometimes not crashing for a couple weeks. I'll have to give it a month
to have a good level of confidence that the problem is fixed. wrote:
Quoted text here. Click to load it

Re: Thinkpad 600X Crash Problem (con't) wrote:
Quoted text here. Click to load it

Same here with my 600E (which has two 128MB sticks). For several weeks
my Win2k partition occasionally gave me blue screens, particularly when
ram usage hit a "delicate" spot of 180-220MB. After reseating the RAM,
no problems (that was over 6 months ago).

Same thing can happen with desktops. Once a year or so, it doesn't hurt
to remove and reseat the ram in your system, just to "flex" those ram
slots a little. And with desktops, the same can be done with the CPU,
drive and port connectors, and expansion cards. You can also use the
opportunity to remove the accumulated dust (which can hamper cooling).

Re: Thinkpad 600X Crash Problem (con't)

I had another crash today.

But since I had cleared the option in Windows to automatically reboot
on system failure I was able to read and copy down the jibberish on the
blue screen of death (thanks to Gary L's advice).

Here is what the jibberish said.

<start quote>

*** STOP: 0x00000050 (0xFC3BA8A1,0x00000000,0xBC94116C,0x00000000)

*** Address BC94116C base at BC93E000, Date Stamp 41afde9e -

Beginning dump of physical memory
Physical memory dump complete. Contact your system administrator or
technical support group.

<end quote>

I really have no idea what all of this jibberish means. The only clue I
can think of is related to the fact that the file name Fastfat.SYS is
mentioned. Since FAT is a type of hard drive format, I am thinking that
perhaps the problem might have something to do with the hard drive
(although mine is NTFS formatted, not FAT). Also a previous poster
(Adrios) mentioned he has a somewhat similar problem that turned out to
be a bad hard drive.

Does anyone here have any advice on what the problem might be and what
the next step shoud be towards solving it?

-Jonathan wrote:
Quoted text here. Click to load it

Re: Thinkpad 600X Crash Problem (con't)

In comp.sys.laptops wrote:
Quoted text here. Click to load it

"gibberish"  (n : unintelligible talking [syn: ]).

Quoted text here. Click to load it

Yes, well, that's likely a fault accessing address 0x50. No
surprise, since the zeroth page (where that address is sited) is
intended to be off limits! An access likely means that some program
pointer is null, and the program is looking at offset 0x50 in some
large struct that has a null address.

I suppose the stuff in brackets is a bit of the stack. Those would
be addresses of routines, I suppose.

Quoted text here. Click to load it

Well, it seems to associate those addresses with routines from some
file. That'so obviously a  file system driver (or accelerator, who
knows!), so your driver has a bug.

Quoted text here. Click to load it

Well? Where?

Quoted text here. Click to load it

Go ahead.

Why? I've just guessed, and surely you can do as well as I can! You
have windows experience, and I don't.

Quoted text here. Click to load it

It could be anything. Do what the message aid and ask your technical
support or sysadmin for help. There will be data in the core dump that
can help them.

Quoted text here. Click to load it

Do what the message says.  Though the problem surfaced in a driver ,
it could be a hardware fault, memory fault, or anything. It could be
corruption in the driver file itself. It could be a corruption caused
by a virus. Check all those possibilities.


Re: Thinkpad 600X Crash Problem (con't)

Peter T. Breuer wrote:
Quoted text here. Click to load it

Damn! Spelling mistake! My old nemisis, strikes again!

Quoted text here. Click to load it

I just had another crash today with a different file reported. I didn't
copy the file name down though. So it seems the problem is probably not
related to a specific file.

Quoted text here. Click to load it

In the toilet maybe. Any suggestions?

Quoted text here. Click to load it

THIS GROUP is my technical support.

Quoted text here. Click to load it

But I can't even spell, how do you expect me to know what 0xFC3BA8A1

Quoted text here. Click to load it

Whew, that's a relief. I was thinking it was going to be something

Thanks for the advice.


Re: Thinkpad 600X Crash Problem (con't)

Quoted text here. Click to load it

I know exactly what you mean.

I would suspect some sort of hardware problem.  Intermittant problems
are the hardest to troubleshoot.  You could try removing and
reinstalling the RAM memory to see if that clears things up.  Same
thing with the hard drive and optical drive.  You could also download
and run Sysoft Sandra benchmarking software that can really tax your
machine and help prove that it is a hardware issue [AFAIK it is still
available for download].  If you can get the software to test each
hardware system of the laptop basically independently, it could narrow
down the area of the problem.  [It's been awhile since I ran Sysoft
Sandra, so I don't know it's capabilities too well].  Hope this helps.

Re: Thinkpad 600X Crash Problem (con't)

On 29 Oct 2005 23:23:16 -0700, GomJabbar wrote:

Quoted text here. Click to load it

I have a bad memory chip that causes the same
behaviour when I try to use it. I would suggest
thet the O P remove the memory sticks and try
to run the machine on only its internal 64 MB's.

It will be slow of course but still doable. If it
seems stable with that reinsert one stick
and try again.


Re: Thinkpad 600X Crash Problem (con't)

A quick google for PAGE_FAULT_IN_NONPAGED_AREA found this result on the
MS site:

"This problem occurs because the driver for the USB Universal Reader
from Lexar Media, Inc is not compatible with Windows XP."

Further reading point to other possible causes but I guess its a
starting point.

Re: Thinkpad 600X Crash Problem (con't)

Went back to your original July post to confirm that you reformatted
the HD and did fresh install of Windows 2000.  This is right approach
but sometimes doesn't catch everything.

Your initial take was that you had bad RAM but most of your tests seem
to indicate that it was clean.  The problem may not be in physical RAM
but in the virtual RAM swapfile on the disk.  I've had more time to go
back and look at my old HD that wasn't working.  It did have a lot of
bad sectors but the data was intact for the most part.  I'm guessing
that if you have similar issue to me then your swapfile is corrupt.
This explains why you get a different page fault error each time.  If
the swapfile is corrupt on the disk then when it pages it in and tries
to read the address location it bombs (BSOD).

If you still have the HD from the 600E you may want to try using it
with a fresh Windows 2000 install.  Then you can run diagnostics
against the original 600X drive.  One of the early posts mentions the
ultimate boot CD ( ).  The
tool that I mentioned for IBM-Hitachi HD - Drive Fitness Test is on
there.  If your HD manufacturer is someone else (Maxtor, Seagate,
Western-Digital, Samsung, etc.) they are also there.  These tools also
include utils to fix the problem.  The only manufacturer that I know
that does not provide these tools is Toshiba but you might be able to
use one of the other third party tools.

Regarding the formatting; if you used Windows to format the drive it
sometimes doesn't catch all the potential hardware issues.  The above
mentioned tools are better for validating health.  There are also other
third party monitoring tools that will run in Windows such as HDDLife.

Hope this helps,
Atrios wrote:
Quoted text here. Click to load it


Site Timeline