BSOD caused by Ntfs.sys and ntoskrnl.exe (Windows 10, 2018)

[JayTee3]

Screencap of my minidump in bluescreenview:

https://i.imgur.com/5m9pL8V.png

Help?

 

[JayTee3]

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

I just did this, removed the RTCore64.sys and there were 3 mentions of the NTIOlib so its odd that it needs to be deleted but deleted all 3, also contacted nvidia and did a fresh reinstall using Revo pro instead of DDU this time and removed all signs and registery and etc of NVIDIA. So hopefully im okay, will update you.

 

[JayTee3]

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

No crash for 14 days (well maybe 1? but eh)... until now
https://1drv.ms/u/s!AtKsB23i-mF6pzKYzT1G2Y6Tyzww

can u take a look at this?

 

[johnbl]

looks like a service called plays.exe created a file, then tried to resize it but the pool was corrupted. Pool is just data stored in memory by a device driver. the error indicated that the memory block was modified when it was free (meaining no device driver owned the memory) Most likely some other driver had data in memory and wrote beyond its owned memory block. To find this you would have to have a kernel or full memory dump and you would need to run verifier.exe functions to cause the system to bugcheck when a driver attempts to access memory that is not assigned to it.

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

No crash for 14 days (well maybe 1? but eh)... until now
https://1drv.ms/u/s!AtKsB23i-mF6pzKYzT1G2Y6Tyzww

can u take a look at this?

 

[JayTee3]

looks like a service called plays.exe created a file, then tried to resize it but the pool was corrupted. Pool is just data stored in memory by a device driver. the error indicated that the memory block was modified when it was free (meaining no device driver owned the memory) Most likely some other driver had data in memory and wrote beyond its owned memory block. To find this you would have to have a kernel or full memory dump and you would need to run verifier.exe functions to cause the system to bugcheck when a driver attempts to access memory that is not assigned to it.

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

No crash for 14 days (well maybe 1? but eh)... until now
https://1drv.ms/u/s!AtKsB23i-mF6pzKYzT1G2Y6Tyzww

can u take a look at this?

So what should I do? Full memory dump is impossible now, I could do kernel I guess.

Do u want me to run verifier.exe? And if so can u run me through it?

 

[johnbl]

first set your memory dump type to kernel, so proper debug info is saved when the system bugchecks.
then start cmd.exe as an admin then run
verifier.exe /standard /all
and reboot your system.

NOTE: be sure you know how to get into windows safe mode, in case the system bugchecks on the reboot process.
if it does you would run this command to turn off verifier after the bugcheck.
verifier.exe /reset

you want to run until you get the next bugcheck, then turn off verifier or you machine will run slowly until you do.

with verifier running, is some driver attempts to modify memory that it no longer owns the system will call a bugcheck and it should name the driver that attempted to make the change. Without verifier checking, the system does not check and just uses the modified data and later crashes. verifier should catch the case where one driver frees up a memory block to the system, the system gives the memory block to a second driver, then the first driver modifies the memory block (it does not own) it should bugcheck here rather than when the second driver tries to use the modified data which may or may not cause a bugcheck.

looks like a service called plays.exe created a file, then tried to resize it but the pool was corrupted. Pool is just data stored in memory by a device driver. the error indicated that the memory block was modified when it was free (meaining no device driver owned the memory) Most likely some other driver had data in memory and wrote beyond its owned memory block. To find this you would have to have a kernel or full memory dump and you would need to run verifier.exe functions to cause the system to bugcheck when a driver attempts to access memory that is not assigned to it.

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

No crash for 14 days (well maybe 1? but eh)... until now
https://1drv.ms/u/s!AtKsB23i-mF6pzKYzT1G2Y6Tyzww

can u take a look at this?

So what should I do? Full memory dump is impossible now, I could do kernel I guess.

Do u want me to run verifier.exe? And if so can u run me through it?

 

[JayTee3]

first set your memory dump type to kernel, so proper debug info is saved when the system bugchecks.
then start cmd.exe as an admin then run
verifier.exe /standard /all
and reboot your system.

NOTE: be sure you know how to get into windows safe mode, in case the system bugchecks on the reboot process.
if it does you would run this command to turn off verifier after the bugcheck.
verifier.exe /reset

you want to run until you get the next bugcheck, then turn off verifier or you machine will run slowly until you do.

with verifier running, is some driver attempts to modify memory that it no longer owns the system will call a bugcheck and it should name the driver that attempted to make the change. Without verifier checking, the system does not check and just uses the modified data and later crashes. verifier should catch the case where one driver frees up a memory block to the system, the system gives the memory block to a second driver, then the first driver modifies the memory block (it does not own) it should bugcheck here rather than when the second driver tries to use the modified data which may or may not cause a bugcheck.

looks like a service called plays.exe created a file, then tried to resize it but the pool was corrupted. Pool is just data stored in memory by a device driver. the error indicated that the memory block was modified when it was free (meaining no device driver owned the memory) Most likely some other driver had data in memory and wrote beyond its owned memory block. To find this you would have to have a kernel or full memory dump and you would need to run verifier.exe functions to cause the system to bugcheck when a driver attempts to access memory that is not assigned to it.

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

No crash for 14 days (well maybe 1? but eh)... until now
https://1drv.ms/u/s!AtKsB23i-mF6pzKYzT1G2Y6Tyzww

can u take a look at this?

So what should I do? Full memory dump is impossible now, I could do kernel I guess.

Do u want me to run verifier.exe? And if so can u run me through it?

Alright, will do then update you
Also heres one from today https://1drv.ms/u/s!AtKsB23i-mF6pzN8VJO0ZT9Qy9bH
It's probably the same thing but if its something else let me know

Thanks and merry christmas!

 

[JayTee3]

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

I did this and it just crashes and restarts repeatedly (3 times till it has the repair windows screen, then had to launch into safe mode with cmd to reset verifier). What do I do?

 

[JayTee3]

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

first set your memory dump type to kernel, so proper debug info is saved when the system bugchecks.
then start cmd.exe as an admin then run
verifier.exe /standard /all
and reboot your system.

