- Thread starter
- Moderator
- #4,911
I thought it was v422 so maybe that? I'll also try the newest build that I see you're about to release.
Here we go
Last edited:
I thought it was v422 so maybe that? I'll also try the newest build that I see you're about to release.
England
England
Germany
Got it again, full watchdog logs.
Faulting application name: MediaPortal.exe, version: 1.18.100.0, time stamp: 0x5a53f531 Faulting module name: nvwgf2um.dll, version: 23.21.13.9065, time stamp: 0x5a4d6da2 Exception code: 0xc0000005 Fault offset: 0x0077e825 Faulting process ID: 0x1ae4 Faulting application start time: 0x01d388d4e9156ba7 Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5601d21ccd639df9\nvwgf2um.dll Report ID: 1832230f-d8d6-435f-895f-36ad5c0f908d Faulting package full name: Faulting package-relative application ID:
England
v428 Was/is looking good but did get one Madvr crash durring heavy testing, unable to reproduce so far, crash report and logs are attached. Crash should be nearly at the end of the log.