BSOD(Dmp.files attached)

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by GearsOfWar3, Sep 17, 2011.

  1. GearsOfWar3

    Joined:
    Sep 17, 2011
    Messages:
    10
    Likes Received:
    0
    Hi guys been having blue screen lately since i've recently installed my graphics card here are the minidumpsView attachment dmp.zip Thanks guys sincerely , Brandon
     
  2. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    Hi welcome to the forum.

    Could you get CPU-z and take pics with snipping tool of each tab making sure you take pics of each populated memory slot in the program. Can you check the motherboard manufactures site for an updated bios. If your overclocking anything could you revert to stock settings be it video card or processor. Also please update to SP1 as it fixes multiple issues.

    Your latest dump was Stop 0xBE

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
    An attempt was made to write to readonly memory.  The guilty driver is on the
    stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff9600007f960, Virtual address for the attempted write.
    Arg2: 0a00000111096021, PTE contents.
    Arg3: fffff88005dd6de0, (reserved)
    Arg4: 000000000000000b, (reserved)
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xBE
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88005dd6de0 -- (.trap 0xfffff88005dd6de0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000800 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff9600006f45f rsp=fffff88005dd6f70 rbp=fffff900c019c34c
     r8=0000000000000000  r9=0000000000000000 r10=0000000080000000
    r11=00000000ffff0000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    win32k!fsg_CreateGlyphData+0x1eb:
    fffff960`0006f45f 6641894500      mov     word ptr [r13],ax ds:00000000`00000000=????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000314e9c2 to fffff800030ce5c0
    
    STACK_TEXT:  
    fffff880`05dd6c78 fffff800`0314e9c2 : 00000000`000000be fffff960`0007f960 0a000001`11096021 fffff880`05dd6de0 : nt!KeBugCheckEx
    fffff880`05dd6c80 fffff800`030cc6ae : 00000000`00000001 00000000`00000005 00000000`00000000 fffff960`000818fa : nt! ?? ::FNODOBFM::`string'+0x4223e
    fffff880`05dd6de0 fffff960`0006f45f : 00000000`00000005 fffff900`c019c34c fffff900`c019d1f8 00000000`00000005 : nt!KiPageFault+0x16e
    fffff880`05dd6f70 fffff960`0006c2b7 : fffff900`c019c1b8 fffff880`00000001 fffff900`c019c304 fffff900`c019e588 : win32k!fsg_CreateGlyphData+0x1eb
    fffff880`05dd7040 fffff960`0006bded : fffff900`c019c020 fffff900`c019c0d0 00000000`00000000 fffff880`058b6c00 : win32k!fsg_GridFit+0xb7
    fffff880`05dd70d0 fffff960`0006b9f1 : fffff900`c019fc58 fffff900`c019c0d0 fffff880`00000001 00000000`00000000 : win32k!fs__Contour+0x3a9
    fffff880`05dd71a0 fffff960`0006c89c : fffff900`c012ca90 fffff880`05dd7540 00000000`00000000 fffff880`058b6c00 : win32k!bGetGlyphOutline+0x129
    fffff880`05dd71e0 fffff960`0006c804 : fffff900`c012ca90 00000000`0000001d 00000000`0000001d 00000000`ffffffff : win32k!lGetGlyphBitmap+0x4c
    fffff880`05dd73a0 fffff960`0006c532 : 00000000`00000000 00000000`ffffffff fffff900`c01314f0 fffff900`c01314f0 : win32k!ttfdQueryFontData+0x278
    fffff880`05dd7400 fffff960`00040b7a : fffff960`0006c4c0 fffff900`c01314f0 00000000`00000001 00000000`00000000 : win32k!ttfdSemQueryFontData+0x72
    fffff880`05dd7460 fffff960`0007f6d2 : fffff900`c01314f0 00000000`00000072 fffff880`05dd77f0 00000000`00000000 : win32k!PDEVOBJ::QueryFontData+0x82
    fffff880`05dd74f0 fffff960`0007bbe7 : 00000000`00000072 fffff880`05dd77f0 00000000`00000002 00000000`0000001d : win32k!xInsertMetricsPlusRFONTOBJ+0x13a
    fffff880`05dd75c0 fffff960`0007b87d : fffff880`05dd7cf8 fffff880`05dd77f0 fffff900`c0081014 00000000`0000000f : win32k!RFONTOBJ::bGetGlyphMetricsPlus+0x1f7
    fffff880`05dd7640 fffff960`0007b270 : 00000000`00000000 fffff880`05dd7bd0 fffff900`c00be010 00000000`00000038 : win32k!ESTROBJ::vCharPos_H3+0x16d
    fffff880`05dd76c0 fffff960`000528de : 00000980`41800000 00000000`00000000 fffff880`00000001 fffff880`05dd7bd0 : win32k!ESTROBJ::vInit+0x350
    fffff880`05dd7750 fffff960`00051d5f : fffff900`00000000 00000000`00000003 00000000`00000002 00000000`00000000 : win32k!GreExtTextOutWLocked+0xb12
    fffff880`05dd7b70 fffff960`00051c39 : 00000000`03010035 00000000`00000000 00000000`00000002 fffff960`00051a40 : win32k!GreExtTextOutWInternal+0x10f
    fffff880`05dd7c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!GreExtTextOutW+0x3d
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!fsg_CreateGlyphData+1eb
    fffff960`0006f45f 6641894500      mov     word ptr [r13],ax
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  win32k!fsg_CreateGlyphData+1eb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4df2d94e
    
    FAILURE_BUCKET_ID:  X64_0xBE_win32k!fsg_CreateGlyphData+1eb
    
    BUCKET_ID:  X64_0xBE_win32k!fsg_CreateGlyphData+1eb
    
    Followup: MachineOwner
    When you've collated the information can you post the screenshots so we can investigate further.

    NnsUK
     
  3. GearsOfWar3

    Joined:
    Sep 17, 2011
    Messages:
    10
    Likes Received:
    0
    Cpu. Caches. Mainboard. Memory. SPD. Graphics. Here Are The Screenshots and i have service pack 1 downloaded.. it just says its not but it is glitched or something all i had to do was enter my windows 7 cd-key in again
     
  4. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    Can you get MBAM Free and do a scan of your system. If that comes back clean can you install microsoft security essential and let that do a full scan aswell. On looking through your .dmp files the windows version being reported is 6.1.7600 and not 6.1.7601. Can you grab the windows 7 update readiness tool and then install all the important and critical updates in windows update. If after doing all of those if you still bsod can you post the new dumps. Then goto your bios and set the command rate for your memory to 2T.
     
  5. GearsOfWar3

    Joined:
    Sep 17, 2011
    Messages:
    10
    Likes Received:
    0
    alright done the microsoft thing.. what about the command rate thing in the bios i cant seem to find it..
     
  6. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    Hey nmsuk, the stack trace seems to have several references to fonts or glyphs or bitmaps. This might go along with the new video card mentioned. Any chance some type of special font is being used, or would something like these entries be caused by a bad video driver--maybe related to DirectX?

    Just asking because I have not seen those types of entries before.
     
  7. GearsOfWar3

    Joined:
    Sep 17, 2011
    Messages:
    10
    Likes Received:
    0
    Hey SaltGrass I Am Actually Having Problems With My Video Driver I Think It Keeps Saying Display Driver has Stopped Responding Freezing My Computer Screen Working For The Next 5 mints then stopping then working Then Aventually freezing to where i have to hard-reboot my computer .. and i have also have dx bsod before but that was only when driver verifier was on.. it said dxgmms1.sys and dxkrnl.sys
     
  8. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    Could be called command. Rate or ma timing
     
  9. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    The mention of glyphs and fonts is a problem my end as I used windows 8 to do the debugging
     
  10. GearsOfWar3

    Joined:
    Sep 17, 2011
    Messages:
    10
    Likes Received:
    0
    Ok About The Thing In The Bios.. I went to OC tweaker then found dram timing and then inside that i found something that says command? and its on auto and the options are auto , 1 or 2 .. is that what im looking for ??
     
  11. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    Yes that's the setting :)
     
  12. Dynamics

    Dynamics New Member

    Joined:
    Sep 10, 2011
    Messages:
    70
    Likes Received:
    0
    Alright , so what is this exactly suppose to do... my friend(works and rebuilds them "still not that intelligent") is really good with computers and said that the dram timing command should have nothing to do with my problem o_O. not that i doubt you but im just asking what it does.. im kinda lost.. about these blue screens of death lol.. can you give me a short summary of what i does XD?
     
  13. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    Simplified it's the delay between commands 1T is faster but if suffering instabilities use 2T. I agree to disagree with your friend :)
     
    1 person likes this.
  14. Dynamics

    Dynamics New Member

    Joined:
    Sep 10, 2011
    Messages:
    70
    Likes Received:
    0
    Oh Gotcha, Im Gears Also Btw.. I made that account because i forgot the password to this one lol.. i changed command rate to 2t and started it got all the ways where it said windows 7 welcome loading screen , then blue screen.. i restarted with normal setting i had it on.. i got to the desktop this time click the start menu button and it like froze.. like i could move the mouse around but not like click anything i could hit alt-control-delete and bring that up.. but it was just froze couldnt click anything and earlier while surfing the web i got some weird thing saying 0x00001 could not recieve 0x0000002 ( (---Example ) and the error at the top was like in chinesee or something .. im starting to think that i got a bad memory ... its a ddr3 dual channel... also when i went in the bios it said memory mode single channel... does that have anything to do with it.. because i mean i just wiped my system yesterday put a fresh clean load of windows 7 and im still having problems...
     
  15. nmsuk

    nmsuk Windows Forum Admin
    Staff Member Premium Supporter

    Joined:
    Sep 7, 2009
    Messages:
    2,709
    Likes Received:
    195
    Which slots do you have the memory in?
     
  16. Saltgrass

    Saltgrass Excellent Member
    Microsoft Community Contributor

    Joined:
    Oct 16, 2009
    Messages:
    15,157
    Likes Received:
    393
    I can't find where anyone has asked you about your system. When you get time, could you go over the components used in your system, such as make and model of motherboard, Hard drives and connections, Video Card, Power supply, etc.

    When you do a fresh install of Windows 7, are you running it is a basic mode for a while without installing other software? Where are you getting your drivers?

    I would try running the system outside of Windows, like an Ubuntu live version for testing. You might even try installing a 32 bit version of Windows 7 to see if it might be related to the x64 drivers.

    I do still see the Font comment in the Stack Trace, so it might be relevant.

    Windows 7 seems to have changed the way memory is managed. I would think the memory corruption message may be caused by other things than just the basic memory.
     

Share This Page

Loading...