"MediaPortal has stopped working" error after adding Ram Drive for Timeshifting (1 Viewer)

[Johncmug]

Yes, it was definitely after 11:35p when I woke up and seen the screen was black.

I use the PowerScheduler plug-in. It is set to the HTPC setting. It puts the pc to sleep after 30 minutes.

When I got up in the morning the error was on the screen. I didn't need to wake the pc up. When I use mediaportal (which is every day) i just press a button on the remote and it "wakes the tv up" to media portal. I could move the mouse or press something on the keyboard.... but typically I am just using the remote to get to the recordings. This wakes up the tv.

 

[mm1352000]

Right.

I've noticed that regular PowerScheduler activity (normally happens every 15 seconds) in the TV Server log files stopped at 4:25 AM. This caused me to go back and look at the Windows application event log, and I noticed something I'd previously missed (sorry!):
[collapse]
"10/18/2017 4:25:18 AM";"Application Error";"Application Crashing Events";"Error";"Faulting application name: MediaPortal.exe, version: 1.17.100.0, time stamp: 0x59a3d8b3 Faulting module name: ntdll.dll, version: 10.0.15063.608, time stamp: 0x802f667e Exception code: 0xc0000005 Fault offset: 0x0005da74 Faulting process id: 0x2c84 Faulting application start time: 0x01d34661124466db Faulting application path: C:\Program Files (x86)\Team MediaPortal\MediaPortal\MediaPortal.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 2e51256d-bf08-476e-99c6-68720203134a Faulting package full name: Faulting package-relative application ID: ";"1000"
"10/18/2017 4:25:19 AM";"Windows Error Reporting";"(0)";"Information";"Fault bucket , type 0 Event Name: FaultTolerantHeap Response: Not available Cab Id: 0 Problem signature: P1: MediaPortal.exe P2: 1.17.100.0 P3: 59A3D8B3 P4: ffffbaad P5: P6: P7: P8: P9: P10: Attached files: \\?\C:\WINDOWS\SERVIC~2\LOCALS~1\AppData\Local\Temp\FTH966B.tmp\fthempty.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER968B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER968A.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER96D9.tmp.txt These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 842c5ba9-84fb-40ca-a0e3-c85cb2a3c258 Report Status: 536870914 Hashed bucket: ";"1001"[/collapse]

So it looks like the real crash happened at that time.
Exception code 0xc0000005 means it was an access violation error - one of the most difficult to get to the bottom of.
Faulting module "ntdll.dll" - a core Windows component - means we have essentially zero additional insight into what went on.


When other people have experienced problems like this and managed - often through sheer luck, unfortunately - to figure out what caused them, it has tended to be something related to drivers.

To me it looks like these errors started for you on September 21.
On September 17 I see you updated the Intel Chipset drivers.
Further, on September 18 I see Windows installed a significant update:
"9/18/2017 6:13:31 PM";"Microsoft-Windows-WindowsUpdateClient";"(1)";"Information";"Installation Successful: Windows successfully installed the following update: 2017-09 Cumulative Update for Windows 10 Version 1703 for x64-based Systems (KB4038788)";"19"

Given that the problem seems to happen every few days (a bit variable), to me it seems entirely plausible that one or both of those updates - or anything similar at around the same date could be the cause. For example, if you installed the RAM driver in that window then you could be right... and the obvious next action would be to try reverting that change (ie. uninstall it).

 

[Johncmug]

Yes, that Windows Update brought the pc down for a few days. I couldn't get it to boot. Eventually I got it to boot but the video and audio drivers were hosed. It took me about a week to get the pc working right.

It could be that it has been giving me that error since the update? But I remember it starting since the Ramdrive.. I could be wrong.

Ironically, that "ntdll.dll" error is the same one I get at work... when I try to run mstsc. I guess it followed me home.

I'll back it up and starting dinking with it again... one driver at a time. Thanks for your help and pointing me in the right direction. I appreciate it.