Bsod in windows xp home

[Sex_monkey]

hi im hoping on here will help me with my troubles
a long time ago,my psu died and it had to be replaced,and windows had to be repaired. since then my pc has bee restarting randomly.i have been fixing it for a while now i have it down to 3 possibilitys
1 ram
2 video ram
3 drivers
im going to post some mini dumps from this week im hoping someone will maybe point me in the right direction because im not to sure what most of this means.
for the moment im about to swap the ram to diff slots,and then completly.
memtest ran for 7 hours and my ram was fine.

----------------------------------------------------------
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: 87e8c188, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80514698, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: 87e8c188

FAULTING_IP:
nt!MiCompleteProtoPteFault+264
80514698 8b06 mov eax,dword ptr [esi]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

TRAP_FRAME: a74acb80 -- (.trap 0xffffffffa74acb80)
ErrCode = 00000000
eax=000005c4 ebx=00000000 ecx=00000000 edx=000006f3 esi=87e8c188 edi=77e7d793
eip=80514698 esp=a74acbf4 ebp=a74acc18 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!MiCompleteProtoPteFault+0x264:
80514698 8b06 mov eax,dword ptr [esi] ds:0023:87e8c188=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8051f656 to 804f9deb

STACK_TEXT:
a74acb00 8051f656 00000050 87e8c188 00000000 nt!KeBugCheckEx+0x1b
a74acb68 805437c8 00000000 87e8c188 00000000 nt!MmAccessFault+0x9a8
a74acb68 80514698 00000000 87e8c188 00000000 nt!KiTrap0E+0xd0
a74acc18 805156fe 80000000 77e7d793 00000000 nt!MiCompleteProtoPteFault+0x264
a74acc5c 80515855 00000000 77e7d793 c03bf3e8 nt!MiResolveProtoPteFault+0x204
a74acce0 8051fdca e20bcbb0 77e7d793 c03bf3e8 nt!MiDispatchFault+0xf1
a74acd4c 805437c8 00000008 77e7d793 00000001 nt!MmAccessFault+0x111c
a74acd4c 77e7d793 00000008 77e7d793 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006f0ec 00000000 00000000 00000000 00000000 0x77e7d793


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiCompleteProtoPteFault+264
80514698 8b06 mov eax,dword ptr [esi]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiCompleteProtoPteFault+264

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 45e53f9d

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x50_nt!MiCompleteProtoPteFault+264

BUCKET_ID: 0x50_nt!MiCompleteProtoPteFault+264

Followup: MachineOwner

----------------------------------------------------------------------

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf8a0259, The address that the exception occurred at
Arg3: aa7ef630, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
win32k!RGNOBJ::vDownload+2e
bf8a0259 238d48108b71 and ecx,dword ptr [ebp+718B1048h]

TRAP_FRAME: aa7ef630 -- (.trap 0xffffffffaa7ef630)
Unable to read trap frame at aa7ef630

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

MISALIGNED_IP:
win32k!RGNOBJ::vDownload+2e
bf8a0259 238d48108b71 and ecx,dword ptr [ebp+718B1048h]

LAST_CONTROL_TRANSFER: from bf8a0311 to bf8a0259

STACK_TEXT:
aa7ef6c0 bf8a0311 00000002 02ec8050 aa7ef704 win32k!RGNOBJ::vDownload+0x2e
aa7ef6e4 bf8a03d5 e304049f 00000030 aa7ef704 win32k!GreGetRegionData+0x85
aa7ef870 8054086c e304049f 00000030 02ec8050 win32k!NtGdiGetRegionData+0x59
aa7ef870 7c90eb94 e304049f 00000030 02ec8050 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0013f234 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!RGNOBJ::vDownload+2e
bf8a0259 238d48108b71 and ecx,dword ptr [ebp+718B1048h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!RGNOBJ::vDownload+2e

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner
-------------------------------------------------------------------
any help appreciatted and i have many saved crash dumps!!
cheers
hugh

 

[Nodsu]

System RAM is easy to test - just run memtest86 on it

Bad video RAM doesn't make the system crash - you would experience things like image distortion and text corruption (in text mode) instead.

As for "drivers", you might want to narrow this down a bit.. You have dozens of different drivers on your system.

 

[Sex_monkey]

i ran memtest,no errors after 7 hours,but i think it is still possible for the ram to be at fault.
drivers-most mini dumps were telling me
ntfs.sys
ntkrnlpa.exe
win32k.sys
were the problems but im not sure i did the crash dump thing properly

 

[Grummangy]

Some things to try

Firstly, do you have one ore two stick of ram installed in the system.

If 2, remove them both and insert 1 at a time. Power on and use system. If the system fails again insert the other. This will tell you if one is bad.

If u have one ask a friend if they have one u can test with noting if it is DDR or DDR2, speed does not matter so much as faster ram will always run at whatever the M/B can handle. Physical characteristics will not allow you to insert DDR into DDR2 slots and vice versa. The majority of RAM is clearly marked these days. If not buy one and keep it in your system as an upgrade as you go.

Bad RAM means having it replaced and I do like memtest, but it will not pick up all errors. It also means there is a chance that you will want to re-load windows or recovery fresh so save your data if u can. Bad RAM at installation means a suspect operating system as mentioned in another thread.

Other possibilities are, faulty RAM controller, is there a possibility when you lost the PSU it spiked the M/B. Also the Processor could have copped a jolt.

This one deff sounds like ram tho, the processes that are being shut down or failing are random. Re-image or reload after replacement of RAM in this case.

Hope this helps.

 

[Sex_monkey]

Cheers for the advice
at the moment i have 2 sticks of 512mb corsair ddr ram rated for up to 550mhz
at the moment i just moved the ram to the other 2 sockets and so far so good.but if it fails i will remove one stick,and i also have a 1gb ram stick for backup.

 

[Tedster]

learn how to read your own minidumps: https://www.techspot.com/vb/topic31341.html