re: Question about 'Dealing with Bad Memory (RAM)'
Friday, March 11, 2005 at 5:44 pm Windows XP Annoyances Discussion Forum
Posted by Donna Price
(11 messages posted)
Okay, here goes:
SUMMARY OF STOP ERROR MESSAGES (BLUE SCREENS)
STOP: 0x0000007E
STOP: 0x0000008E - This message referenced "win32k.sys"
STOP: 0x000000C2 - BAD_POOL_CALLER
STOP: 0x000000D1 - DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x00000050 - PAGE_FAULT_IN_NONPAGED_AREA
STOP: 0x000000F4 - This message referenced "A process or thread crucial to your system
operation has unexpectedly exited or been terminated"
STOP: 0x000000C5
STOP: 0x0000000A - IRQL_NOT_LESS_OR_EQUAL
(0xF79A4D4C, 0x00000002, 0x00000000, 0x8051B699)
STOP: 0x000000E3 - This message referenced "savrt.sys" and "a thread tried to release
a resource it did not own" Address EFB81028 base at EFB7A000,
Datestamp 3fa3986d
STOP: 0x0000008E
(0xC0000005, 0x805525A1, 0xEF9CC600, 0x00000000)
STOP: 0x0000000A - IRQL_NOT_LESS_OR_EQUAL
(0x00000004, 0x00000002, 0x00000001, 0x804E6DEE)
STOP: 0x000000D1 - DRIVER_IRQL_NOT_LESS_OR_EQUAL / referenced "portcls.sys"
(0x00000024, 0x00000002, 0x00000001, 0xF722D1A2)
Address F722D1A2 base at F722C000, Datestamp 41107f13
Stop: 0x0000007E
(0xC0000005, 0x804D7007, 0xF7B54CC0, 0xF7B549BC)
STOP: 0x0000007E
STOP: 0x00000019 - BAD_POOL_HEADER
(0x00000020, 0x842D5D18, 0x842D5EE8, 0x0A3ADE28)
STOP: 0x0000008E
STOP: 0x0000001A - MEMORY_MANAGEMENT
(0x00041785, 0xC0C00000, 0x80562F00, 0x00000000)
STOP: 0x000000D1 - DRIVER_IRQL_NOT_LESS_OR_EQUAL
(0x00000000, 0x00000002, 0x00000000, 0x00000000)
STOP: 0x00000050 - PAGE_FAULT_IN_NONPAGED_AREA
(0xEEC1B450, 0x00000000, 0xEEC1B450, 0x00000000)
STOP: 0X0000000A - IRQL_NOT_LESS_OR_EQUAL
(0x00000001, 0x0000001C, 0x00000001, 0x804E1C51)
STOP: 0x0000000A - IRQL_NOT_LESS_OR_EQUAL
(Ox00000004, 0x0000001C, 0x00000001, 0x904E2679)
STOP: 0x000000D6 - This message referenced "atisgkaf.sys"
(0x89A39000, 0x00000000, 0xF78A7000, 0x00000000)
Address F78A741E base at F78a7000, Datestamp 3ea6e04d
STOP: 0x000000C4
(0x00000090, 0xF771F120, 0X00000000, 0x00000000)
"A device driver attempting to corrupt the system has been caught. The faulty driver
currently on the kernel stack must be replaced by a working version"
STOP: 0x0000008E - This referenced "ati3d2ag.dll"
(0xC0000005, 0xBFA31956, 0xEFA96B9C, 0x00000000)
Address BFA31956 base at BFA28000, Datestamp 40872C03
This is just a drop in the bucket....I have 12 legal pages filled with the errors
but I think this is a sample of each error I've received. The following are just
the STOP messages without the details, all in the order they were received:
0x00000050
0x0000008E
0x00000024 (referenced ntfs.sys)
0x00000050
0x0000008E (referenced win32k.sys)
0x0000008E
0x0000000A
0x0000008E (referenced win32k.sys)
0x0000000A
0x0000008E
0x0000008E
0x0000008E
0x10000050
0x0000008E (referenced win32k.sys)
0x0000007F
0x0000000A
0x0000000A
0x0000000A
0x000000C5
0x00000074
0xC0000221
0x00000071
0x00000050
0x00000024
0x0000008E
0x00000050 (referenced ntfs.sys)
0x00000050
0x0000008E
0x0000008E
0x0000000A
0x0000000A
0x00000050
0x0000000A
0x0000000A
0x0000008E
I notated where files were referenced.
On Friday, March 11, 2005 at 5:00 pm, triplate wrote:
>Post some of the Errors first..lets have a look at the direction...unless you,ve
>taken a lap apart before..i dont recommend it..if MemTest86 says the Ram is good..i,d
>go with it...;)
|
All messages in this thread [show all]
 |  |  | re: Question about 'Dealing with Bad Memory (RAM)' (Donna Price: Fri, Mar 11, 2005, 5:44 pm) |
| |
| |
Return to the Windows XP Discussion Forum
|
|