NOTE: be sure you know how to get into windows safe mode, in case the system bugchecks on the reboot process.
if it does you would run this command to turn off verifier after the bugcheck.
verifier.exe /reset

you want to run until you get the next bugcheck, then turn off verifier or you machine will run slowly until you do.

with verifier running, is some driver attempts to modify memory that it no longer owns the system will call a bugcheck and it should name the driver that attempted to make the change. Without verifier checking, the system does not check and just uses the modified data and later crashes. verifier should catch the case where one driver frees up a memory block to the system, the system gives the memory block to a second driver, then the first driver modifies the memory block (it does not own) it should bugcheck here rather than when the second driver tries to use the modified data which may or may not cause a bugcheck.

looks like a service called plays.exe created a file, then tried to resize it but the pool was corrupted. Pool is just data stored in memory by a device driver. the error indicated that the memory block was modified when it was free (meaining no device driver owned the memory) Most likely some other driver had data in memory and wrote beyond its owned memory block. To find this you would have to have a kernel or full memory dump and you would need to run verifier.exe functions to cause the system to bugcheck when a driver attempts to access memory that is not assigned to it.

after you boot into safe mode with a command prompt. you would do the following commands
cd c:\
dir /s RTCore64.sys
this will search your driver and find all versions of the file for you
then you would use the path to the file and the del command.
like
del c:\windows\system32\driver\rtcore64.sys
(or what ever path the directory command returns)

do this for both drivers.
cd c:\
dir /s NTIOLib_X64.sys
then delete the files it finds

the problem still can be the graphic driver, you just remove the overclock drivers so to reduce the amount of timing issues in the gpu.

some graphics cards have problems with the gpu versions 400 and above and might need a firmware update. (or roll back the driver to a version 399 or less)

same two overclock drivers still running.
bugcheck was in the graphics driver
you might boot into safe mode, then search the drive for the two drivers and delete them from your system so they are no longer running. then reboot into windows and run autoruns as an admin to confirm the drivers are not longer running.

bugcheck looks like a stack overflow. you might want to run Malwarebytes scan

if you have already removed the overclock drivers you might just want to reinstall windows from a clean install image. then make sure you do not install any add on utilities from your motherboard vendor. (just install the required drivers)

if you know that you do not have the drivers installed, then run a rootkit scan.

Logitech USB Video Class Driver (WebCam)
lvuvc64.sys Fri Aug 19 02:26:11 2011
(look for update from logitech)

sometimes drivers get reinstalled by a task in the task scheduler

hardware like the webcam will be detected by the windows plug and play and will reinstall a few seconds after you uninstall it. so you should update it or disable the hardware (in bios if there is a option)

basically the stack for the graphics nvidia graphics driver got corrupted.
I looked at the raw stack, and it looks like mostly a bunch of calls to the nvidia graphics driver.

you still have two overclock drivers running so I would assume that the GPU missed a hardware signal and was not able to complete its gpu software driver calls and the stack overflowed which caused a bugcheck in the graphics driver.

system was up for a hour, was running chrome

overclock drivers:
RTCore64.sys Fri Sep 30 05:03:17 2016
NTIOLib_X64.sys Wed Mar 29 00:26:33 2017

still have old webcam driver from 2011

your cpu came out Q1'17 your cpu overclock driver should be removed.

you can use autoruns to prevent the overclock drivers from loading
https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns

went into autorun as admin and unticked and deleted those 2 drivers (I think i did that last time but they came back?)

Also what is the old webcam driver called from 2011?

Update:
https://1drv.ms/u/s!AtKsB23i-mF6pzDOOQ4TionMrsWz

Still crashed

How do I search after booting into safe mode and where do i delete them? It wasn't BSODing often till i upgraded graphics driver so i feel like its something to do with NVIDIA GeForce Experience possibly which i thought it might be idk.

I ran a malwarebytes scan and it was fine so idk.

No crash for 14 days (well maybe 1? but eh)... until now
https://1drv.ms/u/s!AtKsB23i-mF6pzKYzT1G2Y6Tyzww

can u take a look at this?

So what should I do? Full memory dump is impossible now, I could do kernel I guess.

Do u want me to run verifier.exe? And if so can u run me through it?

 

[johnbl]

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

 

[JayTee3]

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

As i told you, I can't turn the verifier flags on as it puts my pc in a restart loop

 

[johnbl]

you turn them on, reboot, the system bugchecks and makes a memory dump, then you boot into safe mode run
verifer.exe /reset and reboot back in to normal mode. then copy the memory dump to a cloud server and post a link.
the verifier only needs to be running until the memory dump is made.
best if you change the memory dump type to kernel so that the proper debug info will be saved.
even if you can not get verifier running the kernel memory dump will have much more debug info and internal error logs.

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

As i told you, I can't turn the verifier flags on as it puts my pc in a restart loop

 

[JayTee3]

you turn them on, reboot, the system bugchecks and makes a memory dump, then you boot into safe mode run
verifer.exe /reset and reboot back in to normal mode. then copy the memory dump to a cloud server and post a link.
the verifier only needs to be running until the memory dump is made.
best if you change the memory dump type to kernel so that the proper debug info will be saved.
even if you can not get verifier running the kernel memory dump will have much more debug info and internal error logs.

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

As i told you, I can't turn the verifier flags on as it puts my pc in a restart loop

"You turn them on, reboot"

No, what happens when i turn on verifier my computer WONT EVEN START UP PROPERLY. Verifier.exe puts it in an endless loop of it, and no it doesn't make a memory dump or mini dump or anything.

 

[johnbl]

get the system to produce a kernel memory dump, it will be a much larger file but it will contain a lot more debug info.
you can google "how to force a memory dump using a keyboard" then make the registry settings and force a memory dump while the system is working. let the system run for some time (say 10 minutes) before you force the memory dump. I can take a look at the internal error logs and see if something strange is going on.

