[Win10x64] Frequent freezes sometimes BSODS fairly consistent for months.

[chalicex]

· OS - Win 10
· x64
· What was original installed OS on system? Win 10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Purchased myself
· Age of system (hardware) Purchased last september other than the 2 spare hard drives pulled from my other system
· Age of OS installation - have you re-installed the OS? Current installation about 2 weeks old maybe, I don't remember. Have reinstalled a few times trying different things to possibly fix it.
,
· CPU - Ryzen 1700
· Video Card - 1080ti
· MotherBoard - Asus ROG Crosshair VI Hero
· Power Supply - brand & wattage - 750w EVGA Gold

Nothing in particular seems to happen before crashes, frequency from anywhere between once or twice a day, sometimes I go 2 weeks without a crash. Have run memory diagnostics, hard drive diagnostics, no errors there. Have attempted to run Driver Verifier but it error'd out almost immediately and bricked windows and had to reinstall again.

 

[jcgriff2]

Most of the dumps list USBXHCI.sys as the probable cause.

It is a Microsoft USB 3.0 extensible host controller driver. It can only be updated/patched via Windows Updates.

Driver Reference Table (DRT) | USBXHCI.sys

Since it is a Microsoft Windows driver, it cannot be the cause. It is listed in the dumps as a default of sorts. Either a 3rd party driver is hiding behind the Microsoft driver or unknown hardware failure is the actual cause.

.... Have attempted to run Driver Verifier but it error'd out almost immediately and bricked windows and had to reinstall again.

We need to get the mini kernel memory dump from this BSOD. Driver Verifier's job is to check drivers and force a BSOD when it comes upon a 3rd party driver that fails its checks. It obviously found a rogue driver -- or you have unknown hardware failure. Unfortunately, the dumps are incapable of telling us which piece of hardware has failed. Dumps are only good for figuring out software problems.

Can you connect the SATA HDD to another system and copy out the \windows\minidump folder? (Whichever drive you installed Windows onto).

When Driver Verifier flags a driver, it disables it. In your case, either a boot driver or one that is vital to Windows was flagged.

Did you select only non-Microsoft drivers?

Also, I see that you have 2 SSDs. Go to the manufacturer's support site and install any firmware upgrades.

Your SSDs:

Samsung SSD 850 EVO 500GB
SAMSUNG SSD PM800 2.5" 128GB

SSD Tools & Software | Download | Samsung V-NAND SSD | Samsung Semiconductor Global Website

Download - Find By Type or Product | Samsung V-NAND SSD | Samsung Semiconductor Global Website

Lastly, assuming that USB is involved in your BSODs, what is plugged into the USB ports?

Regards. . .

jcgriff2

 

[chalicex]

I do not currently have a working second system to plug it into to try to get the minidump folder. When I ran Driver Verifier I followed the steps listedon the site mostly I believe, followed the steps from someone else but most appeared to be the same. Selected only Non-Microsoft drivers.

I will update the firmware for the 500GB SSD, but can't find much information for the 128GB one so I will try to just disconnect it entirely as I don't really use it for much anyway.

For USB devices I just have my mouse wireless G602, keyboard Steelseries 750, samson c01U microphone, and occasionally a ps4 controller.

I do run with a moderate overclock on the cpu, but I still get crashes running at full bios defaults, any combination of settings, ram speeds, etc. The problem is mostly that even with a more aggressive overclock or none at all I can do burn tests for cpu/gpu/ram all night or longer and never get a crash. Completely stable, only issue I've noticed is the GPU power draw fluctuates a fair bit, but the 12v rail on my psu seems to be within specs so I'm not sure if it's worth going out and buying a better psu. But all my crashes appear during very mild use. It has never crashed while idle. For drivers I've tried a fresh install with letting windows handle all drivers, not even using my motherboard manufacturer provided ones and still crash. Since writing the post I have only crashed one additional time, exact same error code in the dump, occurred while playing a game of league of legends. I'll update the SSD firmware and stay in touch, thank you so much for your time.

 

[jcgriff2]

For USB devices I just have my mouse wireless G602, keyboard Steelseries 750, samson c01U microphone, and occasionally a ps4 controller.

I do run with a moderate overclock on the cpu, but I still get crashes running at full bios defaults, ....

Does the microphone require a 3rd party (non-Microsoft) driver? If so, please make sure that it is updated.

I would normally suggest resetting BIOS to default settings (re: over-clocking), as the o/c could cause BSODs &/or different bugchecks when BSODs do occur.

If there is ever a way to get the VERIFIER_ENABLED dump after a BSOD but before reinstalling Windows - please do so. It may very well contain the answer here, namely the name of the offending 3rd party driver. If the VERIFIER_ENABLED dump were to contain (flag) a Microsoft driver, then we know the crashes are definitely caused by unknown hardware failure.

Lastly - your installation technique is perfect by allowing Windows to locate and install drivers for all of your devices. Usually, the only drivers that Windows cannot locate are those related to a laptop's keyboard or some video and audio devices.

Also, glad that you got the firmware upgrade installed. Out-of-date firmware for SSDs can absolutely cause BSODs and wreaked havoc on us and users several years ago when the SSD market exploded in popularity.

Regards. . .

jcgriff2