Windows 10 BSOD System_Service_Exception dxgkrnl.sys

I've been getting bsod's for quite a while now on windows 10 preview builds but so far those seemed to occur because of a Realtek driver. Maybe some bsod's were also related to the current ones so here is a link to a topic in which I submitted those.

Lately I've been having Bsod's on the day or day after I install a new geforce driver. I'm using 2 GTX 560 TI's SLI mode in build 10130. Geforce 350.12 seems to be stable through multiple windows 10 builds and no bsod's happen while I'm on this driver. All installs of geforce drivers explained below I did with a clean install as option through the nvidia installer, but I've also used Display Driver Uninstaller (DDU) multiple times, but this did not help with anything.

When I'm updating to 353.30 (or the hotfix version 353.38) this will make me get a bsod message in a few hours after use, with the latest occurence within 5 minutes after installing 353.30. Often when this Bsod shows, after restarting the computer it will work for a few minutes, then bsod again with the same message and will continue doing this until a message from windows shows saying something like ''it seems you are having difficulties starting up, would you like to...." and I get the option for going back to a Restore point.

These restore points usually save the day and the geforce driver will be put back to 350.12. This also helps with restore points which were created just that day so it's unlikely more factors are included which can cause the bsod's.

There are some problems with turning SLI on with the new drivers which makes me suspect that they have an influence on the bsod. First of all getting to the nvidia configuration screen with SLI options almost never works after a (clean or not) install of 353.12. It always takes me multiple reinstalls of the driver to be able to turn SLI on. Otherwise this tab within the nvidia configuration screen will only show PhysX configuration (instead of the full "Configure SLI, Surround and PhysX").

Yesterday when I received driver 353.30 through windows update, SLI was yet again disabled and I didn't bother to go reinstall this same driver for getting the SLI options. However doing so I did not get any bsod for a full day. Now after this day I did reinstall 353.30 a few times in order to get the SLI option and within minutes of turning it on I got the bsod message again.

I know that one day of going without a bsod isn't any proof at all for SLI being the culprit, but since SLI seems to be a difficult thing to turn on anyway it might lead to something.

For now I can only supply you with 1 dump + specs of an hour ago here, since Ccleaner did its job too well and deleted the other bsod's from over the weeks :P As I mentioned in the beginning of the post there are some other dumps in the other topic.

I was fine with sticking to 350.12 for a while since that driver is working well for me on windows 10, but as of yesterday I'm getting the windows 10 driver 353.30 forced through windows update so I can not stick with that unless I reinstall it every single day after a Windows Update. With Windows 10 less than a month away I would like to know if there is something on my end that I can do against these bsod's.

Thanks in advanced, Flippiej.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello Flippiej,

Thank you for posting your question on Microsoft community.

I would like to know some information about the issue so that we could help you better.

What is the make and model of your computer?

I appreciate you for providing details about the issue and your efforts towards resolving it.

If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss.

This issue may occur either due to corrupt display driver or if BIOS is not up to date.

I would suggest you to uninstall and reinstall display driver and check. Please follow these steps:

a. Press Windows + X keys together and click device manager.
b. Click to expand display adapters.
c. Right click the adapter and click uninstall.

You may need to restart the computer afterwards.

Now, you may reinstall the latest display driver from the computer manufacturer's website.

You may refer this article:
Download and install drivers
http://windows.microsoft.com/en-us/windows-8/all-drivers
(Also holds good for Windows 10)

Please also update BIOS from the manufacturer's website and check the issue.

Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.

I hope this information helps.

Please do let us know if you need any further assistance.

Thank you

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi, thanks for your fast reply.

I will put down some specs of my computer, but I've also included a msinfo32 save file with the dump in my previous post.

  • Motherboard: Gigabyte GA-Z68X-UD3H-B3 rev. 1.3
  • Bios: F12 (latest non-beta one)
  • Processor: Intel core i5-2500k @ 4.0GHz (turbo OC in BIOS)  
  • RAM: Corsair Vengeance 8GB(4x2GB) DDR3 1600MHz 
  • Videocards: MSI GTX 560 Ti, 1GB, Twin FrozrII (no OC), MSI GTX 560 Ti, 1GB, Hawk (no OC)
  • PSU: CoolerMaster GX 750W
  • Soundcard: onboard one from realtek that is with the motherboard
  • Sound system: Logitech Z-10
  • Monitors: Samsung Syncmaster P2470HD, Benq GL2450
  • Keyboard: Logitech G110
  • Mouse: Logitech G500
  • SSD: Samsung 840 EVO 250GB (main drive) ; OCZ Vertex 3 Max Iops 120 GB
  • Webcam: Logitech (yes yes I know it I have a lot of logitech devices :P ) HD C525

I've just used your described method for removing the display driver. Afterwards I used windows update for the geforce driver update since the one that comes through windows update is the latest one also on the nvidia website(353.30).

While updating this driver through Windows Update I also received the new Slow Ring build 10162. Upon starting with the new build I was able to turn on SLI without having to reinstall the geforce driver and I've had no bsod yet (45 minutes and counting).

