Windows 10: Frequent Random BSODs with different Errors

**axe0** · 24 Feb 2017

@BSODHunter, what makes you think that the issue is not a driver problem?

**Xinef** · 24 Feb 2017

Uninstalled RivaTuner, but couldn't find Intel Extreme Tuning Utility. Don't think I've installed that before.

Ran FurMark, did not notice any artifacting, max temperature reached 81 C. Was not sure how long to run it, but I stopped at around 20 minutes.

And... after I stopped the test, realized there was no log saved. Didn't take a screen shot, thought a log will be produced. If you need me to do it again, I will run it sometime this weekend again.

**Xinef** · 26 Feb 2017

Another one, same thing, playing D3 PTR and had Spotify running.

**axe0** · 26 Feb 2017

Check MSI for LAN driver updates.

Code:

0: kd> lmvm e2xw10x64
Browse full module list
start             end                 module name
fffff805`3a690000 fffff805`3a6b9000   e2xw10x64 T (no symbols)           
    Loaded symbol image file: e2xw10x64.sys
    Image path: e2xw10x64.sys
    Image name: e2xw10x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Sep 14 22:52:26 2016 (57D9B88A)
    CheckSum:         00030598
    ImageSize:        00029000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

**Xinef** · 26 Feb 2017

Downloaded the latest drivers from MSI site, but seems like I already have the latest version. Did an uninstall of the driver and Installed it again. Will report back is anymore BSODs occur.

**Xinef** · 12 Mar 2017

Haven't had any BSODs during game play, but had one last night, when I was shutting off my PC.
As soon as I hit Shut Down, it froze and Blue screen came up.
Attached logs.

**BSODHunter** · 13 Mar 2017

Sorry, theres really no information in the dump file this time. the bugcheck code itself says that it can be driver or hardware related. Also I cant see something in the eventlog.

**axe0** · 13 Mar 2017

Diagnostic Test Frequent Random BSODs with different Errors

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

**BSODHunter** · 09 May 2017

Is there any news or did you fix the problem?

Windows 10: Frequent Random BSODs with different Errors

Posting Permissions