T500, BSODs every few days

[jeanluc]

Hello,

I got a T500 - 2081 (with XP SP2) about 2 months ago and have had several blue screens since. I haven't been able to trace it to a particular driver (I didn't install any exotic software as I'm using the laptop for programming). I've updated the BIOS and the display drivers (which I understand caused some problems) and the post-SP2 Windows patches are all up-to-date but I still got a blue screen today while the laptop was doing nothing.

The versions I have are:

BIOS Version/Date LENOVO 6FET64WW (2.12 ), 13/03/2009
ATI Driver Version 6.14.10.6879

I dumped the crash events from the system log - I am curious if anyone else has seen these.

Thanks, JL.

System log on \\MU:
[3383] System Error
Type: ERROR
Computer: MU
Time: 30/04/2009 4:15:29 PM ID: 1003
Error code 000000f4, parameter1 00000003, parameter2 86d29340, parameter3 86d294b4, parameter4 805d1650.


[3044] System Error
Type: ERROR
Computer: MU
Time: 25/04/2009 9:16:24 PM ID: 1003
Error code c0000138, parameter1 00000f21, parameter2 e3b26d00, parameter3 00000000, parameter4 00000000.


[2888] System Error
Type: ERROR
Computer: MU
Time: 24/04/2009 9:50:42 PM ID: 1003
Error code 000000f4, parameter1 00000003, parameter2 876eeda0, parameter3 876eef14, parameter4 805d1650.


[2289] System Error
Type: ERROR
Computer: MU
Time: 02/04/2009 8:38:29 PM ID: 1003
Error code 000000f4, parameter1 00000003, parameter2 86d9bda0, parameter3 86d9bf14, parameter4 805d164c.


[810] System Error
Type: ERROR
Computer: MU
Time: 07/02/2009 12:55:46 AM ID: 1003
Error code 00000077, parameter1 c0000056, parameter2 c0000056, parameter3 00000000, parameter4 01d69000.

[rkawakami]

Welcome to thinkpads.com!

What I would recommend first would be to run a memory diagnostic. memtest86+ is available here:

http://www.memtest.org/#downiso

Create the boot diskette or CD, boot the system with it and let it run for at least three complete passes through all of the tests. This will verify that your memory is working properly.

[archer6]

Hello,

I got a T500 - 2081 (with XP SP2) about 2 months ago and have had several blue screens since. I haven't been able to trace it to a particular driver (I didn't install any exotic software as I'm using the laptop for programming). I've updated the BIOS and the display drivers (which I understand caused some problems) and the post-SP2 Windows patches are all up-to-date but I still got a blue screen today while the laptop was doing nothing.

The versions I have are:

BIOS Version/Date LENOVO 6FET64WW (2.12 ), 13/03/2009
ATI Driver Version 6.14.10.6879

I dumped the crash events from the system log - I am curious if anyone else has seen these.

Thanks, JL.

System log on \\MU:
[3383] System Error
Type: ERROR
Computer: MU
Time: 30/04/2009 4:15:29 PM ID: 1003
Error code 000000f4, parameter1 00000003, parameter2 86d29340, parameter3 86d294b4, parameter4 805d1650.


[3044] System Error
Type: ERROR
Computer: MU
Time: 25/04/2009 9:16:24 PM ID: 1003
Error code c0000138, parameter1 00000f21, parameter2 e3b26d00, parameter3 00000000, parameter4 00000000.


[2888] System Error
Type: ERROR
Computer: MU
Time: 24/04/2009 9:50:42 PM ID: 1003
Error code 000000f4, parameter1 00000003, parameter2 876eeda0, parameter3 876eef14, parameter4 805d1650.


[2289] System Error
Type: ERROR
Computer: MU
Time: 02/04/2009 8:38:29 PM ID: 1003
Error code 000000f4, parameter1 00000003, parameter2 86d9bda0, parameter3 86d9bf14, parameter4 805d164c.


[810] System Error
Type: ERROR
Computer: MU
Time: 07/02/2009 12:55:46 AM ID: 1003
Error code 00000077, parameter1 c0000056, parameter2 c0000056, parameter3 00000000, parameter4 01d69000.

---------------------------
Greetings & Welcome to the Forum.

I have experienced a near identical issue on one of my T500's (2081-CTO). This ThinkPad is 15 weeks old, running XP SP2 updated.

