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

Laptop that goes to a blue screen on start up


  • Please log in to reply
16 replies to this topic

#1 dcmike

dcmike

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:09:00 AM

Posted 12 January 2012 - 05:28 PM

I have a CF-50 Tough book with Windows XP. When I start the computer it will go to a blue screen after I logged on and have been on the computer for a couple minutes. Then the duration of time on the computer and going to a blue screen gets shorter. The computer then automatically starts back up and tries to reboot. The last time it did this the computer did a disk check and it came back as ok. I can hear the hard drive running on start up but not always after that.

I am not sure if this is a hard drive problem or a virus or some something else. It also started this after I used the computer at work and they have a free wifi in the building. Any help would would be appreciated.

BC AdBot (Login to Remove)

 


#2 Allan

Allan

  • BC Advisor
  • 8,644 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:00 AM

Posted 12 January 2012 - 05:45 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#3 mark1956

mark1956

  • Security Colleague
  • 271 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Spain
  • Local time:02:00 PM

Posted 12 January 2012 - 06:00 PM

If the hard drive stops the system would crash. The symptoms you have described sound like overheating as once everything is warmed up, on the next reboot, it takes less time to reach the temperature that causes the BSOD.

I'm not sure why the PC would be doing a disc check though as this would usually only happen if it is detecting errors, too much heat could be a contributory factor.

You could start by getting a can of compressed air from a computer store and blowing it through all the vents, you might be surprised by how much dust comes out.

Have a good listen to it when you switch it on and see if you can detect if the fan is running, feel the vents underneath to see if there is any air blowing out.

Let us know how you get on.

Edited by mark1956, 12 January 2012 - 06:03 PM.


#4 dcmike

dcmike
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:09:00 AM

Posted 12 January 2012 - 06:07 PM

Ok thanks.

The file you asked for.

Attached Files

  • Attached File  BSOD.txt   58.06KB   11 downloads

Edited by hamluis, 12 January 2012 - 07:09 PM.


#5 mark1956

mark1956

  • Security Colleague
  • 271 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Spain
  • Local time:02:00 PM

Posted 12 January 2012 - 06:25 PM

I didn't think 2 minutes of up time was enough to even locate and post the minidump files or I would have asked for them.

The errors would suggest a memory fault and possibly a problem with the hard drive which would explain disk check running at start up.

Start with this memory test and if that comes up clean continue with the hard drive diagnostics.

Preliminary checks
You should first check the model of RAM stick that you have on the manufacturers site for the recommended voltage setting and then make sure it is set correctly in the PC's Bios. An incorrect voltage setting may be the reason for your problems so test the PC's performance again if the voltage was incorrect.

Errors can also be caused by dirty contacts, mismatched sticks or using them in the wrong slots. Check all sticks are the same make and specification, check the motherboard manual for the correct slots to use. Remove all the sticks and clean the contacts with a soft pencil eraser and blow out the slots with a can of compressed air.

Download Memtest86+ from here

When the download is complete right click the file and select Extract Here and burn the image to a CD.

In windows 7 right click the extracted file, select Open With, then select Windows Disc Image Burning Tool then follow the prompts. For all other versions of windows (if you do not have an ISO burner) download this free software. ImgBurn
Install the program and start the application. Select the top left hand option to burn image file to disk and then on the next window click on the small yellow folder icon and browse to the ISO file you have downloaded. Then click on the two grey discs with the arrow in between (bottom left) and leave it to complete the operation.

Testing
Boot the PC into the Bios setup and set the CD/DVD drive to 1st in the boot sequence. Insert the disk in the drive then reboot and the disc will load into dos. Leave the test to run through at least 8 cycles or until it is showing some errors. If errors show in the test, remove all but one of your RAM sticks and repeat the test on each stick until you find the one that is faulty. This is a long slow test and should ideally be run overnight.

The memtest will not be 100% accurate but should easily detect any major faults.

IMPORTANT
Always disconnect your PC from the mains supply when removing Ram sticks and earth your hands to discharge any static electricity to avoid damage to sensitive components. If performing this test on a laptop PC you should also remove the battery before removing or replacing the RAM sticks.

Identify the make of your hard drive and then use one of the links below to get the manufacturer's diagnostics for ISO (CD) not the one for Windows.

When the download is complete right click the file and select Extract Here and burn the image to a CD.

