Windows 10: BSD & random auto rebooting even on newly repaired clean install

I tried to delete my previous posts since no one answered them, but this one contains the latest minidump files. Attn Admin, please del previous posts but NOT this one if the other posts still exist--no need for any duplicate posts. Thanks!My Lenovo Ideacentre 5 14ARE05 AMD 4600G tower has experienced random reboots even after getting sent off for repair where they replaced bad memory and reinstalled OS. PC came with Win 10 but reboot issues do not change whether it's Win 10 or 11. In fact, immediately after a clean Win 11 install, fully updated, I experienced a random reboot w/i a few hou

:)

 

BSD & random auto rebooting even on newly repaired clean install

My Lenovo Ideacentre 5 14ARE05 (AMD 4600G) tower has experienced random reboots even after getting sent off for repair where they replaced bad memory and reinstalled OS. PC came with Win 10 but reboot issues do not change whether it's Win 10 or 11. In fact, immediately after a clean Win 11 install, fully updated, I experienced a random reboot w/i a few hours before any software was installed, just using MS Edge and some Edge Extensions installed. I retested machine on my end and it passes all memory and intensive CPU tests. I have a copy of the first two fresh minidumps and their respective screenshots below: Minidump – Google Drive

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\012123-13156-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 22621 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff806`6e600000 PsLoadedModuleList = 0xfffff806`6f213010

Debug session time: Sat Jan 21 04:22:33.870 2023 (UTC - 5:00)

System Uptime: 0 days 9:03:48.428

Loading Kernel Symbols

...............................................................

................................................................

......................................................

Loading User Symbols

Loading unloaded module list

.........

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff806`6ea28f20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffd05`0a971ef0=000000000000000a

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)

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 a kernel debugger is available get the stack backtrace.

Arguments:

Arg1: 0000000000001007, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, bitfield :

bit 0 : value 0 = read operation, 1 = write operation

bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)

Arg4: fffff8066ea62beb, address which referenced memory

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 1515

Key : Analysis.DebugAnalysisManager

Value: Create

Key : Analysis.Elapsed.mSec

Value: 2501

Key : Analysis.IO.Other.Mb

Value: 12

Key : Analysis.IO.Read.Mb

Value: 0

Key : Analysis.IO.Write.Mb

Value: 24

Key : Analysis.Init.CPU.mSec

Value: 217

Key : Analysis.Init.Elapsed.mSec

Value: 13734

Key : Analysis.Memory.CommitPeak.Mb

Value: 89

Key : Bugcheck.Code.DumpHeader

Value: 0xa

Key : Bugcheck.Code.Register

Value: 0xa

Key : Dump.Attributes.AsUlong

Value: 1808

Key : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key : Dump.Attributes.ErrorCode

Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage

Value: 0

FILE_IN_CAB: 012123-13156-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808

Kernel Generated Triage Dump

BUGCHECK_CODE: a

BUGCHECK_P1: 1007

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8066ea62beb

READ_ADDRESS: fffff8066f31c468: Unable to get MiVisibleState

Unable to get NonPagedPoolStart

Unable to get NonPagedPoolEnd

Unable to get PagedPoolStart

Unable to get PagedPoolEnd

unable to get nt!MmSpecialPagesInUse

0000000000001007

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: msedge.exe

TRAP_FRAME: fffffd050a972030 -- (.trap 0xfffffd050a972030)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000000000000 rcx=fffffd050a972218

rdx=0000000000000fff rsi=0000000000000000 rdi=0000000000000000

rip=fffff8066ea62beb rsp=fffffd050a9721c0 rbp=fffffd050a972230

r8=0000000000000fff r9=0000000000000000 r10=0000000000000008

r11=fffffd050a972138 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na pe nc

nt!KiHeteroChooseTargetProcessor+0x9d:

fffff806`6ea62beb 488b5f08 mov rbx,qword ptr [rdi+8] ds:00000000`00000008=????????????????

Resetting default scope

STACK_TEXT:

fffffd05`0a971ee8 fffff806`6ea3e5a9 : 00000000`0000000a 00000000`00001007 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

fffffd05`0a971ef0 fffff806`6ea39c34 : 00000000`00000fff 00000000`00000000 fffff806`6acfb180 fffff806`6e81e1c5 : nt!KiBugCheckDispatch+0x69

