BSOD 0x7E caused by cdd.dll playing Tomb Raider

[Circle]

This just suddenly started happening last night. I'm about 30% done with the game when this started happening repeatedly.

I ran memtest last night and sfc /scannow, neither found anything.

cdd.dll stands for Canonical Display Driver, so I updated my display drivers from 13.3 to 13.6 after the first BSOD. The gpu was overclocked using MSI Afterburner, however after receiving the first bluescreen, I stopped because I just wanted to play the game. (The overclock was stable for the entirety of BioShock Infinite, Crysis 3, and FarCry3) But the problem still persists, as it later bluescreened at 3:54 and 4:32.

 

[Arc]

Hello Circle.

* Uninstall WinCDEmu. Such a program may cause any type of malfunctions.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Update Asmedia 106x SATA Host Controller Driver, as it is old.

fffff880`0107e000 fffff880`0108d000   asahci64   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\asahci64.sys
[COLOR=Red]    Image name: asahci64.sys
    Timestamp:        Wed Sep 21 15:12:57 2011[/COLOR] (4E79B1A1)
    CheckSum:         00010EE2
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Search for updates in ASMedia Technology Inc. ???? Or you can take it from ASMEDIA drivers & firmwares.

Make it sure that the Crucial M4-CT256M4 SSD2 is running with the most recent firmware.
Crucial.com Product Downloads - Firmware Updates

Uninstall the following programs:

• Unified Remote
• Windows7FirewallControl

You are using a Beta of Display driver. You are strongly advised to use a WHQL only. Uninstall all items of the display driver in Control panel > Programs and Features. Then follow

• Drivers - Clean Left over Files after Uninstalling
• Update your ATI/AMD display driver.
  You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.
  
  
  
  
  During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Let us know the results.
_____________________________________________________________________________________
BSOD ANALYSIS:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff9600060b2e5, fffff8800217d318, fffff8800217cb70}

