Sorry you are having problems, we will take a look.
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
BSOD Index
STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION
Usual causes: Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)
BSOD Index
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Seven Forums.zip\Seven Forums\062310-39671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Wed Jun 23 08:48:00.387 2010 (GMT-4)
System Uptime: 0 days 6:26:26.495
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff900c2b52000, 0, fffff96000075d83, 0}
Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!DrvTextOut+4cc )
Followup: MachineOwner
---------
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: fffff900c2b52000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000075d83, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c40e0
fffff900c2b52000
FAULTING_IP:
win32k!draw_clrt_nf_ntb_o_to_temp_start+7b
fffff960`00075d83 41803b00 cmp byte ptr [r11],0
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88002af8050 -- (.trap 0xfffff88002af8050)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff9600031ba60
rdx=0000000000000006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000075d83 rsp=fffff88002af81e8 rbp=000000007fffe95e
r8=0000000000000001 r9=0000000000000001 r10=0000000000000039
r11=fffff900c2b52000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!draw_clrt_nf_ntb_o_to_temp_start+0x7b:
fffff960`00075d83 41803b00 cmp byte ptr [r11],0 ds:3120:fffff900`c2b52000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002f0ce54 to fffff80002e8c600
STACK_TEXT:
fffff880`02af7ee8 fffff800`02f0ce54 : 00000000`00000050 fffff900`c2b52000 00000000`00000000 fffff880`02af8050 : nt!KeBugCheckEx
fffff880`02af7ef0 fffff800`02e8a6ee : 00000000`00000000 fffff900`c2c610a4 fffff900`c21cbc00 fffff800`02ed79dc : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`02af8050 fffff960`00075d83 : fffff900`c00cf650 00000000`000000ac 00000000`0000002c 00000000`00000025 : nt!KiPageFault+0x16e
fffff880`02af81e8 fffff960`000aa988 : fffff900`c00bf010 fffff880`02af9400 fffff900`c2b50740 00000000`0000002c : win32k!draw_clrt_nf_ntb_o_to_temp_start+0x7b
fffff880`02af8220 fffff960`00084da8 : 00000000`00000000 fffff900`c2b50740 fffff900`c2c61030 fffff900`0000002c : win32k!vExpandAndCopyText+0x268
fffff880`02af85b0 fffff960`0064b4e0 : fffff900`00000025 00000000`000000aa fffff900`c21f7ca0 fffff880`02af9340 : win32k!EngTextOut+0xe28
fffff880`02af8940 fffff960`00099e67 : fffff900`c43c7ce8 fffff880`02af9400 fffff900`c21f7ca0 fffff880`02af9340 : cdd!DrvTextOut+0x4cc
fffff880`02af8d50 fffff960`00083f0b : 00000000`00000000 00000000`00000001 fffff960`0064b014 00000000`00000001 : win32k!OffTextOut+0xdf
fffff880`02af8dd0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SpTextOut+0x2bb
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd!DrvTextOut+4cc
fffff960`0064b4e0 488b8c24e0000000 mov rcx,qword ptr [rsp+0E0h]
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: cdd!DrvTextOut+4cc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bde94
FAILURE_BUCKET_ID: X64_0x50_cdd!DrvTextOut+4cc
BUCKET_ID: X64_0x50_cdd!DrvTextOut+4cc
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_Seven Forums.zip\Seven Forums\062310-49967-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03041e50
Debug session time: Wed Jun 23 16:25:19.045 2010 (GMT-4)
System Uptime: 0 days 7:36:04.154
Loading Kernel Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d89f8789b9, b3b7465ef2045baf, fffff80002e4cea4, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See Patching Policy for x64-Based Systems: Information for Driver Developers
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d89f8789b9, Reserved
Arg2: b3b7465ef2045baf, Reserved
Arg3: fffff80002e4cea4, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
BUGCHECK_STR: 0x109
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002e74600
STACK_TEXT:
fffff880`035625d8 00000000`00000000 : 00000000`00000109 a3a039d8`9f8789b9 b3b7465e`f2045baf fffff800`02e4cea4 : nt!KeBugCheckEx
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: BAD_STACK
Followup: MachineOwner
This appears to be a hardware/driver issue. I would like to address the easy things first.
You have a very old driver on your system. Old drivers do not play well with Windows 7. Upgrade the driver and software or uninstall it.
pcouffin.sys Tue Dec 05 09:39:30 2006 (457584A2) This driver is Patin-Couffin low level access layer for CD devices or low level access layer for CD/DVD/BD devices or VSO Software pcouffin belongs to the software Low level access layer for CD devices or Patin couffin engine or VSO Software pcouffin by VSO Software (www.vso-software.fr).
I also see that you have AVG installed. AVG is known to cause BSOD's on some systems. I suggest that uninstall AVG for the purpose of troubleshooting. I suggest you install MSE in its place. Use the AVG uninstall tool > Info > Tool (32bit) - Tool (64 bit). If you have AVG Indentity Protection installed uninstall it also >Info > Tool
After you have done these, run your system and let's see what happens.