[SOLVED] Strange BSOD/reboot issue after Win 11 upgrade

[lucid_power_daoc]

Hi, all. I hope someone can help me out here because I cannot find any info on this myself to fix whatever is going on.

Here's how this happened: I've got a relatively new PC built around two months ago (ASUS z690 d4 + wifi, 12700k, 2x16 gb FURY RAM, ASUS TUF 3080 v2, and an AIO cooler with temps never exceeding 55-60c on any component). It was fine for all this time until Win11 got installed. I tried to update my iGPU drivers before and after, but they wouldn't update properly. The setup would start, go halfway, and disappear. I'd reboot my PC and the intel driver & support assistant would say I have everything updated. Weird. At this point, I decided to use DDU to remove those drivers while in safe mode.

Anyway, recently I've been playing a game mostly at night called 7 days to die. Now, this game has stuttering where the entire PC freezes for a second or two (happens only online) because the server needs to save everything. Sometimes this causes the game to crash locally, but the PC is definitely unusable when this happens. Apparently this is normal according to players because it's just the way it's coded (and FWIW, I don't have stuttering issues outside of this game on any other relatively intensive game). However, I've seen something more from that: the PC freezes, BSODs without creating a memory dump properly (it ends up being corrupt) and then reboots with no display (shows no signal on screen). Weirdly, it reboots & runs like normal (apparently it loads Windows because I see my aura software load up). I have to force turn it off, though, by holding it down or shutting it off at the PSU because the display issue doesn't fix itself.

So, I used to have everything run through my displayport which was directly hooked into the mobo instead of the GPU, but then I switched to the dedicated one. And now I'm able to kind of get more info on why this is happening, I think. Before, I'd just get corrupt dump files. Now, using whocrashed, the latest dump produced something of value:

