home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
madVR support in MP1
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="daWooky" data-source="post: 1240078" data-attributes="member: 122090"><p>hey seb, tried v465 bit further on my other systems yesterday.<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p>on good old htpc (1703/358.28) with dx9 fse - all seems nicely running even no strange scalings at starts (maybe its also a bit nv driver or winver related)</p><p>and no old gui´s seen with tv guide and playlist usage...so no faults spotted there <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up (y)" loading="lazy" data-shortname="(y)" /><img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up (y)" loading="lazy" data-shortname="(y)" /></p><p>but before that i experienced quite the opposite on desktop (1709/390.77). bluescreen with a playlist on file change and tv stopping always led immediately to bluescreens.</p><p>so i tried it without madvr display rate change and it ran ok, then with mepo drr- it ran synonymous also ok .. then i've tried it with both madvr setting to switch when fullscreen, it ran longer but also crashed at the tv stop ..</p><p>whocrashed analysis shows that it is not only the graphics driver, norton is also involved in the game...</p><p>[SPOILER="cdanalysis"]<strong>Crash Dump Analysis</strong> </p><p>Crash dump directory: C:\WINDOWS\Minidump</p><p></p><p>Crash dumps are enabled on your computer.</p><p></p><p><strong>On Fri 16.02.2018 18:36:46 your computer crashed</strong></p><p>crash dump file: C:\WINDOWS\Minidump\021618-5875-01.dmp</p><p>This was probably caused by the following module: <a href="http://www.google.com/search?q=symnets.sys" target="_blank">symnets.sys</a> (SYMNETS+0x71110)</p><p>Bugcheck code: 0xFC (0xFFFFAA81D273D260, 0x8A0000025C6008E3, 0xFFFFF80310C090B0, 0x3)</p><p>Error: <a href="http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p>file path: C:\WINDOWS\System32\Drivers\NGCx64\160C000.068\SYMNETS.SYS</p><p>product: <a href="http://www.google.com/search?q=Symantec%20Security%20Drivers" target="_blank">Symantec Security Drivers</a></p><p>company: <a href="http://www.google.com/search?q=Symantec%20Corporation" target="_blank">Symantec Corporation</a></p><p>description: Network Security Driver</p><p>Bug check description: This indicates that an attempt was made to execute non-executable memory.</p><p>This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.</p><p>A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symnets.sys (Network Security Driver, Symantec Corporation).</p><p>Google query: <a href="http://www.google.com/search?q=symnets.sys+Symantec%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">Symantec Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p></p><p></p><p></p><p><strong>On Fri 16.02.2018 18:36:46 your computer crashed</strong></p><p>crash dump file: C:\WINDOWS\memory.dmp</p><p>This was probably caused by the following module: <a href="http://www.google.com/search?q=nvlddmkm.sys" target="_blank">nvlddmkm.sys</a> (nvlddmkm+0x12908)</p><p>Bugcheck code: 0xFC (0xFFFFAA81D273D260, 0x8A0000025C6008E3, 0xFFFFF80310C090B0, 0x3)</p><p>Error: <a href="http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p>file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a39871618b19f06\nvlddmkm.sys</p><p>product: <a href="http://www.google.com/search?q=NVIDIA%20Windows%20Kernel%20Mode%20Driver,%20Version%20390.77" target="_blank">NVIDIA Windows Kernel Mode Driver, Version 390.77 </a></p><p>company: <a href="http://www.google.com/search?q=NVIDIA%20Corporation" target="_blank">NVIDIA Corporation</a></p><p>description: NVIDIA Windows Kernel Mode Driver, Version 390.77</p><p>Bug check description: This indicates that an attempt was made to execute non-executable memory.</p><p>This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.</p><p>A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.77 , NVIDIA Corporation).</p><p>Google query: <a href="http://www.google.com/search?q=nvlddmkm.sys+NVIDIA%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">NVIDIA Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p></p><p></p><p></p><p><strong>On Fri 16.02.2018 17:46:56 your computer crashed</strong></p><p>crash dump file: C:\WINDOWS\Minidump\021618-5781-01.dmp</p><p>This was probably caused by the following module: <a href="http://www.google.com/search?q=idsvia64.sys" target="_blank">idsvia64.sys</a> (IDSvia64+0x89C9B)</p><p>Bugcheck code: 0xFC (0xFFFFD4899AF94260, 0x8A000002884008E3, 0xFFFFF802370E40B0, 0x3)</p><p>Error: <a href="http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p>file path: C:\Program Files\Norton Security with Backup\NortonData\22.9.0.71\Definitions\IPSDefs\20180215.001\IDSvia64.sys</p><p>product: <a href="http://www.google.com/search?q=Symantec%20Intrusion%20Detection" target="_blank">Symantec Intrusion Detection</a></p><p>company: <a href="http://www.google.com/search?q=Symantec%20Corporation" target="_blank">Symantec Corporation</a></p><p>description: IDS Core Driver</p><p>Bug check description: This indicates that an attempt was made to execute non-executable memory.</p><p>This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.</p><p>A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: idsvia64.sys (IDS Core Driver, Symantec Corporation).</p><p>Google query: <a href="http://www.google.com/search?q=idsvia64.sys+Symantec%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">Symantec Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p></p><p></p><p></p><p><strong>On Fri 16.02.2018 15:24:44 your computer crashed</strong></p><p>crash dump file: C:\WINDOWS\Minidump\021618-6421-01.dmp</p><p>This was probably caused by the following module: <a href="http://www.google.com/search?q=ntoskrnl.exe" target="_blank">ntoskrnl.exe</a> (nt+0x175430)</p><p>Bugcheck code: 0xFC (0xFFFFC78B99E53260, 0x8A00000224643863, 0xFFFFF8003D6E40B0, 0x0)</p><p>Error: <a href="http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p>file path: C:\WINDOWS\system32\ntoskrnl.exe</p><p>product: <a href="http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System" target="_blank">Microsoft® Windows® Operating System</a></p><p>company: <a href="http://www.google.com/search?q=Microsoft%20Corporation" target="_blank">Microsoft Corporation</a></p><p>description: NT Kernel & System</p><p>Bug check description: This indicates that an attempt was made to execute non-executable memory.</p><p>This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.</p><p>The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.</p><p></p><p></p><p></p><p><strong>On Fri 16.02.2018 15:20:07 your computer crashed</strong></p><p>crash dump file: C:\WINDOWS\Minidump\021618-5593-01.dmp</p><p>This was probably caused by the following module: <a href="http://www.google.com/search?q=symnets.sys" target="_blank">symnets.sys</a> (SYMNETS+0x71110)</p><p>Bugcheck code: 0xFC (0xFFFF80031F22D0A0, 0x8A0000015FE008E3, 0xFFFFF803874E40B0, 0x3)</p><p>Error: <a href="http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a></p><p>file path: C:\WINDOWS\System32\Drivers\NGCx64\160C000.068\SYMNETS.SYS</p><p>product: <a href="http://www.google.com/search?q=Symantec%20Security%20Drivers" target="_blank">Symantec Security Drivers</a></p><p>company: <a href="http://www.google.com/search?q=Symantec%20Corporation" target="_blank">Symantec Corporation</a></p><p>description: Network Security Driver</p><p>Bug check description: This indicates that an attempt was made to execute non-executable memory.</p><p>This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.</p><p>A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symnets.sys (Network Security Driver, Symantec Corporation).</p><p>Google query: <a href="http://www.google.com/search?q=symnets.sys+Symantec%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY" target="_blank">Symantec Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY</a>[/SPOILER]<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite7" alt=":p" title="Stick Out Tongue :p" loading="lazy" data-shortname=":p" /></p><p>i will see what to do with those errors but somehow it seems its still running a bit unpredictable with fcu <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p></blockquote><p></p>
[QUOTE="daWooky, post: 1240078, member: 122090"] hey seb, tried v465 bit further on my other systems yesterday.:) on good old htpc (1703/358.28) with dx9 fse - all seems nicely running even no strange scalings at starts (maybe its also a bit nv driver or winver related) and no old gui´s seen with tv guide and playlist usage...so no faults spotted there (y)(y) but before that i experienced quite the opposite on desktop (1709/390.77). bluescreen with a playlist on file change and tv stopping always led immediately to bluescreens. so i tried it without madvr display rate change and it ran ok, then with mepo drr- it ran synonymous also ok .. then i've tried it with both madvr setting to switch when fullscreen, it ran longer but also crashed at the tv stop .. whocrashed analysis shows that it is not only the graphics driver, norton is also involved in the game... [SPOILER="cdanalysis"][B]Crash Dump Analysis[/B] Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. [B]On Fri 16.02.2018 18:36:46 your computer crashed[/B] crash dump file: C:\WINDOWS\Minidump\021618-5875-01.dmp This was probably caused by the following module: [URL='http://www.google.com/search?q=symnets.sys']symnets.sys[/URL] (SYMNETS+0x71110) Bugcheck code: 0xFC (0xFFFFAA81D273D260, 0x8A0000025C6008E3, 0xFFFFF80310C090B0, 0x3) Error: [URL='http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] file path: C:\WINDOWS\System32\Drivers\NGCx64\160C000.068\SYMNETS.SYS product: [URL='http://www.google.com/search?q=Symantec%20Security%20Drivers']Symantec Security Drivers[/URL] company: [URL='http://www.google.com/search?q=Symantec%20Corporation']Symantec Corporation[/URL] description: Network Security Driver Bug check description: This indicates that an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symnets.sys (Network Security Driver, Symantec Corporation). Google query: [URL='http://www.google.com/search?q=symnets.sys+Symantec%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']Symantec Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] [B]On Fri 16.02.2018 18:36:46 your computer crashed[/B] crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: [URL='http://www.google.com/search?q=nvlddmkm.sys']nvlddmkm.sys[/URL] (nvlddmkm+0x12908) Bugcheck code: 0xFC (0xFFFFAA81D273D260, 0x8A0000025C6008E3, 0xFFFFF80310C090B0, 0x3) Error: [URL='http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7a39871618b19f06\nvlddmkm.sys product: [URL='http://www.google.com/search?q=NVIDIA%20Windows%20Kernel%20Mode%20Driver,%20Version%20390.77']NVIDIA Windows Kernel Mode Driver, Version 390.77 [/URL] company: [URL='http://www.google.com/search?q=NVIDIA%20Corporation']NVIDIA Corporation[/URL] description: NVIDIA Windows Kernel Mode Driver, Version 390.77 Bug check description: This indicates that an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 390.77 , NVIDIA Corporation). Google query: [URL='http://www.google.com/search?q=nvlddmkm.sys+NVIDIA%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']NVIDIA Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] [B]On Fri 16.02.2018 17:46:56 your computer crashed[/B] crash dump file: C:\WINDOWS\Minidump\021618-5781-01.dmp This was probably caused by the following module: [URL='http://www.google.com/search?q=idsvia64.sys']idsvia64.sys[/URL] (IDSvia64+0x89C9B) Bugcheck code: 0xFC (0xFFFFD4899AF94260, 0x8A000002884008E3, 0xFFFFF802370E40B0, 0x3) Error: [URL='http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] file path: C:\Program Files\Norton Security with Backup\NortonData\22.9.0.71\Definitions\IPSDefs\20180215.001\IDSvia64.sys product: [URL='http://www.google.com/search?q=Symantec%20Intrusion%20Detection']Symantec Intrusion Detection[/URL] company: [URL='http://www.google.com/search?q=Symantec%20Corporation']Symantec Corporation[/URL] description: IDS Core Driver Bug check description: This indicates that an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: idsvia64.sys (IDS Core Driver, Symantec Corporation). Google query: [URL='http://www.google.com/search?q=idsvia64.sys+Symantec%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']Symantec Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] [B]On Fri 16.02.2018 15:24:44 your computer crashed[/B] crash dump file: C:\WINDOWS\Minidump\021618-6421-01.dmp This was probably caused by the following module: [URL='http://www.google.com/search?q=ntoskrnl.exe']ntoskrnl.exe[/URL] (nt+0x175430) Bugcheck code: 0xFC (0xFFFFC78B99E53260, 0x8A00000224643863, 0xFFFFF8003D6E40B0, 0x0) Error: [URL='http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] file path: C:\WINDOWS\system32\ntoskrnl.exe product: [URL='http://www.google.com/search?q=Microsoft%C2%AE%20Windows%C2%AE%20Operating%20System']Microsoft® Windows® Operating System[/URL] company: [URL='http://www.google.com/search?q=Microsoft%20Corporation']Microsoft Corporation[/URL] description: NT Kernel & System Bug check description: This indicates that an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. [B]On Fri 16.02.2018 15:20:07 your computer crashed[/B] crash dump file: C:\WINDOWS\Minidump\021618-5593-01.dmp This was probably caused by the following module: [URL='http://www.google.com/search?q=symnets.sys']symnets.sys[/URL] (SYMNETS+0x71110) Bugcheck code: 0xFC (0xFFFF80031F22D0A0, 0x8A0000015FE008E3, 0xFFFFF803874E40B0, 0x3) Error: [URL='http://www.google.com/search?q=MSDN+bugcheck+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL] file path: C:\WINDOWS\System32\Drivers\NGCx64\160C000.068\SYMNETS.SYS product: [URL='http://www.google.com/search?q=Symantec%20Security%20Drivers']Symantec Security Drivers[/URL] company: [URL='http://www.google.com/search?q=Symantec%20Corporation']Symantec Corporation[/URL] description: Network Security Driver Bug check description: This indicates that an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: symnets.sys (Network Security Driver, Symantec Corporation). Google query: [URL='http://www.google.com/search?q=symnets.sys+Symantec%20Corporation+ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY']Symantec Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY[/URL][/SPOILER]:p i will see what to do with those errors but somehow it seems its still running a bit unpredictable with fcu ;) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
madVR support in MP1
Contact us
RSS
Top
Bottom