Random reboots & many error messages

[Doffy]

Hello.

I tried to figure this out with people from my own country but they havent been much help so now I come to you guys who hopefully have more experience and knowledge of these sort of problems.

My comp crashes like once or twice everyday and I've tried everything. I have run that Memtest thingy because thats what they told me to do but my RAM is fine.

The lastest error message in the Event Viewer is this:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000008f, 0x0001ab73, 0x00072873, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini052809-01.dmp.

I have no idea if this has anything to do with drives (but I highly doubt it since my drivers are from the official sites). But I posted the topic here anyway, please move it if its wrong.

 

[snowchick7669]

Hi Doffy,

Anyway you can upload the dumpfile listed here

A dump was saved in: C:\WINDOWS\Minidump\Mini052809-01.dmp.

 

[Route44]

That 0x4E error is a very strong indicator of corrupted memory.

0x0000004E: PFN_LIST_CORRUPT
This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.


How long did you run Memtest? The minimum is 7 Passes. Please attach your five latest minidumps as snowchick7669 instructed so that she or someone else can read them and see if we can find a more definitive answer.

Also, please give us your system specs, particularly motherboard make and model and the type, plus the amount and make of your RAM.

 

[Doffy]

Here's the latest crash / minidump file.

My mother board is Asus P5N-E Sli and I will find out what model and make my RAM is later. Thanks!

 

[snowchick7669]

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e89b3bc4, 1, bf80f380, 2}


Could not read faulting driver name
Probably caused by : memory_corruption

Followup: memory_corruption

As per Route44's post, how long did you run memtest?

It also mentioned firefox.exe in the debugging

*******************************************************************************
* *
* 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: e89b3bc4, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: bf80f380, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: e89b3bc4

FAULTING_IP:
win32k!RGNOBJAPI::RGNOBJAPI+89
bf80f380 08a8200f8434 or byte ptr [eax+34840F20h],ch

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from bf81532e to bf80f380

STACK_TEXT:
b4172cb0 bf81532e 0104003f 00000460 0000011f win32k!RGNOBJAPI::RGNOBJAPI+0x89
b4172ce4 bf815398 b9e39248 b4172d1c 00000000 win32k!xxxRedrawWindow+0xd8
b4172cfc bf815423 b9e39248 b4172d1c 00000001 win32k!xxxInvalidateRect+0x32
b4172d50 8054060c 00040074 b4172d1c 00000001 win32k!NtUserInvalidateRect+0x77
b4172d50 7c90eb94 00040074 b4172d1c 00000001 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012ea2c 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
bf80f380-bf80f3bf 64 bytes - win32k!RGNOBJAPI::RGNOBJAPI+89
[ c2 08 00 90 90 90 90 90:08 a8 20 0f 84 34 01 00 ]
64 errors : !win32k (bf80f380-bf80f3bf)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE_64

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_64

BUCKET_ID: MEMORY_CORRUPTION_LARGE_64

Followup: memory_corruption

Please review Route44's post about running memtest on your RAM, for at least 7 passes.

If all clear then try reinstalling/updating firefox, as all the errors have been when firefox is performing an action

 

[Doffy]

I ran memtest all the way to the end, and it said everything was fine. As for firefox: trust me it has nothing to do with firefox, theres something in my computer which is casing it to crash all the time, Ive reinstalled and uninstalled but it keeps happening. Im also familure with registry so I have removed all the firefox stuff before I installed it again and I have tried all the versions. I also have a backup which I made when everything windows was installed clean which I have restored again and again and again but that doesnt help either. Ive defragmented to, but that doesnt help.

One thing I noticed tho was that when I scanned with avast that the antivirus program couldnt scan pagefile.sys on my D drive, is that suspicious?

 

[Doffy]

Here's another minidump file

 

[Doffy]

bump......

 

[Route44]

Sorry, Doffy, for the delay. The error is, again, 0x50 and it specifically cited memory corruption. When you say I ran memtest all the way to the end what does this mean? Are saying you let it run for a full 7 Passes?

Also, do you know how to access your BIOS?

In your next posting please give us the make, type, and the amount of RAM installed. Plus, give us your security software you have installed.

 

[Doffy]

It means that I waited until it says complete. But I will try to do it again ok. =)

 

[Route44]

It means that I waited until it says complete. But I will try to do it again ok. =)

Hmmm, Memtest will keep on going until you stop it manually. Nowhere will it say complete. There are 8 individual tests per Pass. You need to run it for a minimum of 7 Passes; longer if possible.

Again, in your next posting please give us the make, type, and the amount of RAM installed. Plus, give us your security software you have installed