| Author |
Windows 2000 rebooting problem
|
|
| prezbedard 2003-02-13, 1:07 pm |
| My brother's computer has been rebooting on its lately. I had him flsh his BIOS with the latest version however that did not alievieate the problem. I had him email me the System log. After looking through it for a short time a notice an entry repeated quite often.
"The computer has rebooted from a bugcheck"
Eachj enty has a different code next to it and the codes are reapeated iwth the numerous entries. I have attached a text file of the log with entries for 2/8 to 2/12. There are numerous entries of "The computer has rebooted from a bugcheck" each with a different error code.
I will continue to try and analyze it myself but your help is greatly apprecited.
Thanks | |
| prezbedard 2003-02-13, 1:08 pm |
| oops this was supposed to be an edit of the origianl post.
quote:
Originally posted by prezbedard
My brother's computer has been rebooting on its lately. I had him flsh his BIOS with the latest version however that did not alievieate the problem. I had him email me the System log. After looking through it for a short time a notice an entry repeated quite often.
"The computer has rebooted from a bugcheck"
Each enty has a different error code next to it and the codes are reapeated with the numerous entries. I have attached a text file of the log with entries for 2/8 to 2/12. There are numerous entries of "The computer has rebooted from a bugcheck" each with a different error code.
I will continue to try and analyze it myself but your help is greatly apprecited.
Thanks
| |
| anthonie 2003-02-13, 8:27 pm |
| Try to do a search on www.eventid.net. I normally get a lot of information and tips from there regarding errors reported in the system log.
Good luck! | |
| Tsakali 2003-02-13, 8:52 pm |
| I am not familiar with the eventlogs you are describing, but in some extreme cases cpu temperature could be causing the problem... what is your friend doing when the system rebots?
what's the temp of the system and the cpu?
another far fetched issue could be the power supply | |
| prezbedard 2003-02-14, 9:23 am |
| The power supply is brand new 350w.
This was happening with the older power supply which was 250w. | |
| prezbedard 2003-02-14, 10:28 pm |
| I have some more specific information on the error. I had my brother uncheck the auto reboot in startup and recovery. He got the following in a blue screen.
Stop: 0X00000050 (0X9AE6C984, 0X00000000, 0XA000C8EA, 0X00000002)
PAGE_FAULT_IN_NONPAGED_AREA
Date Stamp 3db42a96 Win32k.sys
Beginning dump of physical memory | |
| Tsakali 2003-02-15, 3:26 am |
| I just had the same error( but the adresses where not the same, not important in this matter)
is you brother using dynamic volumes (NTFS)or regular partitions(NTFS or FAT)?
When I was using dynamic volumes after 3 working days my system producesd the same error, out of nowhere... next time I tried to reboot it could not recognize the hardrive.
I moved the drive to another system, ran scandisk on it, but from what i could tell no errors were reported.
I moved the drive to it's native system and it booted up...but in the disk management snap-in it reported that the hardrive was "at risk" well soon enough at soe reboots the system took along time to recognize the drive and all kinds of activities that recomended a bad drive
I had to reformat the drive as regular primary/extended partitions.. and it fixed the problem, so it seems, I've been using it ever since for about 2 weeks with no problem.
I know re-installing is the devil himself to solving a problem but in my situation there was no other way, it had simply stoped working(couldn't even boot before I reformated)
sorry for the long and mostly pointless post but I feel like since you are still having problems you would welcome any input.
Just throwing out ideas but did you try to mess around with the paging file? doubt it would fix the problem but try to move it to snother "volume" or drive if available | |
| prezbedard 2003-02-15, 10:02 am |
| I did some searching for
PAGE_FAULT_IN_NONPAGED_AREA
error and found several different sources that all mentioned memory problems.
So I'm thinking posssiblely corrupted physical memory.
I do believe though he is not using dynamic drives.
Here is one of pieces of info I found:
Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors
The information in this article applies to:
* Microsoft Windows 2000 Server
* Microsoft Windows 2000 Advanced Server
* Microsoft Windows 2000 Professional
* Microsoft Windows 2000 Datacenter Server
* Microsoft Windows NT Server 4.0
* Microsoft Windows NT Workstation 4.0
* Microsoft Windows NT Server, Enterprise Edition 4.0
This article was previously published under Q183169
SYMPTOMS
Windows NT computers, and those built on Windows NT technology, may stop responding (hang) with one or more of the following STOP error messages:
STOP: 0x0000000a
STOP: 0x0000001e
STOP: 0x00000050
CAUSE
These errors may be caused by one or more of the following:
* Hardware failure (memory, processor, or motherboard).
* Anti-virus software that is running on your computer.
* Drivers installed by third-party software.
RESOLUTION
To resolve these behaviors, perform one or more of the following:
* Replace the faulty hardware. You may be able to determine the faulty hardware by running diagnostics provided by the manufacturer. Please contact the hardware manufacturer for more information.
* Disable any anti-virus software that is running on your computer. If the STOP errors no longer occur, contact the anti-virus software manufacturer about a possible upgrade.
* Disable any third-party drivers that may be running. If the STOP errors no longer occur, contact the third-party manufacturer about a possible upgrade. | |
| sgirardo 2003-02-15, 10:31 am |
| When does this problem occur?
Has your brother recently added new hardware/software?
How much RAM does it have?
Has he added/upgraded memory?
Does he have antivius software?
I have checked the log file that you posted.
As you have originally stated there were many different errors.
All had event ID 1001, for the "rebooting from debug error" with the following codes:
leaving off the zeros.
50
23
4E
0A
24
24
Here is a good link for troubleshooting these errors.
http://www.microsoft.com/technet/tr...td/gsstdapa.asp | |
| sgirardo 2003-02-15, 10:58 am |
| The article you posted listed the following possibilities:
* Hardware failure (memory, processor, or motherboard).
* Anti-virus software that is running on your computer.
* Drivers installed by third-party software.
RESOLUTION
To resolve these behaviors, perform one or more of the following:
* Replace the faulty hardware. You may be able to determine the faulty hardware by running diagnostics provided by the manufacturer. Please contact the hardware manufacturer for more information.
* Disable any anti-virus software that is running on your computer. If the STOP errors no longer occur, contact the anti-virus software manufacturer about a possible upgrade.
* Disable any third-party drivers that may be running. If the STOP errors no longer occur, contact the third-party manufacturer about a possible upgrade.
I would say most likely to least likely, in reverse order of article:
1 drivers
2 antivirus
3 hardware
I say this because in the log file you posted
there are a string of errors on 2/8/03, before the first "reboot error"
(actually they are not listed as errors but information)
The protected system file rasadhlp.dll was not restored to its original, valid version because the Windows File Protection restoration process was cancelled by user interaction, user name is admin. The file version of the bad file is 5.0.2168.1.
Did this first start happening on 2/8?
I would look in event viewer for the first instance of the 1001 error, and look at errors just prior to this happenening.
I would start by running driver verifer.
Then try removing any new software/drivers. | |
| prezbedard 2003-02-15, 11:27 am |
| No that is not the whole log file.
The log file starts on 9/15/2002 but the 1001 error starts on 1/18/2003. I am goign to check with him to see what he may have added around that time.
I just went through the log and it seems to be happening at least every other day to everyday. There are also a couple entries where it happened 4 times in one day. | |
| Tsakali 2003-02-15, 12:48 pm |
| as you can remember from the basics, if the error does not report the same adress every time the error occurs then it's prolly not your ram | |
| prezbedard 2003-02-15, 7:28 pm |
| quote:
Originally posted by Tsakali
as you can remember from the basics, if the error does not report the same adress every time the error occurs then it's prolly not your ram
I know but several of the different stop errors turned up similar information on causes and possible resolutions.
One suggestion I made to him was to run
chkdsk since I found entries in the log file pertaining to possible corrupted ntfs. |
|
|
|