none
BSOD windows 8.1 .dmp file inside RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    https://drive.google.com/open?id=1BJhjrNSaa6rIpQW1d4R_7aFvTuC0Czqx

    google file of the .dmp, just started happening 2 days ago after an update so i'm assuming it's software related, doesn't happen constantly, sometimes i can go hours without blue screening, get a DPC watchdog violation when i let it error report

    The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0x0000000000000000, 0x0000000000000000). 

    • Edited by jsgames Tuesday, January 30, 2018 10:40 AM
    Tuesday, January 30, 2018 10:23 AM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    As I know, the 0x00000133 means drivers may take much time in DPC routines, may be deadlocked or misbehaving. And with the first parameter is set to 1, which means the problem is a result of DPCs running from multiple drivers.

    As you mentioned the problem happens after you did the update, it is suggested that you can roll back the display drivers. Go to Device Manager, right click the Nvida driver, and click roll back or uninstall. Then reboot your machine.

    If the problem still exists, please let me know. We should enable the NT Kernel Logger or Circular Kernel Context Logger ETW traces on the system.Once the logging is enabled and the system bug checks, dump out the list of ETW loggers using !wmitrace.strdump. Find the ID of the NT Kernel logger or the Circular logger.  You can then use !wmitrace.logsave (ID) (path to ETL) to write out the ETL log to a file. Here is an example:https://blogs.msdn.microsoft.com/ntdebugging/2012/12/07/determining-the-source-of-bug-check-0x133-dpc_watchdog_violation-errors-on-windows-server-2012/

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


    Wednesday, January 31, 2018 7:05 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    If you have any problems, please feel free to contact me.

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

    Thursday, February 1, 2018 9:27 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    hey it's me i forgot my other password, would you be willing to team viewer me and fix my computer not sure what else to do to fix it. i can post another dump file but it's gonna be the same thing
    Friday, February 2, 2018 3:30 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Just create a new thread in the Forum and describe your problems on details. We are glad to help you.

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

    Friday, February 2, 2018 5:11 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did you replace the misbehaving driver to fix the BSOD?

    How is the computer functioning at this time?

    When was the last BSOD?

    Do you need help fixing the BSOD and computer environment?

    To evaluate the BSOD please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command:

    Make sure the default language is English so that the logs can be scanned and read.

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use one drive or drop box to place share links into the the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    It will automatically collect these files:  msinfo32, dxdiag, mini dumps, drivers hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There is 1 file for you to find manually:  memory dump file:

    C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    Sometimes the dxdiag file needs to be found and saved manually:  In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread



    Friday, February 2, 2018 7:26 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    PC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
     DISPATCH_LEVEL or above. The offending component can usually be
     identified with a stack trace.
    Arg2: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
     additional information regarding the cumulative timeout
    Arg4: 0000000000000000

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


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  6.3.9600.18895 (winblue_ltsb.180101-1800)

    SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.

    SYSTEM_PRODUCT_NAME:  GA-78LMT-USB3

    BIOS_VENDOR:  Award Software International, Inc.

    BIOS_VERSION:  FA

    BIOS_DATE:  04/23/2013

    BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.

    BASEBOARD_PRODUCT:  GA-78LMT-USB3

    BASEBOARD_VERSION:  x.x

    DUMP_TYPE:  2

    BUGCHECK_P1: 1

    BUGCHECK_P2: 1e00

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

    CPU_COUNT: 6

    CPU_MHZ: dbc

    CPU_VENDOR:  AuthenticAMD

    CPU_FAMILY: 15

    CPU_MODEL: 2

    CPU_STEPPING: 0

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0x133

    PROCESS_NAME:  dwm.exe

    CURRENT_IRQL:  d

    ANALYSIS_SESSION_HOST:  LT-PC

    ANALYSIS_SESSION_TIME:  02-02-2018 02:29:45.0562

    ANALYSIS_VERSION: 10.0.15063.468 amd64fre

    LAST_CONTROL_TRANSFER:  from fffff802baf91e92 to fffff802baf5bea0

    STACK_TEXT:  
    fffff802`bcb56c88 fffff802`baf91e92 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
    fffff802`bcb56c90 fffff802`baeb6de7 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1eec2
    fffff802`bcb56d20 fffff802`bb596b4f : ffffe001`9b107340 ffffe001`9e4710e0 fffff802`bb5e2910 ffffe001`9b107340 : nt!KeClockInterruptNotify+0x787
    fffff802`bcb56f40 fffff802`baed3bb3 : fffff802`bb5e2870 fffff802`baefcaf7 fffff801`00000000 00000000`00000000 : hal!HalpTimerClockInterrupt+0x4f
    fffff802`bcb56f70 fffff802`baf5d3da : fffff802`bb5e2870 ffffe001`9e4710e0 ffffd000`22249238 ffffd000`22249238 : nt!KiCallInterruptServiceRoutine+0xa3
    fffff802`bcb56fb0 fffff802`baf5d8a7 : 00000000`6723f24b fffff802`bafdf926 ffffe001`9e4710e0 00000000`00000002 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
    ffffd000`22248f10 fffff802`bae8862b : 00000000`00000082 00000000`00002487 00000000`00002006 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37
    ffffd000`222490a0 fffff802`baf5cc46 : ffffe001`9d5d5340 00000000`00000000 ffffe001`9b6c4000 ffffe001`9e3a2000 : nt!KxWaitForSpinLockAndAcquire+0x1f
    ffffd000`222490d0 fffff801`7f890a2f : ffffe001`a17be290 fffff801`81f6bda0 ffffd000`22249238 00000000`00000000 : nt!KeSynchronizeExecution+0x36
    ffffd000`22249110 fffff801`81f34058 : 00000000`00000000 ffffd000`22249230 ffffe001`9d5d51f0 00000000`00000000 : dxgkrnl!DpSynchronizeExecution+0xaf
    ffffd000`22249160 00000000`00000000 : ffffd000`22249230 ffffe001`9d5d51f0 00000000`00000000 ffffd000`22249230 : nvlddmkm+0xc9058


    STACK_COMMAND:  kb

    THREAD_SHA1_HASH_MOD_FUNC:  2462e0115e937b3b62d9681f822ae171f8b2fe2c

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  96e8b3210b11da272f7077374c15d874077a639b

    THREAD_SHA1_HASH_MOD:  55916e7f1ab06eab2249544634f8f2dc80831f25

    FOLLOWUP_IP: 
    dxgkrnl!DpSynchronizeExecution+af
    fffff801`7f890a2f 8806            mov     byte ptr [rsi],al

    FAULT_INSTR_CODE:  c0330688

    SYMBOL_STACK_INDEX:  9

    SYMBOL_NAME:  dxgkrnl!DpSynchronizeExecution+af

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgkrnl

    IMAGE_NAME:  dxgkrnl.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  59e1c8f5

    IMAGE_VERSION:  6.3.9600.18838

    BUCKET_ID_FUNC_OFFSET:  af

    FAILURE_BUCKET_ID:  0x133_ISR_dxgkrnl!DpSynchronizeExecution

    BUCKET_ID:  0x133_ISR_dxgkrnl!DpSynchronizeExecution

    PRIMARY_PROBLEM_CLASS:  0x133_ISR_dxgkrnl!DpSynchronizeExecution

    TARGET_TIME:  2018-01-30T08:59:47.000Z

    OSBUILD:  9600

    OSSERVICEPACK:  18895

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  784

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 8.1

    OSEDITION:  Windows 8.1 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2018-01-01 22:56:56

    BUILDDATESTAMP_STR:  180101-1800

    BUILDLAB_STR:  winblue_ltsb

    BUILDOSVER_STR:  6.3.9600.18895

    ANALYSIS_SESSION_ELAPSED_TIME:  4ff

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x133_isr_dxgkrnl!dpsynchronizeexecution

    FAILURE_ID_HASH:  {558c278d-5c04-0e1d-c3fd-1cbb6a5abeff}
    Friday, February 2, 2018 7:32 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    that's the full report i got
    Friday, February 2, 2018 7:32 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Could you please create a new post in the forum? Since the problem you post is different from jsgames.

    In addition, please upload the complete dump file to a network drive and share the link here.

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

    Friday, February 2, 2018 7:44 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    a pimp named slickback,

    Open a new thread and post the information below:

    Leave a link in this thread so that your new thread is available.

    To evaluate the BSOD please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command:

    Make sure the default language is English so that the logs can be scanned and read.

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use one drive or drop box to place share links into the the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    It will automatically collect these files:  msinfo32, dxdiag, mini dumps, drivers hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There is 1 file for you to find manually:  memory dump file:

    C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    Sometimes the dxdiag file needs to be found and saved manually:  In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

    Friday, February 2, 2018 8:49 AM
    |