On Fri 28-Aug-20 12:23:13 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\082820-49578-01.dmp
This was probably caused by the following module: l6podhd564.sys (0xFFFFF8037EEE2FBE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8037EEE2FBE, 0xFFFFD80A8638A900, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\l6podhd564.sys
product: GuitarPort
company: Line 6
description: GuitarPort WDM Audio Device Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: l6podhd564.sys (GuitarPort WDM Audio Device Driver, Line 6).
Google query: l6podhd564.sys Line 6 SYSTEM_SERVICE_EXCEPTION
On Fri 28-Aug-20 12:23:13 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: stream.sys (STREAM+0x1F61)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8037EEE2FBE, 0xFFFFD80A8638A900, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\stream.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: WDM CODEC Class Device Driver 2.0
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 28-Aug-20 11:41:45 AM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\082820-67500-01.dmp
This was probably caused by the following module: ucx01000.sys (0xFFFFF8035D6D5C93)
Bugcheck code: 0x10D (0x4, 0x0, 0xFFFFF8035D6D5C93, 0xFFFF9E0CB62C0DB0)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\ucx01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Controller Extension
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 27-Aug-20 11:09:13 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\082720-63328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0xFFFF8705DEC6E022, 0x2, 0x0, 0xFFFFF80275EAABF2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 04-Jul-20 2:53:16 PM your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\070420-58296-01.dmp
This was probably caused by the following module: ucx01000.sys (0xFFFFF8003DAD5736)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8003DAD5736, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ucx01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Controller Extension
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\082720-54031-01.dmp
BSOD - IRQL and L6PODHD564.sys Error
in Computer Audio Setup and Troubleshooting
Posted
Hello!
My setup:
POD HD 500 and Dell Inspiron 15 500 i7 8GBRAM
Drivers:
The most recently drivers by Monkey Line 6.
Problem:
The problem always happen when I connect my POD on my computer. After a few minutes the BSOD comes and the errors are the following:
Stop code: IRQL_NOT_OR_EQUAL or
Stop code: SYSTEM_SERVICE_EXCEPTION - What failed: L6PODHD564.sys
I run a program to see more information (Log at the bottom).
My attempts:
-Restart the system.
-Uninstall and reinstall all drivers.
-Update the firmware of POD HD 500
-Remove all USB connections and keep only the POD HD
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Fri 28-Aug-20 12:23:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082820-49578-01.dmp
This was probably caused by the following module: l6podhd564.sys (0xFFFFF8037EEE2FBE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8037EEE2FBE, 0xFFFFD80A8638A900, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\l6podhd564.sys
product: GuitarPort
company: Line 6
description: GuitarPort WDM Audio Device Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: l6podhd564.sys (GuitarPort WDM Audio Device Driver, Line 6).
Google query: l6podhd564.sys Line 6 SYSTEM_SERVICE_EXCEPTION
On Fri 28-Aug-20 12:23:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: stream.sys (STREAM+0x1F61)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8037EEE2FBE, 0xFFFFD80A8638A900, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\stream.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: WDM CODEC Class Device Driver 2.0
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 28-Aug-20 11:41:45 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082820-67500-01.dmp
This was probably caused by the following module: ucx01000.sys (0xFFFFF8035D6D5C93)
Bugcheck code: 0x10D (0x4, 0x0, 0xFFFFF8035D6D5C93, 0xFFFF9E0CB62C0DB0)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\ucx01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Controller Extension
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 27-Aug-20 11:09:13 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082720-63328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C23C0)
Bugcheck code: 0xA (0xFFFF8705DEC6E022, 0x2, 0x0, 0xFFFFF80275EAABF2)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 04-Jul-20 2:53:16 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\070420-58296-01.dmp
This was probably caused by the following module: ucx01000.sys (0xFFFFF8003DAD5736)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8003DAD5736, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ucx01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB Controller Extension
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\082720-54031-01.dmp