[SOLVED] I got BSOD more than 3 weeks now.. - Windows 7 x64

kakatran

New member
Joined
Mar 17, 2014
Posts
3
I got BSOD randomly after I play Game, it doesn't happen during or before, but just after. It has been happen ever since I update the GPU and Factory restore my computer. One just happen right now : I turn on youtube to watch video and I turn on a game, then I alt tab out of game right after it launch to continue to watch youtube - It crash right after and this is the dump file it came with:

Code:
[COLOR=#070F14][FONT=Verdana].....[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]*******************************************************************************[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]* *[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]* Bugcheck Analysis *[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]* *[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]*******************************************************************************[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]Use !analyze -v to get detailed debugging information.[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]BugCheck 3B, {c0000005, fffff80002c885fe, fffff880088870b0, 0}[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]Probably caused by : cdd.dll ( cdd!DrvAssociateSharedSurface+7b )[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]Followup: MachineOwner[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]---------[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]1: kd> !analyze -v[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]*******************************************************************************[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]* *[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]* Bugcheck Analysis *[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]* *[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]*******************************************************************************[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]SYSTEM_SERVICE_EXCEPTION (3b)[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]An exception happened while executing a system service routine.[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]Arguments:[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]Arg1: 00000000c0000005, Exception code that caused the bugcheck[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]Arg2: fffff80002c885fe, Address of the instruction which caused the bugcheck[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]Arg3: fffff880088870b0, Address of the context record for the exception that caused the bugcheck[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]Arg4: 0000000000000000, zero.[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]Debugging Details:[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]------------------[/FONT][/COLOR]


[COLOR=#070F14][FONT=Verdana]EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]FAULTING_IP: [/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff800`02c885fe f00fba3100 lock btr dword ptr [rcx],0[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]CONTEXT: fffff880088870b0 -- (.cxr 0xfffff880088870b0)[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]rax=fffffa8006bcfa60 rbx=0000000000000000 rcx=0000000000000000[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]rdx=0000000040002200 rsi=fffff900c2641030 rdi=fffffa8006bcfa60[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]rip=fffff80002c885fe rsp=fffff88008887a80 rbp=0000000000000000[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]r8=ffffffffb1121700 r9=0000000000000040 r10=00000000034af9a0[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]r11=fffff88008887b08 r12=ffffffffb1121700 r13=0000000040002200[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]r14=0000000004d6cf20 r15=0000000000000001[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]iopl=0 nv up ei ng nz na po nc[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26:[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff800`02c885fe f00fba3100 lock btr dword ptr [rcx],0 ds:002b:00000000`00000000=????????[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]Resetting default scope[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]CUSTOMER_CRASH_COUNT: 1[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]BUGCHECK_STR: 0x3B[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]PROCESS_NAME: dwm.exe[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]CURRENT_IRQL: 0[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]LAST_CONTROL_TRANSFER: from fffff960006d6d3f to fffff80002c885fe[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]STACK_TEXT: [/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff880`08887a80 fffff960`006d6d3f : 00000000`00000000 00000000`00000000 ffffffff`b1121712 00000000`00000020 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff880`08887ab0 fffff960`001dd365 : 00000000`00000000 fffff900`c2692460 00000000`034afa40 00000040`00000230 : cdd!DrvAssociateSharedSurface+0x7b[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff880`08887b10 fffff960`00200749 : 00000000`00000001 fffff880`08887c60 00000000`034afa40 00000000`00008729 : win32k!GreSetRedirectionSurfaceSignaling+0x125[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff880`08887b60 fffff800`02cbdad3 : fffffa80`06bcfa60 fffffa80`06bc51a0 ffffffff`fffd67f0 fffffa80`06bc51a0 : win32k!NtGdiHLSurfSetInformation+0x209[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff880`08887be0 000007fe`ff6d4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]00000000`034af978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff6d4efa[/FONT][/COLOR]


[COLOR=#070F14][FONT=Verdana]FOLLOWUP_IP: [/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]cdd!DrvAssociateSharedSurface+7b[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]fffff960`006d6d3f ba0c000000 mov edx,0Ch[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]SYMBOL_STACK_INDEX: 1[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]SYMBOL_NAME: cdd!DrvAssociateSharedSurface+7b[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]FOLLOWUP_NAME: MachineOwner[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]MODULE_NAME: cdd[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]IMAGE_NAME: cdd.dll[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]DEBUG_FLR_IMAGE_TIMESTAMP: 4d3fbfc6[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]STACK_COMMAND: .cxr 0xfffff880088870b0 ; kb[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]FAILURE_BUCKET_ID: X64_0x3B_cdd!DrvAssociateSharedSurface+7b[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]BUCKET_ID: X64_0x3B_cdd!DrvAssociateSharedSurface+7b[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]Followup: MachineOwner[/FONT][/COLOR]
[COLOR=#070F14][FONT=Verdana]---------[/FONT][/COLOR]

[COLOR=#070F14][FONT=Verdana]================================================[/FONT][/COLOR]
My system currently is :
Window 7 Pro, 64 bit.
Bios Ver 6.05
Processor: Intel 2 Duo E7500 @ 2.93
RAM: 4GB
Display: NVIDIA Gefore GTX 750, 1 GB OC
PSU: Corsaic 430w

I believe all my devices are up to date except GPU, I am currently using the Driver that came along with its CD because I thought that the latest driver causes BSDO
Any help is appreciated,

thank you.

p.s: I have include the dump file below
 

Attachments

Last edited by a moderator:
Hi,

The attached DMP file is of the SYSTEM_SERVICE_EXCEPTION (3b) bug check.

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

Code:
1: kd> .trap fffff880`088878f0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006bcfa60 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000040002200 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c885fe rsp=fffff88008887a80 rbp=0000000000000000
 r8=ffffffffb1121700  r9=0000000000000040 r10=00000000034af9a0
r11=fffff88008887b08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
[COLOR=#ff0000]nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26[/COLOR]:

Code:
1: kd> knL
  *** Stack trace for last set context - .thread/.cxr resets it
 # Child-SP          RetAddr           Call Site
00 fffff880`08887a80 fffff960`006d6d3f [COLOR=#ff0000]nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26[/COLOR]
01 fffff880`08887ab0 fffff960`001dd365 [COLOR=#4b0082]cdd!DrvAssociateSharedSurface+0x7b[/COLOR]
02 fffff880`08887b10 fffff960`00200749 win32k!GreSetRedirectionSurfaceSignaling+0x125
03 fffff880`08887b60 fffff800`02cbdad3 win32k!NtGdiHLSurfSetInformation+0x209
04 fffff880`08887be0 000007fe`ff6d4efa nt!KiSystemServiceCopyEnd+0x13
05 00000000`034af978 00000000`00000000 0x7fe`ff6d4efa

^^ We have a cdd.dll routine (Canonical Display driver) called into ExEnterCriticalRegionAndAcquireFastMutexUnsafe. This puts the caller into a wait state if the specified fast mutex cannot be acquired immediately. Otherwise, the caller is given ownership of the mutex and exclusive access to the resource that the mutex protects until the caller releases the mutex.

Essentially, drivers can use fast mutexes if they require a low-overhead form of mutual exclusion for code that runs at IRQL <= APC_LEVEL. A fast mutex can protect a code path that must be entered by only one thread at a time. To enter the protected code path, the thread acquires the mutex. If another thread has already acquired the mutex, execution of the current thread is suspended until the mutex is released. To exit the protected code path, the thread releases the mutex.

What appears to have happened here is the mutex was never acquired, therefore the system bugchecked.



1. Update to Service Pack 1 ASAP: Learn how to install Windows 7 Service Pack 1 (SP1)

2. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

3. Uninstall SmartDefrag.

4. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

5. If all of the above fail to stop the crashes, please run a Memtest for NO less than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

Regards,

Patrick
 
Thanks Patrick,

I just finish doing all the steps except the memtest one. I also installed the latest driver for BIOS and Motherboard chipset. I have not install the latest driver for the graphic card, because NVIDIA Control Panel always stop working when I try to use it in the latest version. With that being said, the Gefore GTX 750 Just came out last February so its included driver should be pretty much up to date (its newest driver came out 3/10/14). I will reply if BSOD still happen to me. Thanks again
 
Great, thanks for the update.

I would prefer an update even if you don't crash, just so I know it's solved!

Regards,

Patrick
 
It've been 11 days since the fix and everything went very smooth. I resume my daily usage of games and videos and BSOD did not happen anymore. As for the service pack, I manually download the content onto a CD since the window update doesn't show it. As the story goes on, my window update acted funny so I turn off the checking for update and did not install any since the service pack. The reason is that there was a certain update that install the files when I turn on the computer and it goes on for like 1 hour and then it fail and have to revert, it happen 3 times but I don't really know which file because I'm too lazy and I don't really think these updates are neccessary at this time since my computer is doing well.

Thanks again Pat
 
My pleasure, glad to hear the crashes have ceased. If the update issue ever becomes bothersome, or a larger-scale problem, head over to our Updates forum here and it'll get taken care of.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top