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

POD HD 500X blue screen of death issue!


tomerd
 Share

Recommended Posts

Hi Guys,

 

I bought my new POD HD 500X about a week ago, and since then i encountered a blue screen issue which happened twice already.

The issue occurs while plugging out the POD USB cable from my computer.

This makes me very nerves since the main reason i bought the POD HD 500X is for recording and mostly using it with my PC..also i'm worried those errors are causing damage to my PC.

 

Here is the error i got from the blue screen (shared from blue screen viewer): 

 

==================================================
Dump File         : 012515-18158-01.dmp
Crash Time        : 1/25/2015 10:21:09 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff800`02ed415e
Parameter 3       : fffff880`0dd7dcb0
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+76e80
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18700 (win7sp1_gdr.141211-1742)
Processor         : x64
Crash Address     : ntoskrnl.exe+76e80
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\012515-18158-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 321,248
Dump File Time    : 1/25/2015 10:22:37 PM
==================================================
 
Here is my computer (desktop) settings:
 
windows 7 64 bit 
Intel Core i5 4690 3.5Ghz 6MB L3 Cache s1150
Asus H97M-PLUS
G.Skill Ares 2x4GB DDR3 1600Mhz 
Asus GTX750
Western Digital Caviar Blue 1TB 64MB 7200RPM Sata III
 
I tried asking line 6 support but they didn't respond..please if you know what's causing this and how to solve this issue let me know, Thank you. 
 
 
Link to comment
Share on other sites

What hurghanico said. I've found a way to deliberately cause a blue screen if I turn off the pod while Reaper is still open and using the pod ASIO driver. However, there is a setting within Reaper that fixes this. Unfortunately, I can't recall the setting, but was likely something under audio or audio/device in preferences. Other programs might have similar settings.

 

What was your system doing when it crashed?

  • Upvote 1
Link to comment
Share on other sites

What hurghanico said. I've found a way to deliberately cause a blue screen if I turn off the pod while Reaper is still open and using the pod ASIO driver. However, there is a setting within Reaper that fixes this. Unfortunately, I can't recall the setting, but was likely something under audio or audio/device in preferences. Other programs might have similar settings.

 

What was your system doing when it crashed?

 

Can you please try to find the setting? I use POD with Reaper as well. I'd like to know.

Link to comment
Share on other sites

I just tried looking for that setting, but no luck. My system doesn't bluescreen when I shut the pod off but hard locks after about 10 seconds of the pod being off.

 

When I got this to work it was quite some time ago, about a year. A lot of things are different now; the version of Reaper and the entire computer hardware, plus whatever updates for the OS (windows 7 64-bit) were released. The pod driver version was probably different too.

Link to comment
Share on other sites

Hi guys,

 

I understand what you are saying about not plugging out the POD when other programs are active, but i'm pretty sure that this wasn't the case when the blue screen occurred.

I wasn't working with a DAW for sure...not cubase not media player..nothing which i can remember...

I just updated the POD drivers..closed the pod HD edit program, and disconnected it from my computer and then it happened...

It happened twice already and in both cases i didn't had other programs active.

 

Is there a way to check if some programs are using the POD HD before disconnecting it?  

I'm starting to think that maybe the POD is having some issues with other drivers in my computer but i'm not sure....

Link to comment
Share on other sites

You could also try a different USB port.

 

Not to be too much of a downer, but this sort of behavior sounds like a hardware issue. Could be the pod or something with the computer. To be sure it's not the pod, if you have access to another computer, see if works on that.

Link to comment
Share on other sites

while the POD is connected to the PC open the windows sound control panel and check if the POD is set as the main audio interface..

 

another thing you could check is if your antivirus and/or other security programs are interfering with the POD driver, sometimes happened..

 

 

Now that i think of it, another strange thing which happened was that after i rebooted my computer (when i got the blue screen), my antivirus (Microsoft security essentials) was turned off and showed me that my computer is at risk...so maybe it really has to do with my antivirus....is there a way i can check if my antivirus is interfering with the pod driver??

 

 

You could also try a different USB port.

 

Not to be too much of a downer, but this sort of behavior sounds like a hardware issue. Could be the pod or something with the computer. To be sure it's not the pod, if you have access to another computer, see if works on that.

 

I tried another USB port..it happened on the 2 of them...i can see why you are thinking it's a hardware problem with my computer but it's a new computer and it only happened to me while using the POD so i'm not sure if that's the case...

 

Thanks for your help guys!

Link to comment
Share on other sites

I had the BSOD issue with HD500 connected to my old PC a couple of years ago. Contacted Line 6 support, but no luck. I switched to third-party ASIO driver (ASIO4ALL) and that helped. The same HD500 works with my new PC fine with original driver.

 