Probably caused by : cdd.dll ( cdd!CHwCommandBuffer::FlushGdiCommands+135 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff9600060b2e5, The address that the exception occurred at
Arg3: fffff8800217d318, Exception Record Address
Arg4: fffff8800217cb70, Context Record Address

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!CHwCommandBuffer::FlushGdiCommands+135
fffff960`0060b2e5 48896808        mov     qword ptr [rax+8],rbp

EXCEPTION_RECORD:  fffff8800217d318 -- (.exr 0xfffff8800217d318)
ExceptionAddress: fffff9600060b2e5 (cdd!CHwCommandBuffer::FlushGdiCommands+0x0000000000000135)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000008
Attempt to write to address 0000000000000008

CONTEXT:  fffff8800217cb70 -- (.cxr 0xfffff8800217cb70)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800f955800
rdx=fffffa800fa0b830 rsi=fffff900c346b2f0 rdi=fffff900c00c1d48
rip=fffff9600060b2e5 rsp=fffff8800217d550 rbp=fffff900c00c2580
 r8=fffff900c00c14e8  r9=0000000000000000 r10=ffffffffffffffbf
r11=fffff8800217d838 r12=fffffa800f955800 r13=0000000000000000
r14=0000000000000001 r15=0000000000000004
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
cdd!CHwCommandBuffer::FlushGdiCommands+0x135:
fffff960`0060b2e5 48896808        mov     qword ptr [rax+8],rbp ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000008

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003714100
GetUlongFromAddress: unable to read from fffff800037141c0
 0000000000000008 Nonpaged pool

FOLLOWUP_IP: 
cdd!CHwCommandBuffer::FlushGdiCommands+135
fffff960`0060b2e5 48896808        mov     qword ptr [rax+8],rbp

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff960006095d5 to fffff9600060b2e5

STACK_TEXT:  
fffff880`0217d550 fffff960`006095d5 : fffffa80`0fa0b830 fffffa80`0fa0b830 00000000`00000002 fffff900`c00c0020 : cdd!CHwCommandBuffer::FlushGdiCommands+0x135
fffff880`0217d840 fffff960`00605c21 : ffffffff`fffd74f6 00000000`00000001 00000000`00000001 fffffa80`00000000 : cdd!CDDPDEV::FlushGdiOutput+0x81
fffff880`0217d870 fffff800`0377aede : 00000000`0297ef9f fffffa80`0f9e6b50 00000000`00000080 fffffa80`0f965b30 : cdd!PresentWorkerThread+0x8b5
fffff880`0217dc00 fffff800`034cd906 : fffff880`02f65180 fffffa80`0f9e6b50 fffff880`02f700c0 fffff880`00e107cb : nt!PspSystemThreadStartup+0x5a
fffff880`0217dc40 00000000`00000000 : fffff880`0217e000 fffff880`02178000 fffff880`0217d3a0 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  cdd!CHwCommandBuffer::FlushGdiCommands+135

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdd

IMAGE_NAME:  cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a90a5

STACK_COMMAND:  .cxr 0xfffff8800217cb70 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_cdd!CHwCommandBuffer::FlushGdiCommands+135

BUCKET_ID:  X64_0x7E_cdd!CHwCommandBuffer::FlushGdiCommands+135

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

 

[Circle]

Thank you for your reply!

Can I reinstall WinCDEmu later if it is not found to be the problem? I've been using it for years and it is the only CD emulator I've found that's not full of included junk.

Are Unified Remote and Windows7 Firewall Control really possibly be causing the issue? Unified Remote allows me control over Windows Media Center from bed as well as the speaker system from around the house using my cellphone and I use it quite often. I also really like how Windows7 Firewall Control gives me much simpler control over the built in windows7 firewall.

I used autoruns from systeminternals.net to already cherry pick which programs I want starting. Every program that currently starts, I want to start.

Before I start uninstalling those programs and changing settings I've purposely set, especially before flashing a new SSD firmware, I'm going to system image the machine. Just in case everything doesn't work out, I want to go back to the way I currently have the system set up.

The googling I've done on the 0x7E bugcheck seems to suggest a possible ram issue. Since I already passed memtest, I decided to do prime95 overnight with it set to custom, using 14440MB of ram. It only ran a few hours before BSOD 0x124. I backed the overclock from 4.2GHz to 4.0GHz. Again it ran only a few hours before BSOD 0x124. Whats interesting, is I used these sames settings to verify the stability of 4.2GHz 5 months ago, and it ran 18hrs stable before I stopped it.

The system is now at stock settings. I'm going to do that system image then run prime95 while I go to work. Once off work I will quickly post the results of that, but then I gotta leave town. I won't be back until Tuesday of next week. When I get back, I'll be able to do everything you suggest doing to fix the problem.

P.S. If the computer so happens to fail prime95 at stock settings, which hardware would be most at fault?

Thank you again. I really do appreciate your help and taking the time to do this.

 

[Arc]

I'd say negative about WinCDEmu. Hardware virtualization is a process that is subject to fail. CD images may be handled otherwise, not by mounting, but by extracting. Winrar or free 7-zip does it efficiently.

Remote control programs are strongest suspects of a stop 0x7E. I cannot say that it will be an efficient troubleshooting by keeping them in the system. Those have their utility, but limitations too, at the same time.

A 7E may be caused by the RAM, but in most of the cases it is not the RAM actually. You may have the necessary info at BSOD Index.

Also, a crashing system should not be overclocked.

If you think, you may test the RAM too, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

 

[Circle]

Hmm, I never did consider extracting the CD contents first, I new it was possible, but didn't think the game or etc it contains would be able to read from a folder properly, as it would expect a disk.

I will remove the remote control programs for this issue on Tuesday. I have a few other remote programs as well, should they be removed too? Such as Input Director, Remote Potato, and LogMeIn Hamachi.

This wasn't a crashing system, until 5-29-2013 at 12:21AM. It had a 10 on the reliability index for almost the entire month of May. But I know what you mean, and I have disabled all overclocks.

I won't be able to run prime 95 before work, as I need to leave now, and the backup is only 3/4 complete. NVM, suddenly jumped from 3/4 to done.

Thanks again.

 

[Circle]

It's stable at stock.

Be back Tuesday.