you turn them on, reboot, the system bugchecks and makes a memory dump, then you boot into safe mode run
verifer.exe /reset and reboot back in to normal mode. then copy the memory dump to a cloud server and post a link.
the verifier only needs to be running until the memory dump is made.
best if you change the memory dump type to kernel so that the proper debug info will be saved.
even if you can not get verifier running the kernel memory dump will have much more debug info and internal error logs.

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

As i told you, I can't turn the verifier flags on as it puts my pc in a restart loop

"You turn them on, reboot"

No, what happens when i turn on verifier my computer WONT EVEN START UP PROPERLY. Verifier.exe puts it in an endless loop of it, and no it doesn't make a memory dump or mini dump or anything.

 

[JayTee3]

get the system to produce a kernel memory dump, it will be a much larger file but it will contain a lot more debug info.
you can google "how to force a memory dump using a keyboard" then make the registry settings and force a memory dump while the system is working. let the system run for some time (say 10 minutes) before you force the memory dump. I can take a look at the internal error logs and see if something strange is going on.

you turn them on, reboot, the system bugchecks and makes a memory dump, then you boot into safe mode run
verifer.exe /reset and reboot back in to normal mode. then copy the memory dump to a cloud server and post a link.
the verifier only needs to be running until the memory dump is made.
best if you change the memory dump type to kernel so that the proper debug info will be saved.
even if you can not get verifier running the kernel memory dump will have much more debug info and internal error logs.

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

As i told you, I can't turn the verifier flags on as it puts my pc in a restart loop

"You turn them on, reboot"

No, what happens when i turn on verifier my computer WONT EVEN START UP PROPERLY. Verifier.exe puts it in an endless loop of it, and no it doesn't make a memory dump or mini dump or anything.

Like this then restart?

