BSOD again whilst using Chrome.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\BSODDmpFiles\JJD1988\Windows_NT6_BSOD_jcgriff2\021012-31746-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e51670
Debug session time: Fri Feb 10 12:21:55.934 2012 (GMT-7)
System Uptime: 0 days 5:06:43.949
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960001cf5ce, fffff8800877f950, 0}

Probably caused by : hardware ( win32k!vSpComposite+a06 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960001cf5ce, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800877f950, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!vSpComposite+a06
fffff960`001cf5ce 0000            add     byte ptr [rax],al

CONTEXT:  fffff8800877f950 -- (.cxr 0xfffff8800877f950)
rax=0000000000000010 rbx=fffff900c0000de0 rcx=0000000000000001
rdx=0000000000000004 rsi=fffff900c0000750 rdi=fffff900c3468bd0
rip=fffff960001cf5ce rsp=fffff88008780330 rbp=fffff900c0000750
 r8=fffff880087805b8  r9=fffff880087805b8 r10=fffff88008780480
r11=00000000000001c6 r12=0000000000000000 r13=fffff900c2599018
r14=fffff900c2967430 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210202
win32k!vSpComposite+0xa06:
fffff960`001cf5ce 0000            add     byte ptr [rax],al ds:002b:00000000`00000010=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!vSpComposite+a06
fffff960`001cf5ce 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001cf5ce

STACK_TEXT:  
fffff880`08780330 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!vSpComposite+0xa06


FOLLOWUP_IP: 
win32k!vSpComposite+a06
fffff960`001cf5ce 0000            add     byte ptr [rax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!vSpComposite+a06

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xfffff8800877f950 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner
---------

Loading Dump File [E:\BSODDmpFiles\JJD1988\Windows_NT6_BSOD_jcgriff2\021012-30404-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e51670
Debug session time: Fri Feb 10 07:13:38.755 2012 (GMT-7)
System Uptime: 0 days 0:04:15.770
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960006631c6, fffff8800852edf0, 0}

Probably caused by : cdd.dll ( cdd!vGDIDirtyUpdate+132 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960006631c6, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800852edf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
cdd!vGDIDirtyUpdate+132
fffff960`006631c6 f6832008000008  test    byte ptr [rbx+820h],8

CONTEXT:  fffff8800852edf0 -- (.cxr 0xfffff8800852edf0)
rax=0000000000000000 rbx=fffff900c00c0020 rcx=fffffa800c7b5b60
rdx=fffffa800b240b70 rsi=fffff8800852fd68 rdi=fffffa800b2b8d10
rip=fffff960006631c6 rsp=fffff8800852f7d0 rbp=fffff8800852fad0
 r8=fffff900c2968010  r9=0000000000000000 r10=0000000000000000
r11=fffff8800852f790 r12=0000000000000001 r13=fffff900c00c7638
r14=fffffa800b2b8d10 r15=fffff900c2b497a8
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00210286
cdd!vGDIDirtyUpdate+0x132:
fffff960`006631c6 f6832008000008  test    byte ptr [rbx+820h],8 ds:002b:fffff900`c00c0840=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960006631c6

STACK_TEXT:  
fffff880`0852f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!vGDIDirtyUpdate+0x132


FOLLOWUP_IP: 
cdd!vGDIDirtyUpdate+132
fffff960`006631c6 f6832008000008  test    byte ptr [rbx+820h],8

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cdd!vGDIDirtyUpdate+132

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7c546

STACK_COMMAND:  .cxr 0xfffff8800852edf0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_cdd!vGDIDirtyUpdate+132

BUCKET_ID:  X64_0x3B_cdd!vGDIDirtyUpdate+132

Followup: MachineOwner
---------

1. Points toward hardware. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...
2. Points toward memory or graphics card, possibly graphics card memory. Same possible causes as 1.

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
  
• Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.
  
  
  1. Download the latest drivers for your display card(s)
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Expand Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
     
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  
  
  Alternatively:
  
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Expand Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
     
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
  
  
• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode. Start logging the temperature through sensor-only mode when the computer first starts, and let it run during stress or until a crash occurs.
  
  Save the CSV file in a place you will remember, and then compress the CSV file to a zip file and upload to here for us to analyze by following the steps in Screenshots and Files - Upload and Post in Seven Forums.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.