As for your BIOS suggestion, I'm now on version F12 and there is a later version of my Bios to install, but this version is a beta driver for uefi in 2013. F12 is the last official stable release from 2012 and I prefer to not use something that's beta for my BIOS, while F12 has been running fine for years. Especially since there won't be any new updates.

I have tweaked my BIOS settings a little bit, as in that I've changed the turbo settings for my CPU to 4.0 GHz. This is the only thing that is different from the default settings and this also has been stable for a year or two. If you want I can change this back to test it... but I prefer to now wait and see if the new preview build that I'm using changes anything.

5 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Flippiej,

Thank you for your response.

It is good that BSOD has not reappeared.

I appreciate your time.

However, you may also update chipset drivers from the following links:

http://download.gigabyte.us/FileList/Driver/mb_driver_chipset_intel_6series.exe

http://download.gigabyte.us/FileList/Driver/mb_driver_intel_me_6series.exe

Please keep us updated on the status of the issue.

Thank you

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I was able to install the chipset driver, the other one does not want to install because my pc does not meet the lowest requirements :P

I did install those once when I was on windows 8, so they might still apply on my system anyway.

I just got 2 more BSOD again within minutes after each other and I've placed them together with the other dump over here. The only thing I did after the 1st BSOD was opening up this website to post a message and copying the dump to my onedrive. During the first one I was watching a video with Chrome.

edit: I'll be gone for a holiday, so I won't be able to reply for 2 weeks.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Came back today from my holiday and was welcomed back by a bsod just minutes after starting my computer hehe :P

I've updated to the last build now (RTM I suppose since the buildnumber is gone) and haven't got the bsod so far, but I'll report back here when it does. Any other ideas so far which might be of help to me if it does return again? :)

Thanks in advanded.

Edit the day after: and here is a new dump from the latest build with the name 072015-10500-01.dmp 

edit 23/7: I've added more dumps to the list from the last days. In the mean time I've got the nvidia hotfix driver forced through windows update (353.38), which also just gave me 2 bsod within minutes after each other. The dumps are all in the map :P

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Replying again here since it's been some time since the last reply and I got more dumps and geforce builds since my last update.

I'm on a clean installed windows 10 pro, 64 bit official version since today with the latest geforce 353.62 driver... which still gives me bsod's. With clean install I mean that I've opted out of the insider versions and let windows refresh my computer (with deleting all of the files on the drive). I've added the latest dumps to the folder I'm sharing as well.

There are recently also bsod's with the error Page_Fault_in-Nonpaged_Area in addition to the System_Service_Exception.

I've already looked that one up and found some suggestions with turning your virtual memory for the harddrive off, restarting and turn it back on, but that didn't stop that bsod from coming back again.

Edit: Continuing the search on what to do. I've now let SLI disabled on 353.62, because I've found that the games I'm playing atm are still fine without it and I was already suspicious of SLI for a while as possible culprit. So far no bsod yet after a day of use, but I'll just let this stay on for a week and report back here if no bsod occurs. I wouldn't be too surprised if SLI is causing part the problem. In the years using SLI it has caused problems multiple times and I'll make sure to never get 2 videocards together again for the small extra performance it gives.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Flippiej,

I'm jumping in here as well as I'm also getting the same BSOD's as you.

Also clean install after I thought it was an issue with upgrade - not complaining as I was due.

Still I'm now on NVidia version 353.62 and as soon as I move to surround (sli) it bombs out.

Crash analysis below.

I'm leaning towards a DirectX 12 issue...

Will do some more reading and see what dxdiag comes up with.


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 1/08/2015 1:51:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080115-12078-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA6D6E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8011AB66D6E, 0xFFFFD0002507D2C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 1/08/2015 1:51:08 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrHistoryInit+0x7F9E)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8011AB66D6E, 0xFFFFD0002507D2C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi windsurfer_dude.

Too bad you're in the same situation. I can confirm that I haven't got a single bsod for a couple of days now with SLI disabled.

From reading the geforce forums there seems to be a general problem with a memoryleak in Vram with SLI enabled in Windows 10, although no one is reporting bsod's as we have.

Nvidia did confirm that issue and said they're working on it, so let's hope that those coming fixes will also stop our bsod's from happening.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yeah non-SLI works fine, but when I want to play games over my 3 screens I need it spanned.

It's strange though that is sort of works, if I don't go into Windows Display properties after I've spanned it doesn't crash.

But then it's not really ok as it has some zoomed in affect that makes my 5760x1080 look zoomed in.

My racing car game looks like I have my head on the dashboard as opposed to my normal sitting position.

 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Update - I think I found my issue.

Looked like my FW for my video cards was out a revision... strange as the latest revision was still over a year old.

2x GTX670FTW 2GB (ver 80.04.5C.00.70)

Updated and then I could span - as I could before - but this time I could go into the Windows Display setting without it crashing...

Then I saw the size of the txt bar was at 125% - reduced that back to 100% and looked normal.

Rebooted - Still looked good.

Played my driving game and all worked sweet...

So stoked I'm back to normal with Win10 fully running!

Hope this helps someone! :)

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated November 24, 2023 Views 48,974 Applies to: