BSOD twice today dont know the origin of the problem


  1. Posts : 5
    32 bit ultimate
       #1

    BSOD twice today dont know the origin of the problem


    Hey im new on the forum! So please pardon me if i'm rude or anything like that.
    Today i had 2 BSOD but i dont know the problem, the first one i was seeing a video on youtube and it happend, the second one i was away from the PC and when i came back there was the BOSD.
    I got the zip file with the info. Please help!
    Wriken
      My Computer


  2. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #2

    Hello and welcome to SevenForums.

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {d, 0, 0, 0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_POLICY::Enable+13 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    UNEXPECTED_KERNEL_MODE_TRAP (7f)
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
    Else
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    Endif
    kb will then show the corrected stack.
    Arguments:
    Arg1: 0000000d, EXCEPTION_GP_FAULT
    Arg2: 00000000
    Arg3: 00000000
    Arg4: 00000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_d
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  csgo.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre
    
    LAST_CONTROL_TRANSFER:  from 938d914d to 82e4a2bf
    
    STACK_TEXT:  
    a5257b60 938d914d badb0d00 00015724 00000000 nt!KiSystemFatalException+0xf
    a5257bd8 938e5bdb 00000000 b2eb7868 00000000 dxgmms1!VIDMM_POLICY::Enable+0x13
    a5257bf8 938e5cf5 87a4a000 87a4a000 b262c400 dxgmms1!VIDMM_PROCESS::InitializeProcessAdapterInfo+0x16b
    a5257c10 938e5e14 87a4a000 00000001 b469d5b0 dxgmms1!VIDMM_PROCESS::OpenAdapter+0x2b
    a5257c28 938c7613 87a4a000 b469d5b0 a5257c4c dxgmms1!VIDMM_DEVICE::Init+0x72
    a5257c38 9381a3de b262c400 87a4a000 b469d5b0 dxgmms1!VidMmInitDevice+0x13
    a5257c4c 93881065 86167490 b262c400 87a4a000 dxgkrnl!VIDMM_EXPORT::VidMmInitDevice+0x1a
    a5257c78 938815a0 00000000 00000001 87892000 dxgkrnl!DXGDEVICE::Initialize+0x147
    a5257c9c 9388126e a5257d0c 00000001 00000000 dxgkrnl!DXGADAPTER::CreateDevice+0xf4
    a5257d28 82e468c6 001bc7ac 001bc7d0 771c70f4 dxgkrnl!DxgkCreateDevice+0x1a2
    a5257d28 771c70f4 001bc7ac 001bc7d0 771c70f4 nt!KiSystemServicePostCall
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    001bc7d0 00000000 00000000 00000000 00000000 0x771c70f4
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_POLICY::Enable+13
    938d914d 83e001          and     eax,1
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  dxgmms1!VIDMM_POLICY::Enable+13
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5164d8b5
    
    IMAGE_VERSION:  6.1.7601.18126
    
    FAILURE_BUCKET_ID:  0x7f_d_dxgmms1!VIDMM_POLICY::Enable+13
    
    BUCKET_ID:  0x7f_d_dxgmms1!VIDMM_POLICY::Enable+13
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x7f_d_dxgmms1!vidmm_policy::enable+13
    
    FAILURE_ID_HASH:  {1a6dceb5-b6c3-0e1c-31a0-b1f97e6349c2}
    
    Followup: MachineOwner
    ---------
    dxgmms1.sys is what caused the crash, its DirectX Graphics MMS.

    DxDiag Version: 6.01 32bit Unicode.

    Please update Direct X, and see how the BSOD's are then.

    Also you Graphic card driver is out of date.

    Driver Version: 8.970.100.1100

    Please update: Legacy
      My Computer


  3. Posts : 5
    32 bit ultimate
    Thread Starter
       #3

    Thanks :) ill try that
      My Computer


  4. Posts : 3,904
    Windows 7 Ultimate 64-bit
       #4

    No worries let me know how it goes.
      My Computer


  5. Posts : 5
    32 bit ultimate
    Thread Starter
       #5

    Hello after a few months without any problems, a few weeks ago i started having blue screens every 2 days and i dont seem to find the solution, here's the debug file
      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 11:51.
Find Us