none
windows crashing (maybe here is where to post?) RRS feed

  • Question

  • I have been having an issue with my p.c. for a little while now where I am watching something on Netflix or on demand  on one monitor while playing a game or doing homework on the other. I have ran two monitors for quite a while. Didnt have any issue until about a 2 months ago. What happens is my pc will randomly reboot once a day. One time i did happen twice. I have ran a scan and repair, checked drivers for updates, ran a hardware check, tried running one monitor, updated the power supply, added an additional fan none of this has worked. My wife told me to add a debug program and see if anyone can make heads or tails of it.

    any help would be greatly appreciated.

    I believe the fallowing is the debug file where the crash occurred. If it is not I have other files that I can scower through.

    Loading control script C:\Program Files\DebugDiag\Scripts\CrashRule_IIS.vbs
    DumpPath set to C:\Users\Michael\Desktop\debug
    [4/15/2018 2:05:58 PM]
      Process created. BaseModule - C:\WINDOWS\system32\DllHost.exe. BaseThread - System ID: 10064
      C:\WINDOWS\SYSTEM32\ntdll.dll loaded at 0x44790000
      Thread created. New thread - System ID: 10072
      Thread created. New thread - System ID: 10076
      Thread created. New thread - System ID: 10080
      Thread created. New thread - System ID: 10084
      Thread created. New thread - System ID: 10088
      Thread created. New thread - System ID: 10092
      Thread created. New thread - System ID: 10096
      C:\WINDOWS\System32\KERNEL32.DLL loaded at 0x445d0000
      C:\WINDOWS\System32\KERNELBASE.dll loaded at 0x414b0000
      C:\WINDOWS\System32\ucrtbase.dll loaded at 0x41b60000
      C:\WINDOWS\System32\combase.dll loaded at 0x436f0000
      C:\WINDOWS\System32\RPCRT4.dll loaded at 0x43250000
      C:\WINDOWS\System32\bcryptPrimitives.dll loaded at 0x41720000
      C:\WINDOWS\System32\kernel.appcore.dll loaded at 0x40ae0000
      C:\WINDOWS\System32\msvcrt.dll loaded at 0x44520000
      C:\WINDOWS\System32\clbcatq.dll loaded at 0x41c60000
      C:\WINDOWS\System32\user32.dll loaded at 0x43ab0000
      C:\WINDOWS\System32\win32u.dll loaded at 0x41a90000
      C:\WINDOWS\System32\GDI32.dll loaded at 0x436c0000
      C:\WINDOWS\System32\gdi32full.dll loaded at 0x417a0000
      C:\WINDOWS\System32\msvcp_win.dll loaded at 0x419f0000
      C:\WINDOWS\System32\sechost.dll loaded at 0x41d00000
      C:\WINDOWS\System32\IDStore.dll loaded at 0x24d10000
      C:\WINDOWS\System32\bcrypt.dll loaded at 0x407e0000
      C:\WINDOWS\system32\USERENV.dll loaded at 0x40a10000
      C:\WINDOWS\System32\profapi.dll loaded at 0x40b70000
      Thread created. New thread - System ID: 10204
      Initializing control script
      Clearing any existing breakpoints
      
      Current Breakpoint List(BL)
    [4/15/2018 2:06:01 PM]
      Thread exited. Exiting thread - System ID: 10204. Exit code - 0x00000000
    [4/15/2018 2:06:05 PM]
      Thread exited. Exiting thread - System ID: 10096. Exit code - 0x00000000
      C:\WINDOWS\System32\IDStore.dll Unloaded from 0x24d10000
      C:\WINDOWS\System32\profapi.dll Unloaded from 0x40b70000
      C:\WINDOWS\system32\USERENV.dll Unloaded from 0x40a10000
      Thread exited. Exiting thread - System ID: 10076. Exit code - 0x00000000
      Thread exited. Exiting thread - System ID: 10088. Exit code - 0x00000000
      Thread exited. Exiting thread - System ID: 10092. Exit code - 0x00000000
      Thread exited. Exiting thread - System ID: 10084. Exit code - 0x00000000
      Thread exited. Exiting thread - System ID: 10080. Exit code - 0x00000000
      Thread exited. Exiting thread - System ID: 10064. Exit code - 0x00000000
      Process exited. Exit code - 0x00000000

    Debugging Overhead Cost:
    Total Elapsed Ticks = 7140 (100%)
    Total Ticks Spent in Debugger Engine = 2718 (38%)
    Total Ticks Spent in Crash Rule Script = 16 (0%)

    • Edited by Sofakushin Sunday, April 15, 2018 7:34 PM
    • Moved by Stanly Fan Tuesday, April 24, 2018 2:19 AM
    Sunday, April 15, 2018 7:32 PM

All replies

  • This is a Forum for programmers having issues with Windows Forms applications.

    You should mention what version of Windows you have, i.e. XP, 7, 8 or 10 so that you can be provided a Forum to post in.


    La vida loca

    Sunday, April 15, 2018 7:52 PM
  • About debugdiag:
    If you get BSOD(s)? then I have my doubts that debugdiag is the right tool.
    Approach would be more something like this
    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/blue-screen-data
    Loading the kernel-dump with a kernel-debugger and doing an '!analyze -v' may lead - if you are lucky - to the cause of the problem.
    But often interpretation of output can be tricky.

    With kind regards

    Tools
    Debugging Using WinDbg Preview
    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-using-windbg-preview
    or
    Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)
    https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/
    Monday, April 16, 2018 8:16 AM