( following instructions from https://www.dell.com/support/article/au/en/audhs1/sln283146/windows-server-how-to-force-windows-to-generate-a-memory-dump-using-the-keyboard?lang=en )

 

[johnbl]

yep reboot and try the keyboard input to force a memory dump

get the system to produce a kernel memory dump, it will be a much larger file but it will contain a lot more debug info.
you can google "how to force a memory dump using a keyboard" then make the registry settings and force a memory dump while the system is working. let the system run for some time (say 10 minutes) before you force the memory dump. I can take a look at the internal error logs and see if something strange is going on.

you turn them on, reboot, the system bugchecks and makes a memory dump, then you boot into safe mode run
verifer.exe /reset and reboot back in to normal mode. then copy the memory dump to a cloud server and post a link.
the verifier only needs to be running until the memory dump is made.
best if you change the memory dump type to kernel so that the proper debug info will be saved.
even if you can not get verifier running the kernel memory dump will have much more debug info and internal error logs.

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

As i told you, I can't turn the verifier flags on as it puts my pc in a restart loop

"You turn them on, reboot"

No, what happens when i turn on verifier my computer WONT EVEN START UP PROPERLY. Verifier.exe puts it in an endless loop of it, and no it doesn't make a memory dump or mini dump or anything.

Like this then restart?

( following instructions from https://www.dell.com/support/article/au/en/audhs1/sln283146/windows-server-how-to-force-windows-to-generate-a-memory-dump-using-the-keyboard?lang=en )

 

[JayTee3]

yep reboot and try the keyboard input to force a memory dump

get the system to produce a kernel memory dump, it will be a much larger file but it will contain a lot more debug info.
you can google "how to force a memory dump using a keyboard" then make the registry settings and force a memory dump while the system is working. let the system run for some time (say 10 minutes) before you force the memory dump. I can take a look at the internal error logs and see if something strange is going on.

you turn them on, reboot, the system bugchecks and makes a memory dump, then you boot into safe mode run
verifer.exe /reset and reboot back in to normal mode. then copy the memory dump to a cloud server and post a link.
the verifier only needs to be running until the memory dump is made.
best if you change the memory dump type to kernel so that the proper debug info will be saved.
even if you can not get verifier running the kernel memory dump will have much more debug info and internal error logs.

this is a minidump file, showing a memory management bugcheck with a undocumented error code
while doing some calls to virtual memory. (pagefile.sys)

verifier flags not turnned on.

kernel dump files are stored in a different file name and location by default.
look for the file c:\windows\memory.dmp

Also heres the kernel memory dump from the crash just today https://1drv.ms/u/s!AtKsB23i-mF6pzQQ5XiKmnlXT5D4

As i told you, I can't turn the verifier flags on as it puts my pc in a restart loop

"You turn them on, reboot"

No, what happens when i turn on verifier my computer WONT EVEN START UP PROPERLY. Verifier.exe puts it in an endless loop of it, and no it doesn't make a memory dump or mini dump or anything.

Like this then restart?

( following instructions from https://www.dell.com/support/article/au/en/audhs1/sln283146/windows-server-how-to-force-windows-to-generate-a-memory-dump-using-the-keyboard?lang=en )

I waited till it crashed properly instead of a force crash to be more realistic, gosh my internet sucks so this took overnight to upload the kernel memory dump but here

https://drive.google.com/file/d/1Em9xAUTk_EmJRRiiNyJcA1EyCrG4FY_6/view?usp=sharing

 

[johnbl]

guessing that your usb 3 port 4 has a logictech webcam on it
since you have a old driver for it installed:
Logitech USB Video Class Driver (WebCam)
\SystemRoot\system32\DRIVERS\lvuvc64.sys Mon Oct 22 19:12:08 2012
https://carrona.org/drivers/driver.php?id=lvuvc64.sys

and the bugcheck was in video code and the usb driver was some kind of video driver.

you should see if you can get a update for the driver and I would put it on a usb2 port.
------------------------
download and run usb port viewer from https://www.uwe-sieber.de/usbtreeview_e.html
find out what is on usb 3 port 4 and either fix the device or remove it and the driver.
some devices might not work on usb 3, some devices might require a custom updated driver, some devices might also require a firmware update from the vendor of the device. since the device has failed or was removed I can not read what the device was.

you might find that putting it on a usb 2 port may work for you. depending on what the device is.
it looks like the device stopped working and the system tried to reset the device to get it working again.


--------------
looks like the system thinks you have a video device on usb 3 port 4 that was removed.
the system tried to clean up the memory it used but there was something still trying to access the memory. (looks like your virus scanner)


4) !device_info 0xffffa58865bbb570, !devstack ffffa58864f8b060
Current Device State: EnumeratedAsFailedUnknown.WaitingForDevicePortEventsForFailedDevice
Desc: <none>
USB\VID_0000&PID_0000&REV_0000 Vendor ID not listed with USB.org
!wdfhandle 0x5a779b074fd8 (UCXUSBDEVICE)Error: Unable to get controller specific info for device with wdfhandle 0x00005a779b074fd8


here is the error log for the device:
[63] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[62] <OperationSuccess> EnablingDeviceInUCX
[61] <OperationSuccess> CreatingUCXDefaultEndpoint
[60] <OperationSuccess> CreatingUCXDevice
[59] <PortResetComplete> SettingSpeedFlagFor20Devices
[58] <Push> Resetting1
[57] <TimerFired> EnumeratingAtAddressZeroInEnum
[56] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[55] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[54] <Pop> EnumeratingAtAddressZeroInEnum
[53] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[52] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[51] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[50] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[49] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[48] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[47] <No> WaitingForPostReset1ExtendedTimer
[46] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[45] <OperationSuccess> EnablingDeviceInUCX
[44] <OperationSuccess> CreatingUCXDefaultEndpoint
[43] <OperationSuccess> CreatingUCXDevice
[42] <PortResetComplete> SettingSpeedFlagFor20Devices
[41] <Push> Resetting1
[40] <TimerFired> EnumeratingAtAddressZeroInEnum
[39] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[38] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[37] <Pop> EnumeratingAtAddressZeroInEnum
[36] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[35] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[34] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[33] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[32] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[31] <Push> GettingDeviceDescriptorInEnumAtZero
[30] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[29] <PDOD0ExitFinal> FlushingPnpEventsForFailedDevice
[28] <Push> WaitingForDevicePortEventsForFailedDevice
[27] <OperationSuccess> EnumeratedAsFailedUnknown
[26] <PDOD0Entry> D0EntryForUnknownDevice
[25] <Pop> WaitingForD0EntryForFailedDevice
[24] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[23] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[22] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[21] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[20] <Push> WaitingForDevicePortEventsForFailedDevice
[19] <OperationSuccess> WaitingForD0EntryForFailedDevice
[18] <Pop> ReportingFailedUnknownDeviceToPnp
[17] <OperationSuccess> ReturningOperationSuccessInReportingUnknownDevice
[16] <OperationSuccess> MarkingUnknownDeviceAsFailed
[15] <Push> CreatingUnknownChildPDOAndReportingToPnp
[14] <OperationSuccess> ReportingFailedUnknownDeviceToPnp
[13] <OperationFailure> ReleasingPowerReferenceOnHubOnEnumerationFailure
[12] <Pop> Enumerating
[11] <OperationSuccess> ReturningOperationFailureInEnum
[10] <PortDisabled> ReleasingAddressZeroOwnershipOnEnumFailure
[ 9] <Yes> DisablingOnEnumAfterFailureInEnumWithAddress0Ownership
[ 8] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[ 7] <Pop> EnumeratingAtAddressZeroInEnum
[ 6] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[ 5] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[ 4] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[ 3] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[ 2] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[ 1] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[ 0] <No> WaitingForPostReset1ExtendedTimer

 

[JayTee3]

guessing that your usb 3 port 4 has a logictech webcam on it
since you have a old driver for it installed:
Logitech USB Video Class Driver (WebCam)
\SystemRoot\system32\DRIVERS\lvuvc64.sys Mon Oct 22 19:12:08 2012
https://carrona.org/drivers/driver.php?id=lvuvc64.sys

and the bugcheck was in video code and the usb driver was some kind of video driver.

you should see if you can get a update for the driver and I would put it on a usb2 port.
------------------------
download and run usb port viewer from https://www.uwe-sieber.de/usbtreeview_e.html
find out what is on usb 3 port 4 and either fix the device or remove it and the driver.
some devices might not work on usb 3, some devices might require a custom updated driver, some devices might also require a firmware update from the vendor of the device. since the device has failed or was removed I can not read what the device was.

you might find that putting it on a usb 2 port may work for you. depending on what the device is.
it looks like the device stopped working and the system tried to reset the device to get it working again.


--------------
looks like the system thinks you have a video device on usb 3 port 4 that was removed.
the system tried to clean up the memory it used but there was something still trying to access the memory. (looks like your virus scanner)


4) !device_info 0xffffa58865bbb570, !devstack ffffa58864f8b060
Current Device State: EnumeratedAsFailedUnknown.WaitingForDevicePortEventsForFailedDevice
Desc: <none>
USB\VID_0000&PID_0000&REV_0000 Vendor ID not listed with USB.org
!wdfhandle 0x5a779b074fd8 (UCXUSBDEVICE)Error: Unable to get controller specific info for device with wdfhandle 0x00005a779b074fd8


here is the error log for the device:
[63] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[62] <OperationSuccess> EnablingDeviceInUCX
[61] <OperationSuccess> CreatingUCXDefaultEndpoint
[60] <OperationSuccess> CreatingUCXDevice
[59] <PortResetComplete> SettingSpeedFlagFor20Devices
[58] <Push> Resetting1
[57] <TimerFired> EnumeratingAtAddressZeroInEnum
[56] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[55] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[54] <Pop> EnumeratingAtAddressZeroInEnum
[53] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[52] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[51] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[50] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[49] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[48] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[47] <No> WaitingForPostReset1ExtendedTimer
[46] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[45] <OperationSuccess> EnablingDeviceInUCX
[44] <OperationSuccess> CreatingUCXDefaultEndpoint
[43] <OperationSuccess> CreatingUCXDevice
[42] <PortResetComplete> SettingSpeedFlagFor20Devices
[41] <Push> Resetting1
[40] <TimerFired> EnumeratingAtAddressZeroInEnum
[39] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[38] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[37] <Pop> EnumeratingAtAddressZeroInEnum
[36] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[35] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[34] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[33] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[32] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[31] <Push> GettingDeviceDescriptorInEnumAtZero
[30] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[29] <PDOD0ExitFinal> FlushingPnpEventsForFailedDevice
[28] <Push> WaitingForDevicePortEventsForFailedDevice
[27] <OperationSuccess> EnumeratedAsFailedUnknown
[26] <PDOD0Entry> D0EntryForUnknownDevice
[25] <Pop> WaitingForD0EntryForFailedDevice
[24] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[23] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[22] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[21] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[20] <Push> WaitingForDevicePortEventsForFailedDevice
[19] <OperationSuccess> WaitingForD0EntryForFailedDevice
[18] <Pop> ReportingFailedUnknownDeviceToPnp
[17] <OperationSuccess> ReturningOperationSuccessInReportingUnknownDevice
[16] <OperationSuccess> MarkingUnknownDeviceAsFailed
[15] <Push> CreatingUnknownChildPDOAndReportingToPnp
[14] <OperationSuccess> ReportingFailedUnknownDeviceToPnp
[13] <OperationFailure> ReleasingPowerReferenceOnHubOnEnumerationFailure
[12] <Pop> Enumerating
[11] <OperationSuccess> ReturningOperationFailureInEnum
[10] <PortDisabled> ReleasingAddressZeroOwnershipOnEnumFailure
[ 9] <Yes> DisablingOnEnumAfterFailureInEnumWithAddress0Ownership
[ 8] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[ 7] <Pop> EnumeratingAtAddressZeroInEnum
[ 6] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[ 5] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[ 4] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[ 3] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[ 2] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[ 1] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[ 0] <No> WaitingForPostReset1ExtendedTimer

1) I'm confused as I updated the most recent logitech webcam driver for my webcam? Theres these recent downloads for the camera but they all seem like programs and nothing to do with real drivers for the camera: https://support.logitech.com/en_us/product/hd-pro-webcam-c920/downloads

