BSOD on startup every day - Trying to identify specific causation

YELDUR 1 Reputation point
2021-10-15T13:38:02.73+00:00

Hi all,

For the past week or so I've been experiencing BSODs whenever I power on the computer first during the day; after we REACH the Windows splash screen, I have no further issues, even when restarting.

rom reviewing the Event Logs I can see one in there stating the following:

"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
followed closely by:
"The driver \Driver\WudfRd failed to load for the device PCI\VEN_5853&DEV_1003\1&1a590e2c&0&03."

So far as far as causation goes, this is the only thing throwing flags, as I've successfully performed Windows Memory Diagnostics with no issues being found, system file checks with no corruption being found, and lastly checking in on the device manager and checking all tabs to ensure nothing in there is throwing errors. As far as I can tell, these issues began this week.

I know that this week I plugged in a new keyboard that is different to that of my old one, and in doing so I needed to download some more drivers for it, however I went from a Roccat Aimo 120 to a Roccat Aimo 100, to which the only real difference is the fact that the 100 doesn't have a hand wrest with the keyboard. Besides that, it doesn't appear any different specification wise, so I'm unclear on whether this is the cause. I also changed my power plan on the rig from Balanced to Performance, though I don't expect this to be the cause.

Originally I believed perhaps that drivers were the issue, however, now I'm not so sure.

To cut a long story short, I ran a bugcheck analysis using the Windows Debug tools which threw me the following: 

12: kd> !analyze -v
***

    *
    Bugcheck Analysis *
    *

***

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff83816716da08
Arg3: 0000800000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3249

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 10478

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

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

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

Key : MemoryManagement.PFN
Value: 800000000

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


BUGCHECK_CODE: 1a

BUGCHECK_P1: 41792

BUGCHECK_P2: ffff83816716da08

BUGCHECK_P3: 800000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: autochk.exe

