F5F Stay Refreshed Hardware Desktop Random Crash and BSOD

Random Crash and BSOD

Random Crash and BSOD

Pages (2): Previous 1 2
J
JamTheJoker
Member
102
01-24-2021, 02:27 PM
#11
some driver caused memory corruption and led to a network service crash.
likely culprit is the file located at C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys dated June 9, 2022 (possibly a burner version).
i plan to install Microsoft Autoruns64, find the driver and either disable or uninstall it.
https://learn.microsoft.com/en-us/sysint...s/autoruns
i also updated the Realtek network adapter for my motherboard (rtcx21x64.sys released October 3, 2021).
a newer Realtek driver is available from 3-10/2025.
notes:
C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys Thu Jun 9 00:43:50 2022
rtcx21x64.sys Sun Oct 3 23:54:20 2021
CtiAIo64.sys Mon Jul 8 19:39:21 2024
IOMap64.sys Mon Dec 2 00:42:15 2024
AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024
J
JamTheJoker
01-24-2021, 02:27 PM #11

some driver caused memory corruption and led to a network service crash.
likely culprit is the file located at C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys dated June 9, 2022 (possibly a burner version).
i plan to install Microsoft Autoruns64, find the driver and either disable or uninstall it.
https://learn.microsoft.com/en-us/sysint...s/autoruns
i also updated the Realtek network adapter for my motherboard (rtcx21x64.sys released October 3, 2021).
a newer Realtek driver is available from 3-10/2025.
notes:
C:\WINDOWS\SysWOW64\DRIVERS\TbsbIo64.sys Thu Jun 9 00:43:50 2022
rtcx21x64.sys Sun Oct 3 23:54:20 2021
CtiAIo64.sys Mon Jul 8 19:39:21 2024
IOMap64.sys Mon Dec 2 00:42:15 2024
AMDRyzenMasterDriver.sys Mon Sep 2 23:16:28 2024

V
Venpirman
Member
219
01-26-2021, 10:04 AM
#12
when you first start using verifier, it's best to limit its execution to the next boot. you can achieve this by setting a command line switch /bootmode oneboot. then you would open cmd.exe with admin privileges and run something like verifier.exe /all /bootmode oneboot. this process will initiate a boot, and if the system fails it creates a memory dump while verifier remains active, allowing a normal reboot without needing to enter safe mode or type verifier.exe /reset. there are additional boot mode configurations that may be helpful: https://learn.microsoft.com/en-us/window...mmand-line. it's also worth noting that excluding certain drivers from checks can be beneficial. verifier often highlights the first problematic driver and initiates a bug check, but it might not be the actual issue. you can modify the command with /driver.exclude to skip those drivers and focus on others.
V
Venpirman
01-26-2021, 10:04 AM #12

when you first start using verifier, it's best to limit its execution to the next boot. you can achieve this by setting a command line switch /bootmode oneboot. then you would open cmd.exe with admin privileges and run something like verifier.exe /all /bootmode oneboot. this process will initiate a boot, and if the system fails it creates a memory dump while verifier remains active, allowing a normal reboot without needing to enter safe mode or type verifier.exe /reset. there are additional boot mode configurations that may be helpful: https://learn.microsoft.com/en-us/window...mmand-line. it's also worth noting that excluding certain drivers from checks can be beneficial. verifier often highlights the first problematic driver and initiates a bug check, but it might not be the actual issue. you can modify the command with /driver.exclude to skip those drivers and focus on others.

J
josiecatz__10
Senior Member
640
01-26-2021, 11:19 AM
#13
Thanks to everyone, I chose to purchase a new PC and eliminate this mystery.
J
josiecatz__10
01-26-2021, 11:19 AM #13

Thanks to everyone, I chose to purchase a new PC and eliminate this mystery.

Pages (2): Previous 1 2