Jump to content

BSOD experience need help

Carlisle05

OS - windows 7
·  x64
· What OS was originaly installed on the system? none
· Age of system (2 years)
· Age of OS installation - have you re-installed the OS? around a year
· CPU model i7 4770
· Video Card model igpu
· MotherBoard - gigabyte h97
· Power Supply - seasonic 850watts

· System Manufacturer SOTA
· Laptop or Desktop?desktop

 

 

files link: 
dump: https://drive.google.com/file/d/0B7KF5AmxJR_lQWRvMWs0WWhzQVU/view?usp=sharing

perfmon: https://drive.google.com/file/d/0B7KF5AmxJR_lVWdWR1FCaHJIbDQ/view?usp=sharing

not sure about google drive. i never use it. please tell me if im doing it wrong. 

 

TIA

Carisle

Edited by Carlisle05
Link to comment
Share on other sites

Link to post
Share on other sites

Explain more please.. In your own words.

And GPU? How come i7 with 850watts and you are using only your igpu???

Security Analyst & Tech Enthusiast

Ask me anything.

Link to comment
Share on other sites

Link to post
Share on other sites

hi stareX,  2 words unfinished business! planned to do sli with 750ti then 290x was release but having heat issue then 970 is release but also having 3.5gb issue and 980 is so expensive for me so still waiting for worth it semi future proof graphics card.  does it matter to my concern?

Link to comment
Share on other sites

Link to post
Share on other sites

First of all let me organize for you.

You can't SLI a 750ti.

Heat issues were on a reference card, there are cooled ones now for the 290x.

GTX 970 does have 4GB, the 0.5 are reserved (for over 1080p yes?)

GTX 980? Well yes it is expensive but doesn't matter.

Other than that, please explain what do you see in the BSOD error, what does it tell you that failed.

What are you doing when it happens and how often does it show up? Constantly or it was 1 time only? Could be system overload.

Security Analyst & Tech Enthusiast

Ask me anything.

Link to comment
Share on other sites

Link to post
Share on other sites

Since I was PM'd by the OP, here are my findings:

 

 

It seems that your BSODs aren't being caused by driver, but rather by some corrupt Windows system files, in specific cdd.dll which is causing the Win32k.sys to fail. The next likely cause is an hardware issue with your memory, as the BSODs are more or less happening during memory operations.

 

I would first start by running an SFC check.

Follow the instructions here: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Follow option 2. What does the command say? Are there any corrupted system files?

