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.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
Update Asmedia 106x SATA Host Controller Driver, as it is old.
Code:
fffff880`0107e000 fffff880`0108d000 asahci64 (deferred)
Image path: \SystemRoot\system32\DRIVERS\asahci64.sys
Image name: asahci64.sys
Timestamp: Wed Sep 21 15:12:57 2011 (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
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:
Code:
*******************************************************************************
* *
* 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
---------