Make a new backup image.
Restart WDV with the following settings:
Only test one driver: mrcbt.sys
Only run one customized test: [ ] 0x02000000 Code integrity checks.
If there is no immediate BSOD then post a new querysettings.
For any BSOD post a new V2 share link into the newest post.
Same BSOD pre-login as before.
V2 logs:
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Today is 01/03/2023.
The last BSOD dump file was from 01/01/2023.
Make a new restore point.
Restart WDV with the same settings > create BSOD > repeat multiple times to create many dump files
(make a new restore point after each BSOD and before restarting WDV)
Then post a new V2 share link into the newest post.
It BSOD before windows login screen even shows up and right after HP startup. Every time it has done that in the past on this thread (see post 53) it has never given a mini dump file--presumably because windows has not properly started yet.
verifier /reset or /bootmode.... never works in this scenario and I always end up using a restore point (which may mean any minidump created is lost).
Make a fresh backup image using Macrium.
Then uninstall the Macrium software.
Make a new restore point.
Restart WDV:
a) test all non-Microsoft drivers
b) test no Microsoft drivers
c) run all customized tests except:
[ ] 0x00000004 Randomized low resources simulation.
If there is no immediate BSOD then post a new querysettings.
For any BSOD post a new V2 share link into the newest post.
Created new image backup.
Uninstalled Macrium completely.
Made restore point.
##Same failure: BSOD post HP bootup and pre-windows login screen--except no cause listed.
Hit power button to reboot. It was so bad that the reboot went into a black screen: nothing. Mouse not lite up either (NOTE: it did this the last 3 BSODs). So, I hit the power button again.
This time, the system was so messed up it went straight to a restore point on its own.
I originally wanted to troubleshoot for PC not waking up from sleep mode (making BSODs instead).
Question 1: Is this taking me that route to find the sleep problem or did we find other problems?
Question 2: Are these other problems with the BSODs corrupting files and making more problems?
Question 3: Does failing a driver test mean that software will create a BSOD or just that the software may fail now and then (but otherwise my PC will be stable and not crash)?
thank you for any answers.
BSOD:
The most recent BSOD were cause by a misbehaving Macrium driver.
Failed to write to the tracking file on device \Device\HarddiskVolume22 with status 0xC0000185
Failed to write to the tracking file on device \Device\HarddiskVolume22 with status 0xC0000185
The previous session did not finalize the tracking file on device \Device\HarddiskVolume22. The tracking file has been reset.
The checksum for the tracking file on device \Device\HarddiskVolume22 is incorrect. The tracking file has been reset.
Failed to write to the tracking file on device \Device\HarddiskVolume20 with status 0xC0000185
The previous session did not finalize the tracking file on device \Device\HarddiskVolume20. The tracking file has been reset.
Please make a new restore point.
Restart WDV with all of the customized tests except
[ ] 0x00000004 Randomized low resources simulation.
Test only this driver:
nvlddmkm.sys
If there is no immediate BSOD then post a new querysettings.
It's good.
Test these drivers:
nvlddmkm.sys
netwtw10.sys
ibtusb.sys
If there is no immediate BSOD post a new querysettings.
Quote