In Windows 7 right click the extracted file, select Open With, then select Windows Disc Image Burning Tool then follow the prompts. For all other versions of windows (if you do not have an ISO burner) download this free software. ImgBurn
Install the program and start the application. Select the top left hand option to burn image file to disk and then on the next window click on the small yellow folder icon and browse to the file you have downloaded from the links below. Then click on the two grey discs with the arrow in between (bottom left) and leave it to complete the operation.

Boot the PC into the Bios setup and set the CD/DVD drive to 1st in the boot sequence. Insert the disk in the drive then reboot and the disc will load into dos.

Excelstore Use EStest CD image
Hitachi/IBM Use the Drive Fitness Test - CD Image.
Seagate, Samsung, Maxtor & Quantum Follow links for SeaTools
Western Digital

Toshiba/Fujitsu
If you have a Toshiba/Fujitsu hard drive I would suggest the use of the diagnostics from the Seagate link as this will work on all makes of drive and on any OS.


Edited by mark1956, 12 January 2012 - 06:27 PM.


#6 dcmike

dcmike
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:09:00 AM

Posted 12 January 2012 - 06:35 PM

Mark1956,

Allan asked for the minidump files.

#7 Allan

Allan

  • BC Advisor
  • 8,644 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:00 AM

Posted 12 January 2012 - 06:42 PM

I asked that you post the files. I'll do that for you

Dump File : Mini011212-06.dmp
Crash Time : 1/12/2012 4:50:42 PM
Bug Check String : DRIVER_CORRUPTED_EXPOOL
Bug Check Code : 0x100000c5
Parameter 1 : 0x00000004
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x8054b71a
Caused By Driver : NDIS.sys
Caused By Address : NDIS.sys+15f10
File Description : NDIS 5.1 wrapper driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-0852)
Processor : 32-bit
Crash Address : ntoskrnl.exe+7471a
Stack Address 1 : NDIS.sys+15f10
Stack Address 2 : NDIS.sys+17d4b
Stack Address 3 : NDIS.sys+1ae9f
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011212-06.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini011212-05.dmp
Crash Time : 1/12/2012 4:40:33 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0xed5de563
Parameter 3 : 0xed3a3a3c
Parameter 4 : 0x00000000
Caused By Driver : ipfltdrv.sys
Caused By Address : ipfltdrv.sys+6563
File Description : IP FILTER DRIVER
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.0 (xpclient.010817-1148)
Processor : 32-bit
Crash Address : ipfltdrv.sys+6563
Stack Address 1 : ipfltdrv.sys+8fa
Stack Address 2 : ipfltdrv.sys+9c4
Stack Address 3 : ntoskrnl.exe+c807
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011212-05.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini011212-04.dmp
Crash Time : 1/12/2012 4:35:51 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054c139
Parameter 3 : 0xede079ac
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75139
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntoskrnl.exe+75139
Stack Address 1 : ntoskrnl.exe+7511e
Stack Address 2 : ntoskrnl.exe+b7ae4
Stack Address 3 : ntoskrnl.exe+95ff6
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011212-04.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini011212-03.dmp
Crash Time : 1/12/2012 4:35:01 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054bc34
Parameter 3 : 0xf79ef890
Parameter 4 : 0xf79ef58c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74c34
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntoskrnl.exe+74c34
Stack Address 1 : ntoskrnl.exe+95f57
Stack Address 2 : ntoskrnl.exe+95d19
Stack Address 3 : ntoskrnl.exe+95ff6
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011212-03.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini011212-02.dmp
Crash Time : 1/12/2012 4:34:09 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054c007
Parameter 3 : 0xedb27418
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+75007
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntoskrnl.exe+75007
Stack Address 1 : ntoskrnl.exe+7511e
Stack Address 2 : win32k.sys+2a50
Stack Address 3 : win32k.sys+5731
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011212-02.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini011212-01.dmp
Crash Time : 1/12/2012 4:13:24 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xedbffffc
Parameter 2 : 0x000000ff
Parameter 3 : 0x00000000
Parameter 4 : 0x804db973
Caused By Driver : win32k.sys
Caused By Address : win32k.sys+2767
File Description : Multi-User Win32 Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6178 (xpsp_sp3_gdr.111123-1620)
Processor : 32-bit
Crash Address : ntoskrnl.exe+4973
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini011212-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini010812-01.dmp
Crash Time : 1/8/2012 12:42:38 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0xc039eda4
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x804e8fd9
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+11fd9
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntoskrnl.exe+11fd9
Stack Address 1 : ntoskrnl.exe+a72b
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini010812-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini121811-06.dmp
Crash Time : 12/18/2011 1:42:49 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001902fe
Parameter 2 : 0xed753570
Parameter 3 : 0xed75326c
Parameter 4 : 0xf73c2295
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+27b4e
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
Crash Address : ntoskrnl.exe+5c846
Stack Address 1 : Ntfs.sys+dff0
Stack Address 2 : Ntfs.sys+546d4
Stack Address 3 : ntoskrnl.exe+c807
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121811-06.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini121811-05.dmp
Crash Time : 12/18/2011 1:39:50 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x1000000a
Parameter 1 : 0x00000004
Parameter 2 : 0x000000ff
Parameter 3 : 0x00000001
Parameter 4 : 0x804db355
Caused By Driver : sr.sys
Caused By Address : sr.sys+d000
File Description : System Restore Filesystem Filter Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Crash Address : ntoskrnl.exe+4355
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121811-05.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini121811-04.dmp
Crash Time : 12/18/2011 1:37:42 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 0x001902fe
Parameter 2 : 0xedbbf518
Parameter 3 : 0xedbbf214
Parameter 4 : 0x8054bf8f
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+dff0
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
Crash Address : ntoskrnl.exe+5c846
Stack Address 1 : Ntfs.sys+dff0
Stack Address 2 : Ntfs.sys+31033
Stack Address 3 : ntoskrnl.exe+c807
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121811-04.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

