Windows 10: KMODE_EXCEPTION_NOT_HANDLED BSoD while playing XCOM

I can't seem to catch a break. I have tried numerous solutions and it's getting to the point where I feel like my lack of understanding is leading me to potentially making a mistake that might cost me more than it helps in the long run. The nvlddmkm.sys file has a lot to do with it but I'm also seeing ntoskrnl.exe. I thought it was a driver issue but I keep trying to troubleshoot and nothing works. I checked my listed specs on here and I think it's mostly up to date.

:)

 

BSOD Memory_Management and other

Just had another BSOD, this time it was a KMODE_EXCEPTION_NOT_HANDLED. Was playing Guild Wars 2 while Firefox was open playing a video on Youtube.

another minidump

 

Fresh install, 4 different BSOD's

So, I managed last night to play both Xcom and the updated version of Dying light (which previously had hangs and freezes) for over two hours total, that's a huge change, and the only thing I did was tweak graphics settings in the game itself. However, after
an hour or so of playing Xcom today, I had a BSOD, a repeat as the machine tried to reboot, and then again when I tried to open chrome and skype to write this. Only the first BSOD created a dmp though.

Link to latest bsod: https://onedrive.live.com/redir?resid=3E2BBFAB9B78F356!872&authkey=!ANfX_soyYxHhE_4&ithint=file,dmp

Also, have had speccy running anytime I do anything, temps definitely weren't too high.

 

Hello *Smile

The BSOD files do indicate the graphics driver. If you have not yet done a full uininstall followed by installing the minimum drivers necessary please do this to see if it helps.

The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

 

Okay I ran the uninstaller in Safe Mode, and now I'm getting the latest driver, I will restart in safe mode and then select to do a clean install. I haven't run that uninstaller before so I am optimistic, I will let you know what happens. Thank you for your quick response.

 

When I did the reinstall I selected to do a clean installation. I unchecked the 3D vision driver as well as the HD audio driver and just installed the graphics driver. There was no PhysX driver listed so I am assuming that is included with the graphics driver.

 

Okay so between my various tasks today I had about 2 hours to test the stability now that I've replaced the drivers. The game suffered a CTD after the first hour, but I figured it was due to the previous BSOD issues. I verified file integrity and sure enough steam found a missing file so I let it redownload and played for another 45 mins or so with no apparent issues. Is there anything I should do? I have the GPU performance test program and I haven't run a chkdisk in a while. Should I toe the line and just hope for the best or should I be responsible?

 

It will not hurt to run a Furmark GPU test provided you monitor the GPU temperature and abort the test if it goes above 80°C/176°F.

Chkdsk is also worth running to verify your disks are all OK. Follow the procedure in this tutorial: Drive Error Checking in Windows 10

 

Thank you very much! I will do both of those things, but for now I'm marking this as solved! So very appreciated.

 

I just had another crash and decided to run furmark and I got to 80°C very quickly.

 

Post a new set of log files then we can take a look at what happened.

The GPU can tolerate short periods of up to 95°C but I prefer to keep them at around 80-85°C max. Perhaps try running with the case open or add another system fan.

 

Okay I've updated the attached crash log in the initial post with the most recent data. If you need me to I can attach it to a new reply. What perplexes me about all of this is that I've been able to run Doom IV and if memory serves it was no problem. Is it possible to have a technological hex of some sort that causes a person to never have good luck with computers? Is there a ritual I can do? I'm half kidding...

 

Hey,
Okey so you are still getting BSODs after using DD uninstaller.

Code: *** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : nvlddmkm.sys ( nvlddmkm+261d39 ) Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_f37f8f12da8b10d7\nvlddmkm.sys Image name: nvlddmkm.sys Browse all global symbols functions data Timestamp: Thu Mar 16 23:38:26 2017 (58CB13E2) *** WARNING: Unable to verify timestamp for hcmon.sys*** ERROR: Module load completed but symbols could not be loaded for hcmon.sys hcmon+0x318a Image path: \SystemRoot\system32\DRIVERS\hcmon.sys Image name: hcmon.sys Browse all global symbols functions data Timestamp: Thu Aug 18 07:43:53 2016 (57B54B19) *** WARNING: Unable to verify timestamp for CMUSBDAC.sys*** ERROR: Module load completed but symbols could not be loaded for CMUSBDAC.sys CMUSBDAC+0x12e823 Image path: \SystemRoot\system32\DRIVERS\CMUSBDAC.sys Image name: CMUSBDAC.sys Browse all global symbols functions data Timestamp: Tue Nov 29 05:30:23 2016 (583D045F)[/quote]

i can see references in the stack to hcmon.sys (VMware). I also found a reference in the stack to a DAC Device driver (cmusbdac.sys) by looking at the manufactors webiste there might not be any windows 10 drivers for the device.

So I would suggest uninstalling VMware and the USB DAC device or update them. please note that I'm just getting into analysing BSODs so you might wanna wait for Philc43 to get back to you.

 

I found a VMware listed in my drivers and removed it. I don't know how to find the USBDAC driver and I don't know what USB device it is referring to. Is it my old Kinect? maybe. I think I will unplug it just to be safe. I was messing around with the developer tools for it for a while.

 

Okay so you did find the VMware driver.

It's some kind of digital-to-analog converter USB device. I doubt that it's the kinect.

A DAC Device tend to be connected into a sound amplifier. I don't know if some USB headsets have a DAC built in. In that case it might be a USB headset.

I'm afraid that I'm not sure where you could find an updated version of the driver.