Could an aging drive cause windows to return a 0x00000050 error

[Alpha90]

Hello all. I am debugging a windows xp sp3 32bit machine and every time I shut the machine off windows logs a 0x00000050 error and does a core dump. I know my drive is aging and using smartmontools and it reports that the reallocated sector count is not 0 so i do have some bad sectors on the hard drive.

Researching what the error code means I came across a page on msdn that said the error code is PAGE_FAULT_IN_NONPAGED_AREA. It came with 4 possibilities of what the issue could be. 1 Faulty hardware which other than the hard drive issue I do not have this issue Ive run memcheck86+ for over a day with no error, I have stress tested the cpu with mprime for a day, and i use smartmontools to check the hard drive. 2. Faulty system service. While that might be the issue I have not changed any service status in a rather long time and I am running a barebones install with almost every superfluous service disabled and only 15 services running. 3. Anti virus issue. I use an anti virus as I do not use this OS everyday but I periodically run clamav on the partition in linux. 4. Corrupt File System. It suggested I run Chkdsk /f /r and I did not find any errors with the filesystem so I am assuming it is not corrupt.

 

[Arc]

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

So yes, a driver may cause this issue.

 

[Alpha90]

I tried running my dump file through a debugger and I found it was partially corrupt and I cant really get any useful information out of it but maybe someone more experienced can.

Output log for the debugger.

**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
Unable to read PsLoadedModuleList
**************************************************************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
**************************************************************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get program counter
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e4a1ba98, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf2ca468, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 00000001, (reserved)

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 1
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 2
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 3
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 4
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 5
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 6
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 7
GetContextState failed, 0xD0000147
Unable to read selector for PCR for processor 0

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get MmPageSize (0x0) - probably bad symbols
 e4a1ba98 

FAULTING_IP: 
+1562faf0006db04
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
bf2ca468 ??              ???

MM_INTERNAL_CODE:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x50

STACK_TEXT:  
GetContextState failed, 0xD0000147
Unable to get current machine context, NTSTATUS 0xC0000147


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner
---------

GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

Other information about my system its a i7 3770k based system, 32gb of ram, asus p8-77v pro mobo, A Asus Xonar sound card, and radeon 6900hd series graphics card..
I also have in my rig 3 gnu/linux distro's, and win7 64bit pro. The kernel message logs / boot logs for the linux distros are clean as is the system event log for the win7 install so what ever the problem is its localized to my windows xp 32bit home install.

Also an edit what ever process is failing looks to be after bootup and possibly after winlogin, and there is not a minidump file created.

 

[derekimo]

Just some stuff I found while searching...

This part of your dump is interesting,

unable to get MmPageSize (0x0) - probably bad symbols

As is this part,

Unable to get current machine context, NTSTATUS 0xC0000147

Which has a reference here towards the bottom,

Save Support Dollars by Checking Your Memory Dump before Calling Support - Ntdebugging Blog - Site Home - MSDN Blogs

About possibly not having a page file.

 

[Arc]

Other information about my system its a i7 3770k based system, 32gb of ram, asus p8-77v pro mobo, A Asus Xonar sound card, and radeon 6900hd series graphics card..

It is just a waste of such a nice build with an expired operating system.

It is strongly recommended that you upgrade to a later alive OS.

Windows XP support has ended - Microsoft Windows

 

[Alpha90]

Yeah the full power of my machine is pretty hamstrung with the xp install but I use it for legacy video games that I can't get to work on Wine or windows 7... However I don't waste my machine I have 5 hard drives and over 15 partitions with data windows 7 64bit and linux. I just can't get legacy stuff to work on the newer builds... Sometimes even XP barely works and I have to use power shell scripts to artificially limit processes to a single core or force a screen resolution.

 

[Alpha90]

Ok I was trying to tinker with my problem to see what it was and I tried deleting my core dump to see if maybe if I allowed a clean dump over an over written dump might allow me to have a greater picture of what has happened. On my next boot up I checked my syslogs and they were clean and I checked process explorer and the the dump utility process was not running. I checked in my windows directory and a new dump file was not created. Does this make sense at all because I do not know what happened to fix my problem.