So you're saying to see if i can update it and put it in a usb 2 port? I didn't even realize it was in a usb 3, thanks for the heads up I guess.

2) There is nothing running at port 4. Also from the viewer I don't think I have any usb 2 slots. https://i.imgur.com/d03wzpC.png

But in the same image looks like port 6 is corrupting?

3) Would the video device be the webcam? I assume so right? But in the USB viewer it shows port 6 is the issue but port 14 (the webcam) is fine

 

[johnbl]

google "how show hidden or removed devices in device manager"
then see if the system has a removed device that still has a driver associated with the port

usb device are kind of strange, the drivers get associated with the actual port and they get hidden when the device is removed.

guessing that your usb 3 port 4 has a logictech webcam on it
since you have a old driver for it installed:
Logitech USB Video Class Driver (WebCam)
\SystemRoot\system32\DRIVERS\lvuvc64.sys Mon Oct 22 19:12:08 2012
https://carrona.org/drivers/driver.php?id=lvuvc64.sys

and the bugcheck was in video code and the usb driver was some kind of video driver.

you should see if you can get a update for the driver and I would put it on a usb2 port.
------------------------
download and run usb port viewer from https://www.uwe-sieber.de/usbtreeview_e.html
find out what is on usb 3 port 4 and either fix the device or remove it and the driver.
some devices might not work on usb 3, some devices might require a custom updated driver, some devices might also require a firmware update from the vendor of the device. since the device has failed or was removed I can not read what the device was.

you might find that putting it on a usb 2 port may work for you. depending on what the device is.
it looks like the device stopped working and the system tried to reset the device to get it working again.


--------------
looks like the system thinks you have a video device on usb 3 port 4 that was removed.
the system tried to clean up the memory it used but there was something still trying to access the memory. (looks like your virus scanner)


4) !device_info 0xffffa58865bbb570, !devstack ffffa58864f8b060
Current Device State: EnumeratedAsFailedUnknown.WaitingForDevicePortEventsForFailedDevice
Desc: <none>
USB\VID_0000&PID_0000&REV_0000 Vendor ID not listed with USB.org
!wdfhandle 0x5a779b074fd8 (UCXUSBDEVICE)Error: Unable to get controller specific info for device with wdfhandle 0x00005a779b074fd8


here is the error log for the device:
[63] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[62] <OperationSuccess> EnablingDeviceInUCX
[61] <OperationSuccess> CreatingUCXDefaultEndpoint
[60] <OperationSuccess> CreatingUCXDevice
[59] <PortResetComplete> SettingSpeedFlagFor20Devices
[58] <Push> Resetting1
[57] <TimerFired> EnumeratingAtAddressZeroInEnum
[56] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[55] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[54] <Pop> EnumeratingAtAddressZeroInEnum
[53] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[52] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[51] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[50] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[49] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[48] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[47] <No> WaitingForPostReset1ExtendedTimer
[46] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[45] <OperationSuccess> EnablingDeviceInUCX
[44] <OperationSuccess> CreatingUCXDefaultEndpoint
[43] <OperationSuccess> CreatingUCXDevice
[42] <PortResetComplete> SettingSpeedFlagFor20Devices
[41] <Push> Resetting1
[40] <TimerFired> EnumeratingAtAddressZeroInEnum
[39] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[38] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[37] <Pop> EnumeratingAtAddressZeroInEnum
[36] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[35] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[34] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[33] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[32] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[31] <Push> GettingDeviceDescriptorInEnumAtZero
[30] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[29] <PDOD0ExitFinal> FlushingPnpEventsForFailedDevice
[28] <Push> WaitingForDevicePortEventsForFailedDevice
[27] <OperationSuccess> EnumeratedAsFailedUnknown
[26] <PDOD0Entry> D0EntryForUnknownDevice
[25] <Pop> WaitingForD0EntryForFailedDevice
[24] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[23] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[22] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[21] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[20] <Push> WaitingForDevicePortEventsForFailedDevice
[19] <OperationSuccess> WaitingForD0EntryForFailedDevice
[18] <Pop> ReportingFailedUnknownDeviceToPnp
[17] <OperationSuccess> ReturningOperationSuccessInReportingUnknownDevice
[16] <OperationSuccess> MarkingUnknownDeviceAsFailed
[15] <Push> CreatingUnknownChildPDOAndReportingToPnp
[14] <OperationSuccess> ReportingFailedUnknownDeviceToPnp
[13] <OperationFailure> ReleasingPowerReferenceOnHubOnEnumerationFailure
[12] <Pop> Enumerating
[11] <OperationSuccess> ReturningOperationFailureInEnum
[10] <PortDisabled> ReleasingAddressZeroOwnershipOnEnumFailure
[ 9] <Yes> DisablingOnEnumAfterFailureInEnumWithAddress0Ownership
[ 8] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[ 7] <Pop> EnumeratingAtAddressZeroInEnum
[ 6] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[ 5] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[ 4] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[ 3] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[ 2] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[ 1] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[ 0] <No> WaitingForPostReset1ExtendedTimer

