If all non-windows drives are removed/detached this event viewer entry should disappear:
Then the drives will be reattached one at a time to find the drive related to this entry.Code:The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
Normal boot can be used.
it still bsods with all drives detached in normal startup.
im not worried about finding a specific drive at this point, all 3 are old and need to be replaced anyways.
If you detach all non-windows that will allow confirmation that the entry was related to the other drives.
Once that has been confirmed the next step will be Windows driver verifier.
Instructions will be posted later in the day,
Chkdsk C:
Code:Windows has made corrections to the file system.
Windows driver verifier is designed to stress test drivers.
Misbehaving drivers should cause BSOD depending upon selected customized stress tests.
If dump files are created and collected they can be debugged to find misbehaving drivers.
After each BSOD you will need to return to the desktop by turning off the tool.
The tool after a BSOD is turned off in the Windows Recovery Environment by running the reset or bootmode commands.
When back on the desktop you will run V2 and search for C:\windows.memory.dmp
Upload a new V2 and if the memory.dmp is < 1.5 GB post a share link.
Start the testing with the 3 customized settings in the TF link.
If there are no immediate BSOD the increase the number of customized settings by 3 - 5 / hour up to the 19 in the Microsoft link.
Plan to run the tool for 48 hours. Then an additional 36 hours after the last BSOD.
If there are no BSOD then that will complete the troubleshooting with this tool.
While using the tool there can be performance problems and slow boots.
Customized test settings may need to be modified.
Make a new restore point.
When you are comfortable with the commands to turn off the tool you can start running windows driver verifier.
Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983
v2 log after verfier bsod
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
it blue screened in about 2 mins, it still does not make memory dumps or minidumps.
and when it bsods it just turns 75% of the screen blue and just freezes like that.
Has Windows verifier been started?
i started it, restarted and it ran for like 2 mins and bsoded and froze on the blue screen, then restarted in safe mode and turned verifier off via cmd verifier /reset. then restarted and ran v2 log.
i cant really let it run for 48 hours in normal mode because since the auto restart is turned off it just blue screens instantly and gets stuck there.
unless i need to turn off verifier via verifier/ delete existing settings?
Usually the computer's BSOD shortly after Windows verifier is started.
However there are many times it occurs substantially later.
So the tool initially captures the misbehaving driver(s) and then it can run for long periods without a BSOD.
This then indicates that the drivers were fixed (no BSOD for 36 hrs).
The automatic restart is turned off so that BSOD are not missed.
so keep veirifier on and just restart when it bsods unitll it no longer bsods. ok
- - - Updated - - -
i have to disable verifier before i can run v2log?
so "enable verifier/restart/wait for bsod/restart/disable verifier/restart/run v2log" ? then repeat untill no longer bsods?
- - - Updated - - -
this is a log after like 10 bsods in verifier
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Quote