Okay, I think we might have something definitive to work with. The first error is 0xD1 and these are usually dy drivers but can also be caused by faulty or mismatched memory. It only cited a Windows OS driver.

The second error is 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).


This minidump specificaqlly cited memory corruption as your issue and corrupted memory will cause a system to throw out a number of error codes as well as differing causes but the bottom line is bad RAM. So you will need to run Memtest on your memory.

See the link below and follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

If you have errors you have corrupted memory and it needs to be replaced.

Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


Link: http://www.techspot.com/vb/topic62524.html


* Get back to us with the results.


*** If Memtest shows no errors then find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?

yes, iv ran memtest before, they are all matching ram. ddr2 which my mobo supports, i also ran each stick individually and tested the slots.. they all worked fine.. i arent sure about the 7 passes, would take some time but ill do it again tomorrow/day after =) the ram i have is
DDR 1GB Patriot, i have 4 sticks taking up all 4 slots. lol


sorry for my slow reply, i didnt realise we had rolled onto a page 2 so i thaught i was just being ignored or something >_<, sorry =]

*** If Memtest shows no errors then find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?

Also, refresh our memory, what OS are you running? What make is your motherboard?

Have you run a harddrive diagnostics?

My voltage should be 2.1V
motherboard: gigabyte GA-965GM-S2
OS: windows xp
and yes i have, long and short.

all this info was earlier in this thread lol

Sorry, but I do a number of these threads and I can't remember all the details.

What does your BIOS show the memory voltage set at?

i cant seem to find the voltage setting, iv looked in all categories, which would they usually be in? i could take som pictures/list the options available? and lol ok, sorry =]

I downloaded your mobo manual and it appears you are correct: There doesn't seem to be a memory voltage option. Unfortunately some motherboard model BIOS are designed this way.

Why? Who knows, but it makes absolutely no sense especially when someone like yourself really needs to see the memory voltage settings. I'm very suprised Gigabyte did this because they are a Tier 1 motherboard manufacture.

* My next suggestion is to contact their tech support directly and give them the following:

a. Mother model and Issues.

b. Minidump reads with error codes and cited probable causes, i.e. corrupted memory.

c. All diagnostic steps taken.


*** I have often found email contact, though slower, can get more indepth answers.

okay =) i have a... large.. collection of minidumps now XD

Woa! Post your latest 5.

i have quite a few, but these are the only 3 that i havent uploaded so far

For whatever reason one dump was corrupted and thus unreadable.

One is 0x50 but kept repeating that the module list was unable to load due to corruption.

And the third was 0xA and specifically cited memory corruption as the issue.

Nothing new, unfortunately.

damn... wonder how they became corrupt. and memory seems to be the source but from which component lol. im getting a new hard drive tomorrow/day after, if that doesnt do anything i think i should look at ram, as for the BIOS problems i dno if they would go

im starting to believe i need a new graphics card, i ran linux yesterday perfectly, no crashes and no errors. the only thing that changes when i run linux is my graphics drivers dont run because theyre not compatible with linux unless you find a manual way to do it. so i think its a driver related issue to do with the graphics card, im ordering a new one tomorrow and it will be here for tuesday so, next day delivery. when it gets here ill tell you if i still crash wish me luck lol

There is a VRAM test for your video card. 0x50 errors can be caused by this but I've only seen it happen occasionally; the overwhelming memory issues have been with the system RAM.

If you go to MajorGeeks.com thay will have the VRAM test that you can download for free.