none
BSOD (blue screen of death ) Windows 7, 32 bit, professional

    Dotaz

  • The screen suddenly turns blue and says dumping physical memory

    I have done the following 

    * In control panel ---> system---> unchecked the restart, changed dmp file to 256 KB

    *In run---> cmd--->as an administrator I did  scannw; chkdsk; both gave no errors or issues though it took a lot of time.

    * I also did a  built in self test for the memory(RAM) which comes in the start up screen and there also no error came.

    THough it didn't restart now automatically Blue screen still comes,


    úterý 12. listopadu 2013 17:47

Odpovědi

  • the dump shows bugcheck 0x116:

    Bug Check 0x116: VIDEO_TDR_ERROR
    http://msdn.microsoft.com/en-us/library/ff557263%28v=vs.85%29.aspx

    The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 87185418, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 9304d9b0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000c, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    igdkmd32!DxgkDdiCollectDbgInfo+0
    9304d9b0 55              push    ebp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    dxgkrnl!TdrBugcheckOnTimeout
    dxgkrnl!TdrIsRecoveryRequired
    dxgmms1!VidSchiReportHwHang
    dxgmms1!VidSchWaitForCompletionEvent
    dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines
    dxgmms1!VIDMM_GLOBAL::WaitForAllPagingEngines
    dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback
    nt!MmRotatePhysicalView
    dxgmms1!VIDMM_PROCESS_HEAP::Rotate
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource
    dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList
    dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation
    dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer
    dxgmms1!VidSchiSubmitRenderCommand
    dxgmms1!VidSchiSubmitQueueCommand
    dxgmms1!VidSchiRun_PriorityTable
    dxgmms1!VidSchiWorkerThread
    nt!PspSystemThreadStartup
    nt!KiThreadStartup
    
    
    IMAGE_NAME:  igdkmd32.sys
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmd32.sys
    
    BUCKET_ID:  0x116_IMAGE_igdkmd32.sys
    
          d:\sym\dl\igdkmd32.pdb\E0CDC49B931C4F6786A0C319D039E3BD1\igdkmd32.pdb
        Loaded symbol image file: igdkmd32.sys
        Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
        Image name: igdkmd32.sys
        Timestamp:        Wed May 06 20:13:40 2009 (4A01D354)
    

    update the Intel graphic card driver. Your is from 2009!

    Also install the Windows 7 Sp1, you're still at RTM Level (7600) which nol onger gets new updates!

     7600.16841.x86fre.win7_gdr.110622-1503

    Learn how to install Windows 7 Service Pack 1 (SP1)
    http://windows.microsoft.com/en-us/windows7/install-windows-7-service-pack-1


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

    středa 13. listopadu 2013 12:13

Všechny reakce

  • Analyze minidump. Use Nirsoft BSOD viewer for the first look and WinDbg for deeper analysis. You should find the primary cause of problem.

    Regards

    Milos

    úterý 12. listopadu 2013 18:16
  • 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"


    úterý 12. listopadu 2013 18:16
  • We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

    WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you dont know what it is you probably are not overclocking.

    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  

    *

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy (compress them)

    *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.

     

    Link for how to  upload below.
    *
    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.
    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    System specs are extremely useful so please include whatever you know.

    Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...

    You can read more about BSODS here
    You can learn how to test your memory here
    Asking an effective question to get help fast here
    Basic troubleshooting tips can be found here
    Driver verifier-Tracking down a mis behaving driver  here
    Links to out other wiki's can be found here.


    Co-Authored by  JMH3143

    Wanikiya and Dyami--Team Zigzag

    úterý 12. listopadu 2013 18:30
    Moderátor
  • https://skydrive.live.com/redir?resid=7401E6C246E0BE23!107&authkey=!ABOK9YftfL3m--8

    this is the link to the memory dump file

    středa 13. listopadu 2013 10:20
  • the dump shows bugcheck 0x116:

    Bug Check 0x116: VIDEO_TDR_ERROR
    http://msdn.microsoft.com/en-us/library/ff557263%28v=vs.85%29.aspx

    The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 87185418, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 9304d9b0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000c, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    igdkmd32!DxgkDdiCollectDbgInfo+0
    9304d9b0 55              push    ebp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    nt!KeBugCheckEx
    dxgkrnl!TdrBugcheckOnTimeout
    dxgkrnl!TdrIsRecoveryRequired
    dxgmms1!VidSchiReportHwHang
    dxgmms1!VidSchWaitForCompletionEvent
    dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines
    dxgmms1!VIDMM_GLOBAL::WaitForAllPagingEngines
    dxgmms1!VIDMM_MEMORY_SEGMENT::RotateCopyCallback
    nt!MmRotatePhysicalView
    dxgmms1!VIDMM_PROCESS_HEAP::Rotate
    dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource
    dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList
    dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation
    dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer
    dxgmms1!VidSchiSubmitRenderCommand
    dxgmms1!VidSchiSubmitQueueCommand
    dxgmms1!VidSchiRun_PriorityTable
    dxgmms1!VidSchiWorkerThread
    nt!PspSystemThreadStartup
    nt!KiThreadStartup
    
    
    IMAGE_NAME:  igdkmd32.sys
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmd32.sys
    
    BUCKET_ID:  0x116_IMAGE_igdkmd32.sys
    
          d:\sym\dl\igdkmd32.pdb\E0CDC49B931C4F6786A0C319D039E3BD1\igdkmd32.pdb
        Loaded symbol image file: igdkmd32.sys
        Image path: \SystemRoot\system32\DRIVERS\igdkmd32.sys
        Image name: igdkmd32.sys
        Timestamp:        Wed May 06 20:13:40 2009 (4A01D354)
    

    update the Intel graphic card driver. Your is from 2009!

    Also install the Windows 7 Sp1, you're still at RTM Level (7600) which nol onger gets new updates!

     7600.16841.x86fre.win7_gdr.110622-1503

    Learn how to install Windows 7 Service Pack 1 (SP1)
    http://windows.microsoft.com/en-us/windows7/install-windows-7-service-pack-1


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

    středa 13. listopadu 2013 12:13
  • Hello  Dear, I know some steps to fix blue screen error in windows. I hope after performing these steps your problem will be solved.

    Try these:-

    - Disconnect incompatible hardware

    - Check and repair disk errors

    -  Perform System Clean-Up with Reginout

    -  Scan for Malicious Content

    - Run System File Check Up:-

    > Open My Computer
    > Right Click on (:C)
    > Go to Properties
    > Click on Tools tab
    > Click on Check Now under Error-Checking
    > Click on Start
    > Click on Yes for scheduling Disk Check on restarting your laptop
    > Restart your computer
    > Disk Check will automatically start when you logon Windows

    Thanks

    středa 13. listopadu 2013 13:59
  • "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    Wanikiya and Dyami--Team Zigzag

    středa 13. listopadu 2013 15:40
    Moderátor
  • The screen suddenly turns blue and says dumping physical memory

    I have done the following 

    * In control panel ---> system---> unchecked the restart, changed dmp file to 256 KB

    *In run---> cmd--->as an administrator I did  scannw; chkdsk; both gave no errors or issues though it took a lot of time.

    * I also did a  built in self test for the memory(RAM) which comes in the start up screen and there also no error came.

    THough it didn't restart now automatically Blue screen still comes,

    we required above activation key purc


    pátek 13. července 2018 10:48