none
BSOD occur with BugCheck error 1001

    Question

  • Hello Everyone...I need your assistance to fix my problem. My computer just crashed with a blue screen and sometimes it freeze. I've searched this error on google and I end up here.

    https://onedrive.live.com/?id=56CE63709EDBEB64!108&cid=56CE63709EDBEB64&group=0

    That's the link to my memory minidump file. Honestly I had 3 memorydump files, but I uploaded only one file to focus on it. Just let me know if you really need the other two dump files. THANK YOU!!! and GOD BLESS US ALL..

    Monday, October 5, 2015 12:59 PM

All replies

  • Your link is broken try it again.

    Wanikiya and Dyami--Team Zigzag

    Monday, October 5, 2015 1:16 PM
    Moderator
  • https://onedrive.live.com/redir?resid=56CE63709EDBEB64!108&authkey=!AJ0GaIah4YVtEVM&ithint=folder%2cdmp

    That's it...sorry It's my first time to use onedrive. THANKS!!

    Tuesday, October 6, 2015 7:49 AM
  • These crashes were called BCC116 and are related to your video sub system.  Please follow the instructions in this wiki

    Wanikiya and Dyami--Team Zigzag

    Tuesday, October 6, 2015 10:44 AM
    Moderator
  • Thanks for your reply Team Zigzag.

    I've read the instructions of your given link..

    This is the article instructions:

    Summary

    BCC 116 & 117 are called video time out and recover and are related to the video sub system.  Most often related to a driver but they can also be related to heat, overclocking, and occasionally under powered Power supply units.

    The user will often see "your video has stopped and it recovered" but eventually it will not be able to recover.

    Details

    "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"

    The first step would be to install the newest driver, (by completely removing the current driver, and installing the newest driver available),. and it it continues to malfunction, revert to a much older driver as some new drivers are somewhat buggy. If playing with video driver versions hasn't helped, make sure the box is not overheating.

    In recent Operating systems 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 you have a desktop 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 it does, it might be as simple as dust buildup and subsequently inadequate cooling.

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

    I did it. I update and install the newest video driver before, but still continue to crash. So I revert to a previousolder driver in a pre-installation dvd.

    Maybe I gonna try to download and install cpu-z and gpu-z, but I had already installed Asus EPU-4 Engine and Asus Cool & Quiet. So my question is should I uninstall both EPU and Cool & Quiet before to install cpu-z and gpu-z??  Thanks!




    • Edited by Nardoo Wednesday, October 7, 2015 4:45 AM
    Wednesday, October 7, 2015 4:43 AM
  • Hi Nardoo,

    Thank you for your question.

    If update driver could not work, for testing, we could replace the Power and video card to check if the issue persist.

    Best Regard,

    Jim

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Wednesday, October 7, 2015 7:05 AM
  • Are you by chance Overclocking

    Wanikiya and Dyami--Team Zigzag

    Wednesday, October 7, 2015 11:14 AM
    Moderator
  • Thanks Jim,

    That would be a nice idea, but I only had one computer and I don't have any other video card.

    Thursday, October 8, 2015 9:23 AM
  • I don't know...
    Thursday, October 8, 2015 9:25 AM
  • Thanks Jim,

    That would be a nice idea, but I only had one computer and I don't have any other video card.

    Hi Nardoo,

    We could re-plug the video card to check if the issue persist.

    Best Regard,

    Jim


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Monday, October 12, 2015 1:05 AM
  • I've already done that, But the problem still the same it didn't fix. Maybe I could replace the power cord or CRT but I don't have any. Now I re-install my windows then after a few hours a blackscreen on my monitor but my CPU still on, So I restart my PC then it says the windows has unexpected shutdown, I click the details and I found out that it was a Bluescreen again...T_T I have uploaded two dump files one from kernel reports and one from minidump to the location below:

    https://onedrive.live.com/redir?resid=56CE63709EDBEB64!108&authkey=!AJ0GaIah4YVtEVM&ithint=folder%2cdmp


    Friday, November 13, 2015 2:30 PM
  • These crashes were called BCC117 and are related to your video sub system.  Please follow the instructions in this wiki

    Microsoft (R) Windows Debugger Version 10.0.10563.566 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\zigza\Desktop\WD-20151113-2047.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*E:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*E:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0x82a1a000 PsLoadedModuleList = 0x82b64850
    Debug session time: Fri Nov 13 07:47:13.525 2015 (UTC - 5:00)
    System Uptime: 0 days 0:44:49.977
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............
    Loading User Symbols
    Mini Kernel Dump does not contain unloaded driver list
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 117, {84eba050, 8ef45036, 0, 0}
    
    Unable to load image nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+113036 )
    
    Followup:     MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for a real bugcheck.)
    Arguments:
    Arg1: 84eba050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 8ef45036, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 00000000, The secondary driver specific bucketing key.
    Arg4: 00000000, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_P1: ffffffff84eba050
    
    BUGCHECK_P2: ffffffff8ef45036
    
    BUGCHECK_P3: 0
    
    BUGCHECK_P4: 0
    
    FAULTING_IP: 
    nvlddmkm+113036
    8ef45036 ??              ???
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    CPU_COUNT: 2
    
    CPU_MHZ: c8e
    
    CPU_VENDOR:  AuthenticAMD
    
    CPU_FAMILY: 10
    
    CPU_MODEL: 6
    
    CPU_STEPPING: 3
    
    BUGCHECK_STR:  0x117
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 10.0.10563.566 amd64fre
    
    STACK_TEXT:  
    807a5cb4 8f8eb101 00000000 8ef45036 8c0a607e dxgkrnl!TdrUpdateDbgReport+0x68
    807a5cdc 8f8eacc0 00000000 82a5150e 84eba050 dxgkrnl!TdrCollectDbgInfoStage2+0x1ab
    807a5d18 8f8eb15c 84eba050 867d6788 807a5d3c dxgkrnl!DXGADAPTER::Reset+0xb6
    807a5d28 8f94b20b 84eba050 867d6788 00000000 dxgkrnl!TdrResetFromTimeout+0x12
    807a5d3c 8f94e485 867d6788 00000000 86840948 dxgmms1!VidSchiRecoverFromTDR+0x15
    807a5d50 82c23f5e 867d6788 ab1a3627 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    807a5d90 82acb219 8f94e406 867d6788 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+113036
    8ef45036 ??              ???
    
    SYMBOL_NAME:  nvlddmkm+113036
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d9e7e9b
    
    FAILURE_BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  0x117_IMAGE_nvlddmkm.sys
    
    PRIMARY_PROBLEM_CLASS:  0x117_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x117_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {a93e9c2e-fca7-af48-d0f1-0cc77d4c6965}
    
    Followup:     MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Friday, November 13, 2015 4:45 PM
    Moderator