Blue Screen - STOP 0x0000007e - NTFS.SYS - Address f854d379 base at f8528000, Datestamp 41107eea ????
Hi,
I've got a Fujitsu Lifebook S Series running Windows XP Professional and it has started blue screening recently and I can't figure out why. Sometimes the computer will work for hours without a problem and other times it will blue screen just as i'm logging into windows. So far I've run multiple diagnostic utilities * on the hard drive which have all confirmed that the drive is OK and doesn't have any bad sectors. I also ran MEM TEST which didn't find any memory errors. As for viruses/Spyware the machine has been throughly scanned in safe mode by SpySweeper 5.3, Ad-Aware and SpyBot and they all found relatively few spyware programs running. I've since removed what was found but am still experience the same problem . Symantec corporate edition is installed and fully updated. A full system scan didn't find any virus.
The event log does NOT always have an entry when a blue screen occurs. However sometimes it does. The last event long entry for System Error had the following description:
1st entry - Error Code 10000050, parameter 1 ebbad8cc, parameter2 00000000, parameter3 bf820d67, parameter4 00000000
2nd entry - Error Code 10000050, parameter 1 e6071c58, parameter2 00000000, parameter3 ef0fe883, parameter4 0000000
The blue screen error message is as follows:
STOP: 0x0000007e (90x0000005, 0xF854D379, 0XF8BA9AB4, 0XF8BA97B0)
*** NTFS.SYS - Address f854d379 base at f8528000, Datestamp 41107eea
Beginning dump of physical memory
I also get:
DRIVER_IRQL_NOT_LESS _OR_EQUAL
STOP: 0x000000D1 (OxEED41488, 0x00000002, 0x00000000, 0xeedd87b3)
*** rdbsss.sys - address EED41488 base at EED2B000, Datestamp 445b1fab
**** SYMTDI.SYS - Address EEDD87B3 base at EEDC1000, Datestamp 40ca5a34d
Is there any way to pinpoint what these messages actually mean?
Thanks!
I've got a Fujitsu Lifebook S Series running Windows XP Professional and it has started blue screening recently and I can't figure out why. Sometimes the computer will work for hours without a problem and other times it will blue screen just as i'm logging into windows. So far I've run multiple diagnostic utilities * on the hard drive which have all confirmed that the drive is OK and doesn't have any bad sectors. I also ran MEM TEST which didn't find any memory errors. As for viruses/Spyware the machine has been throughly scanned in safe mode by SpySweeper 5.3, Ad-Aware and SpyBot and they all found relatively few spyware programs running. I've since removed what was found but am still experience the same problem . Symantec corporate edition is installed and fully updated. A full system scan didn't find any virus.
The event log does NOT always have an entry when a blue screen occurs. However sometimes it does. The last event long entry for System Error had the following description:
1st entry - Error Code 10000050, parameter 1 ebbad8cc, parameter2 00000000, parameter3 bf820d67, parameter4 00000000
2nd entry - Error Code 10000050, parameter 1 e6071c58, parameter2 00000000, parameter3 ef0fe883, parameter4 0000000
The blue screen error message is as follows:
STOP: 0x0000007e (90x0000005, 0xF854D379, 0XF8BA9AB4, 0XF8BA97B0)
*** NTFS.SYS - Address f854d379 base at f8528000, Datestamp 41107eea
Beginning dump of physical memory
I also get:
DRIVER_IRQL_NOT_LESS _OR_EQUAL
STOP: 0x000000D1 (OxEED41488, 0x00000002, 0x00000000, 0xeedd87b3)
*** rdbsss.sys - address EED41488 base at EED2B000, Datestamp 445b1fab
**** SYMTDI.SYS - Address EEDD87B3 base at EEDC1000, Datestamp 40ca5a34d
Is there any way to pinpoint what these messages actually mean?
Thanks!
> 0x0000007E: SYSTEM_THREAD_EXCEPTION_NO
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues
There's more detail from same url. Note that the device driver is mentioned again .. be worth following up.
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues
There's more detail from same url. Note that the device driver is mentioned again .. be worth following up.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Periodically investigating & found a suggested method (should you require it) of 'resetting' the Page file that is used by the Virtual Memory Manager, in case it may be damaged ..
"Error Message with RAM Problems or Damaged Virtual Memory Manager":
http://support.microsoft.com/?kbid=810093
"Error Message with RAM Problems or Damaged Virtual Memory Manager":
http://support.microsoft.com/?kbid=810093
ASKER
It turned out to be a faulty memory chip. I went back an ran MEM Test again but this time I let it run for about 20 minutes and only then did it start to find errors. I've replaced the chip and so far no more blue screens.
Thanks!
Thanks!
Thanks for the report, glad you've fixed it.
When using a memory chip tester it's always advisable to run it for several hours, even overnight if convenient. You should be ok now.
Thank you.
When using a memory chip tester it's always advisable to run it for several hours, even overnight if convenient. You should be ok now.
Thank you.
The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.
Details here >
http://aumha.org/win5/kbestop.htm