fffffd05`0a972030 fffff806`6ea62beb : fffff806`6acfb180 fffffd05`0a972230 fffffd05`0a972338 00000000`00000000 : nt!KiPageFault+0x474

fffffd05`0a9721c0 fffff806`6e8c3306 : 00000000`00000000 00000000`00000000 00000000`00000fff fffff806`6acfb180 : nt!KiHeteroChooseTargetProcessor+0x9d

fffffd05`0a972270 fffff806`6e8c6204 : 00000000`00000000 ffffe608`44504f70 ffff4ad4`93a1a5f9 ffffe608`4303f440 : nt!KiDeferredReadySingleThread+0x7f6

fffffd05`0a972640 fffff806`6e8c5b9b : ffffe608`4450b160 ffffe608`00000000 00000000`00000000 00000000`00000000 : nt!KiExitDispatcher+0x184

fffffd05`0a9729e0 fffff806`6edbf2c9 : 00000000`00000000 fffffd05`0a972b60 00000000`00000000 ffffe608`4303f580 : nt!KeSetEvent+0xeb

fffffd05`0a972a70 fffff806`6ea3dce8 : ffffe608`442b5080 ffffe608`4450a7e0 00000000`00000000 ffffe608`00000000 : nt!NtSetEvent+0xb9

fffffd05`0a972ae0 00007ffa`d444efc4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28

000000f2`7fdfed28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`d444efc4

SYMBOL_NAME: nt!KiHeteroChooseTargetProcessor+9d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.1105

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 9d

FAILURE_BUCKET_ID: AV_nt!KiHeteroChooseTargetProcessor

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {107bb024-437a-c58e-f3f5-25fae0d730fc}

Followup: MachineOwner

---------

2nd BSD:

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\012123-9578-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22621 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Machine Name:

Kernel base = 0xfffff805`73400000 PsLoadedModuleList = 0xfffff805`74013010

Debug session time: Sat Jan 21 19:52:48.925 2023 (UTC - 5:00)

System Uptime: 0 days 15:30:01.731

Loading Kernel Symbols

...............................................................

................................................................

.......................................................

Loading User Symbols

Loading unloaded module list

.........

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff805`73828f20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff805`76b05c70=0000000000000133

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DPC_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.

Arg2: 0000000000001e00, The watchdog period (in ticks).

Arg3: fffff8057411c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding the cumulative timeout

Arg4: 0000000000000000

Debugging Details:

------------------

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: TickPeriods ***

*** ***

*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 1578

Key : Analysis.DebugAnalysisManager

Value: Create

Key : Analysis.Elapsed.mSec

Value: 1734

Key : Analysis.IO.Other.Mb

Value: 0

Key : Analysis.IO.Read.Mb

Value: 0

Key : Analysis.IO.Write.Mb

Value: 0

Key : Analysis.Init.CPU.mSec

Value: 124

Key : Analysis.Init.Elapsed.mSec

Value: 8739

Key : Analysis.Memory.CommitPeak.Mb

Value: 87

Key : Bugcheck.Code.DumpHeader

Value: 0x133

Key : Bugcheck.Code.Register

Value: 0x133

Key : Dump.Attributes.AsUlong

Value: 1808

Key : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key : Dump.Attributes.ErrorCode

Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage

Value: 0

FILE_IN_CAB: 012123-9578-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808

Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8057411c340

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: msedgewebview2

STACK_TEXT:

