Weird program behavior & BSoD

You had many BSOD reports and I checked only a few.
Try this hot fix. The problem seems to be driver: dxgmms1.sys
The October 2009 stability and reliability update for Windows 7 and Windows Server 2008 R2 is available.

If problem persists, repost and a detail analysis will be made.

ITunes is also know to cause BSOD problems

SPTD part of Daemon or Alchohol 120% is also a known cause of BSOD
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads

Clear out the old reports and if it happens again repost.

Yes, I would do it via disc clean up. Be sure to include system files by checking the box
Disk Cleanup - Open and Use
This way we are sure that you are clearing the correct folder.
Be sure to check after clean up that the folder has been cleared.

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

Code:

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Code:

Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c46e50
Debug session time: Sat Oct 23 23:40:21.958 2010 (GMT-4)
System Uptime: 0 days 1:36:22.597
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 50, {fffff0a00c480cc0, 0, fffff80002d6d95f, 7}
 
 
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKeyControlBlock+f )
 
Followup: MachineOwner
---------
 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
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: fffff0a00c480cc0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002d6d95f, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000007, (reserved)
 
Debugging Details:
------------------
 
 
Could not read faulting driver name
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb10e0
fffff0a00c480cc0 
 
FAULTING_IP: 
nt!CmpDelayDerefKeyControlBlock+f
fffff800`02d6d95f 448b01          mov     r8d,dword ptr [rcx]
 
MM_INTERNAL_CODE:  7
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0x50
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
TRAP_FRAME:  fffff880031cba00 -- (.trap 0xfffff880031cba00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff0a00c480cc0
rdx=0000000000000705 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d6d95f rsp=fffff880031cbb90 rbp=fffff880031cbc74
r8=000000003b9aca07  r9=000000002dae1657 r10=fffff0a00c480cc0
r11=fffff8a00307ca80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!CmpDelayDerefKeyControlBlock+0xf:
fffff800`02d6d95f 448b01          mov     r8d,dword ptr [rcx] ds:fffff0a0`0c480cc0=????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff80002af8849 to fffff80002a79740
 
STACK_TEXT:  
fffff880`031cb898 fffff800`02af8849 : 00000000`00000050 fffff0a0`0c480cc0 00000000`00000000 fffff880`031cba00 : nt!KeBugCheckEx
fffff880`031cb8a0 fffff800`02a7782e : 00000000`00000000 fffff8a0`0307ca70 00000000`00001f00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e0b
fffff880`031cba00 fffff800`02d6d95f : 00000000`00000000 fffff800`02d6dbfe 00000000`00000002 fffff800`02a4eb3e : nt!KiPageFault+0x16e
fffff880`031cbb90 fffff800`02d6dafd : fffff8a0`0307ca70 00000000`00000004 00000000`00000004 00000000`00000001 : nt!CmpDelayDerefKeyControlBlock+0xf
fffff880`031cbbd0 fffff800`02cd1aee : fffff8a0`0307ca70 fffff880`031cbc5c 00000000`00000004 00000000`00000004 : nt!CmpCleanUpKcbCacheWithLock+0x69
fffff880`031cbc00 fffff800`02a86961 : fffff800`02cd17b4 fffff800`02c1e5f8 fffffa80`0551ab60 00000000`00000000 : nt!CmpDelayCloseWorker+0x33a
fffff880`031cbcb0 fffff800`02d1dc06 : 08547440`28f24411 fffffa80`0551ab60 00000000`00000080 fffffa80`05505040 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`02a57c26 : fffff880`02fd5180 fffffa80`0551ab60 fffff880`02fdffc0 d849035a`04421201 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
nt!CmpDelayDerefKeyControlBlock+f
fffff800`02d6d95f 448b01          mov     r8d,dword ptr [rcx]
 
SYMBOL_STACK_INDEX:  3
 
SYMBOL_NAME:  nt!CmpDelayDerefKeyControlBlock+f
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: nt
 
IMAGE_NAME:  ntkrnlmp.exe
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
 
FAILURE_BUCKET_ID:  X64_0x50_nt!CmpDelayDerefKeyControlBlock+f
 
BUCKET_ID:  X64_0x50_nt!CmpDelayDerefKeyControlBlock+f
 
Followup: MachineOwner

Outdated Drivers

Code:

pcouffin pcouffin.sys Tue Dec 05 09:39:30 2006
Rt64win7 Rt64win7.sys Thu Feb 26 04:04:13 2009

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command

Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. If the list is extensive I have included the driver verifier test so that you may determine which drivers are in need of immediate attention.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done:
www.duplexsecure.com/en/downloads

Uninstall your current Anti Virus and replace with Microsoft Security Essentials.
www.microsoft.com/Security_Essentials/


Scan with your Anti Virus

Test Hard Drive www.carrona.org/hddiag.html or this test http://www.tacktech.com/display.cfm?ttid=287

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
These reports are not definitive but merely point the way to a solution. It is very important to remember that the dump reports only give clues as to the problem and although it is very easy to analyze only one or two, usually more are needed. If you experience additional BSOD after installing a current version of the driver in question, be sure to post so that we can use the additional information to assist you in preventing the BSOD's