Blue Screen of Death after Sleep ... (Brand new custom build)


  1. Posts : 1
    Windows 7 Pro 64 bit
       #1

    Blue Screen of Death after Sleep ... (Brand new custom build)


    Last weekend I built my first home theater PC. It was a lot of fun and everything went smooth until I started getting the Blue Screen of Death. It seems to happen after it wakes up from sleep (S3). It's not always a BSOD but sometimes its a black screen (nothing). After restarting machine it's usually ok. This is a Mini ITX machine with the following components. I purchased everything from NewEgg and all the parts arrived together and everything was built at once on the same day (Saturday Jan. 7th). So all the following components are all brand new.

    Case: Silverstone SG06-450 Mini ITX (450 watt PSU)

    Motherboard: Biostar TH61 ITX

    Processor: Intel Core i3-2105 Sandy Bridge 3.1GHz LGA 1155 65W Dual-Core Desktop Processor Intel HD Graphics 3000

    RAM: G.SKILL Ripjaws X Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333

    Solid State Drive: SanDisk Ultra SDSSDH-120G-G25 2.5" 120GB SATA II Internal (SSD)

    Optical Drive: Sony Optiarc Black 4.8X BD-ROM 8X DVD-ROM 24X CD-ROM SATA Slim Internal 12.7mm Slot Blu-ray Combo Model BC-5650H-01


    Below is my minidump file C:\Windows\MiniDump

    HELP!!!:) Thanks!

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [G:\011112-6973-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\XPsymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02c12000 PsLoadedModuleList = 0xfffff800`02e57670
    Debug session time: Wed Jan 11 08:40:51.758 2012 (UTC - 6:00)
    System Uptime: 0 days 10:38:20.096
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    ............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff96000290ad7, fffff88008cecea0, 0}
    
    Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::SetShape+157 )
    
    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: fffff96000290ad7, Address of the instruction which caused the bugcheck
    Arg3: fffff88008cecea0, 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!SFMLOGICALSURFACE::SetShape+157
    fffff960`00290ad7 488b5508        mov     rdx,qword ptr [rbp+8]
    
    CONTEXT:  fffff88008cecea0 -- (.cxr 0xfffff88008cecea0)
    rax=fffff88008ced8c8 rbx=0000000000000000 rcx=fffff900c2ff9d40
    rdx=fffff900c00c0010 rsi=0000000000000000 rdi=fffff900c2ff9d40
    rip=fffff96000290ad7 rsp=fffff88008ced880 rbp=0000000000000018
     r8=000000003b1207e6  r9=00000000000007dd r10=0000000000001797
    r11=fffff88008ced8b0 r12=0000000000000001 r13=fffff900c00c0010
    r14=fffff900c00c0010 r15=8000000000001000
    iopl=0         nv up ei pl nz na pe nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
    win32k!SFMLOGICALSURFACE::SetShape+0x157:
    fffff960`00290ad7 488b5508        mov     rdx,qword ptr [rbp+8] ss:0018:00000000`00000020=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff96000290ad7
    
    STACK_TEXT:  
    fffff880`08ced880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SFMLOGICALSURFACE::SetShape+0x157
    
    
    FOLLOWUP_IP: 
    win32k!SFMLOGICALSURFACE::SetShape+157
    fffff960`00290ad7 488b5508        mov     rdx,qword ptr [rbp+8]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  win32k!SFMLOGICALSURFACE::SetShape+157
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5a
    
    STACK_COMMAND:  .cxr 0xfffff88008cecea0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
    
    BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
    
    Followup: MachineOwner
    ---------
    Last edited by XrayPhil; 11 Jan 2012 at 13:00. Reason: Added info
      My Computer


  2. Posts : 3,139
    Systems 1 and 2: Windows 7 Enterprise x64, Win 8 Developer
       #2

    Sorry you are having problems.

    Please do the following:

    https://www.sevenforums.com/crashes-d...tructions.html
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:29.
Find Us