Windows 10: Debugger restarting my computer in off hours

Howdy!

I apologize in advance for what may be a redundant thread. My computer just started exhibiting a weird behavior wherein Windows restarts without incident during the hours in which I am not using it. I am mostly bothered by this because it didn't use to do this.

Here is a cut and paste of the error message from event viewer and the most recent minidump as translated by Winbgchk preview. Thank you for any help that you might be able to give me and let me know if you need any more information.

Event viewer message: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: da48aee9-9755-4e5f-a367-6398b5f265ab.

Minidump command text translation:
Microsoft (R) Windows Debugger Version 10.0.18206.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\090318-20953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff802`f049a000 PsLoadedModuleList = 0xfffff802`f0848170
Debug session time: Mon Sep 3 03:19:52.901 2018 (UTC - 7:00)
System Uptime: 1 days 1:05:36.835
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+425 )

Followup: MachineOwner
---------

nt!KeBugCheckEx:
fffff802`f0642ca0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbe04`8c7f6320=000000000000000a
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1301

BIOS_DATE: 03/14/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: MAXIMUS IX CODE

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: 0

READ_ADDRESS: fffff802f08e7388: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
0000000000000000

CURRENT_IRQL: 2

FAULTING_IP:
+0
00000000`00000000 ?? ???

PROCESS_NAME: PrecisionX_x64.exe

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

ANALYSIS_SESSION_HOST: DESKTOP-OLLIN

ANALYSIS_SESSION_TIME: 09-03-2018 09:59:25.0136

ANALYSIS_VERSION: 10.0.18206.1001 amd64fre

TRAP_FRAME: ffffbe048c7f6460 -- (.trap 0xffffbe048c7f6460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000f193f2c000 rbx=0000000000000000 rcx=00000000c0000102
rdx=00000000000000f1 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=ffffbe048c7f65f0 rbp=0000000000000000
r8=ffff9a804fee3180 r9=0000000000000002 r10=ffff9a804fee3104
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
00000000`00000000 ?? ???
Resetting default scope

IP_IN_FREE_BLOCK: 0

LAST_CONTROL_TRANSFER: from fffff802f0653869 to fffff802f0642ca0

FAILED_INSTRUCTION_ADDRESS:
+0
00000000`00000000 ?? ???

STACK_TEXT:
ffffbe04`8c7f6318 fffff802`f0653869 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
ffffbe04`8c7f6320 fffff802`f06504e5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffbe04`8c7f6460 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x425


THREAD_SHA1_HASH_MOD_FUNC: bf99962f16aee8a6a536cfcc5454c0cd4db15ac9

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 79f80cc7f571cb0ec417faf51633559f1df31f0e

THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

FOLLOWUP_IP:
nt!KiPageFault+425
fffff802`f06504e5 33c0 xor eax,eax

FAULT_INSTR_CODE: ffb0c033

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiPageFault+425

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5b6bc221

IMAGE_VERSION: 10.0.17134.254

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 425

FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault

BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault

PRIMARY_PROBLEM_CLASS: AV_CODE_AV_NULL_IP_nt!KiPageFault

TARGET_TIME: 2018-09-03T10:19:52.000Z

OSBUILD: 17134

OSSERVICEPACK: 254

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-08-08 21:25:05

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 3221

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_code_av_null_ip_nt!kipagefault

FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

Followup: MachineOwner
---------

:)

 

NVIDIA Introduces Industry's First Debugger and Profiler For GPU Computing

The CUDA architecture continues to blaze a trail as the leading platform for developing and running GPU Computing applications, with support for C, OpenCL, DirectX Compute, Fortran and other languages and APIs. The latest CUDA 2.2 Beta contains a host of significant new features, including:

Hardware debugger for the GPU
Linux developers can now use a debugger on CUDA-enabled GPUs that offers both the familiar interface of the popular open-source GDB debugger and the ability to debug kernels as they execute on the GPU. The GPU-side debugger has all the features that developers expect from GDB, including the ability to have breakpoints, watch variables, inspect state, etc., as well as additional functions for CUDA-specific features.

Visual Profiler v2.2 for the GPU
The most common step in tuning application performance is profiling the application and then modifying the code. The CUDA Visual Profiler is a graphical tool that enables profiling C applications running on the GPU. This latest release of the CUDA Visual Profiler supports full measurement of memory bandwidth within a kernel, giving developers visibility into one of the most performance-critical areas of CUDA.

Full support for Microsoft Windows Server 2003/2008
Tesla C1060 and S1070 are now fully supported under both Microsoft Windows Server 2003 and 2008, offering developers and high-performance computing users more flexibility in their choice of operating system. CUDA 2.2 runs on Windows, MacOSX and major LINUX distributions.

Additional Features Coming with CUDA 2.2

• Improved OpenGL interop performance
• Texture from pitch linear memory
• Zero-copy support for direct access to system memory
• Pinned shared system memory allows compute kernels to share system memory
• Asynchronous memcopy on Vista

For a full list of new features in CUDA 2.2 and to get early access, see discussion on the CUDA forums.

Source: NVIDIA

 

Debugger

I am trying to play Age of Mythology on my windows 10 computer and it has worked great up to today. I just got a notice that said " Debugger detected. Unload debugger and try again". I have googled and you tubed and I can not find the fix I need. I have
a basic knowledge of computers but I do not have a extensive knowledge. If you can explain step by step or you have a link to a you tube video that would be great! Thank you for whoever is willing to help!

 

Windows 10 infinite restart black screen

Thank you john for all of your help i decided to get the usb my computer came with and factory reset it i didnt have anything that personal or valueable so its ok thanks for the help though i appreciate it