1) I'm confused as I updated the most recent logitech webcam driver for my webcam? Theres these recent downloads for the camera but they all seem like programs and nothing to do with real drivers for the camera: https://support.logitech.com/en_us/product/hd-pro-webcam-c920/downloads

So you're saying to see if i can update it and put it in a usb 2 port? I didn't even realize it was in a usb 3, thanks for the heads up I guess.

2) There is nothing running at port 4. Also from the viewer I don't think I have any usb 2 slots. https://i.imgur.com/d03wzpC.png

But in the same image looks like port 6 is corrupting?

3) Would the video device be the webcam? I assume so right? But in the USB viewer it shows port 6 is the issue but port 14 (the webcam) is fine

 

[JayTee3]

google "how show hidden or removed devices in device manager"
then see if the system has a removed device that still has a driver associated with the port

usb device are kind of strange, the drivers get associated with the actual port and they get hidden when the device is removed.

guessing that your usb 3 port 4 has a logictech webcam on it
since you have a old driver for it installed:
Logitech USB Video Class Driver (WebCam)
\SystemRoot\system32\DRIVERS\lvuvc64.sys Mon Oct 22 19:12:08 2012
https://carrona.org/drivers/driver.php?id=lvuvc64.sys

and the bugcheck was in video code and the usb driver was some kind of video driver.

you should see if you can get a update for the driver and I would put it on a usb2 port.
------------------------
download and run usb port viewer from https://www.uwe-sieber.de/usbtreeview_e.html
find out what is on usb 3 port 4 and either fix the device or remove it and the driver.
some devices might not work on usb 3, some devices might require a custom updated driver, some devices might also require a firmware update from the vendor of the device. since the device has failed or was removed I can not read what the device was.

you might find that putting it on a usb 2 port may work for you. depending on what the device is.
it looks like the device stopped working and the system tried to reset the device to get it working again.


--------------
looks like the system thinks you have a video device on usb 3 port 4 that was removed.
the system tried to clean up the memory it used but there was something still trying to access the memory. (looks like your virus scanner)


4) !device_info 0xffffa58865bbb570, !devstack ffffa58864f8b060
Current Device State: EnumeratedAsFailedUnknown.WaitingForDevicePortEventsForFailedDevice
Desc: <none>
USB\VID_0000&PID_0000&REV_0000 Vendor ID not listed with USB.org
!wdfhandle 0x5a779b074fd8 (UCXUSBDEVICE)Error: Unable to get controller specific info for device with wdfhandle 0x00005a779b074fd8


here is the error log for the device:
[63] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[62] <OperationSuccess> EnablingDeviceInUCX
[61] <OperationSuccess> CreatingUCXDefaultEndpoint
[60] <OperationSuccess> CreatingUCXDevice
[59] <PortResetComplete> SettingSpeedFlagFor20Devices
[58] <Push> Resetting1
[57] <TimerFired> EnumeratingAtAddressZeroInEnum
[56] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[55] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[54] <Pop> EnumeratingAtAddressZeroInEnum
[53] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[52] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[51] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[50] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[49] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[48] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[47] <No> WaitingForPostReset1ExtendedTimer
[46] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[45] <OperationSuccess> EnablingDeviceInUCX
[44] <OperationSuccess> CreatingUCXDefaultEndpoint
[43] <OperationSuccess> CreatingUCXDevice
[42] <PortResetComplete> SettingSpeedFlagFor20Devices
[41] <Push> Resetting1
[40] <TimerFired> EnumeratingAtAddressZeroInEnum
[39] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[38] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[37] <Pop> EnumeratingAtAddressZeroInEnum
[36] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[35] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[34] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[33] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[32] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[31] <Push> GettingDeviceDescriptorInEnumAtZero
[30] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[29] <PDOD0ExitFinal> FlushingPnpEventsForFailedDevice
[28] <Push> WaitingForDevicePortEventsForFailedDevice
[27] <OperationSuccess> EnumeratedAsFailedUnknown
[26] <PDOD0Entry> D0EntryForUnknownDevice
[25] <Pop> WaitingForD0EntryForFailedDevice
[24] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[23] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[22] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[21] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[20] <Push> WaitingForDevicePortEventsForFailedDevice
[19] <OperationSuccess> WaitingForD0EntryForFailedDevice
[18] <Pop> ReportingFailedUnknownDeviceToPnp
[17] <OperationSuccess> ReturningOperationSuccessInReportingUnknownDevice
[16] <OperationSuccess> MarkingUnknownDeviceAsFailed
[15] <Push> CreatingUnknownChildPDOAndReportingToPnp
[14] <OperationSuccess> ReportingFailedUnknownDeviceToPnp
[13] <OperationFailure> ReleasingPowerReferenceOnHubOnEnumerationFailure
[12] <Pop> Enumerating
[11] <OperationSuccess> ReturningOperationFailureInEnum
[10] <PortDisabled> ReleasingAddressZeroOwnershipOnEnumFailure
[ 9] <Yes> DisablingOnEnumAfterFailureInEnumWithAddress0Ownership
[ 8] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[ 7] <Pop> EnumeratingAtAddressZeroInEnum
[ 6] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[ 5] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[ 4] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[ 3] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[ 2] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[ 1] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[ 0] <No> WaitingForPostReset1ExtendedTimer

