BSOD on startup every day - Trying to identify specific causation

YELDUR 1

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.

0 comments

71 answers

Docs 16,871 Reputation points

2021-10-24T21:48:42.503+00:00

Many steps are trial and error.

So as long as you have backup options then you can proceed.

At times system restore points are unavailable or do not complete.

So it's typically best to make free or pay backup images.

The images can be saved to another disk drive or the cloud or both.

The disk drive is useful when there is no internet.

The cloud is useful when there are acts of mother nature: fire, flood, etc.

These are software for free or pay backup images.

Acronis
Aoemi
EaseUS
Macrium
Paragon
etc.

Instructions can be provided if you have another disk drive with space or have space in the cloud.

When applicable restart WDV with the three customized settings.

.
.
.
.
.
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.
YELDUR 1 Reputation point

2021-10-24T21:59:57.117+00:00

Hi Docs,

I have both a 2TB cloud and a 2TB external HDD

I presume that would be fine, but either way I have my D:\ drive backed up to the cloud (or at least the relevant portions of it)

The 2TB external drive is not up to date and hasn't been used to back anything up since I built this rig.
The Cloud is relatively recent and was used to download my C:\Users\Yeldur folder and some specific folders on the D:\ drive.

Aomei was the first one I clicked on that was free, so by luck of the draw I'll go with that one unless you have any other suggestion.

To clarify, would you like me to restart the WDV now or after we've gone through the steps you mention above?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Docs 16,871 Reputation points

2021-10-24T22:05:41.297+00:00

Please start WDV now.

Today I'd like to complete as much as possible.

The backup images you can make once the troubleshooting has completed.

Remind me and I'll post a link for Macrium.

.
.
.
.
.
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.
YELDUR 1 Reputation point

2021-10-24T22:12:26.023+00:00

Understood, on it now and will feed back once complete.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
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 No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Docs 16,871 Reputation points

2021-10-24T23:02:42.47+00:00

1) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
2) re-install the Nvidia GPU driver from the Nvidia website
3) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.4.3 (or newer version if available)
https://www.wagnardsoft.com/

Display Driver Uninstaller: How to use - Windows 7 Help Forums
https://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html

Download Drivers | NVIDIA
https://www.nvidia.com/Download/index.aspx

If BSOD continue then the troubleshooting will move onto hardware.

Many of the dump files have implicated Memory.

All tests have:
true positives
true negatives
false positives
false negatives
accuracy

There is no test for the motherboard.

A motherboard problem is typically made after ruling out RAM.

RAM testing may take a lot of time unless you have RAM to swap.

Indicate whether you can borrow RAM from a friend, neighbor, relative, or local computer store.

.
.
.
.
.
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.
YELDUR 1 Reputation point

2021-10-24T23:10:20.607+00:00

Will do and will feed back once complete.

YELDUR 1 Reputation point

2021-10-24T23:31:39.673+00:00

Hi Docs,

I've reinstalled the GPU drivers as per your instructions

With regards to the RAM, I do have my old PC's RAM inside my other computer; however I do have a DOCP profile set up on this computer for my RAM, so would need to disable that profile first and get it back to "default" before I could use it as they're clocked very differently (3600MHz vs 2600)

The alternative thing I could do is make use of Amazon, because they enable returns regardless of whether you test it first I could simply purchase more of the exact same RAM, install it, test it, then return it once I don't require it. A bit of an odd way to do things, but I can get the RAM shipped out to me with one day delivery.... So it's feasible. And might actually be less tedious than messing around with DOCP profiles.

I am going to guess the next step will be to again re-enable WDV but will wait for that instruction before doing so just in case we don't want to do that.

I must admit I was suspicious of the RAM with the amount of memory based BSOD's I've been getting, which is why I was surprised to see it pass the MemTests we performed.

I sincerely hope this isn't a MoBo problem, that would be truly saddening.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Docs 16,871 Reputation points

2021-10-24T23:52:27.007+00:00

Please make a new restore point then restart WDV.

Post a new V2 and memory dump.

If there are more dumps without misbehaving drivers then reset the BIOS to defaults.

(Wait for new posts.)

.
.
.
.
.
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.
YELDUR 1 Reputation point

2021-10-25T00:13:59.97+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 -> regular BSOD
6) Rebooted again and received a verifier BSOD -> Rebooted -> Loaded into advanced recovery
7) CMD -> ran "verifier /bootmode resetonbootfail" -> Rebooted -> logged in -> regular 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/1IRrrATaot4m0VD7vsgQTjl9OWa90GFyx/view?usp=sharing

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)
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

BSOD on startup every day - Trying to identify specific causation

71 answers

Your answer