On Sun 2/27/2022 1:01:50 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-11625-01.dmp
This was probably caused by the following module: 0n87.sys (0n87)
Bugcheck code: 0x101 (0xA, 0x0, 0xFFFF8000E7B10180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: 0n87.sys .
Google query: 0n87.sys CLOCK_WATCHDOG_TIMEOUT

On Sun 2/27/2022 1:01:50 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: information.sys (information)
Bugcheck code: 0x101 (0xA, 0x0, 0xFFFF8000E7B10180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: information.sys .
Google query: information.sys CLOCK_WATCHDOG_TIMEOUT

On Sun 2/20/2022 10:42:09 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022022-13562-01.dmp
This was probably caused by the following module: 0n87.sys (0n87)
Bugcheck code: 0x101 (0xA, 0x0, 0xFFFFCD8053B89180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: 0n87.sys .
Google query: 0n87.sys CLOCK_WATCHDOG_TIMEOUT

I also analyzed it with windbg, but depending on which dump I'm looking at, it's a bit more inconclusive. Note that the strange thing about this is that it happens every other day and not every day. And, from my experience so far, it only happens with this game (7 days to die) and never outside of it if it's not running. I have no idea why. Can anyone please tell me what's going on? Here's the info from windbg:

Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 22000 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff8046e200000 PsLoadedModuleList = 0xfffff8046ee29b90
Debug session time: Sun Feb 27 01:01:50.902 2022 (UTC + 8:00)
System Uptime: 0 days 23:20:45.500
Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
.Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000

Loading User Symbols
For analysis of this file, run !analyze -v
fffff8046e6164c0 ?? ??? 17: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 000000000000000a, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffff8000e7b10180, The PRCB address of the hung processor. Arg4: 0000000000000008, The index of the hung processor. Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 15 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 14 Key : Analysis.Init.CPU.mSec Value: 46 Key : Analysis.Init.Elapsed.mSec Value: 8874 Key : Analysis.Memory.CommitPeak.Mb Value: 45 Key : WER.CorruptModuleList Value: 1 FILE_IN_CAB: 022722-11625-01.dmp BUGCHECK_CODE: 101 BUGCHECK_P1: a BUGCHECK_P2: 0 BUGCHECK_P3: ffff8000e7b10180 BUGCHECK_P4: 8 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: ffff8000e82ac9e8 fffff8046e6c9266 : 0000000000000101 000000000000000a 0000000000000000 ffff8000e7b10180 : 0xfffff8046e6164c0
ffff8000e82ac9f0 0000000000000101 : 000000000000000a 0000000000000000 ffff8000e7b10180 0000000000000008 : 0xfffff8046e6c9266 ffff8000e82ac9f8 000000000000000a : 0000000000000000 ffff8000e7b10180 0000000000000008 0000000000000000 : 0x101 ffff8000e82aca00 0000000000000000 : ffff8000e7b10180 0000000000000008 0000000000000000 fffff780`00000320 : 0xa


SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: CORRUPT_MODULELIST_CLOCK_WATCHDOG_TIMEOUT

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {505a7e83-2b57-2f1c-5666-16c4a774a5e4}

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

Some stuff I see in event viewer:

Errors

A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect.

Dump file creation failed due to error during dump creation.

A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event.

There are dcom warnings, but I will take care of those right now (I'm guessing they're not responsible for the crashes).

 

[Colif]

i don't know either of the modules named on this error

On Sun 2/27/2022 1:01:50 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-11625-01.dmp
This was probably caused by the following module: 0n87.sys (0n87)
Bugcheck code: 0x101 (0xA, 0x0, 0xFFFF8000E7B10180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: 0n87.sys .
Google query: 0n87.sys CLOCK_WATCHDOG_TIMEOUT

On Sun 2/27/2022 1:01:50 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: information.sys (information)
Bugcheck code: 0x101 (0xA, 0x0, 0xFFFF8000E7B10180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT

they seem strange. 0n87 seems to be an error related to windbg

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

 

[lucid_power_daoc]

i don't know either of the modules named on this error

On Sun 2/27/2022 1:01:50 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\022722-11625-01.dmp
This was probably caused by the following module: 0n87.sys (0n87)
Bugcheck code: 0x101 (0xA, 0x0, 0xFFFF8000E7B10180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: 0n87.sys .
Google query: 0n87.sys CLOCK_WATCHDOG_TIMEOUT

On Sun 2/27/2022 1:01:50 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: information.sys (information)
Bugcheck code: 0x101 (0xA, 0x0, 0xFFFF8000E7B10180, 0x8)
Error: CLOCK_WATCHDOG_TIMEOUT

they seem strange. 0n87 seems to be an error related to windbg

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

Indeed. Strange.

Okay, I used a collection software to gather info, from win7 forums. Here: https://www.mediafire.com/file/aalnob3dv7nsprf/TUF-MONTECH-Sun_02_27_2022__25456_65.zip/file

I just used DDU to uninstall all GPU drivers and reinstall them. Got iGPU updated properly this time. Hope this info helps. Will need more time to test whether it holds stable...

 

[Colif]

it has 2 dumps in it, I will ask a friend to convert them and we see what it shows, as maybe it will be different.

He will reply later.

I would update your BIOS, you are on 0403 which isn't even listed on here - https://www.asus.com/Motherboards-C...g/TUF-GAMING-Z690-PLUS-WIFI-D4/HelpDesk_BIOS/

I would get 1003, it might work better than the one you on.

 

[lucid_power_daoc]

it has 2 dumps in it, I will ask a friend to convert them and we see what it shows, as maybe it will be different.

He will reply later.

I would update your BIOS, you are on 0403 which isn't even listed on here - https://www.asus.com/Motherboards-C...g/TUF-GAMING-Z690-PLUS-WIFI-D4/HelpDesk_BIOS/

I would get 1003, it might work better than the one you on.

Hey, thanks for that. I use Armoury Crate for updates but I didn't receive anything in notifications (also just checked and no info). And yea, there are two dumps. One of them is the "more often one" and the other one is... I'm not sure. It could have been when the PC auto restarted & I shut it down or it could have been when it crashed. Can't tell--the two happened too close to each other.

I just updated the BIOS and got this error on first boot but not on subsequent reboot. If I'm not mistaking, this could be an artifact of a reconfigured BIOS and software in Windows.

On Sun 2/27/2022 9:21:55 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!setjmpex+0x85A9)
Bugcheck code: 0x1 (0x7FFFB5343C14, 0x0, 0xFFFF0000, 0xFFFFF60DD060FAA0)
Error: APC_INDEX_MISMATCH
Bug check description: This indicates that there has been a mismatch in the APC state index.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Whether this will happen again, I don't know, but it seems OK right now. Btw, thank you very much for your time to look into this.

 

[lucid_power_daoc]

For some reason I cannot edit my reply, so I'll have to add: every time I log in now, I am getting BSODs. System pte misuse, system service exception, page fault, and the same APC error. Rebooted, but system says cannot boot into Windows. Rebooted again. Repaired C:\ and got to login.

Thinking maybe it's Razer, I completely force closed all Razer software before it could run and I am able to log in again without BSODing. When I just tried un-installing razer software, I ran into a memory management BSOD. Rebooted several more times. "Repaired" Razer.

System hasn't BSOD'd yet. /sigh spoke too early. Opening new programs BSODs it.

Ran SFC & DISM. Both report no Windows issues.

I am not wrong, it seems. Razer did cause some of them. Not sure about the others. Here are two analyses:

***

• *
• Bugcheck Analysis *
• *

***

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the BugCheck.
Arg2: fffff959c0fbd798
Arg3: 0000000000000001
Arg4: 8a0000085428e96b

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1843

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5435

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

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

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1000

BUGCHECK_CODE: 1a

BUGCHECK_P1: 5100

BUGCHECK_P2: fffff959c0fbd798

BUGCHECK_P3: 1

BUGCHECK_P4: 8a0000085428e96b

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Razer Synapse Service.exe

STACK_TEXT:
ffffb287747a6c98 fffff8078509f30a : 000000000000001a 0000000000005100 fffff959c0fbd798 0000000000000001 : nt!KeBugCheckEx
ffffb287747a6ca0 fffff80784f05e04 : 0000000000000001 0000000000000000 0000000000000000 0000000000000033 : nt!MiFlushTbAsNeeded+0x22805a
ffffb287747a6df0 fffff80784eb9db6 : fffff80785854f00 8a00000200000001 ffff928e00000000 ffff928e00000001 : nt!MiReservePtes+0x2c4
ffffb287747a6eb0 fffff80784ebc749 : ffff928e822de290 0000000000000000 0000000000000001 0000000000000000 : nt!MiMakePageAvoidRead+0x286
ffffb287747a7080 fffff80784ebb9c0 : 0000000000000011 000000000433f048 ffffb28700000000 ffffb28700000000 : nt!MmCopyToCachedPage+0x219
ffffb287747a7150 fffff80784e2e968 : ffff928e822de290 000000000433f048 ffffb287747a7370 ffff828e00000000 : nt!CcMapAndCopyInToCache+0x400
ffffb287747a7300 fffff807875e226e : ffff828e7a060330 0000000000000000 0000000000000700 0000000000000701 : nt!CcCopyWriteEx+0x168
ffffb287747a73b0 fffff807875e0df5 : ffff928e69a41018 0000000000000000 ffff928e69a41018 ffffb287747a7648 : Ntfs!NtfsCommonWrite+0x11fe
ffffb287747a75d0 fffff80784e82555 : ffff928e7478bba0 ffff928e80797aa0 0000000000000000 ffff928e80797ed0 : Ntfs!NtfsFsdWrite+0x205
ffffb287747a76b0 fffff807867a7c75 : ffffb287747a8000 ffffb287747a1000 0000000000000000 ffffb287747a7790 : nt!IofCallDriver+0x55
ffffb287747a76f0 fffff807867a5913 : ffffb287747a7780 0000000000000000 ffff928e8231f400 0000000000000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2b5
ffffb287747a7760 fffff80784e82555 : ffff928e80797aa0 fffff807852fb8f1 0000000100000000 ffff928e8231f380 : FLTMGR!FltpDispatch+0xa3
ffffb287747a77c0 fffff807852f9522 : ffffb287747a7861 ffff928e8231f510 ffffb287747a7861 0000000000000001 : nt!IofCallDriver+0x55
ffffb287747a7800 fffff8078539f9cd : ffff928e00000000 ffffb287747a7aa0 000000000405ddf4 ffff928e80797aa0 : nt!IopSynchronousServiceTail+0x1d2
ffffb287747a78b0 fffff80785028a75 : ffff928e79644080 00000000000004b4 0000000000000000 0000000000dcdb34 : nt!NtWriteFile+0x63d
ffffb287747a79b0 0000000077bc1cf3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
0000000003f5eff8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77bc1cf3


SYMBOL_NAME: nt!MiFlushTbAsNeeded+22805a

MODULE_NAME: nt

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 22805a

FAILURE_BUCKET_ID: 0x1a_5100_nt!MiFlushTbAsNeeded

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {13b6d0a0-8171-b4a6-ae95-907aaf025545}

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

Another:

***

• *
• Bugcheck Analysis *
• *

***

SYSTEM_PTE_MISUSE (da)
A driver has corrupted system PTEs.
Set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes
to a DWORD 3 value and reboot. If the same BugCheck occurs again the stack trace will
identify the offending driver.
Arguments:
Arg1: 0000000000000302, Type of error.
Arg2: ffffd300326f3000
Arg3: 0000000000000001
Arg4: 00000000000326f3

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

*** WARNING: Unable to verify timestamp for WdFilter.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2327

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 42623

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

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

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

Key : WER.OS.Branch
Value: co_release

Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key : WER.OS.Version
Value: 10.0.22000.1


FILE_IN_CAB: 022722-8687-01.dmp

BUGCHECK_CODE: da

BUGCHECK_P1: 302

BUGCHECK_P2: ffffd300326f3000

BUGCHECK_P3: 1

BUGCHECK_P4: 326f3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa7884fdc2508 fffff8047d2b1999 : 00000000000000da 0000000000000302 ffffd300326f3000 0000000000000001 : nt!KeBugCheckEx
ffffa7884fdc2510 fffff8047d0b8b99 : 0000000000000000 fffff8048162a001 0000000000000001 0000000000000002 : nt!MiReleasePtes+0x1f8d89
ffffa7884fdc2660 fffff8047d0b420f : ffffa7884fdc2779 ffff918333ac34a0 0000000000000002 fffff8047d105b88 : nt!MmUnmapLockedPages+0x179
ffffa7884fdc26d0 fffff8047d0b3b67 : ffff918330ff6b30 ffffa7884fdc2a00 ffff918330630460 fffff8048162a001 : nt!IopfCompleteRequest+0x68f
ffffa7884fdc27e0 fffff8048160b7ea : 0000000000000000 0000000000000000 ffff918330630460 ffff918330630460 : nt!IofCompleteRequest+0x17
ffffa7884fdc2810 fffff804823f32b4 : ffff918309f8eaa0 ffffa90545b96d01 ffffa9054b4fb010 ffff9183000003a2 : FLTMGR!FltSendMessage+0x5ca
ffffa7884fdc2960 ffff918309f8eaa0 : ffffa90545b96d01 ffffa9054b4fb010 ffff9183000003a2 ffffa7884fdc2a70 : WdFilter+0x332b4
ffffa7884fdc2968 ffffa90545b96d01 : ffffa9054b4fb010 ffff9183000003a2 ffffa7884fdc2a70 ffffa7884fdc2a34 : 0xffff918309f8eaa0 ffffa7884fdc2970 ffffa9054b4fb010 : ffff9183000003a2 ffffa7884fdc2a70 ffffa7884fdc2a34 ffffa7884fdc2a50 : 0xffffa90545b96d01
ffffa7884fdc2978 ffff9183000003a2 : ffffa7884fdc2a70 ffffa7884fdc2a34 ffffa7884fdc2a50 0000000000000002 : 0xffffa9054b4fb010 ffffa7884fdc2980 ffffa7884fdc2a70 : ffffa7884fdc2a34 ffffa7884fdc2a50 0000000000000002 ffff918309570180 : 0xffff9183000003a2
ffffa7884fdc2988 ffffa7884fdc2a34 : ffffa7884fdc2a50 0000000000000002 ffff918309570180 0000000000000000 : 0xffffa7884fdc2a70 ffffa7884fdc2990 ffffa7884fdc2a50 : 0000000000000002 ffff918309570180 0000000000000000 ffff918309570040 : 0xffffa7884fdc2a34
ffffa7884fdc2998 0000000000000002 : ffff918309570180 0000000000000000 ffff918309570040 ffffa7884fdc2a89 : 0xffffa7884fdc2a50 ffffa7884fdc29a0 ffff918309570180 : 0000000000000000 ffff918309570040 ffffa7884fdc2a89 0000000000000000 : 0x2 ffffa7884fdc29a8 0000000000000000 : ffff918309570040 ffffa7884fdc2a89 0000000000000000 fffff8047d132f64 : 0xffff918309570180


SYMBOL_NAME: WdFilter+332b4

MODULE_NAME: WdFilter

IMAGE_NAME: WdFilter.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 332b4

FAILURE_BUCKET_ID: 0xDA_WdFilter!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {490897ad-2b84-077a-e141-ffd1181d7bd7}

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

New dump files (five in total): https://www.mediafire.com/file/tgz4w3ufsrv02mz/NEW_TUF-MONTECH-Sun_02_27_2022_231657_82.zip/file

Had one more crash when opening a browser. It was an exception on invalid stack. Got another one something about kmode exception. Hmm. Idk what's going on anymore. Logging in throws new problems, too: Netwtw10.sys throws a kmode exception not handled. The only thing that runs stably is safemode, even when opening a ton of tabs and browsers, I don't get BSODs in safemode.

Edit: booted back into Windows. Works as long as I don't launch any browsers it looks like (because they would automatically BSOD the system). Trying to update Asus drivers that I downloaded in safe mode. Let's see if that helps...

Edit 2: This is the first time I am able to boot into Windows and run the browsers without BSOD after having gone into safe mode and having deleted mobo-installed software from the flash. Don't think it will last forever, but who knows. Definitely the strangest behavior I've ever seen from a PC.

Edit 3: reflashed the BIOS again just to be sure. Set all to defaults and then tweaked to same settings as before. Rebooted. No BSOD on restarting browsers, something normally not possible before. /shrug. I really have no idea wtf is going on.

 

[Colif]

its possible that your version of armory crate itself needed an update as you were on an older bios before. All new Asus boards have a trigger in their bios that makes it install Armory crate on first install. Its possible it got an older version. I assumed it grabbed it off the internet on 1st boot.

Netwtw10.sys

that was the intel lan drivers.

let us know if you get any more BSOD, lets see if BIOS update was all it needed.

 

[lucid_power_daoc]

🤓

its possible that your version of armory crate itself needed an update as you were on an older bios before. All new Asus boards have a trigger in their bios that makes it install Armory crate on first install. Its possible it got an older version. I assumed it grabbed it off the internet on 1st boot.


that was the intel lan drivers.

let us know if you get any more BSOD, lets see if BIOS update was all it needed.

Yeah, maybe that's all that was needed for stability w/Win11. Okay, let's see how we fare. Woke up the PC from sleep. Works enough to respond here 😀

I'll report again if needed. Thank you!

 

[lucid_power_daoc]

OK, just an update: it seems like even with a fresh install, after all drivers are updated, I keep getting BSODs about apc index. I will do another fresh install and not update any drivers since I cannot tell what it is that's doing this. That's all I wanted to add. It's stable only that way as I've seen from testing.

 

[Colif]

on clean install, set up this just in case

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

 

[lucid_power_daoc]

on clean install, set up this just in case

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

Well, on fresh install without updating drivers, I think I have no problems. It's only after I update audio, lan, wifi, Bluetooth, Intel Management Engine, etc., that all hell breaks loose. Idk what is the cause of this, but too much stuff is installed. If I get another BSOD, I'll post here. Since it's a fresh install, there are no minidumps to post atm. I will zip up any new ones if they happen, though!

 

[Colif]

You are on latest bios now I assume? you updated right?
so the newest chipset drivers and Intel Management Engine Interface should match what you have now.

so you getting drivers via Armory Crate? Maybe I wouldn't...

Ethernet - download Win11 Auto Installation Program (NetAdapterCx) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software
Most intel can be gathered via - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

You could probably get the audio drivers from the Asus site, its the newest version available. - https://www.asus.com/Motherboards-C...PRIME/PRIME-Z690-P-WIFI-D4/HelpDesk_Download/

a lot of Asus software isn't much good, if you don't use Armory crate for anything else I would remove it.

 

[lucid_power_daoc]

You are on latest bios now I assume? you updated right?
so the newest chipset drivers and Intel Management Engine Interface should match what you have now.

so you getting drivers via Armory Crate? Maybe I wouldn't...

Ethernet - download Win11 Auto Installation Program (NetAdapterCx) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software
Most intel can be gathered via - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

You could probably get the audio drivers from the Asus site, its the newest version available. - https://www.asus.com/Motherboards-C...PRIME/PRIME-Z690-P-WIFI-D4/HelpDesk_Download/

a lot of Asus software isn't much good, if you don't use Armory crate for anything else I would remove it.

Hey,

Yup. I am on latest bios. Ran off to the store, came back, no BSOD. Typically it BSOD's after 20-30 seconds when logging in. Or after 30-40 minutes. I went out for an hour almost.

I do have armory crate but I didn't update any drivers on it. Last time I did all these updates, the PC became unusable as you've seen me report. Currently armory crate has been reinstalled but nothing else from it or from Asus. Previously these drivers were updated through Asus's website (not armory crate). I use armory crate mostly for the fan control stuff and the fan colors, but I could use an alternative if need be.

I'm afraid installing these drivers from Asus's site will destroy this installation. X_X but... I will try. I will update everything w/the suggestions you gave & using the links offered.

Here's a list (which doesn't include some drivers I got through Asus) that Windows removed on a refresh. Refresh seems stable, no crashes. Maybe something in this list is causing problems? =\

Note that previously on crashes, all it took was a simple run of something like "View Reliability History" from search. Instant BSOD.

Edit: So far, I installed all the drivers you recommended. The LAN ones are saying they can't be installed for w/e reason (something about the connection missing), but so far, that's worked safely. Need to finish reinstalling all my programs (again) and to continue to use the PC into another day to see whether BSODs return. I'm thinking the culprit could be audio drivers & perhaps something from the armory crate software. Dunno.

Edit2: Well, I really wanted to change the colors on the RGB lights, so I had to reinstall armory crate's AURA software. And I had to reinstall armory crate itself b/c the fans were not responding in q fan (the service had locked control to itself). I unlocked it, and uninstalled it. In the time that I did that, I got two BSODs. It's probably because I deleted the service & reinstalled the AURA on top without actually rebooting. Addendum: nope. With aura services, BSODs are back non stop.

This error in Reliability Monitor:

Problem Event Name: BlueScreen
Code: 3b
Parameter 1: c0000005
Parameter 2: fffff8017a7ae40a
Parameter 3: ffffa80be543ed70
Parameter 4: 0
OS version: 10_0_22000
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.22000.2.0.0.768.101
Locale ID: 1033

Extra information about the problem
Bucket ID: AV_nt!EtwpDeleteRegistrationObject

Edit3: Seems I have no choice but to reinstall. Reinstalled Windows again because having any services run from Armory Crate, even what's working with the LED lights, is somehow responsible for these garden variety BSODs. This time I decided NOT to install anything related to Aura connect. And so far only got one random IRQL BSOD and nothing else in the four hours that it's been running.

�

App name	Publisher	Version
Acoustica Mixcraft 9 Pro Studio (64-bit)	Acoustica	9.0.0.469
ARMOURY CRATE Lite Service	ASUS	5.0.8
ASUS Framework Service	ASUSTek COMPUTER INC.	2.1.2.3
ASUS Motherboard	ASUSTek Computer Inc.	3.00.10
AURA lighting effect add-on	ASUS	0.0.21
AURA lighting effect add-on x64	ASUS	0.0.21
AURA Service	ASUSTeK Computer Inc.	3.05.29
Discord	Discord Inc.	1.0.9004
f.lux	f.lux Software LLC
GameSDK Service	ASUSTek COMPUTER INC.	1.0.0.4
Intel(R) Management Engine Components	Intel Corporation	2201.16.0.2645
Melodyne 5	Celemony Software GmbH	5.01.01003
Microsoft OneDrive	Microsoft Corporation	21.220.1024.0005
Microsoft Update Health Tools	Microsoft Corporation	4.65.0.0
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161	Microsoft Corporation	9.0.30729.6161
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161	Microsoft Corporation	9.0.30729.6161
Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.28.29913	Microsoft Corporation	14.28.29913.0
Microsoft Visual C++ 2015-2019 Redistributable (x86) - 14.28.29914	Microsoft Corporation	14.28.29914.0
MSI Afterburner 4.6.4	MSI Co., LTD	4.6.4
Nightlife	Acoustica
NVIDIA FrameView SDK 1.2.7321.30900954	NVIDIA Corporation	1.2.7321.30900954
NVIDIA GeForce Experience 3.25.0.84	NVIDIA Corporation	3.25.0.84
NVIDIA Graphics Driver 511.79	NVIDIA Corporation	511.79
NVIDIA HD Audio Driver 1.3.39.3	NVIDIA Corporation	1.3.39.3
NVIDIA PhysX System Software 9.21.0713	NVIDIA Corporation	9.21.0713
Opera GX Stable 83.0.4254.70	Opera Software	83.0.4254.70
Patriot Viper DRAM RGB	Patriot Memory	1.0.9.2
Patriot Viper M2 SSD RGB	Patriot Memory	1.0.6.5
Razer Synapse	Razer Inc.	3.7.0215.021412
Realtek Audio Driver	Realtek Semiconductor Corp.	6.0.9244.1
ROG FAN XPERT 4	ASUSTek Computer Inc.	2.00.03
ROG Live Service	ASUSTek COMPUTER INC.	1.3.12.0
Steam	Valve Corporation	2.10.91.91
Two-Way AI Noise Cancelation	ASUSTek Computer Inc.	1.0.2.4
Universal Holtek RGB DRAM	PD	1.0.0.2
VGA	ASUSTek Computer Inc.	2.11.03
VLC media player	VideoLAN	3.0.16

 

[Colif]

Seems I have no choice but to reinstall.

🙁

If you only want it for rgb, use this - https://rgbsync.com/
or https://www.signalrgb.com/

 

[lucid_power_daoc]

🙁

If you only want it for rgb, use this - https://rgbsync.com/
or https://www.signalrgb.com/

Ooo, I see. Thanks!

And yep, whole day of casual use resulted in PC being stable. I guess there's the culprit then.

Thanks for all your help again!