Driver conflict, how to solve? Logitech G Hub and Line6 Helix LT.

ScothMcBeast · 13 Aug 2020

When I have Logitech G Hub on and I try to use my Line 6 Helix LT I get a BSOD and reboot.
Googling this I found out that there might be a driver conflict causing this.
Not sure how to go about this because no solutions were offered anywhere I could find.

What can I do to make conflicting drivers behave in Win10 64 Pro?

I realize this is probably quite rare issue but is there something to do in general when such a thing comes up? Boot order or something? Any workaround or MacGyverism is welcomed that leads to G hub being up at the same time with Helix and obviously on the one operating system I have.
Any workaround I've come across so far do not include G hub being up but rather "use a cord" or something similar.
I'm not that familiar with modern Windows systems so that I would even know what to google when looking a way to sandbox these two separately in own environments or something.

Thanks for direct ideas or what to go seek.

zbook · 13 Aug 2020

Run V2 and upload results into this thread:
BSOD - Posting Instructions

How to Upload and Post Screenshots and Files at Ten Forums

ScothMcBeast · 14 Aug 2020

zbook said:

Run V2 and upload results into this thread:
BSOD - Posting Instructions

How to Upload and Post Screenshots and Files at Ten Forums

I have no idea what I'm doing but I managed to run some tool that has V2 in it and got a screen crap from the results and posting it now where you pointed.

zbook · 14 Aug 2020

Please upload into this thread.

ScothMcBeast · 14 Aug 2020

DESKTOP-TDRL9FR-(2020-08-14_08-15-39).zip

- - - Updated - - -

I'll add that we are talking about 2 crashes that happened 13 aug between 5-6pm computer time based on dmb file folder.

zbook · 14 Aug 2020

There were multiple missing files.
Please run V2 again > upload results into this thread

Then run the Avast AV uninstall tool then run V2 again and upload results into this thread:
Avast Uninstall Utility | Download aswClear for Avast Removal

Search for C:\windows\memory.dmp > if the file size is < 1.5 GB save to the downloads folder > post a separate share link into this thread

ScothMcBeast · 14 Aug 2020

Crap. Like I said I don't know what I'm doing, so when that happens what I'm not doing is uninstalling AV and running a tool from the internet. So I guess that's the end of this line. Thanks anyway.

zbook · 14 Aug 2020

The logs were incomplete.

The logs displayed multiple drive problems including bad blocks and drive file system corruption.
There were misbehaving Avast drivers and other drivers.

Some of the drives are very large.
Make sure all drives are tested with each: HD tune, Sea Tools for windows, and chkdsk /b /v

For all steps / tests make sure images are posted into the thread:

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com

13) Make sure that there is no over clocking while troubleshooting

14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

15) Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

16) Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools for Windows |
Seagate
How to use SeaTools for Windows | Seagate Support US

17) Open administrative command prompt and type or copy and paste:
chkdsk /b /v
This may take hours to run so plan to run overnight and part of the next day.
Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: changing the drive letter to the applicable drive.

C:\Windows\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot

18) Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to desktop > post into the thread using a one drive, drop box, or google drive share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10

19) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of

20) Download and install Minitool Partition Wizard > click launch > post an image of the results into this thread
MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com
https://www.partitionwizard.com/part...ion-magic.html

21) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

22) The BIOS: Version/Date American Megatrends Inc. 1.10, 22-Aug-18
Upgrade the BIOS to the most up to date non-beta BIOS:
https://www.msi.com/Motherboard/supp...90-GAMING-PLUS

23) these steps / tests can be performed overnight:
a) HD Tune full error scan
b) Sea Tools for Windows long generic test
c) Chkdsk /b /v

24) Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Code:

13-Aug-20 14:23	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000005
P3: fffff80782c200b4
P4: ffffc384ae0f9750
P5: 0
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081320-8015-01.dmp
\\?\C:\Windows\TEMP\WER-17015-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5052.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5063.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5071.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5082.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_8937ee358a4c7b18d56642351d686a8ad9cbbda_00000000_cab_53ccab16-676c-443f-9c22-6178713b8644

Analysis symbol: 
Rechecking for solution: 0
Report Id: f155b822-bd7f-49cd-aaaa-d84a1d109c15
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
13-Aug-20 14:23	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 3b
P2: c0000005
P3: fffff80782c200b4
P4: ffffc384ae0f9750
P5: 0
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\081320-8015-01.dmp
\\?\C:\Windows\TEMP\WER-17015-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5052.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5063.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5071.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5082.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_8937ee358a4c7b18d56642351d686a8ad9cbbda_00000000_53ccab16-676c-443f-9c22-6178713b8644