With mine it would happen while at idle with Maya, when in FireFox, or while in Outlook. However it was random enough to make it difficult to establish a pattern.

I updated the BIOS & ATI drivers. According to my notes the BIOS version is the same as yours.

I just retrieved the error codes I saved from my notes.

[3383] System Error
Type: ERROR
Computer: MU
Time: 27/03/2009 2:31:42 PM ID: 1003
Error code 000000f4, parameter1 00000003, parameter2 86d29340, parameter3 86d294b4, parameter4 805d1650.


[3044] System Error
Type: ERROR
Computer: MU
Time: 20/03/2009 1:27:42 PM ID: 1003
Error code c0000138, parameter1 00000f21, parameter2 e3b26d00, parameter3 00000000, parameter4 00000000.

After approx 4 BSOD's I decided to take action. Then after updating BIOS & drivers, there was no change, I experienced approx 6 more events. So I decided to wipe the drive and start fresh as it came to me. After I returned it to that state, I've not had a single BSOD, or any other issue. In retrospect, if memory serves me correctly these did not occur until after I did the OS updates. So this time I decided to _not_ perform the updates and all is well.

So that's my experience.

Cheers...

[Marin85]

So, it seems the problem could be in the ATI drivers (if memtest turns OK). Did you update from Lenovo, windows update or some other source (like modded drivers)? Unfortunately, I don´t have switchable graphics, but I really wonder whether some of the reported issues with switchable graphics could be solved with modded drivers. (I guess though not every such problem is related to the ATI driver only.)

[jeanluc]

rkawakami: I will run memtest over night and post the results, thank you.

archer6: So you stayed at SP2? Like in your case, the errors appear random. I've also recently disabled the Active Protection System because I've also system freezes of 1-2 minutes in which nothing moved (not even the mouse cursor), but everything would work suddenly again after that time. I don't know if the problems are related and because the disabling of APS was done only a few days ago, it's too early to say whether it made a difference.

Marin85: The drivers are from ATI.

[Marin85]

If memtest doesn´t turn up any problems and the BSODs persist, you may then want to consider ATI drivers from Lenovo. They might be "slightly" outdated compared to the latest ATI driver releases and may also not enjoy top performance, but they always seem to run stable, at least in my experience.

[jeanluc]

Marin85: Memtest ran 23 passes of all tests overnight without any error. I will try the Lenovo drivers, a slight loss of performance is ok as I'm not doing any heavy graphic stuff. Thanks.

[deforest]

If you want, you can use windbg to analyze your minidumps, if you have them enabled and saved. Then you can see if there is a particular module/dll that is the culprit. Instructions for doing this can be found at http://forums.majorgeeks.com/showthread.php?t=35246

The main thing is you want to see if there is a common module/dll that is responsible. And if your little technical you look at the call stack to see if you see a pattern going on there, i.e. what type of activity is going on, sometimes the function names may be useful for that, other times they may be part of the undocumented microsoft api so your milage may vary on this aspect.

[archer6]

<snip>archer6: So you stayed at SP2? Like in your case, the errors appear random. I've also recently disabled the Active Protection System because I've also system freezes of 1-2 minutes in which nothing moved (not even the mouse cursor), but everything would work suddenly again after that time. I don't know if the problems are related and because the disabling of APS was done only a few days ago, it's too early to say whether it made a difference.

I tried SP3 as well, however it made things worse and created some random files that served no purpose. So I went back to SP2 exactly as it came from Lenovo with no updates and my computer is trouble free at this point. It seems the older drivers are stable whereas the new ones are not.

Cheers...

[jeanluc]

deforest: excellent advice, I installed Windbg and checked all the 6 minidumps I have.

The earliest 2 dumps were caused by memory corruption (with the possible causes listed in the first output below). One dump by Probably caused by : ntkrpamp.exe ( nt!KiFastCallEntry+fc ) and the remaining 3 dumps by the hard disk (second output below).

The other day I ran a check disk with the option to find bad sectors, but it didn't find any. I can try again; if still nothing is found, maybe it's the controller, not the HDD itself.

I think I need to contact Lenovo. Thanks everyone for all suggestions!

Code: Select all

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 77, {c0000056, c0000056, 0, 1d69000}

