blue screen when idling or light load, or just sometimes randomly.


  1. Posts : 2
    windows 7 64 bit
       #1

    blue screen when idling or light load, or just sometimes randomly.


    keep getting bsods on idle. the strangest part is that i can prevent the bsods by putting a bit of load in the system, like running a game in the background while im browsing.

    here is what i found on one of the dmp files.


    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\061417-16473-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    WARNING: Whitespace at end of path element
    Symbol search path is: SRV*C:\Symbols*Symbol information


    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.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`0304f000 PsLoadedModuleList = 0xfffff800`03294e90
    Debug session time: Wed Jun 14 13:16:14.363 2017 (UTC + 8:00)
    System Uptime: 0 days 0:12:24.191
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff800030d23a9, 0, ffffffffffffffff}

    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    1: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800030d23a9, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception

    Debugging Details:
    ------------------


    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    FAULTING_IP:
    nt!SwapContext_PatchXRstor+c7
    fffff800`030d23a9 c3 ret

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800033000e8
    ffffffffffffffff

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    BUGCHECK_STR: 0x1E_c0000005

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    PROCESS_NAME: csrss.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000

    STACK_TEXT:
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


    STACK_COMMAND: .bugcheck ; kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800030d2203 - nt!SwapContext_PatchXSave+2
    [ 01:21 ]
    fffff800030d22e4 - nt!SwapContext_PatchXRstor+2 (+0xe1)
    [ 09:29 ]
    fffff800030d24a3 - nt!EnlightenedSwapContext_PatchXSave+2 (+0x1bf)
    [ 01:21 ]
    fffff800030d2586 - nt!EnlightenedSwapContext_PatchXRstor+2 (+0xe3)
    [ 09:29 ]
    4 errors : !nt (fffff800030d2203-fffff800030d2586)

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: ONE_BIT_LARGE

    FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

    BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT_LARGE

    Followup: memory_corruption
    ---------
    Last edited by maeng; 24 Jun 2017 at 05:15.
      My Computer

  2.   My Computer


  3. Posts : 2
    windows 7 64 bit
    Thread Starter
       #3

    file uploaded
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #4
      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:22.
Find Us