[SOLVED] VLC Media Player BSOD - SYSTEM_THREAD_EXCEPTION_NOT_HANDLE dxgmms2.sys

A

aeoip2

Member
Joined
May 29, 2017
Posts
5
This was a BSOD that I had a a few months ago, before I installed the Creaters update. If anyone is familiar with the VLC media player program , I was using the clone feature to test CPU/GPU performance. I set the value to 100 then my computer ran into a BSOD. I tried to re-create the problem and it indeed happened again. I'm pretty sure this BSOD was my fault i caused intentionally. Can anyone please analyze the crashdump to find out what really happened?

Windows 10 Pro x64
Intel 6850k stock speeds
MB: Gigabyte GA-X99-Ultra gaming
Nvidia EVGA 1080
 

Attachments

Similar to your crash in your other thread. This one had more possible culprits, but the NVIDIA driver was at the top of the stack.


STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
 
writhziden said:
Similar to your crash in your other thread. This one had more possible culprits, but the NVIDIA driver was at the top of the stack.


STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control
Click to expand...

So based on those 2 BSODs, my system you think is okay? I ran memtest86 before when I built this computer and showed no errors. This is actually the third time I had a BSOD happen on this computer, this would be the first 2, and then the 3rd in the other thread. Then would this be a problem with the Nvidia driver , like a bug?
 
aeoip2 said:
So based on those 2 BSODs, my system you think is okay? I ran memtest86 before when I built this computer and showed no errors. This is actually the third time I had a BSOD happen on this computer, this would be the first 2, and then the 3rd in the other thread. Then would this be a problem with the Nvidia driver , like a bug?
Click to expand...
It's difficult to say since your BSODs are not too frequent and seem to be have been caused by hardware/software interfaces through Windows. It could be as simple as the Intel Turbo Boost and VLC programs not linking properly with the 1080 since it is a newer adapter. See how the system behaves over the next few weeks and report back if you have any issues outside of those programs.
 
aeoip2 said:
....Then would this be a problem with the Nvidia driver , like a bug?
Click to expand...

It could be a bug in a NVIDIA driver - but very unlikely. If so, that would be up to NVIDIA to fix. The bottom line for you though - you are not running the same version of the NVIDIA driver that you were at the time of the 2 BSODs 4 months ago, so anything involving that NVIDIA driver version is a moot point now.

NVIDIA is very good about updating their drivers. I would think if a bug existed on a recently released driver, there would be a literal ton of posts/complaints across the Internet on NVIDIA driver version XX.XX.XX -- and I just don't see that at this time. I honestly cannot recall the last time that NVIDIA released a new driver and had to issue a new version quickly thereafter due to a bug. A lot of testing goes into new drivers prior to release, including certain Windows tests -- like Driver Verifier.

https://www.sysnative.com/forums/bs...er-bsod-related-windows-10-8-1-8-7-vista.html

If you do believe your NVIDIA driver has a bug, keep on the lookout for a new (or beta) driver to install or revert to a previous version that you know worked.

I agree with Mike (Admin writhziden) 100% - having 2 BSODs over 4 months ago involving NVIDIA and possibly DirectX and not a peep since means that you have no system trouble at this time.

According to the dxdiag report (DirectX Kernel Diagnostics) that you submitted in post #1, your current NVIDIA driver:
Code: 
[U]VIDEO[/U]
Driver Date/Size: [COLOR=red]4/30/2017[/COLOR] 5:00:00 PM, 885032 bytes

The 2 BSODs occurred nearly 4 months ago on the same day within 10 minutes of each other on:
Code: 
Sat [COLOR=#ff0000]Feb 11[/COLOR] [COLOR="#0000FF"]17:32[/COLOR]:17.672 [COLOR=#ff0000]2017[/COLOR] (UTC - 4:00)
Sat [COLOR=#ff0000]Feb 11[/COLOR] [COLOR="#0000FF"]17:42[/COLOR]:20.942 [COLOR=#ff0000]2017[/COLOR] (UTC - 4:00)
The NVIDIA driver installed at the time of the two February 2017 BSODs:
Code: 
nvlddmkm.sys Fri [COLOR=#ff0000]Jan 20[/COLOR] 08:29:59 [COLOR=#ff0000]2017[/COLOR] (588210D7)

Again, as Mike said - You really have nothing to be concerned about at this point in time.

The updated NVIDIA driver likely solved the BSOD issue.

If you happen to encounter new BSODs, then by all means - please come back, create a new thread after following the https://www.sysnative.com/forums/bs...ng-instructions-windows-10-8-1-8-7-vista.html and we'll be glad to help.

Regards. . .

jcgriff2
 
Alright , so after 2 weeks of use I haven't had a BSOD happen on me yet. Also note that never have I yet experienced a single BSOD happen WHILE gaming , since the 5/6 months I have built this computer. And I have ran memtest with no errors after I built it. So in my opinion i think the Nvidia drivers are pretty stable, and I dont think it's the RAM either . I've been installing Nvidia driver updates ever since. At this point , i'm predicting if I mess with Intel/VLC again that BSOD is going to happen. I don't know if it's a bug in their software, with Microsoft Direct X or Nvidia. But i wouldnt know too much about it.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top