none
Error messages that make my computer blue screen and restart? (Windows 8)

    Question

  • Lately, I've been getting random blue screens and my computer restarts. Some of the errors have been "Bad_Pool_Caller," "Driver_Overrun_Stack_Buffer," and "Memory_Management." My computer came with Windows 8 and I just bought it back in January from NewEgg. Every time the "send details" option comes up, I click "view details" and the same three files come up. They are C:\Windows\minidump\030613-19968-01.dmp, C:\Users\Ash\AppData\Local\Temp\WER-68281-0.sysdata, and C:\Windows\Memory.dmp.
    Please help me! :(
    Thursday, March 07, 2013 4:46 AM

Answers

  • the latest dump shows GPU issues:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 000000000000000d, type of pool violation the caller is guilty of.
    Arg2: fffff8a0036533a0
    Arg3: 000000004b3b7844
    Arg4: ffdafa80099e7940
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    dxgkrnl!DxgkThreadCallout+6b
    fffff880`05f4fa1f 48832700        and     qword ptr [rdi],0
    
    BUGCHECK_STR:  0xc2_d
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  explorer.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff802bd8e6c8b to fffff802bd6f1040
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    nt!ExFreePool
    dxgkrnl!DxgkThreadCallout
    win32k!GdiThreadCallout
    win32k!W32pThreadCallout
    win32k!W32CalloutDispatch
    nt!ExCallCallBack
    nt!PspExitThread
    nt!PsExitSpecialApc
    nt!KiDeliverApc
    nt!KiInitiateUserApc
    nt!KiSystemServiceExit
    0x0
    
    
    
    IMAGE_NAME:  dxgkrnl.sys
    
    FAILURE_BUCKET_ID:  0xc2_d_dxgkrnl!DxgkThreadCallout
    
    BUCKET_ID:  0xc2_d_dxgkrnl!DxgkThreadCallout
    
    
    
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Feb 26 20:11:23 2013 (512D08DB)
        CheckSum:         00B193B8

    If you get so many different crashes, also try a memory test:

    http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86


    "A programmer is just a tool which converts caffeine into code"

    Friday, March 08, 2013 6:00 AM

All replies

  • You get bugchecks. A bugcheck (BSOD) is a mechanism to protect your PC from damage.



    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    If you can't see dmp files, make sure your Windows is configured correctly [2][3] to generate dumps.

    If you want to analyze them your own, check those videos [4][5] and read this KB article [6].

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    [2] http://support.microsoft.com/kb/254649
    [3] http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
    [4] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-15-WinDbg-Bugchecks
    [5] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-16-WinDbg-Driver-Verifier, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-17-WinDbg-Driver-Verifier-Part-2, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-18-WinDbg-Driver-Verifier-Part-3
    [6] http://support.microsoft.com/kb/315263

    "A programmer is just a tool which converts caffeine into code"

    Thursday, March 07, 2013 5:46 AM
  • You get bugchecks. A bugcheck (BSOD) is a mechanism to protect your PC from damage.



    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    If you can't see dmp files, make sure your Windows is configured correctly [2][3] to generate dumps.

    If you want to analyze them your own, check those videos [4][5] and read this KB article [6].

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    [2] http://support.microsoft.com/kb/254649
    [3] http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
    [4] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-15-WinDbg-Bugchecks
    [5] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-16-WinDbg-Driver-Verifier, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-17-WinDbg-Driver-Verifier-Part-2, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-18-WinDbg-Driver-Verifier-Part-3
    [6] http://support.microsoft.com/kb/315263

    "A programmer is just a tool which converts caffeine into code"

    Okay. Here is my link:
    https://skydrive.live.com/redir?resid=FF5C7B0BFCC37721!113&authkey=!ALw6AI-_OvurDCI

    There was only one file in my minidump and it is the file that always pops up in the error screen.
    And sorry for the quote, the reply space wouldn't pop up unless I clicked "quote."
    Friday, March 08, 2013 4:05 AM
  • the latest dump shows GPU issues:

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    BAD_POOL_CALLER (c2)
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arguments:
    Arg1: 000000000000000d, type of pool violation the caller is guilty of.
    Arg2: fffff8a0036533a0
    Arg3: 000000004b3b7844
    Arg4: ffdafa80099e7940
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    dxgkrnl!DxgkThreadCallout+6b
    fffff880`05f4fa1f 48832700        and     qword ptr [rdi],0
    
    BUGCHECK_STR:  0xc2_d
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  explorer.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff802bd8e6c8b to fffff802bd6f1040
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    nt!ExFreePool
    dxgkrnl!DxgkThreadCallout
    win32k!GdiThreadCallout
    win32k!W32pThreadCallout
    win32k!W32CalloutDispatch
    nt!ExCallCallBack
    nt!PspExitThread
    nt!PsExitSpecialApc
    nt!KiDeliverApc
    nt!KiInitiateUserApc
    nt!KiSystemServiceExit
    0x0
    
    
    
    IMAGE_NAME:  dxgkrnl.sys
    
    FAILURE_BUCKET_ID:  0xc2_d_dxgkrnl!DxgkThreadCallout
    
    BUCKET_ID:  0xc2_d_dxgkrnl!DxgkThreadCallout
    
    
    
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue Feb 26 20:11:23 2013 (512D08DB)
        CheckSum:         00B193B8

    If you get so many different crashes, also try a memory test:

    http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86


    "A programmer is just a tool which converts caffeine into code"

    Friday, March 08, 2013 6:00 AM
  • So I should do the memtest? What exactly will this do? Does it debug it or just tell me what's wrong with my computer and what i need to fix>
    Friday, March 08, 2013 6:12 AM
  • it checks if the RAM of the Pc is damaged or not.

    "A programmer is just a tool which converts caffeine into code"

    Friday, March 08, 2013 6:19 AM
  • You get bugchecks. A bugcheck (BSOD) is a mechanism to protect your PC from damage.



    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    If you can't see dmp files, make sure your Windows is configured correctly [2][3] to generate dumps.

    If you want to analyze them your own, check those videos [4][5] and read this KB article [6].

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65
    [2] http://support.microsoft.com/kb/254649
    [3] http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
    [4] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-15-WinDbg-Bugchecks
    [5] http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-16-WinDbg-Driver-Verifier, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-17-WinDbg-Driver-Verifier-Part-2, http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-18-WinDbg-Driver-Verifier-Part-3
    [6] http://support.microsoft.com/kb/315263

    "A programmer is just a tool which converts caffeine into code"


    Saturday, September 21, 2013 1:35 PM