BSOD Memory_Management

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Ultimate x64
       #1

    BSOD Memory_Management


    Age of system hardware is 7 days.
    Age of OS is 7 days.
    OS: Windows 7 x64
    Spec: Core i7 950
    12GB Corsair RAM
    Gigabyte GA X58A-UD3R (Rev 2, i think?)
    XFX HD 5670 1GB (ATI)
    Samsung Spinpoint 1TB HDD (sata)



    Somehow, I think this maybe a driver or software issue.

    Edit: Have the latest official Drivers and BIOS installed.
      My Computer


  2. Posts : 878
    Windows 7 Ultimate x64 SP1
       #2

    Hi and welcome to SF! :)
    I ask that you wait a little. Soon will come a member of the BSOD Team to help you. I wish you luck and a nice stay in this forum!
      My Computer


  3. Posts : 507
    Windows 7 Ultimate x64 SP1
       #3

    Hello,
    First uninstall Gigabyte EasyTune6 driver and Gigabyte Easy Saver to see if the BSOD would stop.
    Code:
    c:\windows\gvtdrv64.sys
    c:\windows\gdrv.sys
    Also remove Daemon Software and uninstall its driver (sptd) with SPTDinst. → DuplexSecure - Downloads
    Because sptd have some issue with Windows 7.
    For alternative CD/DVD virtual software you may use magicIso.

    Log
    Code:
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Machine Name:
    Kernel base = 0xfffff800`0305d000 PsLoadedModuleList = 0xfffff800`0329ae50
    Debug session time: Fri Mar 18 06:07:08.033 2011 (GMT-8)
    System Uptime: 0 days 0:17:16.063
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41790, fffffa80048931e0, ffff, 0}
    
    Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, The subtype of the bugcheck.
    Arg2: fffffa80048931e0
    Arg3: 000000000000ffff
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41790
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80003140f9e to fffff800030cd740
    
    STACK_TEXT:  
    fffff880`0d9a1538 fffff800`03140f9e : 00000000`0000001a 00000000`00041790 fffffa80`048931e0 00000000`0000ffff : nt!KeBugCheckEx
    fffff880`0d9a1540 fffff800`03100df9 : 00000000`00000000 00000000`062fdfff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33906
    fffff880`0d9a1700 fffff800`033e4010 : fffffa80`098ea690 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
    fffff880`0d9a1820 fffff800`033e441b : 00000000`00000000 00000000`061f0000 fffffa80`00000001 00000000`00000000 : nt!MiUnmapViewOfSection+0x1b0
    fffff880`0d9a18e0 fffff800`030cc993 : 00000000`06215000 00000000`00000000 fffffa80`09d7fb30 fffff880`0d9a1b50 : nt!NtUnmapViewOfSection+0x5f
    fffff880`0d9a1930 fffff800`030c8f30 : fffff960`00184c58 fffff880`0d9a1ca0 fffffa80`09e56780 00000000`0010ddb8 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`0d9a1ac8 fffff960`00184c58 : fffff880`0d9a1ca0 fffffa80`09e56780 00000000`0010ddb8 fffff880`0d9a1bd0 : nt!KiServiceLinkage
    fffff880`0d9a1ad0 fffff800`030cc993 : 00000000`030111b8 00000000`00000254 00000000`00000000 00000000`00000000 : win32k!NtGdiCreateDIBSection+0x3e4
    fffff880`0d9a1bb0 00000000`73f1056a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0010dd98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73f1056a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!NtGdiCreateDIBSection+3e4
    fffff960`00184c58 488bcf          mov     rcx,rdi
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  win32k!NtGdiCreateDIBSection+3e4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d23ecb0
    
    FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4
    
    BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm win32k
    start             end                 module name
    fffff960`000b0000 fffff960`003c0000   win32k     (pdb symbols)          c:\symbols\win32k.pdb\37B842136414455F88E0369BAAB0B7962\win32k.pdb
        Loaded symbol image file: win32k.sys
        Mapped memory image file: C:\Symbols\win32k.sys\4D23ECB0310000\win32k.sys
        Image path: \SystemRoot\System32\win32k.sys
        Image name: win32k.sys
        Timestamp:        Tue Jan 04 19:59:44 2011 (4D23ECB0)
        CheckSum:         00309E24
        ImageSize:        00310000
        File version:     6.1.7600.16732
        Product version:  6.1.7600.16732
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoftฎ Windowsฎ Operating System
        InternalName:     win32k.sys
        OriginalFilename: win32k.sys
        ProductVersion:   6.1.7600.16732
        FileVersion:      6.1.7600.16732 (win7_gdr.110104-1502)
        FileDescription:  Multi-User Win32 Driver
        LegalCopyright:   ฉ Microsoft Corporation. All rights reserved.
      My Computer


  4. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #4

    I've looked for the actual uninstalled but it seems like i have removed it. Shall i just delete the file then?
      My Computer


  5. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #5

    VISTA_DRIVER_FAULT, i noticed, so i think it maybe my linksys Wireless dongle that could be causing the crash. Since that is the only driver from Vista.

    The one from windows update is 2006 and the one I had running is 2004. Gonna update it and see how things go.
      My Computer


  6. Posts : 507
    Windows 7 Ultimate x64 SP1
       #6

    nsv007 said:
    I've looked for the actual uninstalled but it seems like i have removed it. Shall i just delete the file then?
    Yes, delete it manually.

    nsv007 said:
    VISTA_DRIVER_FAULT, i noticed, so i think it maybe my linksys Wireless dongle that could be causing the crash. Since that is the only driver from Vista.

    The one from windows update is 2006 and the one I had running is 2004. Gonna update it and see how things go.
    That's a good plan.
    Let us know the result.
      My Computer


  7. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Still got the BSOD, starting to think it may just be the dongle not playing nice with win7.
      My Computer


  8. Posts : 13,354
    Windows 7 Professional x64
       #8

    Update your Realtek ethernet drivers: Realtek
    Code:
    Rt64win7.sys    Thu Mar 04 08:42:52 2010 (4B8FB8DC)
    Disconnect the wireless adapter for now, if at all possible.

    Run driver verifier: Driver Verifier - Enable and Disable

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sat Mar 19 12:20:44.939 2011 (UTC - 4:00)
    System Uptime: 0 days 0:12:49.969
    Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4
    SystemProductName = X58A-UD3R
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      
    
      My Computer


  9. Posts : 9
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Jonathan_King said:
    Update your Realtek ethernet drivers: Realtek
    Code:
    Rt64win7.sys    Thu Mar 04 08:42:52 2010 (4B8FB8DC)
    Disconnect the wireless adapter for now, if at all possible.

    Run driver verifier: Driver Verifier - Enable and Disable

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sat Mar 19 12:20:44.939 2011 (UTC - 4:00)
    System Uptime: 0 days 0:12:49.969
    Probably caused by : win32k.sys ( win32k!NtGdiCreateDIBSection+3e4 )
    BUGCHECK_STR:  0x1a_41790
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!NtGdiCreateDIBSection+3e4
    SystemProductName = X58A-UD3R
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      
    
    So, I get a different BSOD to do with win32k.sys. I have put a different wireless card and not had the same vista_driver_fault.

    See attached dump.

    *I have installed the drivers for the ethernet.
      My Computer


  10. Posts : 13,354
    Windows 7 Professional x64
       #10

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
    Debug session time: Sun Mar 20 07:14:57.814 2011 (UTC - 4:00)
    System Uptime: 0 days 0:31:54.930
    Probably caused by : win32k.sys ( win32k!xxxDestroyThreadInfo+dba )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID:  X64_0x50_win32k!xxxDestroyThreadInfo+dba
    SystemProductName = X58A-UD3R
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
      
    
    That came before or after you removed the network adapter?
      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 04:59.
Find Us