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

Computer restarting on its own


  • Please log in to reply
16 replies to this topic

#1 ABNINF

ABNINF

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 03 December 2010 - 09:49 AM

I've just removed some malware/virus from this machine with the help of Gringo in the Malware/Virus/Trojan forum. This problem was happening before everything was removed but it is still happening.

I don't know if this machine is still infected or if it could possibly be a hardware issue.

I'm running Windows XP SP 3. Just now while I was sitting here working at my desk with nothing open on the machine except IE (one tab open) and Mozilla Thunderbird the machine rebooted itself. When it finished rebooting I got an error message that said "The machine had just recovered from a serious error."

Everytime this happens when I go back to sites like BC I'm completely logged out.

Can this be due to a bad hard drive? I have a new one laying around and have thought about putting it in the machine to see but I thought I would get a little input from some pros about whether this COULD be the problem before I did that.

I have a complete Ghost image of the HD and can make another one before I put a new HD in.

Any input is appreciated.

KC

Edit: Moved topic from Windows 95/98/ME to the more appropriate forum. ~ Animal

BC AdBot (Login to Remove)

 


#2 Keithuk

Keithuk

  • Members
  • 957 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:04:06 PM

Posted 03 December 2010 - 03:00 PM

I'm running Windows XP SP 3.

If your running WinXP why have you posted in the Win9x/ME section?

Everytime this happens when I go back to sites like BC I'm completely logged out.

That happens to me sometimes on here. Are you using CCleaner? :wink:

Keith

Windows ME (spare computer)
Windows XP 2002 Professional SP3 (desktop computer)
Windows 7 Professional SP1 32bit (laptop computer)

Windows 8 64bit spare drive for laptop computer


#3 ABNINF

ABNINF
  • Topic Starter

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 03 December 2010 - 04:38 PM


If your running WinXP why have you posted in the Win9x/ME section?





DOH!~ Cause I'm an idiot! :crazy:

Everytime this happens when I go back to sites like BC I'm completely logged out.


That happens to me sometimes on here. Are you using CCleaner? :wink:


Yeah, I have CCleaner but it's not due to that. I haven't run it in a couple of weeks and this has happened a couple of times since I've run CCleaner.

Thanks for pointing out my error. I'll move this to the appropriate board.

KC

Edited by WWPREBroker, 03 December 2010 - 04:39 PM.


#4 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:06 AM

Posted 03 December 2010 - 10:17 PM

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#5 ABNINF

ABNINF
  • Topic Starter

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 04 December 2010 - 12:56 AM

Download BlueScreenView (in Zip file)
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.



Thanks for moving this Broni. I'll be back in the office first thing tomorrow and I'll get you the report. I put a new HD in the machine today .... don't know if that'll make a difference.

KC

#6 ABNINF

ABNINF
  • Topic Starter

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 04 December 2010 - 09:34 AM

Broni,

Y'all know where some of the coolest tools are! I've got your BSOD report here;

