Page Fault BSOD

Here it is.

Absolutist said:

Okay, just got another blue screen. Will upload the minidump when it's back up.

minidump uploaded. Don't know if i needed to run the whole program again, so I just attached the .dmp file.

crashed again. minidump #2 included

Newest crash related to pool_corruption. Event log cant be opened. Try uploading the log again.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.

zigzag3143 said:

Newest crash related to pool_corruption. Event log cant be opened. Try uploading the log again.

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service.
Antivirus software can also trigger this error, as can a corrupted NTFS volume.

I figured it was something to do with the memory. Is there any way to determine which piece of hardware it is, so I can replace it? Attached is another crash dump (happened while idling) and the new event log. Sending two logs because I don't know if i should be including display information. EventLog has no display information, EventLog2 has english.

Three more crashes overnight. One could be due to a power failure. Dumps and event log attached. Also, could faulty ram/faulty graphics card cause missing/corrupt .dll files? That seems to be why my installers are acting all weird. Seems like half of my .dll's are missing/corrupt/unsigned.

Another blue screen, dump and log attached. Just going to compress both into one zip file since it's happening this often, lol.

edit: also did sfc /scannow, attached the log. found errors but could not repair.

OK Lets try this.



These crashes were caused by memory corruptionprobably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

I'll do both of those as soon as I get home from work. Will let you know the results in ~4 hours.

edit: teamviewed to my home computer and turned on driver verifier. After it crashes and i get the dump file i'll test the ram.

Well that didn't take long. When I logged back in, the standard "Do you want to send information about this problem" window came up, and under the more details tab, it directed me to a new dump file called MEMORY.DMP. however, this file is far too large to attach; it's 500 MB. I'll attach the minidump though.

edit: crashed again only 6 minutes later. Want me to attach that minidump as well?

Absolutist said:

Well that didn't take long. When I logged back in, the standard "Do you want to send information about this problem" window came up, and under the more details tab, it directed me to a new dump file called MEMORY.DMP. however, this file is far too large to attach; it's 500 MB. I'll attach the minidump though.

edit: crashed again only 6 minutes later. Want me to attach that minidump as well?

Yep we can take them all. If you want to upload the Memory.dmp (it wont provide much more info) to a file sharing site you can leave a link to it in your next post.

I am doing this one now.

EDIT::: This one inconclusive. Verifier will give us more info.