Windows 10: BSOD on clean install of Windows 10 Pro. Unknown Trigger, Need Help

I have received my first BSOD after a clean installation of Windows 10 Professional only after a couple hours of leaving it idle with a video game downloading in the background (via GOG Galaxy). I'm not sure what the trigger is. This has become all to familiar after making the switch to Windows 10 from 8. I have noticed I only seem to get crashes or instability after installing any NVIDIA driver after 353.62. This clean install, I decided to install all the latest drivers for everything including my videocard (358.50), being hopeful that all the other times were a fluke. I'm stuck, I don't know what to do, I don't really want to revert to windows 8, I enjoy 10 too much.

TL/DR: BSOD on clean install of windows 10 only after few hours. Suspect latest NVIDIA drivers. ALL Hardware(s) (temperatures too) are fine, tested ALL individually on other PC's.

Computer Specs: Attachment 44231

This is my Motherboard


This is my Videocard(s)


This is my Power Supply

could it be software conflicts?

:)

 

Blue Screen While Playing Online Games

Hello, I have recently upgraded from Windows 10 Pro 64-Bit Build 10240 to Windows 10 Pro 64-Bit Build 10586.3. A BSOD is always being triggered when I play online games. The BSOD usually occurs during loading and it has an error message of " KMode_Exception_Not_Handled
caused by dump_wmimmc.sys ".

What is the root cause and the possible solution?

By the way the online game that I play is CABAL Online and this is the only game in my PC that triggers BSOD. Other games work normally aside.

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (storahci.sys) crash in Windows 10

As I stated in my initial question, I performed a clean install of Windows 10 Pro. I had 8.1 previously, and reformatted and installed 10. The computer is activated. Everything worked great for 3 weeks before the BSOD crash began. Please let me know if you
need anything else from me. Thanks for your help.

Ryan

 

How many BSODs have you received so far? There is only one dump in your logs which is blaming your nVidia driver, did you perform a clean install of your GPU driver when you updated it?

You also state Videocard(s). Are you running a single GPU or are you in SLi?
Code: BugCheck 116, {ffffe001c55d44c0, fffff800af2f3384, ffffffffc000009a, 4} Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+a43384 ) Followup: MachineOwner --------- 3: kd> lmvm nvlddmkm start end module name fffff800`ae8b0000 fffff800`af3a4000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Sat Oct 03 03:08:52 2015 (560F38B4) CheckSum: 00ABDFB7 ImageSize: 00AF4000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Hi Calcifer,

What are all those links in the hosts file and why are they there?
There are over 25.000 links in the hosts file *Shock

 

Good spot, some of them are pretty... non-family friendly too. Even dangerous.

 

[/quote] Attachment 44240.
I have received only one that I'm aware of.
I'm running two 780Ti's in SLI Configuration and the drivers were a clean install.

 

The modified host files are to block specific websites and ads. Pulled from here (Using a Hosts File To Make The Internet Not Suck (as much))

 

Can you uninstall one card for testing purposes and test the system. Once you're satisfied all is good reinstate the SLi configuration.

 

I can try that but, these crashes are unprovoked and unspecific so I don't know how to replicate the situation to test it anyways.

 

It could just be the SLi setup in general, I seem to recall it happening before. One crash isn't a lot to work from in this case admittedly, feel free to run the system as it is until you encounter more BSODs if you like then upload new logs. It's definitely blaming your nVidia driver though.

 

I'm going to try and continue using the SLI configuration, see if it happens again, and then without the SLI configuration, so there are a little more crash logs to work with.