Been suffering random BSODs for a year. Ex 0x0000001a, 0x000001e etc

Hello, I have a home made pc with the following components.

MOBO: ASUS P8Z68-V LE
CPU: Intel is 25k
GPU: Nvidia GeForce GTX 560 Ti by EVGA
Power supply: 550W modular Fatal1ty
OS: Win 7 HP
Ram: 2x8GB Corsair Vengeance DDR3
HDD; WD 1TB Black Caviar, seagate 3tb...(not sure was external but popped it in my case because the power calc I used said it would be supported, I only had a laptop before this thus why I had the external in the first place)
ROM Drive: ASUS DVD+/- Read/Write

After seeing what the tool gathers I think most of this info is in there. Something I think would help is a bigger power supply and possibly a replacement MOBO because I've replaced and cleaned RAM once before. I've updated all my drivers to my knowledge.

What is really mind boggling is my roommate actually wanted a PC like mine after they saw it and theirs works 100% But he said he worked out some issues when he first built his.

Any help would be greatly appreciated and I'll be available most anytime for questions.
Thanks in advance.

Welcome to the forums KaenShouten,

Code:

BugCheck 1A, {41790, fffffa800041b5c0, ffff, 0}

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

Code:

Usual causes:  Device driver, memory, kernel

We can see that severe memory management error has happened, and that a page stored within the page table has become corrupt. The page table is used to store the mappings between physical and virtual memory.

• RAM - Test with Memtest86+

Run Memtest86+ for least 9-10 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Arc said:

No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

I would also suggest rolling back to an older WHQL version of your nVidia graphics card driver - NVIDIA Driver Downloads - Advanced Search

Your MSINFO32 file is also corrupt, please upload another file manually using these steps:

1. Start
2. Type: msinfo32
3. File, Save
4. Place file in a zipped folder
5. Upload in your next post - Screenshots and Files - Upload and Post in Seven Forums

What AV protection are you currently running?

I'm using norton 360 for my AV my memtest is still running, started an hour ago, I thought I posted my msinfo 32 before I started it but I'll get that after the test is over. Thanks for the quick response and I will also switch to the more stable graphics driver you recommended. Also I know it says if it looks like it isn't working just to wait, memtest, but what if it really doesn't progress after hours?

It will progress eventually, it will depend upon the amount of RAM being tested too.

Ok so my memtest finished. After 9 passes and 24+ hours later. I didn't see any results pop up as I logged in. Would they be on the USB drive? I didn't see anything saying that in the memtest post so I figured I'd ask. also my sysinfo32 will be uploaded in this post. Feel free to look at that for me at your leisure. I will probably run memtest in certain configurations dependent on the results if they are stored somewhwere.

After some trial and error I have now found the culprit for the memory error. It would seem that from my old set and the replacement they each had 1 bad stick of RAM. I tested these in each DIMM slot and received errors as soon as memtest started. With the good RAM there were no errors even for an extended run of 7 Passes. So bad stock is to blame or possibly some human error from me or the workers that sorted the RAM for shipment.

Again thank you very much for you help in this. All that is left is to analyze the sysinfo right? If there are no errors, with the one I posted, I would be delighted to close this thread.

It's still corrupt, but probably due to the bad RAM corrupting the data, however, I'm quite certain that the bad RAM was the cause for all the BSODs using the data provided by the .dmp files.

I'm glad you managed to find the bad RAM sticks :)

Here is another msinfo32 it finished without anything happening so I think it isn't corrupted. Before it would pause at the end and go into "not responding" and then just close. Let me know please. Also an update no BSOD since we fixed my PC the other day. Thanks a million

The only program I could see which is known to cause BSODs is Norton, most people on the forum (including BSOD Analysts) recommend and use Microsoft Security Essentials with the paid or free version of Malwarebytes. These programs are the most effective and the most stable from my experience. MSE is also free.

Thanks for the advice. I like mse when my sub to norton comes close I will probably transfer to it. I've used it on xp with malware protection and never suffered problems. But like I said thanks for everything. Officially solved at this point.