fffff805`76b05c68 fffff805`73627a6f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`7411c340 : nt!KeBugCheckEx

fffff805`76b05c70 fffff805`736268a4 : 0000bb75`a8606d72 fffff805`6fd71180 00000000`00367e6d 00000000`00000000 : nt!KeAccumulateTicks+0x23f

fffff805`76b05cd0 fffff805`73624d33 : fffff805`7405fe70 00000000`00000000 fffff805`6fd71180 ffff848e`645a2f30 : nt!KiUpdateRunTime+0xf4

fffff805`76b05e90 fffff805`736241ba : fffff805`7405fe70 fffff805`7410de60 fffff805`7410de60 00000000`00000000 : nt!KeClockInterruptNotify+0x763

fffff805`76b05f40 fffff805`73744d5e : 00000081`ec6f9223 fffff805`7410ddb0 fffff805`6fd71180 fffff805`7382ae1b : nt!HalpTimerClockInterrupt+0x10a

fffff805`76b05f70 fffff805`7382b07a : ffff848e`645a2fb0 fffff805`7410ddb0 00000000`000000ff 00005995`01035000 : nt!KiCallInterruptServiceRoutine+0x19e

fffff805`76b05fb0 fffff805`7382b8e7 : 00000000`bf57c6b8 ffff8785`a73e7990 00000000`00000040 fffff805`73e9d1b0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffff848e`645a2f30 fffff805`7374c740 : ffff848e`645a31b0 fffff805`73765de6 00000000`002e7cc0 00000000`00000002 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffff848e`645a30c0 fffff805`736a3e78 : ffff8785`a0eaadac ffff848e`645a31b0 ffff848e`645a3300 00000000`00000000 : nt!ExpWaitForSpinLockSharedAndAcquire+0x40

ffff848e`645a30f0 fffff805`736a653c : 00000000`00000000 00000000`40000001 ffff7d0e`c0000001 ffffc180`08b76400 : nt!ExAcquireSpinLockSharedAtDpcLevel+0x98

ffff848e`645a3120 fffff805`737394f6 : 00000000`00000000 ffff848e`00000000 ffffc180`08b76400 00000000`00000000 : nt!MiLockVadTree+0xcc

ffff848e`645a3150 fffff805`73736590 : fffff805`7406af40 00000000`00000001 ffffc180`08b76400 ffffad2c`ca8081a8 : nt!MiLockStealUserVm+0x1d2

ffff848e`645a31f0 fffff805`737345ef : fffff805`7406af40 ffffc180`08b76400 00000000`00000001 ffffc180`08b76400 : nt!MiStealPage+0x750

ffff848e`645a34a0 fffff805`73734074 : fffff805`00000000 fffff805`00000000 ffff848e`645a3658 fffff805`ffffffff : nt!MiTradePage+0x4b7

ffff848e`645a3550 fffff805`73734ba0 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000000 : nt!MiClaimPhysicalRun+0xcc

ffff848e`645a35f0 fffff805`7386fb30 : fffff805`7406af40 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFindContiguousPagesEx+0x408

ffff848e`645a3840 fffff805`73a4a78b : ffffc480`00000000 00000000`00000000 00000000`00000002 00000000`00004a28 : nt!MiRebuildLargePage+0x176

ffff848e`645a3970 fffff805`736188a5 : ffff8785`8c8c2c00 fffff805`7406af40 00000000`00004a28 00000000`00000000 : nt!MiRebuildLargePages+0x2db

ffff848e`645a3a00 fffff805`7360f4a7 : ffff8785`a21e3040 00000000`00001055 ffff8785`a21e3040 fffff805`73618750 : nt!ExpWorkerThread+0x155

ffff848e`645a3bf0 fffff805`7382de84 : ffffaf80`c52a2180 ffff8785`a21e3040 fffff805`7360f450 ff000000`ff000000 : nt!PspSystemThreadStartup+0x57

ffff848e`645a3c40 00000000`00000000 : ffff848e`645a4000 ffff848e`6459e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nt!KeAccumulateTicks+23f

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.1105

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 23f

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup: MachineOwner

---------

 

Clean Install Workaround for Vista

You may remember this news story on techPowerUp! a couple of days ago relating to the lack of clean installs when using the Upgrade Editions of Vista, which required an old OS to be installed. However, Paul Thurrott has managed to find a workaround for this issue, which ironically lets users do a clean install Vista without any previous version of Windows, albeit a little tedious. Here are the steps:

• Boot from the Windows Vista Upgrade DVD as normal
• When prompted for a product code, leave this blank
• Select the version of Vista you have purchased and let Vista install
• When you boot to your desktop for the first time, run the Vista setup from Windows
• This time enter your product key
• When asked whether you want to do an Upgrade of Custom install, select custom and choose a clean install
• Windows will now install for a second time and you should be able to activate it

Remember, these steps are only advised for use in order to achieve a clean install of Vista, it is only legal to use the upgrade editions if you have previously purchased the appropriate version of Windows.

Source: DailyTech

 

Random Reboots

I've had, as the title suggests, random reboots for the length of the time since I've built my computer (2 years roughly) and they're completely inexplicable.

It happens under no load, high load, watching movies, listening to music, playing games, browsing the web, sitting by itself in the room when the my sleeping monitor is even saying WTF?!

There aren't any Events to view other than the usual 0xC*D event when the service just shrugs at me.

Any thoughts or suggestions? Maybe someone has had the same problem before and it was just a loose molex connection? I'm baffled.