New
#41
Absolutely. The short test passes most of the times even with a bad drive. It's the long test that will really check it.
Absolutely. The short test passes most of the times even with a bad drive. It's the long test that will really check it.
Well my mechanical hd passed the long test what should I do now?
I think you are just trying to give me a hard time. Let's try Driver Verifier.
WarningBe sure to create a System Restore point before proceeding further https://www.tenforums.com/tutorials/4...dows-10-a.html
DRIVER VERIFIER
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Information
What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
Warning
Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.
Tip
- If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
- If you cannot boot in Safe mode, do a System Restore to a point you made earlier.
Let us know the results, with the subsequent crash dumps, if any.
There are no limitations. Use your computer any way you want. We are putting extra stress on the Non Microsoft drivers in hopes it will BSOD and catch the offending driver. Be sure you create a restore point before enabling Driver Verifier. Sort the drivers by Provider and enable it on every driver NOT provided by Microsoft. There is a slight chance you will have to do a clean install, but every precaution has been taken so that does not happen. It's beginning to look like you may end up doing one anyway.
Well the thing about driver verifier and my computer is that it crashes less when dv is on
But when i got bsods when Dv was on they were the same 3 crashes.
plus when driver verifier was on my computer would sometimes boot saying that windows didnt boot correctly
So I think i might have to tick that off the list of fixes.
Please upload the BSOD Posting instructions BSOD - Posting Instructions - Windows 10 Forums. Upload them here. This will tell you how Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.
Loiez, I am going to ask for someone else to look at your dumps. This is the best I could get. Are you running Raid, or is your sata controller set to Raid in BIOS?
Code:Use !analyze -v to get detailed debugging information. BugCheck D1, {2, 2, 0, fffff8010af52523} Probably caused by : storport.sys ( storport!RaidUnitCompleteRequest+a3 ) Followup: MachineOwner FAILURE_BUCKET_ID: AV_storport!RaidUnitCompleteRequest BUCKET_ID: AV_storport!RaidUnitCompleteRequest ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:av_storport!raidunitcompleterequest fffff802`7dbdb468 fffff801`0fe938f1Unable to load image nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys nvlddmkm+0x1a38f1