Windows 7 Random BSOD W7Hx64 when playing videos (DSPlayer/madVR/ffdshow/avisynth)

djoole

New Member
Joined
Jan 30, 2016
Messages
22
Hi,

My HTPC is exclusively used to watch videos, using Kodi DSPlayer + directshow filters.

I was on Seven and never had a BSOD problem.
I upgraded to W10 (clean install), and since then, randomly, but often, when I watch a video, BSODs occur.

I could relate it to the use of ffdshow, itself using avisynth.

If I deactivate ffdshow in DSPlayer, no more BSODs.

I have yet to figure out if it's related to avisynth only (need to deactivate it in ffdshow and let ffdshow activated).

Avisynth is used to upscale the video in order to work enhancement filters in higher resolution in order to have best image quality.


As BSODs stop when i deactivate the use of ffdshow/avisynth, I figured the problem was related to the GPU, maybe the GPU RAM being extensively used.
But the wierd thing is I didn't have any BSOD on W7, with same setup.

Here are the dumps, with the last BSOD of today (IRQ NOT LESS OR EQUAL).

I used DDU to clean the system, and reinstall latest nvidia drivers (361.63)

I hope you can help me sort it out!



I've just noticed there were new drivers (361.75), I'll use DDU again and try them out and let you know if I get new BSODs.
 


Attachments

Solution
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {100000028, 2, 0, fffff80175174964}

*** WARNING: Unable to verify timestamp for e1c65x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c65x64.sys
Probably caused by : NETIO.SYS ( NETIO!RtlCopyMdlToMdlIndirect+214 )

Followup: MachineOwner
...
How old is the system? I wonder if age might have anything to do with it? If you really want to do some testing rather than waiting then you could try setting the overclock again and then running something like Prime95 to stress test the system.
This will let you know if it's stable or not.

I'd run the test for about an hour, monitoring temps as you go.
GIMPS - Free Prime95 software downloads - PrimeNet

Temp monitoring
HWiNFO, HWiNFO32/64 - Download

Oh and post any new dump files please.
 


System was built in April 2013, not that old.
I'll wait for any crash/BSOD without the OC :-)
It would be so nice if it was the cause.
Moreover I don't really need the extra cpu power anymore, it's a remnant of my PC gaming days (over now, thanks to the PS4 :) )
 


Thanks for the update. I'll await your next post and hope all goes well.. :)
 


Back
Top