BSOD Code:3B Before and After fresh OS Install

Page 1 of 2 12 LastLast

  1. Posts : 10
    Windows 7 Ultimate 64bit
       #1

    BSOD Code:3B Before and After fresh OS Install


    I send post yesterday but nobody answer. Somebody has similar problem before some time but I don't know how problem completed.

    For me BSOD only when try to shut down or restart comp.

    BSOD Code: 3b
    Caused by Driver: dxgkrnl.sys
    Caused by Adress: dxgkrnl.sys+2756

    After that computer restart, boot and I shut down normal. I can turn on and again normal restart/shut down. Always after playing game and when immediately try to shut down or computer in idle sometimes and I install some program than software want restart and i see BSOD. For now 5 BSOD for one week.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #2

    The information you provided is a little ambiguous. Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with additional information about your system so we may better help you.

    The driver you mention is part of DirectX. Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.

    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    8. Restart your computer after uninstalling drivers for all display cards
    9. Install the latest driver for the display cards once Windows starts


    Alternatively:
    1. Login as an adminstrative user
    2. Download the latest drivers for your display card(s)
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Expand Display adapters
    8. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer after uninstalling drivers for all display cards
    10. Install the latest driver for the display cards once Windows starts
      My Computer


  3. Posts : 10
    Windows 7 Ultimate 64bit
    Thread Starter
       #3

    My display driver is always last driver. Not preview or beta. I have one graphic card.
    Everytime I uninstall and clean in safe mode with Driver Cleaner Pro or Driver Sweaper or both and first uninstall in device manager. Sound driver is same like always from mobo site

    Now wait 12.1 driver. But I think this is not software issue or is some windows update.

    My computer work almost one year normal.
    No HW install few months. Maybe 11.12 is problem but I am not sure. I must wait few hours or few days to see BSOD.
    Everything is on default clocks and now wait. I flash mobo BIOS, connect everything again.
    PSU only can test 5V and 12V with multimeter on molex and
    both rails are perfect.
    I will test RAM overnight. No BSOD today with several restart but problem it's not over.
    Everything is under warranty but I must know first what is problem???
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with additional information about your system so we may better help you.
      My Computer


  5. Posts : 10
    Windows 7 Ultimate 64bit
    Thread Starter
       #5

    I install BlueScrean Viewer but no minidump file no.
    When hit again i will post.
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #6

    To configure Windows to create minidumps, see Dump Files - Configure Windows to Create on BSOD OPTION ONE part 6. Also, do not use CCleaner or Windows disk cleaner after a blue screen as these may delete the minidump files.
      My Computer


  7. Posts : 10
    Windows 7 Ultimate 64bit
    Thread Starter
       #7

    OK i have BSOD after few minutes but need help to post (sorry).
    I do what you say and save report in my documents Windows_NT6_BSOD_jcgriff2 folder.
    And System Healt Report I save as HTML to desktop.
    What now to do with HTML and folder in my documents.

    I think to copy system healt report in folder Windows_NT6_BSOD_jcgriff2 folder and everything to compress and attach???
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #8

    Vlada said:
    OK i have BSOD after few minutes but need help to post (sorry).
    I do what you say and save report in my documents Windows_NT6_BSOD_jcgriff2 folder.
    And System Healt Report I save as HTML to desktop.
    What now to do with HTML and folder in my documents.
    In your reply box, there is a paperclip symbol for uploading files.

    There is a useful tutorial for how to upload files on these forums, as well. You can follow the Screenshots and Files - Upload and Post in Seven Forums tutorial.
      My Computer


  9. Posts : 10
    Windows 7 Ultimate 64bit
    Thread Starter
       #9

    Attachment 194280

    I am sorry i will try again if this is wrong
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #10

    Code:
    Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Vlada\Windows_NT6_BSOD_jcgriff2\012112-12277-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\users\mike\documents\symbols*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`02c0c000 PsLoadedModuleList = 0xfffff800`02e51670
    Debug session time: Sat Jan 21 10:11:25.386 2012 (UTC - 7:00)
    System Uptime: 0 days 12:00:04.900
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff88005706756, fffff8800ba3fd00, 0}
    
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::ReleaseReference+16 )
    
    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: fffff88005706756, Address of the instruction which caused the bugcheck
    Arg3: fffff8800ba3fd00, 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: 
    dxgkrnl!DXGADAPTER::ReleaseReference+16
    fffff880`05706756 f0480fc17918    lock xadd qword ptr [rcx+18h],rdi
    
    CONTEXT:  fffff8800ba3fd00 -- (.cxr 0xfffff8800ba3fd00)
    rax=fffff8a023800000 rbx=ffbffa8007dc1000 rcx=ffbffa8007dc1000
    rdx=0000000000007a2e rsi=ffbffa8007dc1000 rdi=ffffffffffffffff
    rip=fffff88005706756 rsp=fffff8800ba406e0 rbp=0000000000000001
     r8=000000000000f45c  r9=fffff8a023800000 r10=0000000000ff0011
    r11=fffff88005771578 r12=00000000001f3800 r13=0000000000000000
    r14=0000000000000001 r15=00000000000000ad
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    dxgkrnl!DXGADAPTER::ReleaseReference+0x16:
    fffff880`05706756 f0480fc17918    lock xadd qword ptr [rcx+18h],rdi ds:002b:ffbffa80`07dc1018=????????????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x3B
    
    PROCESS_NAME:  sidebar.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88005706756
    
    STACK_TEXT:  
    fffff880`0ba406e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::ReleaseReference+0x16
    
    
    FOLLOWUP_IP: 
    dxgkrnl!DXGADAPTER::ReleaseReference+16
    fffff880`05706756 f0480fc17918    lock xadd qword ptr [rcx+18h],rdi
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgkrnl!DXGADAPTER::ReleaseReference+16
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa
    
    STACK_COMMAND:  .cxr 0xfffff8800ba3fd00 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x3B_dxgkrnl!DXGADAPTER::ReleaseReference+16
    
    BUCKET_ID:  X64_0x3B_dxgkrnl!DXGADAPTER::ReleaseReference+16
    
    Followup: MachineOwner
    ---------
    If you are overclocking anything, please stop.

    Older versions of ASACPI.SYS are a known BSOD problem on Windows 7. Update the driver by:
    1. Going to the Asus motherboard support site
      When you reach the website:
    2. Scroll down the page and click Utilities
    3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
    4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
    5. Download and install the driver.
    6. After installation is complete, verify that it installed correctly.
      • Click Start Menu
      • Click My Computer
      • Go to C:\WIndows\System32\drivers\
      • Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)


    Thanks to JMH and zigzag3143 for the above information.

    Code:
    ASACPI	fffff880`04572000	fffff880`0457a000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
      My Computer


 
Page 1 of 2 12 LastLast

  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 16:32.
Find Us