Windows 7: BSOD While doing anything for 10 minutes STOP Error 0x00000050

I'm very sorry for posting a lot, but I've been getting so many problems and BSOD with my computer lately. I believe it's a memory problem, but I'm not sure. I'll be going on a vacation for the next 10 days, so I won't have access to internet and my computer. I've been waiting all day for a solid answer on the problem. Everything is telling me it's my RAM, but I want to make sure 100% it is before I do anything else. I've also been also getting BSOD errors like 0x0000001a and 0x0000001e both I believe are hardware/software problems. I am still looking for a 100% answer, I'll be able to do tests/scans tomorrow for a few hours then I'm off. If doing a "factory restore" solves this I would be extremely happy to do it. I had to use Winrar because I didn't have 7-Zip. Thank you SevenForums!

Hello Massaddict and welcome to Sevenforums.

BSOD Analyse

3rd party driver concerns

VirtuWDDM.sys, as far as I'm concerned, is a somewhat known BSOD causer in Windows 7. I'd suggest uninstalling it. If it appears in \SystemRoot\system32\DRIVERS\VirtuWDDM.sys, let me know and we'll troubleshoot further.

You do have a lot of 3rd party drivers. Be aware of those. Sometimes you might not need additional drivers for Windows 7, it'll choose them for you. If you really need them, make sure that they're digitally signed by Microsoft. The only additional drivers I personally recommend, is the Graphics Driver, and the Audio Driver.

Memory

As we covered the 3rd party drivers part, it's even likely that a driver is disturbing your memory. Second possibility is that the sticks themselves, or the motherboard slots are broken. It's very unlikely that the slots are broken though.
Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors.


To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.

Memtest86+ - Advanced Memory Diagnostic Tool

@Bugcheck

Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Can't wait for your results!

Best Regards,
Frederik.

Hi Frederik, I just came back from a 10-day cruise, it was amazing.

I have deleted the VirtuWDDM.sys. Before this post I've ran memtest and it took about an hour to get through 1 pass, I have a pictureimgur: the simple image sharer. I wasn't too sure what was happening and most of the numbers in red were too confusing. Right now nothing unusually has gone wrong when I opened my computer, I will update you if a BSOD happens.

You basically had a bunch of errors by the looks of it. Have you tried to test one stick at the time, and then move it to another slot and test it once again? By that, we can tell what stick is blamed, and if it's the motherboard slots.

If you have a couple of sticks you can borrow from some friends, family etc., that'd be helpful to see if the BSODs will proceed.

Best Regards,
Frederik.

So if I get those red lines, does it mean my RAM is corrupt? After 2 passes the errors stopped going. I plan on doing the stick memtest today, can I get specific steps? My motherboard is ASRock X68 Pro3 Gen3, which slot would it be to put one stick in? Thanks!

There's definitely a good chance that either the stick or the slot is corrupt. Red lines means errors, you can elso see the counter named "Errors".
As I mentioned earlier - to ensure that the stick or slot is bad, do a scan witg Memtest on ONE stick only. Move it to the very first slot and test it. When you passed 6 passes, move it to another slot and test it. Proceed this way until you've tested all the sticks individually, which also counts on the slots.

I am planning on doing this today, I will keep you updated. This is a picture from the memtest I did a few weeks ago. How will I know if it's the slot or the RAM and what if it's both?

For instance, if you test one stick in one slot, and it gives errors, then moves the stick to another slot and it doesn't - that might be slots. It's very unlikely though. Sometimes it might not even give any errors.

Best Regards,
Frederik.