Analysis symbol: 
Rechecking for solution: 0
Report Id: f155b822-bd7f-49cd-aaaa-d84a1d109c15
Report Status: 4
Hashed bucket: 
Cab Guid: 0
07-Aug-20 11:27	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 7f
P2: 8
P3: ffffd100ea00b010
P4: ffff8e04d6d06ff0
P5: fffff8007fc2cb03
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080720-9296-01.dmp
\\?\C:\Windows\TEMP\WER-19406-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BB0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BB1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BC0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BD1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_7f_8e40e663979d422112c905c6c6c894716a8a98a_00000000_cab_4042a579-3cc8-4679-9eb4-860c782165eb

Analysis symbol: 
Rechecking for solution: 0
Report Id: bce63619-8191-4495-9192-7116ed5753be
Report Status: 2049
Hashed bucket: 
Cab Guid: 0
07-Aug-20 11:27	Windows Error Reporting	Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 7f
P2: 8
P3: ffffd100ea00b010
P4: ffff8e04d6d06ff0
P5: fffff8007fc2cb03
P6: 10_0_18362
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\080720-9296-01.dmp
\\?\C:\Windows\TEMP\WER-19406-0.sysdata.xml
\\?\C:\Windows\MEMORY.DMP
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BB0.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BB1.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BC0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5BD1.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_7f_8e40e663979d422112c905c6c6c894716a8a98a_00000000_4042a579-3cc8-4679-9eb4-860c782165eb

Analysis symbol: 
Rechecking for solution: 0
Report Id: bce63619-8191-4495-9192-7116ed5753be
Report Status: 4
Hashed bucket: 
Cab Guid: 0

Code:

Event[6007]:
  Log Name: System
  Source: disk
  Date: 2020-08-11T02:04:57.868
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-TDRL9FR
  Description: 
The device, \Device\Harddisk2\DR2, has a bad block.

Code:

  Log Name: System
  Source: disk
  Date: 2020-07-28T03:19:43.207
  Event ID: 7
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-TDRL9FR
  Description: 
The device, \Device\Harddisk1\DR1, has a bad block.

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 136.7 GB
Total Space: 857.8 GB
File System: NTFS
      Model: Samsung SSD 970 EVO Plus 1TB

      Drive: D:
 Free Space: 195.2 GB
Total Space: 1907.6 GB
File System: NTFS
      Model: ST2000DM001-1ER164

      Drive: E:
 Free Space: 216.8 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: WDC WD20EARS-00J99B0

      Drive: F:
 Free Space: 3595.7 GB
Total Space: 3815.3 GB
File System: NTFS
      Model: ST4000DM 004-2CV104 SCSI Disk Device

      Drive: H:
 Free Space: 80.7 GB
Total Space: 1907.7 GB
File System: NTFS
      Model: ST2000DM 001-1ER164 SCSI Disk Device

      Drive: S:
 Free Space: 109.0 GB
Total Space: 428.7 GB
File System: NTFS
      Model: Samsung SSD 850 EVO 500GB

      Drive: G:
      Model: HL-DT-ST BD-RE  BH12LS38
     Driver: C:\WINDOWS\SYSTEM32\DRIVERS\CDROM.SYS, 10.00.18362.0001 (English), 3/19/2019 07:43:39, 173056 bytes

Code:

Event[3765]:
  Log Name: System
  Source: Ntfs
  Date: 2020-08-01T00:24:37.935
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-TDRL9FR
  Description: 
A corruption was discovered in the file system structure on volume F:.

A corruption was found in a file system index structure.  The file reference number is 0x300000000407e.  The name of the file is "\_Backup\_Drums_bak_2020".  The corrupted index attribute is ":$I30:$INDEX_ALLOCATION".

Code:

Event[3767]:
  Log Name: System
  Source: Ntfs
  Date: 2020-08-01T00:24:37.935
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-TDRL9FR
  Description: 
A corruption was discovered in the file system structure on volume F:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x500000000027d.  The name of the file is "<unable to determine file name>".


Event[3768]:
  Log Name: System
  Source: Ntfs
  Date: 2020-08-01T00:24:37.935
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-TDRL9FR
  Description: 
A corruption was discovered in the file system structure on volume F:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x2000000061d2d.  The name of the file is "<unable to determine file name>".

Code:

Event[3769]:
  Log Name: System
  Source: Ntfs
  Date: 2020-08-01T00:24:37.935
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-TDRL9FR
  Description: 
A corruption was discovered in the file system structure on volume F:.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x3000000006e9c.  The name of the file is "<unable to determine file name>".

Code:

aswSnx.sys   Thu Jul 23 07:10:05 2020 (5F197E1D)

Code:

l6PodHd2_AvsFilter l6PodHd2_AvsFilter.sys Tue Apr  2 06:48:50 2019 (5CA36842)

zbook · 14 Aug 2020

When you uninstall Avast AV make sure that Microsoft Defender is turned on:
How to Turn On or Off Microsoft Defender Antivirus in Windows 10

philc43 · 14 Aug 2020

Hello ScothMcBeast

You have correctly identified a driver conflict and the manufacturers are aware of it.

Please go to the following website and select the driver downloads for W10. You will see that they have issued a new driver for the Line6 tools which, if you download and install it, will fix your problem:

Line 6