1) I'm confused as I updated the most recent logitech webcam driver for my webcam? Theres these recent downloads for the camera but they all seem like programs and nothing to do with real drivers for the camera: https://support.logitech.com/en_us/product/hd-pro-webcam-c920/downloads

So you're saying to see if i can update it and put it in a usb 2 port? I didn't even realize it was in a usb 3, thanks for the heads up I guess.

2) There is nothing running at port 4. Also from the viewer I don't think I have any usb 2 slots. https://i.imgur.com/d03wzpC.png

But in the same image looks like port 6 is corrupting?

3) Would the video device be the webcam? I assume so right? But in the USB viewer it shows port 6 is the issue but port 14 (the webcam) is fine

Also I checked the back of my computer and they're all listed there everything that is plugged in seems to be fine so yeah it might be that

This is what it shows in device manager after the instructions from google https://i.imgur.com/1yU7xPn.png

Should I just remove/uninstall the port driver?

 

[johnbl]

yes, uninstall the port, windows plug and play will reinstall the driver a few seconds later. see if it still thinks there is a device connected when it reinstalles. (hopefully it will not bugcheck)
you might also go in bios and see if there is anything special about that port. one port may chain together a bunch of other ports. since you have a usb3 and a usb 3.1 port your usb 2 devices might be emulated by the usb 3.1 device.
if it has bugs in the chip or driver it might not work correctly. you should check to see if your motherboard has a update for the intel cpu chipset and the asmedia 3.1 usb chipset.
(these also depend on the bios version so you would have to make sure the bios is current)
the intel usb 3 ports are more likely to have fewer bugs since the driver will get updated via windows update.

google "how show hidden or removed devices in device manager"
then see if the system has a removed device that still has a driver associated with the port

usb device are kind of strange, the drivers get associated with the actual port and they get hidden when the device is removed.

guessing that your usb 3 port 4 has a logictech webcam on it
since you have a old driver for it installed:
Logitech USB Video Class Driver (WebCam)
\SystemRoot\system32\DRIVERS\lvuvc64.sys Mon Oct 22 19:12:08 2012
https://carrona.org/drivers/driver.php?id=lvuvc64.sys

and the bugcheck was in video code and the usb driver was some kind of video driver.

you should see if you can get a update for the driver and I would put it on a usb2 port.
------------------------
download and run usb port viewer from https://www.uwe-sieber.de/usbtreeview_e.html
find out what is on usb 3 port 4 and either fix the device or remove it and the driver.
some devices might not work on usb 3, some devices might require a custom updated driver, some devices might also require a firmware update from the vendor of the device. since the device has failed or was removed I can not read what the device was.

you might find that putting it on a usb 2 port may work for you. depending on what the device is.
it looks like the device stopped working and the system tried to reset the device to get it working again.


--------------
looks like the system thinks you have a video device on usb 3 port 4 that was removed.
the system tried to clean up the memory it used but there was something still trying to access the memory. (looks like your virus scanner)


4) !device_info 0xffffa58865bbb570, !devstack ffffa58864f8b060
Current Device State: EnumeratedAsFailedUnknown.WaitingForDevicePortEventsForFailedDevice
Desc: <none>
USB\VID_0000&PID_0000&REV_0000 Vendor ID not listed with USB.org
!wdfhandle 0x5a779b074fd8 (UCXUSBDEVICE)Error: Unable to get controller specific info for device with wdfhandle 0x00005a779b074fd8


here is the error log for the device:
[63] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[62] <OperationSuccess> EnablingDeviceInUCX
[61] <OperationSuccess> CreatingUCXDefaultEndpoint
[60] <OperationSuccess> CreatingUCXDevice
[59] <PortResetComplete> SettingSpeedFlagFor20Devices
[58] <Push> Resetting1
[57] <TimerFired> EnumeratingAtAddressZeroInEnum
[56] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[55] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[54] <Pop> EnumeratingAtAddressZeroInEnum
[53] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[52] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[51] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[50] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[49] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[48] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[47] <No> WaitingForPostReset1ExtendedTimer
[46] <UCXIoctlSuccess> CheckingIfFirstEnumTryAfterReset1
[45] <OperationSuccess> EnablingDeviceInUCX
[44] <OperationSuccess> CreatingUCXDefaultEndpoint
[43] <OperationSuccess> CreatingUCXDevice
[42] <PortResetComplete> SettingSpeedFlagFor20Devices
[41] <Push> Resetting1
[40] <TimerFired> EnumeratingAtAddressZeroInEnum
[39] <No> StartingTimerForEnumRetryInEnumWithAddr0Ownership
[38] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[37] <Pop> EnumeratingAtAddressZeroInEnum
[36] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[35] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[34] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[33] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[32] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[31] <Push> GettingDeviceDescriptorInEnumAtZero
[30] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[29] <PDOD0ExitFinal> FlushingPnpEventsForFailedDevice
[28] <Push> WaitingForDevicePortEventsForFailedDevice
[27] <OperationSuccess> EnumeratedAsFailedUnknown
[26] <PDOD0Entry> D0EntryForUnknownDevice
[25] <Pop> WaitingForD0EntryForFailedDevice
[24] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[23] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[22] <OperationSuccess> WaitingForDevicePortEventsForFailedDevice
[21] <PDOInstallMSOSExt> FlushingPnpEventsForFailedDevice
[20] <Push> WaitingForDevicePortEventsForFailedDevice
[19] <OperationSuccess> WaitingForD0EntryForFailedDevice
[18] <Pop> ReportingFailedUnknownDeviceToPnp
[17] <OperationSuccess> ReturningOperationSuccessInReportingUnknownDevice
[16] <OperationSuccess> MarkingUnknownDeviceAsFailed
[15] <Push> CreatingUnknownChildPDOAndReportingToPnp
[14] <OperationSuccess> ReportingFailedUnknownDeviceToPnp
[13] <OperationFailure> ReleasingPowerReferenceOnHubOnEnumerationFailure
[12] <Pop> Enumerating
[11] <OperationSuccess> ReturningOperationFailureInEnum
[10] <PortDisabled> ReleasingAddressZeroOwnershipOnEnumFailure
[ 9] <Yes> DisablingOnEnumAfterFailureInEnumWithAddress0Ownership
[ 8] <OperationFailure> CheckingIfEnumRetryReachedMaximumInEnumWithAddr0Ownership
[ 7] <Pop> EnumeratingAtAddressZeroInEnum
[ 6] <OperationSuccess> ReturningDeviceOperationFailureInEnumAtZero
[ 5] <OperationSuccess> DeletingUCXDeviceOnOperationFailure
[ 4] <UCXIoctlSuccess> DeletingUCXDefaultEndpointOnOperationFailure
[ 3] <OperationFailure> DisablingDeviceInUCXOnOperationFailure
[ 2] <TransferFailure> ValidatingDeviceDescriptorInEnumAtZero
[ 1] <TimerFired> GettingDeviceDescriptorInEnumAtZero
[ 0] <No> WaitingForPostReset1ExtendedTimer

