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: Oldest
Most helpful Newest Oldest
  1. Docs 16,871 Reputation points
    2021-10-17T00:27:24.477+00:00

    There are settings that can be modified to increase the likelihood that crashes are witnessed by the end user.
    And that when these crashes occur they create dump files that are more useful for those providing help.

    When using the default Windows setting it can be easy to miss BSOD.
    The default setting is to automatically restart after a BSOD.

    The modified setting unchecks automatically restart.
    The end user now can view the BSOD screen with :(
    Sometimes it may display a misbehaving driver.

    There are various types of settings for when a BSOD occurs.
    The 7 is for automatic.
    The goal is to create a dump file that can be shared using a share link.
    Some settings do not allow the creation of a memory dump.
    Other settings allow the creation of a very large dump file that cannot be easily shared.

    The next two commands are to check that the settings were properly modified.

    The next command makes sure that the page file is automatically managed.

    The next command checks to see that it had been properly modified.

    The next command checks to see whether windows had predicted RAM would fail.

    The final command turns off hibernation which also turns off Windows fast startup.

    Some of the dump files had reported: The disk subsystem returned corrupt data while reading from the hibernation file.

    All of the above steps should be maintained during the troubleshooting process.

    When troubleshooting has completed you are free to modify any of the settings to your preferences.

    In addition to the above steps please post images of each of these windows:
    a) startup and recovery system failure settings
    b) virtual memory / page file settings

    If you need instructions on how to open these windows steps can be provided.

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

    1 person found this answer helpful.
  2. Docs 16,871 Reputation points
    2021-10-17T01:11:30.66+00:00

    Type:

    Win + r
    sysdm.cpl

    Click on the advanced tab
    In startup and recovery click settings

    Post an image or share link for the startup and recovery windows.

    Click cancel so that the startup and recovery window closes.

    Under performance click settings.
    Click on the advanced tab.
    Under virtual memory click change.

    Post an image or share link of the virtual memory windows.

    For all steps / tests make sure that images and or share links are posted into this thread.

    When or if changes are made to any of the settings in the virtual memory window make sure that the computer is rebooted so that the settings are maintained.

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

    1 person found this answer helpful.
  3. Docs 16,871 Reputation points
    2021-10-17T02:31:43.17+00:00

    Most end users are better off using visual instead of commands.

    So you will see the settings that can be modified once you post the images or share links into this thread.

    Most of the settings did not need to be modified as they were already default settings.

    The commands are easy to run and they are run routinely so that settings are always optimized to create BSOD and create memory dumps that can be sharred.

    So unless you had modified these settings the only one to reset should be the automatic restart.

    If you had a server you would want to have automatic restart checked.

    Otherwise you may want to have the greatest likelihood of knowing if Windows had had a BSOD.

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

    1 person found this answer helpful.
  4. YELDUR 1 Reputation point
    2021-10-17T03:20:09.403+00:00

    For the reference of Docs, here is what the testing suggests thus far:

    1)

    Microsoft Windows [Version 10.0.19042.1288]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19042.1288

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

    2)

    Microsoft Windows [Version 10.0.19042.1288]
(c) Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-DSA3D75\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set debuginfotype = 7
Updating property(s) of '\\DESKTOP-DSA3D75\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get debuginfotype
DebugInfoType
7


C:\WINDOWS\system32>wmic computersystem where name=%computername% set automaticmanagedpagefile=true
Unexpected switch at this level.

C:\WINDOWS\system32>wmic computersystem where name=%computername% get automaticmanagedpagefile
Unexpected switch at this level.

C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier        {badmemory}

C:\WINDOWS\system32>powercfg -h off

C:\WINDOWS\system32>

    3) (No results for C: yet as it obviously can't dismount the volume the OS is on, so as you suggested this will run on next boot)

    C:\WINDOWS\system32>chkdsk /r /v d:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is Games/Other.

Stage 1: Examining basic file system structure ...
  329472 file records processed.
File verification completed.
 Phase duration (File record verification): 1.21 seconds.
  41 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.49 milliseconds.

Stage 2: Examining file name linkage ...
  1341 reparse records processed.
  362248 index entries processed.
Index verification completed.
 Phase duration (Index verification): 1.97 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 45.95 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.44 milliseconds.
  1341 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 4.45 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 24 unused index entries from index $SII of file 9.
Cleaning up 24 unused index entries from index $SDH of file 9.
Cleaning up 24 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 1.49 milliseconds.
  16389 data files processed.
 Phase duration (Data attribute verification): 0.19 milliseconds.
CHKDSK is verifying Usn Journal...
  37990192 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 53.12 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  329456 files processed.
File data verification completed.
 Phase duration (User file recovery): 10.75 minutes.

Stage 5: Looking for bad, free clusters ...
  25776148 free clusters processed.
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 976744447 KB total disk space.
 873086000 KB in 283880 files.
    91064 KB in 16390 indexes.
     0 KB in bad sectors.
    462787 KB in use by the system.
    65536 KB occupied by the log file.
 103104596 KB available on disk.

   4096 bytes in each allocation unit.
 244186111 total allocation units on disk.
  25776149 allocation units available on disk.
Total duration: 10.80 minutes (648543 ms).

    Was this answer helpful?

    0 comments
  5. Docs 16,871 Reputation points
    2021-10-17T03:27:24.51+00:00

    The RAM testing can be performed while sleeping and / or overnight.

    Was this answer helpful?

    1 person found 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.