==================================================
Dump File : Mini120310-01.dmp
Crash Time : 12/3/2010 8:28:24 AM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x0004b11c
Parameter 3 : 0x00000001
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+21cc5
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini120310-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini112410-01.dmp
Crash Time : 11/24/2010 8:10:29 AM
Bug Check String : REGISTRY_ERROR
Bug Check Code : 0x00000051
Parameter 1 : 0x00000004
Parameter 2 : 0x00000001
Parameter 3 : 0xe14b1be8
Parameter 4 : 0x001599e8
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+21cc5
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini112410-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111510-01.dmp
Crash Time : 11/15/2010 10:34:36 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 0x00000020
Parameter 2 : 0xe15a31d0
Parameter 3 : 0xe15a3298
Parameter 4 : 0x0c19040d
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+21cc5
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini111510-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini111410-01.dmp
Crash Time : 11/14/2010 11:34:28 AM
Bug Check String : MANUALLY_INITIATED_CRASH
Bug Check Code : 0x000000e2
Parameter 1 : 0x00000000
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : Npfs.SYS
Caused By Address : Npfs.SYS+3de5
File Description : NPFS 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\Mini111410-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini110410-01.dmp
Crash Time : 11/4/2010 2:28:04 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : 0xc0000005
Parameter 2 : 0x80544683
Parameter 3 : 0xba53bc14
Parameter 4 : 0xba53b910
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+6d683
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini110410-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini102810-01.dmp
Crash Time : 10/28/2010 6:37:56 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8062a4f0
Parameter 3 : 0xaeac2890
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1534f0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini102810-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini102710-01.dmp
Crash Time : 10/27/2010 7:34:32 AM
Bug Check String : THREAD_STUCK_IN_DEVICE_DRIVER
Bug Check Code : 0x100000ea
Parameter 1 : 0x89af2658
Parameter 2 : 0x8a248520
Parameter 3 : 0xba50fcb4
Parameter 4 : 0x00000001
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+a67
File Description : Watchdog Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5512 (xpsp.080413-2108)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini102710-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100610-01.dmp
Crash Time : 10/6/2010 3:34:06 PM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x00000000
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+21cc5
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini100610-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100510-01.dmp
Crash Time : 10/5/2010 12:18:15 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 0x00000780
Parameter 2 : 0xc06cebd0
Parameter 3 : 0x82139994
Parameter 4 : 0x000004c0
Caused By Driver : hal.dll
Caused By Address : hal.dll+22d0
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\Mini100510-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================

==================================================
Dump File : Mini100210-01.dmp
Crash Time : 10/2/2010 9:10:39 AM
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 0x00000099
Parameter 2 : 0x0003ef7a
Parameter 3 : 0x00000000
Parameter 4 : 0x00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+21cc5
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.5973 (xpsp_sp3_gdr.100427-1636)
Processor : 32-bit
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini100210-01.dmp
Processors Count : 1
Major Version : 15
Minor Version : 2600
==================================================



Thanks for the look!

:thumbsup:

KC

#7 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:06 AM

Posted 04 December 2010 - 05:04 PM

OK, we have very different error types, all involving system files.
That's always tough problem to solve, because it can be anything.
An infection is out of question, since your computer is clean.
We'll have to try to eliminate one possibility after another.

Let's start with this...

Download System Information for Windows (SIW free version)
No installation required.

After it scans your computer, navigate to Hardware>Sensors and post all info from there.

Posted Image

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#8 ABNINF

ABNINF
  • Topic Starter

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 05 December 2010 - 03:12 PM

OK, we have very different error types, all involving system files.
That's always tough problem to solve, because it can be anything.
An infection is out of question, since your computer is clean.
We'll have to try to eliminate one possibility after another.

Let's start with this...

Download System Information for Windows (SIW free version)
No installation required.

After it scans your computer, navigate to Hardware>Sensors and post all info from there.

Posted Image



Broni,

Ok, it was pretty cold when I got in the office so I turned on the heaters to normal settings to let the building warm up. I've been running the machine for a couple of hours now doing some updates and some scans with various programs to get the machine up to normal operating temps.

Here's the report in .txt ... I don't have an account with any of the photo bucket type sites. I have my own but BC won't let it show the pics.

Sensor Value Min Max

KEVIN

WDC WD1200BB-00RDA0

Temperatures
Assembly 35 °C (94 °F) 35 °C (94 °F) 35 °C (94 °F)

KEVIN (EMACHINES T3516)

WDC WD1200BB-00RDA0
Temperatures
Assembly 35 °C (94 °F) 35 °C (94 °F) 35 °C (94 °F)


Thanks!
KC

#9 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:06 AM

Posted 05 December 2010 - 03:28 PM

Those look perfectly fine.