1) I'm confused as I updated the most recent logitech webcam driver for my webcam? Theres these recent downloads for the camera but they all seem like programs and nothing to do with real drivers for the camera: https://support.logitech.com/en_us/product/hd-pro-webcam-c920/downloads

So you're saying to see if i can update it and put it in a usb 2 port? I didn't even realize it was in a usb 3, thanks for the heads up I guess.

2) There is nothing running at port 4. Also from the viewer I don't think I have any usb 2 slots. https://i.imgur.com/d03wzpC.png

But in the same image looks like port 6 is corrupting?

3) Would the video device be the webcam? I assume so right? But in the USB viewer it shows port 6 is the issue but port 14 (the webcam) is fine

Also I checked the back of my computer and they're all listed there everything that is plugged in seems to be fine so yeah it might be that

This is what it shows in device manager after the instructions from google https://i.imgur.com/1yU7xPn.png

Should I just remove/uninstall the port driver?

 

[JayTee3]

yes, uninstall the port, windows plug and play will reinstall the driver a few seconds later. see if it still thinks there is a device connected when it reinstalles. (hopefully it will not bugcheck)
you might also go in bios and see if there is anything special about that port. one port may chain together a bunch of other ports. since you have a usb3 and a usb 3.1 port your usb 2 devices might be emulated by the usb 3.1 device.
if it has bugs in the chip or driver it might not work correctly. you should check to see if your motherboard has a update for the intel cpu chipset and the asmedia 3.1 usb chipset.
(these also depend on the bios version so you would have to make sure the bios is current)
the intel usb 3 ports are more likely to have fewer bugs since the driver will get updated via windows update.

How would I do this in BIOS?

 

[johnbl]

you would do this in control panel device manager. right mouse click to bring up the menu


if you disable hardware in bios, then windows will not see the hardware.

yes, uninstall the port, windows plug and play will reinstall the driver a few seconds later. see if it still thinks there is a device connected when it reinstalles. (hopefully it will not bugcheck)
you might also go in bios and see if there is anything special about that port. one port may chain together a bunch of other ports. since you have a usb3 and a usb 3.1 port your usb 2 devices might be emulated by the usb 3.1 device.
if it has bugs in the chip or driver it might not work correctly. you should check to see if your motherboard has a update for the intel cpu chipset and the asmedia 3.1 usb chipset.
(these also depend on the bios version so you would have to make sure the bios is current)
the intel usb 3 ports are more likely to have fewer bugs since the driver will get updated via windows update.

How would I do this in BIOS?

 

[JayTee3]

you would do this in control panel device manager. right mouse click to bring up the menu


if you disable hardware in bios, then windows will not see the hardware.

yes, uninstall the port, windows plug and play will reinstall the driver a few seconds later. see if it still thinks there is a device connected when it reinstalles. (hopefully it will not bugcheck)
you might also go in bios and see if there is anything special about that port. one port may chain together a bunch of other ports. since you have a usb3 and a usb 3.1 port your usb 2 devices might be emulated by the usb 3.1 device.
if it has bugs in the chip or driver it might not work correctly. you should check to see if your motherboard has a update for the intel cpu chipset and the asmedia 3.1 usb chipset.
(these also depend on the bios version so you would have to make sure the bios is current)
the intel usb 3 ports are more likely to have fewer bugs since the driver will get updated via windows update.

How would I do this in BIOS?

So do I disable it or go into bios and check first? I'm not sure what u said, it sounded like u said i should go into bios and see if it will break any other usb ports if i disable that port before uninstalling it in device manager?

 

[johnbl]

I would use control panel device manager first, to delete the device and let plug and play reinstall it.
if that does not help, I would look at the options in bios for the device. There could be some option to force certain version support, or to turn off certain ports.

you would do this in control panel device manager. right mouse click to bring up the menu


if you disable hardware in bios, then windows will not see the hardware.

yes, uninstall the port, windows plug and play will reinstall the driver a few seconds later. see if it still thinks there is a device connected when it reinstalles. (hopefully it will not bugcheck)
you might also go in bios and see if there is anything special about that port. one port may chain together a bunch of other ports. since you have a usb3 and a usb 3.1 port your usb 2 devices might be emulated by the usb 3.1 device.
if it has bugs in the chip or driver it might not work correctly. you should check to see if your motherboard has a update for the intel cpu chipset and the asmedia 3.1 usb chipset.
(these also depend on the bios version so you would have to make sure the bios is current)
the intel usb 3 ports are more likely to have fewer bugs since the driver will get updated via windows update.

How would I do this in BIOS?

So do I disable it or go into bios and check first? I'm not sure what u said, it sounded like u said i should go into bios and see if it will break any other usb ports if i disable that port before uninstalling it in device manager?