Jump to content
Matinister

POD HD500X BSOD when using DAW

Recommended Posts

Hello, fellows. I bought my POD HD500X like a week ago and as the normal procedures I downloaded line 6 monkey, and installed everything from it to the date also ASIO4ALL. I didn't have any trouble until I started to use DAWs. When I was using and recording with Adobe Audition I got blue screen of death(BSOD) several times and with different errors. Checked all the drivers, and they all were updated.I decided to format my computer and start from cero. So, once again installed everything (all drivers updated incluiding pod's). Decided to give Adobe Audition another chance (I thought the problem was in this DAW), guess what: BSOD again when recording using the POD as interface. Well, tired of that error, I downloaded FL Studio and when recording: BOOM, BSOD once again, at this point I was really tired of those problems, so I gave one more chance to FL. I was working fine with it, recorded several tracks and stuff but I got the BSOD again when I was switching presets with the footswitch of the pod. So im thinking: Is my POD broken by fabric or something?¿Is there any solution to this BSOD problem?

I bought this for recording purposes only and having all these problems is making me want to give it back to the store. Also, my computer description: Windows 10, Intelcore i7,16gb ram, Nvidia gtx 950m.

 

Share this post


Link to post
Share on other sites

Why are you using ASIO4ALL? If you're using the POD as Audio Interface, use the POD drivers. In fact, just about any AI will have it's own drivers. ASIO4ALL dates from a time when vendor drivers were sometimes flakey. Problem was, it was even flakier. Dump ASIO4ALL, load the POD drivers, you should be good to go.

 

You didn't mention if your computer is a laptop or desktop, but since flakey video drivers are a very common cause of BSOD, I ran a search on your Nvidia and found this, among others:

 

http://www.tomsguide.com/answers/id-3172231/bsod-nvidia-gtx-950m-driver-power-state-failure.html

 

The other most common cause for BSOD besides flakey drivers is faulty memory. If all else fails, DL Memtest86 and run it for at least 12 hours.

  • Upvote 1

Share this post


Link to post
Share on other sites

Why are you using ASIO4ALL? If you're using the POD as Audio Interface, use the POD drivers. In fact, just about any AI will have it's own drivers. ASIO4ALL dates from a time when vendor drivers were sometimes flakey. Problem was, it was even flakier. Dump ASIO4ALL, load the POD drivers, you should be good to go.

 

You didn't mention if your computer is a laptop or desktop, but since flakey video drivers are a very common cause of BSOD, I ran a search on your Nvidia and found this, among others:

 

http://www.tomsguide.com/answers/id-3172231/bsod-nvidia-gtx-950m-driver-power-state-failure.html

 

The other most common cause for BSOD besides flakey drivers is faulty memory. If all else fails, DL Memtest86 and run it for at least 12 hours.

Well, the 1st time I got the error was when not using asio at all. Now I uninstalled it and still have BSOD, also checked how to solve by the Nvidia solution and nothing happens. My bad; its a laptop. 

Share this post


Link to post
Share on other sites

Did you run memtest86 for at least 12 hours?

There were LOTS of threads on the Nvidia problems. Keep searching. Unfortunately, random BSODs are really tough to track down. Taking it to a shop could cost more than it's worth. Best to eliminate as many of the most common problems as you can first.

Share this post


Link to post
Share on other sites

I have the same problem as you. I have an xps 8900 i7 16gig and nothing does. There is always a bsod. If I look right, I suspect line 6 it's the cause. The latest drivers date back to 2015. Say they still sell their product: scam.

I have the same problem as you. I have an xps 8900 i7 16gig and nothing does. There is always a bsod. If I look right, I suspect it's the cause. The latest drivers date back to 2015. Say they still sell their product: scam.

Share this post


Link to post
Share on other sites

First, words have meanings. "Scam" does not mean what you think it does.

Second, since thousands of people use this product without issue, could it possibly be a problem with YOUR computer, in connection with which please see my previous post concerning video drivers and memory.

 

It would be nice if OP posted back on his progress/solution.....

Share this post


Link to post
Share on other sites

I have the same problem as you. I have an xps 8900 i7 16gig and nothing does. There is always a bsod. If I look right, I suspect line 6 it's the cause. The latest drivers date back to 2015. Say they still sell their product: scam.

I have the same problem as you. I have an xps 8900 i7 16gig and nothing does. There is always a bsod. If I look right, I suspect it's the cause. The latest drivers date back to 2015. Say they still sell their product: scam.

 

I use my 500X to record directly to Audacity, Reason, Ableton, and ProTools and I've never had a single problem..  Must definitely mean that Line 6 has produced a faulty driver..  

Share this post


Link to post
Share on other sites

I'm getting BSOD also when using reason. It started when I had to replace my computer. So I bought an Alienware Aurora r7 BSOD when using Reason 10. Now I'm using a iBUYPOWER - Desktop - Intel Core i7 8700K - 16GB Memory - NVIDIA GeForce GTX 1080 Ti - 120GB Solid State Drive + 1TB Hard Drive - . Same thing BSOD!!

Share this post


Link to post
Share on other sites
17 hours ago, highlander65 said:

I'm getting BSOD also when using reason. It started when I had to replace my computer. So I bought an Alienware Aurora r7 BSOD when using Reason 10. Now I'm using a iBUYPOWER - Desktop - Intel Core i7 8700K - 16GB Memory - NVIDIA GeForce GTX 1080 Ti - 120GB Solid State Drive + 1TB Hard Drive - . Same thing BSOD!!

 

Have you tried my previous suggestions concerning memory and video drivers? I assume that you're on Windows10. Is it fully updated? Have you optimized your system for audio use? Are you running anti-virus sw? Wireless? Disable all that stuff when using Reason (latest version?), that's PART of optimizing your system. Power plan set for high performance? All USB hubs set to NOT allow sleep mode (in device manager)? GOOGLE windows10 optimization for audio. Most AI sites (Steinberg, Focusrite, others) have a section on doing that.

 

Also, although running memory tests for 12-24 hours is a drag, you can't discount bad memory just because the system is new.

Share this post


Link to post
Share on other sites

BSOD are caused by drivers since they have direct access to hardware.  ASIO4ALL is not required and is probably causing the issue.  The problem now is making sure you get it removed completely and make sure you do a Cold Start.  Meaning do a Shutdown until everything is completely off then start the computer.  Logging out or even a restart on a laptop may not be enough.

 

Memory issues could be causing it but isn't nearly as likely as some remnant of the wrong driver still being loaded.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×