Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD on older laptop


  • Please log in to reply
11 replies to this topic

#1 stipekc

stipekc

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 29 March 2010 - 09:58 AM

The laptop is an IBM Thinkpad T20 2648. Running on XP. Starting about a month ago I started receiving the BSOD's. 2 of which I recall happened while on the internet (home improvement webpage and facebook). Wanting some help in resolving this issue. We'll start with the bluescreen view report.

==================================================
Dump File : Mini032710-01.dmp
Crash Time : 3/27/2010 9:02:57 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x80580fd8
Parameter 3 : 0xf4811aa4
Parameter 4 : 0x00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+6c14
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini032710-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini032310-01.dmp
Crash Time : 3/23/2010 6:37:55 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x100000d1
Parameter 1 : 0x00000020
Parameter 2 : 0x000000ff
Parameter 3 : 0x00000001
Parameter 4 : 0x82154e49
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini032310-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini031810-01.dmp
Crash Time : 3/18/2010 8:57:16 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x00013e85
Parameter 3 : 0x00000004
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5c826
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini031810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini022810-01.dmp
Crash Time : 2/28/2010 12:08:05 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001902fe
Parameter 2 : 0xf4d89794
Parameter 3 : 0xf4d89490
Parameter 4 : 0xf83d07a8
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+257a8
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini022810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini022710-01.dmp
Crash Time : 2/27/2010 11:10:11 AM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 0x00000005
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+2404a
File Description : NT File System Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2111)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini022710-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

Thank you in advance for your time.

BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 56,127 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:12 PM

Posted 29 March 2010 - 12:07 PM

Hi :thumbsup:.

Is the system time accurately reflected in the BIOS?

Among the errors you list, I see two indicating NTFS problems.

The first thing I would try is run chkdsk /r command.

Start/Run...type chkdsk /r (space between k and /) and hit Enter.

Type Y in response to onscreen query and hit Enter.

Reboot the system, the command will execute and then boot into XP on completion.

If any error messages appear during command processing or it is unable to complete...please write down message and post here.

Louis

Edited by hamluis, 29 March 2010 - 12:07 PM.


#3 stipekc

stipekc
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 29 March 2010 - 11:33 PM

Ran chkdsk /r and it completed successfully. There was a screen after the scan but it quickly restarted and didn't catch what it said if it was any significance. i checked the system event log and no errors. Here is a BSOD i received today.

==================================================
Dump File : Mini032910-01.dmp
Crash Time : 3/29/2010 8:19:24 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x000c8313
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804e7930
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+10930
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5913 (xpsp_sp3_gdr.091208-2036)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\minidump\Mini032910-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:04:12 AM

Posted 30 March 2010 - 10:03 AM

I would also run a memtest

#5 stipekc

stipekc
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 30 March 2010 - 10:51 PM

Ran memtest86+ v4.00 and received two errors.
one occured at address 0000c05cda8 with 192.3 MB and the other at address 0001005cd88 with 256.3 MB.
Both stated good at ffffdfff and bad at ffffffff with err-bits 00002000.
I will run more passes time permitting to see if anything else comes up. Hardware is Pentium III 800 MHz and Intel i440BX chipset.
The RAM is 2x256 MB Samsung (which is max) that is said to be compatible. The specifics are 256 MB, PC100, 100Mhz, 144 pin Sdram for laptops that can accept pc100 sdram 16 chips double sided, 8 chips each side, low density, CL2 Non ECC - Non Registered - Non Parity - Unbuffered. RAM was upgraded mid January.

May be a separate issue but the laptop will also randomly turn off. Doesn't go through shut down just BAM -off. This has happened since I acquired it about 6 months ago. Replaced battery but it still happens even when on AC power. Could it be shutting down from getting to hot? Again, may be a differnt issue for another time.

What is the memtest telling us?

#6 hamluis

hamluis

    Moderator


  • Moderator
  • 56,127 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:11:12 PM

Posted 31 March 2010 - 08:13 AM

Any error reflected during Memtest...indicates a problem with the functioning of the RAM. One is as good as a hundred.

You may want to review the following for methodology that can be used to determine just where the problem may lie, Icrontic » Diagnose with Memtest86+ - http://icrontic.com/articles/diagnose_with_memtest86.

Louis

#7 Ken-in-West-Seattle

Ken-in-West-Seattle

  • Members
  • 518 posts
  • OFFLINE
  •  
  • Local time:09:12 PM

Posted 31 March 2010 - 08:18 AM

Laptop memory usually goes bad a little at a time rather than all at once. Replace it while you still can buy it.

#8 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:04:12 AM

Posted 31 March 2010 - 12:01 PM

Hopefully the errors reflected during the test is just the RAM module and not the ram slot.

#9 stipekc

stipekc
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 01 April 2010 - 09:49 AM

Ran Memtest using old 128 MB RAM along with a 256 MB and received a few more errors. So i started from the beginning starting with the 128 MB sticks that were replaced because i wan't having issues with it before other than being slow.

Ran it in each slot and no errors. Ran other one no errors.

Ran each 256 MB stick individually and no errors.

Ran both sticks together again and no errors (3 passes which takes some time)

Ran test 2 with ffffffff pattern where the errors occurred before and after about a dozen passes...nothing. Maybe thats not how it works but now I can't get any errors. Unless they are still starting to fail but for right now are working fine if that makes sense.

Could the CMOS battery be the cause as well as the reason for randomly turning off which it did once during the test after the errors occurred.

I could put back in the old RAM to see if any more BSOD's occur but that's going to be frustrating using it with the slow speed.

Not positive RAM is the issue or what to try next?

#10 stipekc

stipekc
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 01 April 2010 - 09:52 AM

Forgot in the last post one of the slot clips that hold the stick in sometimes doesn't hold it in so the stick will pop up and possibly be touching the cover. Could this cause any issues or shorts?

#11 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:04:12 AM

Posted 01 April 2010 - 12:52 PM

Forgot in the last post one of the slot clips that hold the stick in sometimes doesn't hold it in so the stick will pop up and possibly be touching the cover. Could this cause any issues or shorts?



That can cause issues.

#12 stipekc

stipekc
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:11:12 PM

Posted 09 April 2010 - 08:26 AM

Made sure RAM sticks are secure and have not had any BSOD's reoccur yet. If only it will be that simple.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users