Windows 7 Kernel Version 7600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`0384e000 PsLoadedModuleList = 0xfffff800`03a8be50Debug session time: Sun May 17 08:43:05.408 2015 (UTC - 4:00)System Uptime: 0 days 0:36:34.454********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff960006d6d15, Address of the instruction which caused the bugcheckArg3: fffff880077370d0, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: cdd!DrvAssociateSharedSurface+51fffff960`006d6d15 399f50070000    cmp     dword ptr [rdi+750h],ebxCONTEXT:  fffff880077370d0 -- (.cxr 0xfffff880077370d0)rax=fffff960006d6cc4 rbx=0000000000000000 rcx=fffff900c2b36ce8rdx=0000000040002b00 rsi=fffff900c00e9d30 rdi=0000000000000000rip=fffff960006d6d15 rsp=fffff88007737ab0 rbp=fffff900c2b36ce8 r8=ffffffff8f121045  r9=0000000000000040 r10=000000000224fa30r11=fffff88007737b08 r12=ffffffff8f121045 r13=0000000040002b00r14=000000000458a770 r15=0000000000000001iopl=0         nv up ei ng nz na po cycs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287cdd!DrvAssociateSharedSurface+0x51:fffff960`006d6d15 399f50070000    cmp     dword ptr [rdi+750h],ebx ds:002b:00000000`00000750=????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0x3BPROCESS_NAME:  dwm.exeCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff960002977bd to fffff960006d6d15STACK_TEXT:  fffff880`07737ab0 fffff960`002977bd : 00000000`00000000 fffff900`c015fb50 00000000`0224fad0 00000040`00000280 : cdd!DrvAssociateSharedSurface+0x51fffff880`07737b10 fffff960`002ba969 : 00000000`00000001 fffff880`07737c60 00000000`0224fad0 00000000`0000a2e3 : win32k!GreSetRedirectionSurfaceSignaling+0x125fffff880`07737b60 fffff800`038bf153 : fffffa80`0c9b9b60 fffff880`07737c60 00000000`00000000 000007fe`f5d11a40 : win32k!NtGdiHLSurfSetInformation+0x209fffff880`07737be0 000007fe`fe5d4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0224fa08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe5d4efaFOLLOWUP_IP: cdd!DrvAssociateSharedSurface+51fffff960`006d6d15 399f50070000    cmp     dword ptr [rdi+750h],ebxSYMBOL_STACK_INDEX:  0SYMBOL_NAME:  cdd!DrvAssociateSharedSurface+51FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: cddIMAGE_NAME:  cdd.dllDEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94STACK_COMMAND:  .cxr 0xfffff880077370d0 ; kbFAILURE_BUCKET_ID:  X64_0x3B_cdd!DrvAssociateSharedSurface+51BUCKET_ID:  X64_0x3B_cdd!DrvAssociateSharedSurface+51Followup: MachineOwner 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`03865000 PsLoadedModuleList = 0xfffff800`03aa2e50Debug session time: Mon May 11 08:36:28.931 2015 (UTC - 4:00)System Uptime: 0 days 1:25:38.977********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff960001b4283, Address of the instruction which caused the bugcheckArg3: fffff88006472020, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: win32k!HmgLockEx+a3fffff960`001b4283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]CONTEXT:  fffff88006472020 -- (.cxr 0xfffff88006472020)rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa800b3c1060rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000rip=fffff960001b4283 rsp=fffff88006472a00 rbp=0000000000000000 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000r11=fffff88006472a68 r12=000000000472a600 r13=0000000000000000r14=0000000000000001 r15=0000000000000001iopl=0         nv up ei pl zr na po nccs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246win32k!HmgLockEx+0xa3:fffff960`001b4283 0fb7430c        movzx   eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0x3BPROCESS_NAME:  dwm.exeCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff9600036c6b0 to fffff960001b4283STACK_TEXT:  fffff880`06472a00 fffff960`0036c6b0 : fffff900`c0a4a630 00000000`00000001 00000000`34120d47 fffff900`c0a61690 : win32k!HmgLockEx+0xa3fffff880`06472a70 fffff960`0036bbae : fffff900`c0a4a630 00000000`00000000 00000d47`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40fffff880`06472aa0 fffff960`0036cab3 : 00000000`00000000 00000000`34120d47 fffff900`c0a4a630 00000000`0472a6ec : win32k!SFMLOGICALSURFACE::DeInitialize+0x4efffff880`06472ae0 fffff960`002c95ff : 00000000`00000000 fffff900`c00bf010 fffff900`c0a4a630 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4bfffff880`06472b20 fffff960`002ea908 : 00000000`00000001 00000000`00000001 fffff880`06472c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10ffffff880`06472b60 fffff800`038d6153 : fffffa80`0b3c1060 fffffa80`0c146e90 fffffa80`00000000 fffffa80`0c146e90 : win32k!NtGdiHLSurfSetInformation+0x1a8fffff880`06472be0 000007fe`fe764efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0242f5f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe764efaFOLLOWUP_IP: win32k!HmgLockEx+a3fffff960`001b4283 0fb7430c        movzx   eax,word ptr [rbx+0Ch]SYMBOL_STACK_INDEX:  0SYMBOL_NAME:  win32k!HmgLockEx+a3FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: win32kIMAGE_NAME:  win32k.sysDEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0STACK_COMMAND:  .cxr 0xfffff88006472020 ; kbFAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3Followup: MachineOwner 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7600.16385.amd64fre.win7_rtm.090713-1255Machine Name:Kernel base = 0xfffff800`0381a000 PsLoadedModuleList = 0xfffff800`03a57e50Debug session time: Thu May  7 08:40:53.630 2015 (UTC - 4:00)System Uptime: 0 days 12:48:32.691********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff8000385601e, Address of the instruction which caused the bugcheckArg3: fffff88002d7d0a0, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26fffff800`0385601e f00fba3100      lock btr dword ptr [rcx],0CONTEXT:  fffff88002d7d0a0 -- (.cxr 0xfffff88002d7d0a0)rax=fffffa800c2fd060 rbx=0000000000000000 rcx=0000000000000000rdx=0000000080000b40 rsi=fffff900c0c16830 rdi=fffffa800c2fd060rip=fffff8000385601e rsp=fffff88002d7da80 rbp=0000000000000000 r8=ffffffffcb121887  r9=0000000000000040 r10=ffffffffffffffefr11=fffff88002d7db08 r12=ffffffffcb121887 r13=0000000080000b40r14=0000000007feffa0 r15=0000000000000001iopl=0         nv up ei ng nz na po nccs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26:fffff800`0385601e f00fba3100      lock btr dword ptr [rcx],0 ds:002b:00000000`00000000=????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0x3BPROCESS_NAME:  dwm.exeCURRENT_IRQL:  0LAST_CONTROL_TRANSFER:  from fffff96000626d3f to fffff8000385601eSTACK_TEXT:  fffff880`02d7da80 fffff960`00626d3f : 00000000`00000000 00000000`00000000 ffffffff`cb121812 00000000`00000020 : nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x26fffff880`02d7dab0 fffff960`002377bd : 00000000`00000000 fffff900`c47f4ca0 00000000`0227f970 00000040`00000280 : cdd!DrvAssociateSharedSurface+0x7bfffff880`02d7db10 fffff960`0025a969 : 00000000`00000001 fffff880`02d7dc60 00000000`0227f970 00000000`000099d3 : win32k!GreSetRedirectionSurfaceSignaling+0x125fffff880`02d7db60 fffff800`0388b153 : fffffa80`0c2fd060 fffffa80`0bfdb860 fffffa80`0c2ca250 fffffa80`0bfdb860 : win32k!NtGdiHLSurfSetInformation+0x209fffff880`02d7dbe0 000007fe`fe134efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`0227f8a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fe134efaFOLLOWUP_IP: cdd!DrvAssociateSharedSurface+7bfffff960`00626d3f ba0c000000      mov     edx,0ChSYMBOL_STACK_INDEX:  1SYMBOL_NAME:  cdd!DrvAssociateSharedSurface+7bFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: cddIMAGE_NAME:  cdd.dllDEBUG_FLR_IMAGE_TIMESTAMP:  4a5bde94STACK_COMMAND:  .cxr 0xfffff88002d7d0a0 ; kbFAILURE_BUCKET_ID:  X64_0x3B_cdd!DrvAssociateSharedSurface+7bBUCKET_ID:  X64_0x3B_cdd!DrvAssociateSharedSurface+7bFollowup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

windows resource did not find any integrity violation  :(

Link to comment
Share on other sites

Link to post
Share on other sites

windows resource did not find any integrity violation  :(

What RAM are you using? Is it running with an XMP profile? Are you overclocking your CPU?

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

gskill 1x8gb cl10. XMP Profile im not sure, if its enabled by default then yes if not then no. no i don't overclock my cpu (non-k)

Link to comment
Share on other sites

Link to post
Share on other sites

gskill 1x8gb cl10. XMP Profile im not sure, if its enabled by default then yes if not then no. no i don't overclock my cpu (non-k)

Mind running at least 6 hours of Memtest86+

 

Follow the instructions here: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Post back if there are any issues with the memory.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×