STACK_TEXT:
ffff988d4679f388 fffff8054624423a : 000000000000001a 0000000000041792 ffff83816716da08 0000800000000000 : nt!KeBugCheckEx
ffff988d4679f390 fffff80546242a6f : ffff8688b7883700 0000000000000000 ffff868800000002 0000000000000000 : nt!MiDeleteVa+0x153a
ffff988d4679f490 fffff80546212c10 : 0000000000000001 ffff988d00000000 ffff8688b7883550 ffff8688b7910080 : nt!MiDeletePagablePteRange+0x48f
ffff988d4679f7a0 fffff80546252277 : 000000002ce2db4f 0000000000000000 ffff868800000000 fffff80500000000 : nt!MiDeleteVad+0x360
ffff988d4679f8b0 fffff805465f908c : ffff988d00000000 0000000000000000 ffff988d4679fa10 000002ce2db30000 : nt!MiFreeVadRange+0xa3
ffff988d4679f910 fffff805465f8b65 : 00007ff70784b980 000002ce44f49e50 ffff988d4679fad8 0000000000000000 : nt!MmFreeVirtualMemory+0x4ec
ffff988d4679fa60 fffff80546408bb8 : ffff8688b7910080 ffff868800000001 0000000000000000 ffff868800000000 : nt!NtFreeVirtualMemory+0x95
ffff988d4679fac0 00007ffa4676d134 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000e2f757a4b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`4676d134


MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner

I work in tech, but I am by no means a master, and to be frank, I don't know what I'm reading here. I can gather that it is telling me that there's something wrong with memory, in that it's seeing corruption, but other than that I'm honestly not too sure.

Here's the event log that prompted me finding these issues:

Event ID 1001

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041792, 0xffff83816716da08, 0x0000800000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 15812135-3f48-42c4-b474-5b9fd5a5cf7e.

If there's any more information required, please don't hesitate to ask and I will do my best to gather it for you.

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments

71 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. YELDUR 1 Reputation point
    2021-10-25T00:59:44.887+00:00

    With regards to resetting the BIOS, what are the ramifications of this? Will I need to reflash the BIOS again or will this just simply revert the DOCP changes made back to their defaults (I've made no other changes to the BIOS besides setting up the DOCP changes)

    I'm going to need the system resources for doing my work; I understand this might be an annoyance but is it possible that we can postpone this until such a time that you and I are better available? I know that you're not very available over the course of the next two weeks (at least), and I am not going to be very available this coming week either. As this isn't affecting the operation of my system outside of when I first boot the device up in the morning, I'm happy to wait until you and I are better available, if this is something you are open to?

    If you're not willing to do this, I understand completely, and will try to continue on my own from here, but would appreciate heavily if you could give me some advice about what it is you search for inside the DMP logs to look at whether drivers are the issues etc etc.

    The bottom line of what needs to be done is essentially:

    1) Reset the BIOS (Presumably I do this from the BIOS screen)
    2) If I continue to see BSOD's once this is done, the RAM is the next thing to look at with regards to issue causation
    3) Need to then remove the RAM module, one at a time and test the system with this setup for 1 week at a time
    4) If I receive BSOD's during the general operation of the device during that week then swap the other RAM module into the same DIMM slot

    Once again, I will say thank you very much for all your time on this regardless of where we go from here, I wouldn't have gotten this far without your support and I'm incredibly glad to have had you.

    Was this answer helpful?

    0 comments
  2. YELDUR 1 Reputation point
    2021-10-24T22:32:20.88+00:00

    Hi Docs,

    1) Turned on verifier -> Rebooted
    2) Hit windows desktop splash screen -> verifier BSOD
    3) Rebooted -> Hit a verifier BSOD -> Restarted again
    5) Hit advanced recovery -> CMD -> ran "verifier /reset" -> shut down -> logged in -> verifier BSOD
    6) Rebooted again and received a verifier BSOD -> Rebooted -> Loaded into advanced recovery
    7) CMD -> ran "verifier /bootmode resetonbootfail" -> Rebooted -> Verifier BSOD
    8) Rebooted -> Received regular BSOD -> Rebooted -> Advanced recovery
    9) System Restore -> Restored to the restore point I created

    https://drive.google.com/file/d/1saIrtwcgHQByOpmMbko5CnTtI1DgFwfW/view?usp=sharing
    https://drive.google.com/file/d/1hVP-LfAV2NfEQpeA8p66yYhVoNAQ0gaB/view?usp=sharing

    I should note that the system restores would have likely renamed those drivers back to the place they were, do you need me to rename them before each WDV attempt? I can do so if required.

    Was this answer helpful?

    0 comments
  3. Docs 16,871 Reputation points
    2021-10-24T21:05:28.96+00:00

    When software incompletely uninstall you may be able to use Revo uninstaller:

    https://www.revouninstaller.com/

    The logitech software / drivers came with the logitech hardware.
    The computer should work smoothly without this hardware.
    To have the logitech software work you'll need to reinstall the drivers or find alternative hardware.

    The memory dump is downloading.

    .
    .
    .
    .
    .
    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: Vote = a helpful post
    .
    .
    .
    .
    .

    Was this answer helpful?

  4. YELDUR 1 Reputation point
    2021-10-24T20:40:24.39+00:00

    Hi Docs,

    1) Turned on verifier -> Rebooted
    2) Hit windows desktop splash screen -> Logged in -> regular BSOD
    3) Rebooted -> Hit a regular BSOD -> Restarted again
    5) Hit advanced recovery -> CMD -> ran "verifier /reset" -> shut down -> logged in -> regular BSOD on sign in
    6) Rebooted again and received a regular BSOD on sign in -> Rebooted -> Loaded into advanced recovery
    7) CMD -> ran "verifier /bootmode resetonbootfail" -> Rebooted -> Logged in and received a regular BSOD
    8) Rebooted -> Received regular BSOD -> Rebooted -> Advanced recovery
    9) System Restore -> Restored to the restore point I created

    BSOD dumps:
    https://drive.google.com/file/d/1saIrtwcgHQByOpmMbko5CnTtI1DgFwfW/view?usp=sharing
    https://drive.google.com/file/d/1IQYKEeErTBr044NxucLlx1b9iEuGR2s0/view?usp=sharing

    Reinstalled the chipset drivers successfully
    Renamed the other drivers successfully

    Attempts to uninstall the LG Hub failed, not sure why it failed but it gave me these errors:

    https://drive.google.com/file/d/1SStk3Q5FSj7oCcxP44Bm4kWnc9c7hhHI/view?usp=sharing
    https://drive.google.com/file/d/1cVucCWDWde6BxqD_ay-064vGXB6W2KRz/view?usp=sharing

    Reinstalled the LG Driver as requested however, and this was successful. (Uninstalled, scanned for hardware changes)

    Checked for Windows updates again -> Checked successfully and installed some Windows Defender update

    Was this answer helpful?

  5. Docs 16,871 Reputation points
    2021-10-24T19:44:46.367+00:00

    Make a new restore point:
    https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

    Download to the desktop the chipset drivers from the Asus website.

    Find a new driver to replace: logi_joy_vir_hid.sys and download to the desktop.
    Logitech G HUB Virtual HID Device Driver
    https://www.logitech.com/en-us
    https://support.logi.com/hc/en-us
    https://support.logi.com/hc/en-us/community/topics

    Disconnect the computer from Wifi (hardware off if available) and Ethernet (cat5).

    Rename these drivers:

    ctxusbmon.sys > ctxusbmon.sys.old
    asmtxhci.sys > asmtxhci.sys.old
    asmthub3.sys > asmthub3.sys.old

    Install the chipset drivers from the desktop.

    Uninstall and reinstall: logi_joy_vir_hid.sys
    logi_joy_vir_hid Logitech G HUB Virtual HID Device Driver c:\windows\system32\drivers\logi_joy_vir_hid.sys Kernel Driver

    Don't connect to the internet yet.

    Restart WDV with the 3 customized settings.

    For any new BSOD > post separate share links for each V2 and memory.dmp

    Connect to the Internet.
    Perform Windows updates.

    .
    .
    .
    .
    .
    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: Vote = a helpful post
    .
    .
    .
    .
    .

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.