Need a Debugging read

manolz said:

Thanks,

I'm assuming Driver Verifier turns itself off after a reboot? I made my way back into verifier and can't see an option to stop the service. I'll leave things how they are and post back if I come across another BSOD. Thanks again

You said you used system restore to go back, right? That probably restored it back to before you turned verifier on. It also would have removed any driver updates you have done between when you made the restore point and when you restored.

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

manolz said:

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

Ah, guess I misunderstood. Odd that it was turned off when you came back, though. I haven't used Verifier much myself, and never got it to BSOD when I did, so I turned it off after 36 hours manually.

manolz said:

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

It cant ake as much as 36 continuous hours to make it crash.

zigzag3143 said:

manolz said:

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

It cant ake as much as 36 continuous hours to make it crash.

Okay good to know.

Thanks again !

manolz said:

zigzag3143 said:

manolz said:

I made a system restore point right before my first driver verifier and forced BSOD. Then I googled my error message and attached my mini-dump file. I came across a similiar case with the same error message so I removed the Elaborate Bytes software, installed MSE and ran a quick scan & also updated Realtek Drivers.

Then I turned verifier on again to see if I would crash at the same point but It didn't.

It cant ake as much as 36 continuous hours to make it crash.

Okay good to know.

Thanks again !

My pleasure and let us know if you need help.

If it doesnt crash in that time period we can make it crash.

New minidump.

manolz said:

New minidump.

Your bsod was caused by trixx.sys; please remove all trixx software for further testing.

writhziden said:

manolz said:

New minidump.

Your bsod was caused by trixx.sys; please remove all trixx software for further testing.

Might want to mention that they were driver verified.

zigzag3143 said:

Might want to mention that they were driver verified.

Aye... I suppose it is up to the OP to continue testing with driver verifier running after uninstalling the offending driver. I think it might be safe at this point to disable verifier and run normally and not remove trixx software.

Thanks zigzag3143. I assumed the verifier was intentional, but after reading over the previous posts again, now I see your point.