Run hard drive diagnostics: http://www.tacktech.com/display.cfm?ttid=287 (or http://www.bleepingcomputer.com/forums/index.php?showtopic=28744&hl=hard+drive+diagnostic)
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.
For Toshiba hard drives, see here: http://sdd.toshiba.com/main.aspx?Path=ServicesSupport/FujitsuDrivesUSandCanada/SoftwareUtilities#diagnostic

Note : If you do not know how to set your computer to boot from CD follow the steps here

=========================================================================================

A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...

1. Download - Pre-Compiled Bootable ISO (.zip)
2. Unzip downloaded memtest86+-....iso.zip file.
3. Inside, you'll find memtest86+-....iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:

Posted Image

8. Locate memtest86+-....iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:

Posted Image

10. Once the CD is created, boot from it, and memtest will automatically start to run.

The running program will look something like this depending on the size and number of ram modules installed:


Posted Image

It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.

Posted Image

The following image is the test results area:

Posted Image

The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#10 ABNINF

ABNINF
  • Topic Starter

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 05 December 2010 - 03:32 PM

Well, let me try this.

Posted Image

Thought I might just create an account and see how it goes ... This might be easier for you to read.

Thanks again,
KC

#11 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:06 AM

Posted 05 December 2010 - 03:46 PM

Those are fine....

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#12 ABNINF

ABNINF
  • Topic Starter

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 05 December 2010 - 04:12 PM

Broni,

I'm back at home now but will be back at the office tomorrow. I have some questions though before we start this;

Run hard drive diagnostics: http://www.tacktech.com/display.cfm?ttid=287 (or http://www.bleepingcomputer.com/forums/index.php?showtopic=28744&hl=hard+drive+diagnostic)


This was happening before I installed the brand new HDD I just installed after I started this topic. Do you think it would be worthwhile to run these diagnostics?

A. If you have more than one RAM module installed, try starting/running computer with one RAM stick at a time.


I have 2 sticks of RAM in the machine and they're realtively easy to get to BUT this 'crash' of the machine is fairly infrequent. Would I need to leave out one of the sticks for ?? a week or 2? Then do the same for the other stick?

That's about it. Just a couple of thoughts I figured I would get your input on. I really don't want to run my machine on 1/2 memory for very long. I deal with a lot of photos and stuff in my business and it would slow me considerably.

Muchas Gracias!
KC

#13 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:06 AM

Posted 05 December 2010 - 04:19 PM

Would I need to leave out one of the sticks for ?? a week or 2? Then do the same for the other stick?

Exactly.
Meanwhile, you can also run HDD test to eliminate that possibility.

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 


#14 ABNINF

ABNINF
  • Topic Starter

  • Members
  • 397 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Republic of Texas!
  • Local time:09:06 AM

Posted 12 January 2011 - 12:00 PM

Would I need to leave out one of the sticks for ?? a week or 2? Then do the same for the other stick?

Exactly.
Meanwhile, you can also run HDD test to eliminate that possibility.


Broni,

While I was doing some of the stuff above I was getting some weird error messages and I was still getting the reboots. I went back to Gringo and we rescanned the machine. Gringo says he saw nothing in the scans but he said the tools we were using did more than just scan so maybe it cleaned off the vestiges of something bad.

Since re-running the scans and a couple of other tools the machine seems to be running great. It's been a little over a week ... no strange error messages, no reboots to this point. I'm going to give it a few more days just to make sure. On Friday I'll be running all my regular scans and doing my weekly Ghost of the machine. If it is still running good I'm going to call this one something messed up with the software along the way while cleaning off the bad guys.

I really appreciate your help! Everyone on this site is amazing at helping folks.

KC

#15 Broni

Broni

    The Coolest BC Computer


  • BC Advisor
  • 42,716 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Daly City, CA
  • Local time:08:06 AM

Posted 12 January 2011 - 12:51 PM

Good news :)
Thanks for the update :)

My Website

p4433470.gif

My help doesn't cost a penny, but if you'd like to consider a donation, click p22001735.gif


 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users