BSOD: memory_management / page_fault

[oman212]

Every now and again I get either a 'memory_management' or 'page_fault_in_non_paged_area' BSOD. The frequency varies, sometimes it takes an hour or a week to get another. But they always return.

If I use a memory diagnostic right after a bsod, it shows problems but later on it shows no problems until the next bsod.

The BSODs first started appearing when I replaced my video card and flashed BIOS. Both of these went fine and apart from the BSODs, my PC can do everything fine.

So what could be causing this? My RAM manufacturer offered to replace my RAM for free, but for seem reason I don't think that's the problem.

 

[ttran]

What memory diagnostic did you use? Did you use memtestx86 to test your Ram.
Please upload your minidump to us:
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[oman212]

I used both memtest86+ and the windows one, both showed errors after BSODS (and only then).

 

[ttran]

I suspect the Ram really. Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

BugCheck 50, {fffffab001e4030b, 0, fffff80002f4f75e, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiTrimWorkingSet+1de )

Followup: MachineOwner
---------
BugCheck 50, {fffffaa005b0a9d8, 0, fffff800031a342e, 5}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )

Followup: MachineOwner
---------
BugCheck A, {fffff68000013a80, 0, 0, fffff80002ea7957}

Probably caused by : memory_corruption ( nt!MiDeleteAddressesInWorkingSet+11b )

Followup: MachineOwner
---------
BugCheck 1A, {41790, fffffa8001c4ba40, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

Followup: MachineOwner
---------
BugCheck 24, {1904fb, fffff8800ad91f58, fffff8800ad917c0, fffff80003213b60}

Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2cc9 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80002ff4f8c, fffff88008eceef0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------
BugCheck 1A, {41790, fffffa8000f2c220, ffff, 0}

Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )

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

Hard drive controller was blamed too. Please proceed the following things:
http://www.sevenforums.com/tutorials/433-disk-check.html
HD Diagnostic (Download HD diagnostic test from manufacture site)

 

[zigzag3143]

I used both memtest86+ and the windows one, both showed errors after BSODS (and only then).

TTran is of course correct. Not only did win DB report corruption but the first parameter (C000000005) is also a memory exception.

It is probably memory but can also be a bad mobo slot. Try testing each ream stick seperately in memtest till you find one that pass then use only that one in each mobo slot runnign memtest for each. that will tell you if it is memory or mobo.

Ken

 

[oman212]

Try testing each ream stick seperately in memtest till you find one that pass then use only that one in each mobo slot runnign memtest for each. that will tell you if it is memory or mobo.

Well that's part of the problem, there are only errors right after a BSOD. I just did another test in the Windows Memory Diagnostic with all sticks in and it said they were fine.

Is there perhaps another way of checking the mobo slots? Or should I just wait for errors to come up again?

EDIT: forgot to mention, did both HDD tests and both said it was fine

 

[Tews]

Run memtest86 ... the native windows memory diagnostic tool is iffy at best..

 

[zigzag3143]

Try testing each ream stick seperately in memtest till you find one that pass then use only that one in each mobo slot runnign memtest for each. that will tell you if it is memory or mobo.

Well that's part of the problem, there are only errors right after a BSOD. I just did another test in the Windows Memory Diagnostic with all sticks in and it said they were fine.

Is there perhaps another way of checking the mobo slots? Or should I just wait for errors to come up again?

EDIT: forgot to mention, did both HDD tests and both said it was fine

Other possibilities. Heat (download cpu-z, and gpu-z (both free) to keep track of the temps. The other underpowered PSU (what PS and system specs)?

TO test the mobo slots take the best mem stick put it by iteslf in a mobo slot and run memtest. Get results. test next.

Good luck

Ken