WinDbg ignore missing pages!

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Grizzlyadamz, May 15, 2015.

  1. Grizzlyadamz

    Grizzlyadamz Senior Member

    Joined:
    Jun 3, 2010
    Messages:
    8
    Likes Received:
    0
    Hey, last couple days my PC's been shutting down/restarting without warning. (I uh, can't tell. It hasn't shutdown/restarted *properly* since I put it together a few years ago)
    Figured it might be memory/PSU failure, so I scheduled a mem-test and cleaned out the guts for good measure, (I dunno, maybe something was overheating).
    Mem-test came back clear, but I just had a BSOD.
    WinDbg's workin, question now is:

    How do I actually go about suppressing a missing page error?

    I've tried inputting '.ignore_missing_pages 1' as it suggests, but it just returns 'Suppress kernel summary dump missing page error message' and sits, waiting for input.
    Restarting just runs into the same error.

    How do I tell it to resume?

    Kinda learning on the fly here, so thanks for reading/responding.

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {8, 80050031, 406f8, fffff960002af034}

    Page 3cab6f not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : win32k.sys ( win32k!BltLnkRect+1c )

    Followup: MachineOwner
    ---------

    2: kd> .ignore_missing_pages 1
    Suppress kernel summary dump missing page error message

    -e
    Adwords was messing up --->>> memtest
     
  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,849
    Likes Received:
    1,569
    Hi Grizzly,
    actually this is the first time I've come across this too. I know someone who will probably know the answer so will ask if they'll take a look. Can you tell me what you have the settings at for creating dump files please. Is it 'small memory dump'? If not please change and see if it makes a difference.
     
  3. Grizzlyadamz

    Grizzlyadamz Senior Member

    Joined:
    Jun 3, 2010
    Messages:
    8
    Likes Received:
    0
    Nope, Kernal Memory Dump.
    [​IMG]

    I've been following this guide.


    -e
    I should say, the BSOD the dump is from occurred before I tinkered with any of the settings.
    However, the only setting I changed was 'Automatically restart', which I unchecked.
    Next time I'll know to look at/copy down more of the text on the BSOD display.
     
  4. jcgriff2

    jcgriff2 Honorable Member
    Microsoft MVP

    Joined:
    Sep 12, 2009
    Messages:
    195
    Likes Received:
    29
    Hi. . .

    Sorry, but I'm not following exactly what's going on here.

    Where is this "missing page error" appearing within Windbg and after what KD command is issued?

    Is it actually returning a memory address?

    Can you zip up and attach the dump please so we can run it through Windbg ourselves to check it out?

    Thanks.

    Regards. . .

    jcgriff2
     
  5. jcgriff2

    jcgriff2 Honorable Member
    Microsoft MVP

    Joined:
    Sep 12, 2009
    Messages:
    195
    Likes Received:
    29
    Apologies... I didn't see the spoiler in post #1 that was "hiding" the Windbg output! :0

    I see that the bugcheck is 0x7f (0x8,,,) - a "double fault" -- the error handler was processing/handling an exception that resulted in another exception -- sort of like an error within an error. The CPU then signals a double fault; BSOD ensues.

    Seeing the reference to an actual page in Windbg -- "Page 3cab6f not present in the dump file" - leads me to believe there may be something amiss with the page file. I would first suggest to delete and reallocate the page file before attempting other fixes -

    http://www.sysnative.com/forums/windows-8-windows-rt-tutorials/11716-deletion-reallocation-of-page-file-windows-10-8-1-8-7-vista.html

    For info, I have seen such error messages before (related to missing page(s)), but honestly don't recall what was done to remedy it.

    Seeing as the page file may be an issue here, it would be prudent to test the HDD.

    If HDD, run SeaTools for DOS, LONG test - http://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html

    If SSD, check SSD manufacturer's support site for a firmware upgrade.

    I would still like to see the mini dump, just to make sure we all get the same error message from Windbg (which we should).

    Regards. . .

    jcgriff2
     
    kemical likes this.
  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,849
    Likes Received:
    1,569
    Much thanks John for taking a look at this issue.
     
  7. Grizzlyadamz

    Grizzlyadamz Senior Member

    Joined:
    Jun 3, 2010
    Messages:
    8
    Likes Received:
    0
    As Kemical said, thank you. (you too kemical)


    Following the guide, when I go to "remove the "hidden" and "system" file attributes from the page file.", the elevated cmd prompt returns
    Code:
    File not found -  C:\pagefile.sys
    Taking a looksie in C & E with hidden files & protected windows files displayed, didn't see a trace. Searching also turned up nothing.

    Just set the system to use a pagefile again, (undid what I'd just done), and am in the process of uploading the memory dump. It'll take a while, it's just shy of a gig & upspeed is only 200kb.
    Forgot to compress it. Should be done uploading in ~10min.

    And I finally got around to reading the 'how to ask for help' sticky.
    Heh, when I first started the thread I didn't think it would be this involved.
    Ought I go follow the directions now?


    Here's the dump file: https://www.dropbox.com/s/9p9409zcbud82od/MEMORY.rar?dl=0
    --This is from a second BSOD that occurred under similiar circumstances earlier today. It has the same error in windbg.
     
    #7 Grizzlyadamz, May 15, 2015
    Last edited: May 15, 2015
  8. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,849
    Likes Received:
    1,569
    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ross\Downloads\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\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.18839.amd64fre.win7sp1_gdr.150427-0707
    Machine Name:
    Kernel base = 0xfffff800`0345f000 PsLoadedModuleList = 0xfffff800`036a6730
    Debug session time: Sat May 16 01:40:29.257 2015 (UTC + 1:00)
    System Uptime: 0 days 6:35:48.490
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...................................................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 000007ff`fffd9018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 7F, {8, 80050031, 406f8, fffff960002ef2bc}
    
    Page 3b8f6d not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : win32k.sys ( win32k!BltLnkRect+1c )
    
    Followup: MachineOwner
    ---------
    
    2: kd> hh dbgerr004
           ^ Syntax error in 'hh dbgerr004'
    windbg> .hh dbgerr004
    2: kd> .ignore_missing_pages 1
    Suppress kernel summary dump missing page error message
    2: kd> !analyze -v;r;kv;lmtsmn;.bugcheck;!peb;!sysinfo cpuinfo;!sysinfo machineid; !sysinfo cpuspeed; !sysinfo smbios
    *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: 0000000080050031
    Arg3: 00000000000406f8
    Arg4: fffff960002ef2bc
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x7f_8
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  csrss.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800034d2e69 to fffff800034d38c0
    
    STACK_TEXT: 
    fffff880`0336bce8 fffff800`034d2e69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
    fffff880`0336bcf0 fffff800`034d1332 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0336be30 fffff960`002ef2bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
    fffff880`0770ac80 fffff960`002ef19b : fffff880`0770b390 00550061`00690073 fffffa80`00b96b20 fffff800`034f9b90 : win32k!BltLnkRect+0x1c
    fffff880`0770b2f0 fffff960`000c61f6 : fffff900`00000000 fffff900`00000000 fffff900`c38dd770 fffff880`0770b860 : win32k!BltLnk+0x9c7
    fffff880`0770b640 fffff960`00295827 : fffff900`c00c3010 fffff900`c238d028 00000000`00000000 fffff900`c38dd770 : win32k!EngBitBlt+0x782
    fffff880`0770b740 fffff960`00285730 : fffff900`c00c3010 00000000`00000000 00000000`00000001 fffff900`c0000840 : win32k!BLTRECORD::bBitBlt+0xb4b
    fffff880`0770b930 fffff960`00190537 : fffff900`c2166110 00000000`1001085b 00000000`00000000 00000000`00000020 : win32k!GreStretchBltInternal+0xa14
    fffff880`0770bbd0 fffff960`001907d4 : 00000000`00000000 00000000`00000020 fffff900`c2166110 fffff900`c00c3010 : win32k!BltIcon+0x18f
    fffff880`0770bc80 fffff960`001a5c45 : 00000000`0b010f83 00000000`00000011 fffff900`00000015 00000000`00000000 : win32k!DrawIconEx+0x234
    fffff880`0770bd60 fffff960`001a5e84 : fffff900`c0807f60 00000000`00000006 00000000`0b010f83 00000000`00000007 : win32k!xxxPaintIconsInSwitchWindow+0x65d
    fffff880`0770be70 fffff960`001a675f : fffff900`c0807f60 00000000`23010fda 00000000`00000000 fffff900`c0807f60 : win32k!xxxPaintSwitchWindow+0x1ec
    fffff880`0770bef0 fffff960`0015d429 : 00000000`00000000 00000000`00000000 fffff900`c0807f60 00000000`00000014 : win32k!xxxSwitchWndProc+0xcb
    fffff880`0770bf70 fffff960`000b3d54 : fffff880`0770b000 fffff900`c0807f60 00000000`00000002 00000000`00000000 : win32k!xxxSendMessageTimeout+0x275
    fffff880`0770c020 fffff960`000d7c22 : fffff900`c0807f60 00000000`00000002 00000000`00000003 fffffa80`0caf6b50 : win32k!xxxSendEraseBkgnd+0xb0
    fffff880`0770c080 fffff960`000d79d2 : fffff900`c0807f60 00000000`00000004 00000000`00000004 fffff900`c0807f60 : win32k!xxxSimpleDoSyncPaint+0x192
    fffff880`0770c0b0 fffff960`0013cccf : 00000000`00000088 00000000`00000004 00000000`00000000 00000000`00000000 : win32k!xxxInternalDoSyncPaint+0x1e
    fffff880`0770c100 fffff960`0011e6ea : 00000000`00000000 00000000`00000000 fffff900`c2300950 fffff960`0022dc07 : win32k!xxxRealDefWindowProc+0xece
    fffff880`0770c310 fffff960`001a6837 : fffff900`c0807f60 00000000`00000004 00000000`00000000 fffff800`034c3c37 : win32k!xxxDefWindowProc+0x15e
    fffff880`0770c360 fffff960`00113d13 : fffff900`c31d0010 fffff900`c019d010 00000000`00000064 00000000`00000000 : win32k!xxxSwitchWndProc+0x1a3
    fffff880`0770c3e0 fffff960`0015e127 : fffff900`c019d010 00000000`00000000 fffff900`c00d01e0 fffff900`c1f012a0 : win32k!xxxReceiveMessage+0x6cb
    fffff880`0770c4d0 fffff960`0015e371 : 0000018b`00000000 00000000`00000002 00000029`00000000 fffff880`0770c510 : win32k!xxxRealSleepThread+0xa7
    fffff880`0770c570 fffff960`00115017 : 00000000`00000000 fffff900`c088e9e0 00000000`00000200 00000000`00000000 : win32k!xxxSleepThread+0x59
    fffff880`0770c5a0 fffff960`0015d392 : fffff900`c088e9e0 fffff960`00000000 ffffffff`d801137a fffff880`0770c7c8 : win32k!xxxInterSendMsgEx+0x112a
    fffff880`0770c6b0 fffff960`001a53b8 : ffffffff`d801137a 00000000`00000010 00000000`00000000 fffff900`c088e9e0 : win32k!xxxSendMessageTimeout+0x1de
    fffff880`0770c760 fffff960`001a5ec5 : 00000000`00000007 ffffffff`d801137a fffff900`c20bb260 00000000`00000007 : win32k!DrawSwitchWndHilite+0x22c
    fffff880`0770ca60 fffff960`001a675f : fffff900`c08a8960 00000000`3c01086e 00000000`00000000 fffff900`c08a8960 : win32k!xxxPaintSwitchWindow+0x22d
    fffff880`0770cae0 fffff960`0015d429 : 00000000`00000000 00000000`00000000 fffff900`c08a8960 00000000`00000014 : win32k!xxxSwitchWndProc+0xcb
    fffff880`0770cb60 fffff960`000b3d54 : fffff880`0770b000 fffff900`c08a8960 00000000`00000002 00000000`00000000 : win32k!xxxSendMessageTimeout+0x275
    fffff880`0770cc10 fffff960`000d7c22 : fffff900`c08a8960 00000000`00000002 00000000`00000003 fffffa80`0caf6b50 : win32k!xxxSendEraseBkgnd+0xb0
    fffff880`0770cc70 fffff960`000d79d2 : fffff900`c08a8960 00000000`00000004 00000000`00000004 fffff900`c08a8960 : win32k!xxxSimpleDoSyncPaint+0x192
    fffff880`0770cca0 fffff960`0013cccf : 00000000`00000088 00000000`00000004 00000000`00000000 00000000`00000000 : win32k!xxxInternalDoSyncPaint+0x1e
    fffff880`0770ccf0 fffff960`0011e6ea : 00000000`00000000 00000000`00000000 fffff900`c2300950 fffff960`0022dc07 : win32k!xxxRealDefWindowProc+0xece
    fffff880`0770cf00 fffff960`001a6837 : fffff900`c08a8960 00000000`00000004 00000000`00000000 fffff800`034c3c37 : win32k!xxxDefWindowProc+0x15e
    fffff880`0770cf50 fffff960`00113d13 : fffff900`c3195010 fffff900`c019d010 00000000`00000064 00000000`00000000 : win32k!xxxSwitchWndProc+0x1a3
    fffff880`0770cfd0 fffff960`0015e127 : fffff900`c019d010 00000000`00000000 fffff900`c1f012a0 fffff900`c231cb00 : win32k!xxxReceiveMessage+0x6cb
    fffff880`0770d0c0 fffff960`0015e371 : 0000018b`00000000 00000000`00000002 00000029`00000000 fffff880`0770d100 : win32k!xxxRealSleepThread+0xa7
    fffff880`0770d160 fffff960`00115017 : 00000000`00000000 fffff900`c088e9e0 00000000`00000200 00000000`00000000 : win32k!xxxSleepThread+0x59
    fffff880`0770d190 fffff960`0015d392 : fffff900`c088e9e0 fffff960`00000000 00000000`300114e4 fffff880`0770d3b8 : win32k!xxxInterSendMsgEx+0x112a
    fffff880`0770d2a0 fffff960`001a53b8 : 00000000`300114e4 00000000`00000010 00000000`00000000 fffff900`c088e9e0 : win32k!xxxSendMessageTimeout+0x1de
    fffff880`0770d350 fffff960`001a5ec5 : 00000000`00000007 00000000`300114e4 fffff900`c06fac40 00000000`00000007 : win32k!DrawSwitchWndHilite+0x22c
    fffff880`0770d650 fffff960`001a675f : fffff900`c0810fa0 ffffffff`b50112cf 00000000`00000000 fffff900`c0810fa0 : win32k!xxxPaintSwitchWindow+0x22d
    fffff880`0770d6d0 fffff960`0015d429 : 00000000`00000000 00000000`00000000 fffff900`c0810fa0 00000000`00000014 : win32k!xxxSwitchWndProc+0xcb
    fffff880`0770d750 fffff960`000b3d54 : fffff880`0770b000 fffff900`c0810fa0 00000000`00000002 00000000`00000000 : win32k!xxxSendMessageTimeout+0x275
    fffff880`0770d800 fffff960`000d7c22 : fffff900`c0810fa0 00000000`00000002 00000000`00000003 fffffa80`0caf6b50 : win32k!xxxSendEraseBkgnd+0xb0
    fffff880`0770d860 fffff960`000d79d2 : fffff900`c0810fa0 00000000`00000004 00000000`00000004 fffff900`c0810fa0 : win32k!xxxSimpleDoSyncPaint+0x192
    fffff880`0770d890 fffff960`0013cccf : 00000000`00000088 00000000`00000004 00000000`00000000 00000000`00000000 : win32k!xxxInternalDoSyncPaint+0x1e
    fffff880`0770d8e0 fffff960`0011e6ea : 00000179`0000027e 000001e3`000003c2 00000000`00000000 00000020`00000020 : win32k!xxxRealDefWindowProc+0xece
    fffff880`0770daf0 fffff960`001a6837 : fffff900`c0810fa0 00000000`00000004 00000000`00000000 fffff800`034c3c37 : win32k!xxxDefWindowProc+0x15e
    fffff880`0770db40 fffff960`00113d13 : fffff900`c1f35630 fffff900`c019d010 00000000`00000064 00000000`00000000 : win32k!xxxSwitchWndProc+0x1a3
    fffff880`0770dbc0 fffff960`0015e127 : fffff900`c019d010 00000000`00000000 fffff900`c231cb00 fffff900`c0746930 : win32k!xxxReceiveMessage+0x6cb
    fffff880`0770dcb0 fffff960`0015e371 : 0000018b`00000000 00000000`00000002 00000029`00000000 fffff880`0770dcf0 : win32k!xxxRealSleepThread+0xa7
    fffff880`0770dd50 fffff960`00115017 : 00000000`00000000 fffff900`c088e9e0 00000000`00000200 00000000`00000000 : win32k!xxxSleepThread+0x59
    fffff880`0770dd80 fffff960`0015d392 : fffff900`c088e9e0 fffff960`00000000 ffffffff`f401004a fffff880`0770dfa8 : win32k!xxxInterSendMsgEx+0x112a
    fffff880`0770de90 fffff960`001a53b8 : ffffffff`f401004a 00000000`00000010 00000000`00000000 fffff900`c088e9e0 : win32k!xxxSendMessageTimeout+0x1de
    fffff880`0770df40 fffff960`001a5ec5 : 00000000`00000007 ffffffff`f401004a fffff900`c1e35f90 00000000`00000007 : win32k!DrawSwitchWndHilite+0x22c
    fffff880`0770e240 fffff960`001a675f : fffff900`c08a9510 ffffffff`9001136a 00000000`00000000 fffff900`c08a9510 : win32k!xxxPaintSwitchWindow+0x22d
    fffff880`0770e2c0 fffff960`0015d429 : 00000000`00000000 00000000`00000000 fffff900`c08a9510 00000000`00000014 : win32k!xxxSwitchWndProc+0xcb
    fffff880`0770e340 fffff960`000b3d54 : fffff880`0770b000 fffff900`c08a9510 00000000`00000002 00000000`00000000 : win32k!xxxSendMessageTimeout+0x275
    fffff880`0770e3f0 fffff960`000d7c22 : fffff900`c08a9510 00000000`00000002 00000000`00000003 fffffa80`0caf6b50 : win32k!xxxSendEraseBkgnd+0xb0
    fffff880`0770e450 fffff960`000d79d2 : fffff900`c08a9510 00000000`00000004 00000000`00000004 fffff900`c08a9510 : win32k!xxxSimpleDoSyncPaint+0x192
    fffff880`0770e480 fffff960`0013cccf : 00000000`00000088 00000000`00000004 00000000`00000000 00000000`00000000 : win32k!xxxInternalDoSyncPaint+0x1e
    fffff880`0770e4d0 fffff960`0011e6ea : 00000000`00000000 00000000`00000000 fffff900`c2300950 fffff960`0022dc07 : win32k!xxxRealDefWindowProc+0xece
    fffff880`0770e6e0 fffff960`001a6837 : fffff900`c08a9510 00000000`00000004 00000000`00000000 fffff800`034c3c37 : win32k!xxxDefWindowProc+0x15e
    fffff880`0770e730 fffff960`00113d13 : fffff900`c2b6b630 fffff900`c019d010 00000000`00000064 00000000`00000000 : win32k!xxxSwitchWndProc+0x1a3
    fffff880`0770e7b0 fffff960`0015e127 : fffff900`c019d010 00000000`00000000 fffff900`c0746930 fffff900`c06690e0 : win32k!xxxReceiveMessage+0x6cb
    fffff880`0770e8a0 fffff960`0015e371 : 0000018b`00000000 00000000`00000002 00000029`00000000 fffff880`0770e8e0 : win32k!xxxRealSleepThread+0xa7
    fffff880`0770e940 fffff960`00115017 : 00000000`00000000 fffff900`c088e9e0 00000000`00000200 00000000`00000000 : win32k!xxxSleepThread+0x59
    fffff880`0770e970 fffff960`0015d392 : fffff900`c088e9e0 fffff960`00000000 ffffffff`a80107e4 fffff880`0770eb98 : win32k!xxxInterSendMsgEx+0x112a
    fffff880`0770ea80 fffff960`001a53b8 : ffffffff`a80107e4 00000000`00000010 00000000`00000000 fffff900`c088e9e0 : win32k!xxxSendMessageTimeout+0x1de
    fffff880`0770eb30 fffff960`001a5ec5 : 00000000`00000007 ffffffff`a80107e4 fffff900`c21032a0 00000000`00000007 : win32k!DrawSwitchWndHilite+0x22c
    fffff880`0770ee30 fffff960`001a675f : fffff900`c08c1fd0 00000000`3d0113b3 00000000`00000000 fffff900`c08c1fd0 : win32k!xxxPaintSwitchWindow+0x22d
    fffff880`0770eeb0 fffff960`0015d429 : 00000000`00000000 00000000`00000000 fffff900`c08c1fd0 00000000`00000014 : win32k!xxxSwitchWndProc+0xcb
    fffff880`0770ef30 fffff960`000b3d54 : fffff880`0770b000 fffff900`c08c1fd0 00000000`00000002 00000000`00000000 : win32k!xxxSendMessageTimeout+0x275
    fffff880`0770efe0 fffff960`000d7c22 : fffff900`c08c1fd0 00000000`00000002 00000000`00000003 fffffa80`0caf6b50 : win32k!xxxSendEraseBkgnd+0xb0
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP:
    win32k!BltLnkRect+1c
    fffff960`002ef2bc 89bc24d0010000  mov     dword ptr [rsp+1D0h],edi
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  win32k!BltLnkRect+1c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  55346034
    
    IMAGE_VERSION:  6.1.7601.18834
    
    FAILURE_BUCKET_ID:  X64_0x7f_8_win32k!BltLnkRect+1c
    
    BUCKET_ID:  X64_0x7f_8_win32k!BltLnkRect+1c
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7f_8_win32k!bltlnkrect+1c
    
    FAILURE_ID_HASH:  {0c3348d3-9648-baab-e22f-27fc54198b4b}
    
    Followup: MachineOwner
    
    Hi Grizzly,
    if we take the dump file at face value then Bugcheck 7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.
    Let's run some basic tests and see if anything turns up.
    Test your CPU using the Intel diagnostic application:
    https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool-64-bit-

    This Bugcheck can also be caused by an out of date Bios please update:
    BiosVersion = F10
    BiosReleaseDate = 10/12/2011
    SystemManufacturer = Gigabyte Technology Co., Ltd.
    SystemProductName = Z68X-UD3H-B3
    http://www.gigabyte.com/products/product-page.aspx?pid=3973#bios
    Please ensure I have the correct download page for your motherboard revision (version). This will be written on the board itself and is critical you make sure you have the correct support page. You'll notice by the boards name links to other versions.

    Check your Vram using this app:
    http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en

    Find command prompt in the start menu, right click on it and run as admin. Type:
    sfc /scannow
    Press enter and await results.

    Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
    http://www.memtest.org/

    To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
    Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
    Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

    Post any new dump files.
     
  9. Grizzlyadamz

    Grizzlyadamz Senior Member

    Joined:
    Jun 3, 2010
    Messages:
    8
    Likes Received:
    0
    CPU test came back clear

    Had difficulty with the VRAM app- only wants to test 1gb at a time. Setting a manual limit causes it to choke on color mods, and if I disable the ones it chokes on it stumbles on patterns instead.
    Was a bit too out of my depth there- should I run it with the 1gb limit?

    SFC returned 'Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.log....', here's that- https://www.dropbox.com/s/7xke9sdc9ojo4iy/CBS.log?dl=0

    Next up I'll see about updating the bios.:nerves:

    Memtest86 sometime soon.
     
  10. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,849
    Likes Received:
    1,569
    Hi Grizzly,
    with the Vram app testing 1GB will be fine.

    Code:
    2015-05-17 18:38:18, Info                  CSI    00000361 [SR] Verify complete
    2015-05-17 18:38:18, Info                  CSI    00000362 [SR] Repairing 1 components
    2015-05-17 18:38:18, Info                  CSI    00000363 [SR] Beginning Verify and Repair transaction
    2015-05-17 18:38:18, Info                  CSI    00000364 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
      Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
    2015-05-17 18:38:18, Info                  CSI    00000365 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-05-17 18:38:18, Info                  CSI    00000366 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
      Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
    2015-05-17 18:38:18, Info                  CSI    00000367 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-05-17 18:38:18, Info                  CSI    00000368 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
      Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
    2015-05-17 18:38:18, Info                  CSI    00000369 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-05-17 18:38:18, Info                  CSI    0000036a [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
    2015-05-17 18:38:18, Info                  CSI    0000036b Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
      Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
    2015-05-17 18:38:18, Info                  CSI    0000036c [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-05-17 18:38:18, Info                  CSI    0000036d [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
    2015-05-17 18:38:18, Info                  CSI    0000036e Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
      Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
    2015-05-17 18:38:18, Info                  CSI    0000036f Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\utc.app.json do not match actual file [l:24{12}]"utc.app.json" :
      Found: {l:32 b:FAEZKiflOiLCOqAa0MS5v3+ESiId8lC76TIolP23ss8=} Expected: {l:32 b:6510UErwHGoFg3sRd3gzh3HSbTceuHem3Rnk0NraKS8=}
    2015-05-17 18:38:18, Info                  CSI    00000370 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
    2015-05-17 18:38:18, Info                  CSI    00000371 Hashes for file member \??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
      Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
    2015-05-17 18:38:18, Info                  CSI    00000372 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.1.7601.18839_none_fe0845bb1d97efda\telemetry.ASM-WindowsDefault.json do not match actual file [l:66{33}]"telemetry.ASM-WindowsDefault.json" :
      Found: {l:32 b:ZoaS84aLe2Zi7sApdfaJuO/iiDk8TFPBSAJM0l8Zcho=} Expected: {l:32 b:EeQJzlVPvq9GNIcA2FEwrOjEeuDam1G+ol3x61gKasQ=}
    2015-05-17 18:38:18, Info                  CSI    00000373 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted
    2015-05-17 18:38:18, Info                  CSI    00000374 Ignoring duplicate ownership for directory [l:92{46}]"\??\C:\ProgramData\Microsoft\Diagnosis\ETLLogs" in component Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    
    The above log files mention this update: KB3022345

    Googling this update it would also seem that it's been causing issues with some systems. Can you check to see if it's still installed and if so I'd consider removing it as a test.
     

Share This Page

Loading...