BSOD While doing anything for 10 minutes STOP Error 0x00000050

Hello Massaddict and welcome to Sevenforums.

BSOD Analyse

3rd party driver concerns

Code:

VirtuWDDM.sys Mon Aug 8 11:42:14 2011 (4E3FAF76)

Code:

VirtuWDDM    VirtuWDDM              Kernel        8/8/2011 2:42:14 AM

Code:

2: kd> lmvm VirtuWDDM
start             end                 module name
fffff880`04071000 fffff880`04086000   VirtuWDDM   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\VirtuWDDM.sys
    Image name: VirtuWDDM.sys
    Timestamp:        Mon Aug 08 11:42:14 2011 (4E3FAF76)
    CheckSum:         00010AF4
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

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.

   Warning

Note that the below instructions may break your WARRANTY rules. If you're unsure check manuals, separated warranty papers, stickers on computer for secure permission.

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

Code:

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa8c07385feb, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030b2e85, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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.

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.

Massaddict said:

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.