Windows 10: driver_verifier_iomanager_violation BSOD loop on startup

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

Attachment 57242

Doesn't look like RAM is the problem. Zero errors.

 

Please upload a new zip from the dm log collector.
The next step would be to use driver verifier if I cannot find anything in the new logs.

Warning Please 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.

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.



Note Your 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.

 

Attachment 57289

File attached.

 

According to the logs, no bluescreen has occured after 1th of januari

 

Strange because I definitely received multiple ones. I checked the event log on my computer before it BSOD and I noticed hundreds of Error: 10005 in a short period of time but I think they are also in the log you checked. Also noticed something about bad blocks. I did a chkdsk in CMD prompt and noticed it got a few errors. My SSD always passed every other test though like SMART. It's a Kingston v300 and I updated the firmware around the 17th or so and it didn't really help fix the issue. So it seems to either be the SSD or a driver still.

 

This comes up indeed many times straight after each other.
Code: Event[14005]: Log Name: System Source: disk Date: 2016-01-04T00:49:15.603 Event ID: 7 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Daniel-PC Description: The device, \Device\Harddisk0\DR0, has a bad block.[/quote] HDTune might be able to detect more.





Diagnostics Test

HDD TEST


Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

I will do that when I wake up. I did also notice in the event viewer that crashes seemed to come up after Windows Updates. I noticed it recently failed to install an update twice. I went ahead and deferred it from updating anymore. Things have been stable for 6 hours or so but that doesn't mean anything. Keeping a close eye on the event viewer. Did notice more bad block errors showing up.

 

Attachment 57547Attachment 57548Attachment 57549Attachment 57550Attachment 57551

It couldn't even do the benchmark for 30 seconds without getting a "Read Error/Test Aborted!"

 

Backup everything on the SSD

If you still have warranty, check it for this case.
If it falls under warranty, RMA and replace it, if not or no warranty anymore just replace it.

 

And my initial fear has been realized. The OS and programs are just about the only thing on it. All documents are on different drives. I have a few questions below about the process.

What I'm worried about is will Windows 10 still activate if I clean install it on a new SSD? I've heard that UEFI retains the key or something.

When I did a backup of it to my external a few days ago it gave me bad block errors at the tail end but still seemed to copy most. So would I just clean install or restore that to a new SSD?

Also, are the bad block errors that show up in the windows event viewer new bad blocks or just the fact it ran in to a bad block? I'm guessing .5 percent of the SSD having bad blocks is a lot, especially in only 2 years time. I thought the controller took care of those but I guess the number of bad blocks is growing faster than normal?

 

Depending on how you have made the backup you could restore it.
If it was a copy/paste, then you can't, if you have used a program then you can.

When Windows boots up, it checks if the system is fine.
At boot it noticed the bad blocks, this means that I can't say when the bad blocks occured.

 

So I've replaced the drive with a newer and larger SSD. It's now hanging after awhile and giving me the same blue screen. Since my last post, my computer had been working for weeks without any blue screens. I figured I should get a new SSD anyway and RMA the old one. But it looks like it's still giving issues. I had issues trying to cloning and backing up an image. It blue screened trying to backup an image. Cloning was successful but it looks like there could be residual effects from the old drive? Powering off for awhile and booting allowed me to login and benchmark but if I opened more tabs in a browser or whatever, it would start slowly hanging everything. My new SSD (Micron M500) had zero errors and could actually get through a benchmark unlike the old Kingston one. So I have a feeling I'm going to have to do a complete clean install. Your thoughts?

EDIT: I managed to pull a few dumps it left behind before it froze for good.
Attachment 61847

 

Are you using the same cable?

 

I saw that other thread and changed cables but I get the same results.