Problem with new USB devices not working
Problem with new USB devices not working
I would also remove this driver:
\SystemRoot\system32\pwdrvio.sys Mon Jun 15 18:43:45 2009
old partition wizard driver.
you can run a uninstaller or download and run microsoft autoruns64.exe and delete the entry.
https://learn.microsoft.com/en-us/sysint...s/autoruns
note: you also have some other rarely used drivers installed:
like
HttpDebuggerSdk.sys Fri Mar 30 05:53:50 2018
(just fyi)
----------
looks like the system is waiting for access to a resource that is being used by
mrcbt.sys Mon Sep 2 02:05:35 2024
(macrium driver to monitor file system)
I wonder what this driver could be for:
\SystemRoot\System32\drivers\CLFCL5.21\000.fcl Wed May 18 22:25:38 2016
(old date and strange name 000.fcl)
looks like it is related to powerdvd software
bugcheck shows a corrupted stack with a error code in it:
the error was
0: kd> !error 0xc00000bb
Error code: (NTSTATUS) 0xc00000bb (3221225659) - The request is not supported.
it might be a case where a device went to sleep and could not wake. ( set the system to high performance and reboot to work around the problem until you get a fix)
------------
3rd party defrag software running.
device driver failing install.
you might want to start cmd.exe as an admin then run
net.exe /stop "plug and play"
then go and uninstall the 3rd party defrag software and what ever software plug and play was failing to install.
I would then go into windows device manager, find the option to show hidden devices, enable it then delete any greyed out entries in the list.
if you change the memory dump to kernel, I can read what windows plug and play was failing to install. (if you provide the kernel dump)
most likely a old driver, plug and play detects the device, attempt to install the driver and fails, times out and detects it again 4 minutes later and tries again. This often happens if some software tries to use the driver while it is being updated. code it run on different cores (the installer on one core, and the process that attempts to use the device on another core)
You might guess that it is the defrag software and stop it so that the install/update will complete. USB devices will install the driver on each USB port the device is connected to.
note: run
net.exe start "plug and play"
after you do the cleanup or stop the defrag program.
(or you can just reboot)
machine info:
0: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=2599]
BiosMajorRelease = 5
BiosMinorRelease = 17
BiosVendor = American Megatrends International, LLC.
BiosVersion = 3.B0
BiosReleaseDate = 05/12/2021
SystemManufacturer = Micro-Star International Co., Ltd
SystemProductName = MS-7C02
SystemFamily = To be filled by O.E.M.
SystemVersion = 1.0
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = Micro-Star International Co., Ltd
BaseBoardProduct = B450 TOMAHAWK MAX (MS-7C02)
BaseBoardVersion = 1.0
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3600
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3600 6-Core Processor
Update Status = REG_DWORD 1
VendorIdentifier = REG_SZ AuthenticAMD
0: kd> !sysinfo cpumicrocode
Initial Microcode Version: 00000000:08701021
Cached Microcode Version: 00000000:00000000
Processor Family: 17
Processor Model: 71
Processor Stepping: 00
Note: Cached Microcode Version is not detected!
you can create a live kernel dump and I will take a look at it.
normally I would look at memory.dmp file that is made when the system bugchecks. It has all of the kernel, usb and plug and play info contained in it. I can look at your live kernel dump if you reboot and have the problem occurring at the time of the dump.
my first fix attempt would be to remove any old drivers that deal with file system. (partition wizard)
I would also update the macrium driver. most of the time with a stack like that, it is the named driver that corrupted the stack.
(looks like a driver bug. where they did not check the return code)
from the minidump there were 5 processes waiting for access that was being held by the macrium driver. (check for update)
you also have an older driver:
fltsrv.sys is the Acronis Storage Filter Management Driver from 2015 that often leads to a driver power state failure issue.
check the bug details:
fltsrv.sys Tue Nov 3 08:22:47 2015
such drivers could interfere with the macrium driver.
for updates, refer to this site:
https://care.acronis.com/s/article/1541-...uage=en_US
If applicable, you may choose any GNU/Linux distribution you prefer. For example, Linux Mint serves as a solid alternative to Windows. However, if you aim for a minimal setup, Debian is a viable option.
With GNU/Linux, you have the freedom to tailor it according to your needs. Many distributions still offer long-term support without any additional cost.
To ensure Win10 receives extended security updates, opt for the Home/Pro edition and consider purchasing the ESU.
Further reading:
https://learn.microsoft.com/en-us/window...ty-updates
But obtaining Win10 IoT Enterprise LTSC for personal use is not advisable, as it provides support until 2032-01-13, which may not be legally or ethically acceptable.
Do you have permission from Microsoft to perform an OS backup?
🙄
I don’t believe so.
According to the Windows IoT Enterprise EULA:
https://learn.microsoft.com/en-us/window...-agreement
It clearly states:
How did you obtain this Windows IoT Enterprise?
🤔
You might have upgraded from a previous Windows install and then used a key from the black market to activate it.
If that’s the case:
And regarding your USB connection problem, it likely stems from this:
Nevertheless, this restriction should be maintained because:
As mentioned earlier;
This is your only choice concerning support. Reach out to the device manufacturer or the company’s IT department responsible for the OS.