Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'crashing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • FBV Controllers (MKII / 3)
    • M5
  • Amplifiers
    • Powercab
    • Catalyst
    • Spider V
  • POD
    • POD Go
    • Pocket POD
    • POD Express
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay/XD-V Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

Found 12 results

  1. Hello After updating my iPhone 8 plus to the latest iOS 13.1.2, I'm having problems with the Firehawk remote app. Everything is OK except when I try to edit the Variax model using the app, it crashes all the time. I can still use every other functionality and the pedal works fine, changing models to and from magnetic pickups to Variax models, I just can't edit it on the Remote app. I have another older phone and it works fine there, so must be the latest iOS update. Anyone else experienced this and has a solution?
  2. I installed a trail version of Helix Native 1.91 about 10 days ago and it worked up to now, but since today the plugin does not open and Logic gets stuck - so I have to Force Quite the application. In a thread it was suggested to delete the installation files and reinstall - it did it several times without success. The internet connection is fine, as I also downloaded the installation file and checked the MD5 hash. I also tried with another DAW (tracktion), but same behaviour. What I deleted before reinstallation: /Library/Application Support/Avid/Audio/Plug-Ins/Line 6 /Library/Audio/Plug-Ins/Components/Helix Native.component /Library/Audio/Plug-Ins/VST/Line 6 (did not exist) /Library/Audio/Plug-Ins/VST3/Line 6/* /Library/Application Support/Line 6/*
  3. My Spider V Remote program on my windows 10 PC keeps crashing whenever I change the presets. This particularly happens the most when i mess with the cabinet settings for some reason, but it occasionally happens when I change the other settings as well. I've factory reset and updated my amp but this hasn't solved the problem. The message that comes up is "Spider V is not responding". I've also tried running the program in administrator mode and in windows 8 compatibility mode. Help would be appreciated.
  4. I am getting constant crashes when running Cubase 9 on a brand new Windows 10 HP Pavillion laptop (Intel i7, 8GB RAM) The Line 6 is the default audio driver, I've disabled the webcam, other sound cards, tried removing anti virus software and manually gone through and updated all my drivers. The fault is mostly BAD POOL HEADER and the crash log is saying the the LINE6PODHDPROSE.sys driver is to blame. Running Cubase with the standard audio drivers is fine, running any program other than Cubase is fine. I'm not the most computer literate guy in the world, but I've searched Google and countless forums and followed all their advice and the problem is still occuring. Do Line 6 need to add an update for these drivers to stop this happening? Couple of logs for your perusal: On Fri 13/01/2017 00:25:52 your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: l6podhdprose64.sys (L6PODHDPROSE64+0x6FBC7) Bugcheck code: 0xD1 (0xFFFF860F3A663000, 0x2, 0x1, 0xFFFFF803FF46FBC7) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\drivers\l6podhdprose64.sys product: GuitarPort company: Line 6 description: GuitarPort WDM Audio Device Driver Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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: l6podhdprose64.sys (GuitarPort WDM Audio Device Driver, Line 6). Google query: Line 6 DRIVER_IRQL_NOT_LESS_OR_EQUAL (this was the first DRIVER IRQL NOT LESS OR EQUAL error, the rest have been bad pool headers) On Thu 12/01/2017 20:35:15 your computer crashed crash dump file: C:\WINDOWS\Minidump\011217-25937-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0) Bugcheck code: 0x19 (0x21, 0xFFFFCB0B54460000, 0x1800, 0x27101D8527101D83) Error: BAD_POOL_HEADER file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. This problem might also be caused because of overheating (thermal issue). The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
  5. Before i explain the issue wich pisses me of. If there is any idea in the community to fix this...please let me know. Windows System: Fujitsu E Series Laptop, I5 6200U CPU, 32GB RAM, Samsung SSD System Drive, SanDisk SSD Stroage Drive (internal) Windows 10 Build 1909 Mac: MacBook pro 12§ Retina , Late 2013, Intel I5 2,6Ghz, (GB RAM, 512GB SSD, macOS Catalina 10.15.4 Amp is an Spider V120 MKii on Version 2.02 with FVB3 (v1.02.00) It does not Matter on wich of the above Computers i use the Spider V Remote App. After a few changes to a Preset the Software crashes. The stability Problems oruce since i use the FBV3. Before i could edit the Presets as much as i want. Inside Eventlog (Windows) there is an .NET Runtime Error Event ID 1026 Caused by Spider V Remote.exe EventDetails: Protokollname: Application Quelle: .NET Runtime Datum: 23.04.2020 19:53:37 Ereignis-ID: 1026 Aufgabenkategorie:Keine Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: ws-wit-015.wolfit.intern Beschreibung: Anwendung: Spider V Remote.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: System.InvalidCastException bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.ParamControlManager.setParamValue(System.String, System.String, System.Object, Boolean) bei WindowsCommon.EngineInterface.ParamValueServer.processSetParamValue(System.String, System.String, System.Object, Boolean) bei WindowsCommon.EngineInterface.ParamValueServer.setBoolValue(System.String, System.String, Boolean, Boolean) bei EngineCLIWrapper.EngineWrapper.NativeBoolParamValueReceiver(std.basic_string<char,std::char_traits<char>,std::allocator<char> >*, std.basic_string<char,std::char_traits<char>,std::allocator<char> >*, Boolean, Boolean) bei <Module>.APIV3EngineInterface.Functions.setFloatParamValue(APIV3Engine*, std.basic_string<char,std::char_traits<char>,std::allocator<char> >*, std.basic_string<char,std::char_traits<char>,std::allocator<char> >*, Single) bei EngineCLIWrapper.EngineWrapper.setFloatParamValue(System.String, System.String, Single) bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.ParamControlManager.sendValuesToEngine() bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.ParamControlManager.mouseDraggedOnControlWithID(System.String, System.Windows.Point) bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.SingleSlider.onMouseMove(System.Object, System.Windows.Input.MouseEventArgs) bei System.Windows.Input.MouseEventArgs.InvokeEventHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) bei System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) bei System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) bei System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs) bei System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean) bei System.Windows.Input.InputManager.ProcessStagingArea() bei System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs) bei System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport) bei System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) bei System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) bei System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) bei System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) bei System.Windows.Application.RunDispatcher(System.Object) bei System.Windows.Application.RunInternal(System.Windows.Window) bei System.Windows.Application.Run(System.Windows.Window) bei MainApplication.App.Main() Ereignis-XML: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-04-23T17:53:37.749293500Z" /> <EventRecordID>6904</EventRecordID> <Channel>Application</Channel> <Computer>ws-wit-015.wolfit.intern</Computer> <Security /> </System> <EventData> <Data>Anwendung: Spider V Remote.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: System.InvalidCastException bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.ParamControlManager.setParamValue(System.String, System.String, System.Object, Boolean) bei WindowsCommon.EngineInterface.ParamValueServer.processSetParamValue(System.String, System.String, System.Object, Boolean) bei WindowsCommon.EngineInterface.ParamValueServer.setBoolValue(System.String, System.String, Boolean, Boolean) bei EngineCLIWrapper.EngineWrapper.NativeBoolParamValueReceiver(std.basic_string&lt;char,std::char_traits&lt;char&gt;,std::allocator&lt;char&gt; &gt;*, std.basic_string&lt;char,std::char_traits&lt;char&gt;,std::allocator&lt;char&gt; &gt;*, Boolean, Boolean) bei &lt;Module&gt;.APIV3EngineInterface.Functions.setFloatParamValue(APIV3Engine*, std.basic_string&lt;char,std::char_traits&lt;char&gt;,std::allocator&lt;char&gt; &gt;*, std.basic_string&lt;char,std::char_traits&lt;char&gt;,std::allocator&lt;char&gt; &gt;*, Single) bei EngineCLIWrapper.EngineWrapper.setFloatParamValue(System.String, System.String, Single) bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.ParamControlManager.sendValuesToEngine() bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.ParamControlManager.mouseDraggedOnControlWithID(System.String, System.Windows.Point) bei MainApplication.WindowsCommon.Editor.SignalFlowItemEditor.ModelParamEditor.SingleSlider.onMouseMove(System.Object, System.Windows.Input.MouseEventArgs) bei System.Windows.Input.MouseEventArgs.InvokeEventHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) bei System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) bei System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) bei System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs) bei System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean) bei System.Windows.Input.InputManager.ProcessStagingArea() bei System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs) bei System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport) bei System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) bei System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) bei System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) bei System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) bei MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) bei MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) bei System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) bei System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) bei System.Windows.Application.RunDispatcher(System.Object) bei System.Windows.Application.RunInternal(System.Windows.Window) bei System.Windows.Application.Run(System.Windows.Window) bei MainApplication.App.Main() </Data> </EventData> </Event>
  6. Every time I plug in my Helix, i get BSOD. I followed every trouble shooting step I've seen here and when I called, support had no alternatives to give other than the conclusion that the motherboard was not able to support the device. I called ASUS and they gave me a handful of additional troubleshooting steps that were unsuccessful and it ended, after being escalated 3x, with a "Sorry, that device just isn't compatible." I can plug in all my other midi devices. We tried changing legacy USB settings in Bios. Fiddled with the drivers 900 times (uninstalling, installing one at a time etc.) mobo: ROG Strix Z370E Gaming Midi: Line 6 Helix I'm very frustrated as this issue has been going on for ~20 days and I was hoping to use my Helix as my primary source of tones while getting used to my new DAW to force myself to use it more and become more comfortable. For context, I switched to PC after being a 10ish year mac guy because editing in 4k and multitracking was becoming a nightmare on my imac pro and I have a background in IT using windows devices. Many thanks, J
  7. Once I updated my Macbook Pro late 2013 to MacOS Sierra 10.12 the UX2 usb audio interface crashes the computer. Everytime I plug in the ux2 interface, the computer immediately restarts and gives the error message (white text on black background). I have tried both of my Mac's usb slots, tried taking everything off of the interface (monitors etc.) and tried it with and without power cable on my computer. Also, when I try to start my computer while the UX2 is plugged in, the Mac's starting screen has some white error messages and then the computer restarts. Nothing helps. So atm I CAN'T USE THE INTERFACE AT ALL. Pod Farm software doesn't seem to have any problems. Please tell me if you've had these problems or you can help.
  8. Hello, Can't find anyone with this issue on the forums. I am admittedly new at using DAW and plug-ins but I am adept at using computers. I own a Helix and the Helix Native plug-in. I also have purchased a full Pro Tools 12 (12.8.3 to be exact) perpetual lisence. I am using Windows 10. Helix Native 1.01 plug-in works for me in Pro-Tools. However accessing the Helix Native Plugins Mix window under INSERTS A-E > PLUG-IN > INSTRUMENT > HELIX NATIVE (mono) or HELIX NATIVE (mono/stereo) or the corresondong ones appearing in the EFFECTS branch of INSERTS A-E > PLUG-IN causes either Pro Tools to freeze up permanently forcing software reboot, or sometimes even goes as far as asking me to log in to my Line6 account, only to crash Pro Tools and close the window, again forcing software reboot). PC reboot didn't fix the issue. None of these issues existed in Native 1.01, which still works fine for me. By the way, apart for my first start-up of Pro Tools this morning, I am only able to access the Native plug-in by adding an audio- track, going into the mix window and selecting it from the INSERTS A-E menu. This morning I was able to access it from the other intended place, Pro-Tools menu > AudioSuite>Instrument> but now nothing appears there regardless whetehr I am using Native 1.01 or 1.10. FYI, my Native does appear in the proper place. C:\Program Files\Common Files\Avid\Audio\Plug-Ins\Line 6\Helix Native.aaxplugin Can someone explain how to workaround this bug. Meanwhile I'll try installing Pro-Tools and Native on my Laptop to see if I can reproduce the error. Note: I have done all the steps in this post so I know what I am doing. https://line6.com/support/page/kb/_/recording/helix-native/how-to-find-helix-native-in-pro-tools-r867
  9. HX Edit 2.51 crashes on my MacBook Pro 2012 running OS 10.8.5 whenever I turn on my Helix LT. This happened before I upgraded the LT to from firmware 2.30 to 2.50 and after I upgraded to 2.50. For you computer nerds (like me :) ) the crash report states that there was an uncaught exception 'NSInvalidArgumentException'. I was able to run the previous version on HX Edit just fine, and there is nothing stating that OS 10.8 is incompatible with HX Edit 2.51. Does anyone have a fix for this (without just stating to try uprading to a newer OS, please).... Thanks!!! P.S.: I upgraded to firmware 2.5 using Windows 7 on a Bootcamp installation, in case anyone is wondering.
  10. When I have Presonus Studio Live plugged into firewire to my mac I cannot plug in my Helix to the USB. In logic pro. I have Logic audio settings set for the Presonus. Every time I plug in the helix, the helix freezes. I then have to restart my helix with the USB unplugged. I can use either, my Presonus or my Helix. Why can't they just be friends?
  11. Is anyone else experiencing serious performance issues with the Amplifi app? It used to work perfectly, but I started my Amplifi TT up for the first time in a few weeks, and now I cannot get the app working at all. Most of the time, mine crashes while syncing after opening. Sometimes, it completes the sync, connects, then crashes. I have everything updated, reinstalled the app, applied firmware updates, restarted everything, and I'm experiencing the same issues on my iPhone 6s and 4 week old iPad Air 2. Line 6 support have advised that my Amplifi TT could be the fault, but why would an external device connected by bluetooth cause an app to crash completely? Surely crashes indicate a stability issue with the app. Line 6 have also suggested I reinstall the latest iOS update. Before I go through the upheaval of performing a restore on my iPhone, has anyone tried this and fixed the issue? I'm sceptical it would work. I am loath to contact Apple, as they don't provide support for third-party apps; a full restore is probably just what they suggest in the absence of being able to advise on another company's software. All reviews on the app store are from people experiencing this issue, but Line 6 advise that there is currently no scheduled app update.
  12. Hi, Im using LINE 6 POD STUDIO UX2 with my DAW - Reaper. Whenever Reaper crashes, I get the "There was an error while opening your audio hardware: Error initializing ASIO driver" statement. My line 6 UX2 interface cannot be reinitialized in Reaper without reattaching it. But the UX2 interface works fine with all other programs. Is there a way to reinitialize asio for UX2 in Reaper without having to reboot everytime? (I'm running 32 bit windows 7 - I have the same OS on my notebook and the problem does not occur there so the UX2 is not broken). My sample rate is 128 on UX2 and reaper project, but this issue occurs regardless of what sample rate I use. I've searched the forum for solutions to this but haven't found one. I did everything from the sticky topic. It's a bit tiring... Any solutions I am missing??? Thanks
×
×
  • Create New...