Jump to content

Recommended Posts

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. 

  • Upvote 1

Share this post


Link to post
Share on other sites

Hi Just, I have the same problem the past few months, really enoying and dissapoinment, I try everything, just like you. Well, i m just testing the last possilbe solution that I tried and at the moment the BSOD don't came back.

You shoul look this software:  http://www.resplendence.com/whocrashed

 

that really helps cause analize your last crashes and told you what product (software, memory, etc) failed.

Then when you know about the problem you could attack it.
Zorry for my english I m from Perú, hope this could be helpful mafriend.

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 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

Yep. I now just use the POD for guitar modelling, I'm using a Focusrite as my audio interface and the bsod have stopped so its definitely the Line 6.

 

Very disappointing, wont be buying Line 6 again if they sell these faulty products, its as though they're not aware of the problem even though its a very common one.

Share this post


Link to post
Share on other sites

I'm getting similar problems on a brand new Windows 10 HP Pavillion Desktop with Cubase 9.5

 

I have a Line 6 SonicPort VX and Pod X3 Live

 

Windows 10 is on latest version

 

When trying to install drivers for either of the Line 6 devices (using the correct install process in the Driver installer exe), Windows bluescreens with Line 6 Driver error messages

eg

Stop code: DRIVER_VERIFIER_IOMANAGER_VIOLATION

What failed: l6SonicPortVX_AvsFilter.sys

 

I then have to disconnect USB for the reboot and reconnect, sometimes it bluescreens again, sometimes I can run Cubase for a while before reboot.

 

This appears to be a Line 6 problem with the latest Creators update to Win 10  my other USB interfaces are fine.

 

Has anyone found any workarounds and can Line 6 comment on this

Share this post


Link to post
Share on other sites

Well, I'm underwhelmed with the responses

I've fixed the issue now so in case anyone else has the same problem, I disabled verifier.exe in Windows 10 so the line 6 drivers can load a startup.

Not really a solution but a workaround at least

Share this post


Link to post
Share on other sites

I get WIn10 crashes all the time, with the same 'Bad Pool Header' - not even using PodFarm on this computer (I have a Win7 machine that is more stable for music use). Seems ot be an inherent Win 10 problem.

Share this post


Link to post
Share on other sites

Gk001's suggestion of disabling verifier seems to be working for me so far. Not sure how risky it is!

Usually the thing that seems to be most reliable is to make sure your sample rate for your pod matches that what you're using in your project. 44,000hz at 24bit seems to work for me

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

×