View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014544 | MMW v4 | Other | public | 2017-11-15 00:40 | 2018-01-02 13:13 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | block | Reproducibility | unable to reproduce |
| Status | feedback | Resolution | not fixable | ||
| Product Version | 4.1.19 | ||||
| Summary | 0014544: BSOD in 4.1.19 with Fall Creators update | ||||
| Description | Log is attached. At least twice it seemed to happen while scanning was happening. | ||||
| Additional Information | MEZ-785-90687, DRD-914-30877 | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | |||||
|
|
Martin, in the MEZ-785-90687 user indicated that this happens on Windows 7 too (since the last MM update), so it could mean that it is rather caused by MM update (and not system/driver update) ?? Could you please download and install this previous version from here http://www.mediamonkey.com/sw/MediaMonkey_4.1.17.1840_Debug.exe and try whether the BSOD still appears? From your log it looks that the last operations were access of file \\LOWLANDER03\Multimedia\Temp\Music\Rip\Various Artists\Putumayo Presents- Bluegrass\05. Frank Solivan - Across The Great Divide.flac Could you try whether it is related to access of this particular network drive (or file(s)) or whether the BSOD is rather random and not related to particular network location? |
|
|
FYI: User from MEZ-785-90687 updated to Win10 meanwhile and is no longer seeing BSOD |
|
|
The user from DRD-914-30877 experienced BSOD in tcpip.sys (is a network driver). So disabling UPnP.dll was the workaround for him. We could probably add a KB article about workarounds for the individual BSOD failures? Assigned to Peke to add/update the KB. |
|
|
The same kind of issue experienced in VRX-389-54435 There was no change in UPnP.dll for quite a long time so I doubt that it is related to MM update (as confirmed by users). Based on the BSOD kind (in tcpip.sys network driver): 1) It could be caused by Antivirus software (AVG, Malwarebytes), see: https://answers.microsoft.com/en-us/windows/forum/windows_8-performance/driverirqlnotlessorequal-tcpipsys-blue-screen/a7e6a346-4b7d-41da-a9f8-d8a22f3ea7d9?auth=1 - for the user in question uninstalling Malwarebytes did the trick. Check which AV SW you are using, try to temporarily uninstall it or stop it to see whether it helps. 2) Here: https://www.eightforums.com/bsod-crashes-debugging/53739-random-bsods-driver_irql_not_less_or_equal-tcpip-sys.html network drivers and Windows updates helped. Also this one could help: https://www.youtube.com/watch?v=Rs-wPdUn5d4 or this one http://www.tomshardware.co.uk/answers/id-2577825/bsod-tcpip-sys-driver-irql-equal.html |
|
|
According to Peke another is ZHT-696-39117 Peke, please try to communicate and find out with the affected users (ZHT-696-39117, VRX-389-54435, DRD-914-30877) which from BSOD fixes noted above works so that we can compile the KB article. |
|
|
SUM of past few weeks of tests: Several users reported BSODs and I had remote sessions with some. During Remote sessions renaming of UPnP.dll fixed the problem. NOTE that even DLNA Browser https://www.microsoft.com/en-us/store/p/dlna-browser/9nblggh4vb98 or KODI or PLEX created BSODs. Due the BSOD nature it was really hard to determine what exactly caused the issue, but updating all the drivers (both network and GPU along with windows updates fixed the problem) Usually solution is to try all solutions and see which worked. I also tested many 4.x versions in portable mode to see if I can locate which version started to get BSOD but all were affected on those systems. |
|
|
OK, so assigned to Peke to compile KB article based on the above info. |