It's really bad that Line 6 haven't fixed the issue :(

Link to comment
Share on other sites

Another thought. When you run Line 6 Monkey, does it identify your device correctly?

 

It didn't identified my POD..i had to choose manually - POD HD 5OOX..then i downloaded all the drivers and utilities...

Another strange thing which happened is that a few days ago i plugged in my POD and my computer didn't recognized it...i went to line 6 monkey and had to download the driver again...and then it worked, and once i plugged out the POD i got the blue screen again...

Link to comment
Share on other sites

So at some point it sounds like the drivers do install correctly, and Line 6 Monkey shows no errors? There's green checkmarks by everything? And there's a number listed after ESN: on the left side?

 

Only other thing I can think of is trying a different cable if you have one.

 

And seeing as how you just bought the unit, hopefully you can at least do an exchange with the retailer?

Link to comment
Share on other sites

tomerd,

 

          That is a driver stack error. Normally, I would say make sure that the chipset drivers for your motherboard are up to date(ie. for usb,firewire,video, anything that is on-board) but the biggest culprit is usually the video driver. You can double-check the error here:

 

https://social.technet.microsoft.com

 

Just make sure that all your chipset drivers are up to date, as well as any applicable service packs that Microsoft has made available.

 

 

Sonny

Link to comment
Share on other sites

  • 2 years later...

I have been suffering from same problem for a while now and for me using only line 6 pod HD 500 as my main sound card worked

Steps : 1:goto playback devices

2: set line 6 device as default

playback device

3: setup the quality to 24 bit

48000 hz

4:in DAW setup same bit rate, in

my case 96khz worked inside

DAW(ableton).

-Note: do not connect any other audio hardware to your computer's bus.

-buffer sizes I setup are extra small and 128 bits.

- my PC configuration is Lenovo ideapad laptop with i7 quad-core 8 gigs of ram.

Hope it works for you guys. Keep on rockin'.

Link to comment
Share on other sites

  • 1 year later...
  • 1 year later...

i have a similar issue, each time I try using my pod it keeps crashing my laptop. I uninstalled all windows viruses and uninstalled Nvidia experience but, it keeps crashing. 

i double checked that my drivers are on to date. I tried everything but it just keeps crashing my laptop.

 

im using a pod hd pro x 

 

 

Link to comment
Share on other sites

  • 7 months later...

so Ive been haveing a similar problem as well. i figured i was getting crashes because the software in question, pod hd pro x edit, was still open when turning off my hd pro x rack unit. every time i would get the bsod. well i fixed that buy making sure whether in a daw, pod hd x edit, asio.....anything that may be linked in anyway is shut down first. so basically close out all software first then shut down your unit. this worked for about a day. uugghh. next issue. while using pod hd x edit just making and testing out new patches Ive found it likes to crash to the bsod when it has to think hard. so basically when sending and receiving large amounts of data it crashes. i may be wrong but this seems to be whats happening. or, its just that the software doesn't detect the unit during large data transfers long enough that it crashes. who knows. i made sure, and do this before every session, that all  drivers and software are "UP TO DATE!" ALWAYS. Ive been doing this long enough to know that even something like a product manager can cause issues so Ive made it a habit to update when i fire up my PC. my only solution and advice is don't use it with your main rig. i have a laptop i don't care about and loaded pod hd x edit on that and do all my editing there. for recording i run an out right into my rme interface and good enough for me. im not going to destroy a 3000$ pc for a line 6 toy. Ive had axefx 2 units that totally out preform line 6. but, the line 6 in my option, other then this issue of bsod, has been easier to get the sounds i want with less of the bs. and for me, it nails what im looking for faster and better. just don't connect it to your computer, and that sucks! i put in a support ticket but it sounds like ill be ignored as i have in the past. is line six not interested in happy customers?

Link to comment
Share on other sites

I'm guessing that you are using Windows 10. What build number is it? Are you using both a midi foot controller like the FBV Mark II shortboard and Edit at the same time? Do you always plug the pod HD into the same usb port every time or does it share that port with any other device. Like unplugging the pod so that you can plug another audio device or thumb drive, etc.? Is it connected to an external hub? Do you plug it into a usb port on the front or the back of the computer? Are you using the USB cable that came with the pod or are you using a new/different one? Are you using an usb extension cable? Do you make constant changes to patches in Edit, and save each one as you make them, or do you wait to save them to the pod after several changes?

 

The entire eeprom on any Line6 device, anyone's fx/amp modelers, actual code and saved settings is smaller in file size than most office word documents. So, I doubt that plays any role. However, all in the the first paragraph above are  quite capable of causing all of your problems.

 

Best of luck and I hope that you find your answer,

-mus1prod

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...