GRAM or system RAM? (memory_management)

antaeus · Apr 2, 2013

I am getting BSOD errors on my system, but really only whilst in games. It is the stadard one called with a lot of zeros and then x1A or something. I can try and provoke it at a later time in hopes of a dump file (Which I cant find, odd really).

I have on a previous attempt to isolate the problem tried to make a memtest run. It made a complete pass, but only one. Then I grev impatient. I have read that the minimum to rule out system ram is 7 passes?

Anyway, what are the chances that the memory on my graphics card is corrupt? Because I have not found any viable information regarding what a memory_management can actually cover.

Thank you in advance.

P.S. when I get home from school, I shall try and provoke and error (Usually only happens in games. Lately, Red Faction Armageddon and Bioshock Infinite)

unksol · Apr 2, 2013

The chances of the "memory on your graphics card" being bad is irrelevant. memory tests do not check that. Your gpu either works or doesn't, and BSOD in games does not mean GPU or even memory. It could just be over heating, driver conflicts, bad overclock etc.You need to provide the error code and system event logs. Right now we have no info

antaeus · Apr 2, 2013

Okay,

I will provide a dump file as soon as this computer bothers to generate one.

antaeus · Apr 2, 2013

Well, that didn't take long.

I have looked in the minidump folder, nothing is there. I am looking in the event viewer, and it has this to tell me:

//./root/CIMV2
SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99
0x80041003

Also, i managed to take pictures of the BSOD this time.

*** STOP: 0x0000001A (0x0000000000041790, 0xFFFFFA800467F4C0, 0x000000000000FFFF, 0x0000000000000000)

I monitored the temperature with MSI Afterburner, and at no point did it reach anything critical. (Less than 70 celcius)

Also, attached is a picture of the BSOD.

antaeus · Apr 2, 2013

0x41790
A page table page has been corrupted. On a 64 bit version of Windows, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit version of Windows, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs.

Source: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557391(v=vs.85).aspx

So my page file is at blame?!

UPDATE:
I just tried to deactivate my page file all together, and that worked... a bit better. Took twice as long before my BSOD.

Is it possible I am "just" running out of memory? I should clarify that my games are not installed on my system drive, because I have procrastinated expanding my C: drive.

antaeus · Apr 2, 2013

I made 3 passes over a period of 5 hours in memtest...

I booted up in Parted Magic, and it told me that my NTFS file system was damaged. Strange that Windows does not specify that?

Anyway, I made a complete chkdsk and an sfc /scannow.

I am on bare ground here. Can anyone throw me a bone?

antaeus · Apr 9, 2013

By the way, I fixed it.

I changed the system disk, and that sorted it out.

antaeus · Apr 9, 2013

Well, no. It now does it on it's own when idling.

First a BSOD where it complains about hal.dll and then the same memory management error.

Search

GRAM or system RAM? (memory_management)

antaeus

Honorable

unksol

Splendid

antaeus

Honorable

antaeus

Honorable

antaeus

Honorable

antaeus

Honorable

antaeus

Honorable

antaeus

Honorable

TRENDING THREADS

Latest posts

Moderators online

Share this page