Probably caused by : memory_corruption ( nt!MiMakeOutswappedPageResident+4f5 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in.  Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found.  Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED)  normally indicates
the data could not be read from the disk due to a bad
block.  Upon reboot autocheck will run and attempt to map out the bad
sector.  If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked.  See the knowledge base article on SCSI termination.
Arguments:
Arg1: c0000056, status code
Arg2: c0000056, i/o status code
Arg3: 00000000, page file number
Arg4: 01d69000, offset into page file

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000056 - A non close operation has been requested of a file object with a delete pending.

BUGCHECK_STR:  0x77_c0000056

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from 80511da7 to 804f9f0d

STACK_TEXT:  
ba52fcdc 80511da7 00000077 c0000056 c0000056 nt!KeBugCheckEx+0x1b
ba52fd50 80512c19 c04ebb48 00066afa 00000001 nt!MiMakeOutswappedPageResident+0x4f5
ba52fd8c 8053fb56 008179a0 00000000 8aacf318 nt!MmInPageKernelStack+0x149
ba52fda4 80540026 85a57080 805cec9e 00000000 nt!KiInSwapKernelStacks+0x16
ba52fdac 805cec9e 00000000 00000000 00000000 nt!KeSwapProcessOrStack+0x7c
ba52fddc 80545ebe 8053ffaa 00000000 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiMakeOutswappedPageResident+4f5
80511da7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiMakeOutswappedPageResident+4f5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  48a3f869

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x77_c0000056_nt!MiMakeOutswappedPageResident+4f5

BUCKET_ID:  0x77_c0000056_nt!MiMakeOutswappedPageResident+4f5

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

Code: Select all

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, 86d29340, 86d294b4, 805d1650}

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : hardware_disk

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 86d29340, Terminating object
Arg3: 86d294b4, Process image file name
Arg4: 805d1650, Explanatory message (ascii)

Debugging Details:
------------------

unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase

PROCESS_OBJECT: 86d29340

IMAGE_NAME:  hardware_disk

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: 00000000 

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  ba2279d8 -- (.exr 0xffffffffba2279d8)
ExceptionAddress: 7c92c74d
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 00000000
   Parameter[1]: 7c99c3d8
   Parameter[2]: c0000056
Inpage operation failed at 7c99c3d8, due to I/O error c0000056

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000006 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The required data was not placed into memory because of an I/O error status of "0x%08lx".

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  7c99c3d8

EXCEPTION_PARAMETER3:  c0000056

IO_ERROR: (NTSTATUS) 0xc0000056 - A non close operation has been requested of a file object with a delete pending.

EXCEPTION_STR:  0xc0000006_c0000056

FAULTING_IP: 
+fc
7c92c74d ??              ???

BUGCHECK_STR:  0xF4_IOERR_C0000056

FOLLOWUP_IP: 
+2cb952f0162dfdc
7c99c3d8 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

STACK_COMMAND:  kb

FAILURE_BUCKET_ID:  0xF4_IOERR_C0000056_IMAGE_hardware_disk

BUCKET_ID:  0xF4_IOERR_C0000056_IMAGE_hardware_disk

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

[deforest]

These 2 seems to implicate the drive.

There are three things I would try.

Run the bios diagnostic test from the bios boot screen
Obtain disk test from hard drive manufacture, I use hitachi so they have a hard drive fitness test utility that you can run.
Switch disk mode, i.e. switch disk mode to compatible in bios.

One other thing I tought of is to get some utility and look at your disk smart data, I have speedFan which has this ability, but other tools have it as well, and see if anything looks extra ordinary.

[archer6]

Lenovo system tool box has a very good disk checking utility, it's preloaded on your machine as well.
Start / All Programs / Lenovo Services / Lenovo System Toolbox

Cheers...

[nickv]

Thank goodness someone else is getting this too...I have had a T500 for several months and been suffering all sorts of BSODs - mostly codes: x00000077, sometimes x0000007A . Lenovo support have been relatively unhelpful: I've had the memory changed, the motherboard changed, sent in lots of mini dumps and event logs, and the best they could come up with was "please update some drivers" and "it looks you are running something called VMware - can you uninstall it?"...which I can't and won't - of the four dumps I'd sent in at that point 2 mentioned some VMware module and 2 didn't - so why is VMware the culprit....?

Anyway, I figured out how to get a kernel dump out of Windows and will sent that to Lenovo support...the error exactly matches the one.

If I should get a useful response from them I'll post it here.