New
#21
Please disable driver verifier
- Open an admin command prompt
- Enter "verifier/reset" (without quotes)
Please disable driver verifier
- Open an admin command prompt
- Enter "verifier/reset" (without quotes)
Took a while but I got a brand new BSOD
Update following Logitech drivers
Driver Reference Table - lvuvc64.sys
Driver Reference Table - lvrs64.sys
Driver Reference Table - lvbflt64.sys
As this installation is an upgrade from Windows 7, it is an option to do a clean install.
With an upgrade, Windows is installed above another Windows, this causes problems and is also the reason why there is a folder 'Windows.Old' created.
Windows 10 - Clean Install - Windows 10 Forums
Hey I did a clean install of windows on thursday ... got a new bsod today.
New logs attached.
A 0x1A with hardware module name
Please verify the voltage and frequency values of the RAM are as they should be in the BIOS.Code:SYMBOL_NAME: ONE_BIT FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: memory_corruption
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
NoteDo not run SeaTools on an SSD as the results will be invalid.
Run chkdsk Disk Check - Windows 7 Help Forums
If all above hasn't helped, try running driver verifier.
Read the instructions carefully!
WarningPlease make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
NoteYour system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
Memory running at stock speed and voltage.
Disk check and SeaTools scans all passed without errors.
Running verifier now with:
- I/O Verification
- Force pending I/O requests
- IRP logging
as described by the tutorial ... no problems yet ... will post again once I hit another BSOD.
Once again thanks for helping me out axe0
Ps. I need to decide if I want to replace any of my hardware this week (cause my 30 days return is running out). If you were to guess what are the most likely culprits here? Motherboard? Memory? CPU? Is any of these guaranteed not to be the cause ??