==================================================
Dump File : Mini121811-03.dmp
Crash Time : 12/18/2011 1:36:19 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8054bc34
Parameter 3 : 0xeddb7810
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+74c34
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.6165 (xpsp_sp3_gdr.111025-1629)
Processor : 32-bit
Crash Address : ntoskrnl.exe+74c34
Stack Address 1 : ntoskrnl.exe+152efa
Stack Address 2 : ntoskrnl.exe+8ecf8
Stack Address 3 : ntoskrnl.exe+93989
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini121811-03.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
==================================================

#8 Allan

Allan

  • BC Advisor
  • 8,644 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:00 AM

Posted 12 January 2012 - 06:44 PM

The errors are all over the place. This is typically indicative of either failing hardware or malware. I'd like to rule out the latter first. Have you run full scans with both your installed Anti Virus app AND MalwareBytes? If not, please do so now.

#9 dcmike

dcmike
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:09:00 AM

Posted 12 January 2012 - 06:48 PM

I have ran full scans before but have not used MalwareBytes. I will do now and get back to you.

#10 dcmike

dcmike
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:09:00 AM

Posted 13 January 2012 - 06:07 AM

I have ran full scans and came back with nothing found.

#11 Allan

Allan

  • BC Advisor
  • 8,644 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:00 AM

Posted 13 January 2012 - 08:03 AM

1) What is new or different since the last time everything worked properly (ie, new hw, new sw, virus, error, etc)?

2) Please boot to the Recovery Console and run chkdsk /r

3) As suggested above, let's check the ram: To check the ram, download memtest (http://memtest.org/). Burn it to a cd using a dedicated .iso burning utility (http://www.petri.co.il/how_to_write_iso_files_to_cd.htm), make sure the cd drive is at the top of the boot order in bios, then boot to the newly created cd and run the utility.

#12 dcmike

dcmike
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:09:00 AM

Posted 13 January 2012 - 04:49 PM

Allan,

The one thing that I noticed was, after I used my laptop at work it started the problems. I used the free wireless and thought it was a virus or something along those lines. But the more I think about my children downloaded a program, silverlight or something like that, to play Lego games. I will do the the two things you suggested and post the results. Thank you.

#13 Allan

Allan

  • BC Advisor
  • 8,644 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:00 AM

Posted 13 January 2012 - 04:52 PM

If you think it may be malware (and I'm not convinced that it isn't), you can pot in the Am I Infected forum on this site and link back to this thread.

#14 dcmike

dcmike
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:09:00 AM

Posted 16 January 2012 - 04:58 PM

I used Spybot and MalwareBytes to check for problems with my laptop. I found some spyware with Spybot and not with Malware. So I followed the directions and removed it. I also did a system restore going back a month and ran Spybot and Malware again. So far so go, no more problems.

I don't have the Windows disk for my computer. So can I still use the Recovery Console for my computer?

#15 Allan

Allan

  • BC Advisor
  • 8,644 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:08:00 AM

Posted 16 January 2012 - 05:07 PM

Do you have an av app installed and if so have you run a full scan with it?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users