windows10 pc auto reboot problem

Question

i need help...

as blow is windows dump file

Microsoft (R) Windows Debugger Version 10.0.22549.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\Issue_Log\SC\Nuc_Reeboot\Dump\SC-M-PROD\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff8062ac06000 PsLoadedModuleList = 0xfffff8062b01c4d0
Debug session time: Tue Feb 15 12:38:50.513 2022 (UTC + 9:00)
System Uptime: 19 days 15:25:40.449
Loading Kernel Symbols
...............................................................
....Page 2b104b not present in the dump file. Type ".hh dbgerr004" for details
............................................................
..........Page 11b9ac not present in the dump file. Type ".hh dbgerr004" for details
...............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000000030d018). Type ".hh dbgerr001" for details Loading unloaded module list .................................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8062adbe100 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff903`b81e71a0=000000000000000a
5: 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: 0000000000572310, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8062c9b702b, address which referenced memory

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3984

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 6751

Key  : Analysis.Init.CPU.mSec
Value: 2265

Key  : Analysis.Init.Elapsed.mSec
Value: 28977

Key  : Analysis.Memory.CommitPeak.Mb
Value: 90

Key  : WER.OS.Branch
Value: rs5_release

Key  : WER.OS.Timestamp
Value: 2018-09-14T14:34:00Z

Key  : WER.OS.Version
Value: 10.0.17763.1

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: d1

BUGCHECK_P1: 572310

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff8062c9b702b

WRITE_ADDRESS: 0000000000572310

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXPNP: 1 (!blackboxpnp)

PROCESS_NAME: isIVI.exe

TRAP_FRAME: fffff903b81e72e0 -- (.trap 0xfffff903b81e72e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd78166ced040 rbx=0000000000000000 rcx=0000000000572318
rdx=ffff8806d016ca80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8062c9b702b rsp=fffff903b81e7478 rbp=fffff903b81e7510
r8=0000000000000040 r9=0000000000000007 r10=ffffd78165767180
r11=0000000000572310 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
isMedia_UCI8T+0x2702b:
fffff8062c9b702b 488941f8 mov qword ptr [rcx-8],rax ds:0000000000572310=????????????????
Resetting default scope

STACK_TEXT:
fffff903b81e7198 fffff8062adcf8e9 : 000000000000000a 0000000000572310 0000000000000002 0000000000000001 : nt!KeBugCheckEx
fffff903b81e71a0 fffff8062adcbcd4 : ffff8806a992e8f0 0000000000000000 0000000000573310 0000000000572350 : nt!KiBugCheckDispatch+0x69
fffff903b81e72e0 fffff8062c9b702b : fffff8062c9a00e2 ffffd78165515198 ffff8806ae03da48 0000000000000000 : nt!KiPageFault+0x454
fffff903b81e7478 fffff8062c9a00e2 : ffffd78165515198 ffff8806ae03da48 0000000000000000 ffff8806d21192e0 : isMedia_UCI8T+0x2702b
fffff903b81e7480 fffff8062c99f9d6 : ffff8806cffa3db0 0000000000000001 ffffd78165515198 ffffd78165515198 : isMedia_UCI8T+0x100e2
fffff903b81e74b0 fffff8062c9b5ed0 : ffff8806d1bdbd00 fffff80600000000 fffff903b81e7698 00000000953836e7 : isMedia_UCI8T+0xf9d6
fffff903b81e7550 fffff8062c9b411c : 0000000000000000 ffff8806cac9a440 00000000c0000001 00000001657b1ec0 : isMedia_UCI8T+0x25ed0
fffff903b81e7640 fffff8062ac3db99 : ffff8806a992e8f0 ffff8806c04d1900 00000000953836e7 ffff880600000004 : isMedia_UCI8T+0x2411c
fffff903b81e76f0 fffff8062b1ce6f1 : ffff8806c04d1900 0000000000000000 0000000000000000 ffff8806cac9a440 : nt!IofCallDriver+0x59
fffff903b81e7730 fffff8062b1ce45c : ffffaf8500000000 ffff8806cac9a440 fffff903b81e7a80 fffff903b81e7a80 : nt!IopSynchronousServiceTail+0x1b1
fffff903b81e77e0 fffff8062b1ce526 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0xe0c
fffff903b81e7920 fffff8062adcf305 : 000000000051e0b0 0000000000000000 0000000000000000 fffff8062b1d050f : nt!NtDeviceIoControlFile+0x56
fffff903b81e7990 00007ff92acdfad4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000000869fd78 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`2acdfad4

SYMBOL_NAME: isMedia_UCI8T+2702b

MODULE_NAME: isMedia_UCI8T

IMAGE_NAME: isMedia_UCI8T.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 2702b

FAILURE_BUCKET_ID: AV_isMedia_UCI8T!unknown_function

OS_VERSION: 10.0.17763.1

BUILDLAB_STR: rs5_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7c5f8233-84b6-35ca-1cde-93c703f5477f}

Followup: MachineOwner

---

Answer 1

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html
https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 2

Crash was in isMedia_UCI8T.sys
Google search returns nothing for this binary,
Not for the PROCESS_NAME: isIVI.exe

Answer 3

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--