Blue Screen of Death (SYSTEM_SERVICE_EXCEPTION)

[Peritum]

This is an issue I get with many games, my computer is just really quite unstable for whatever reason, but I was just wondering if anyone had any idea how I could prevent these crashes while playing the game, becuase holy crap, MGSV is a hell of a lot of fun. Thanks for any help you can give me!

[Democracy Officer 0311]

I haven't had blue screens since my first computer. think it was windows xp. yeah that brings back memories. alot of memories. all of them bad. If you know your computer is unstable and blue screening for multiple games, that most likely means your computer is out of date and needs to be tuned up or replaced entirely.

[cerebus23]

https://www.google.com/search?newwindow=1&biw=1341&bih=601&q=system+service+exception+blue+screen+fix&oq=SYSTEM_SERVICE_EXCEPTION+bule&gs_l=serp.1.1.0i22i30k1l5.2409239.2412631.0.2416937.6.6.0.0.0.0.490.1285.0j3j1j0j1.5.0....0...1c.1.64.serp..1.4.1075...0.B_-bwsV1zXM

Google helps :P.

There are a number of results for win 7, win 10 etc. See what one fits your situation and good luck.

[Peritum]

Originally posted by cerebus23:

https://www.google.com/search?newwindow=1&biw=1341&bih=601&q=system+service+exception+blue+screen+fix&oq=SYSTEM_SERVICE_EXCEPTION+bule&gs_l=serp.1.1.0i22i30k1l5.2409239.2412631.0.2416937.6.6.0.0.0.0.490.1285.0j3j1j0j1.5.0....0...1c.1.64.serp..1.4.1075...0.B_-bwsV1zXM

Google helps :P.

There are a number of results for win 7, win 10 etc. See what one fits your situation and good luck.

It's funny, I updated ALL my drivers today and it seemed to have solved the System_Service_Exception problem... except after just 2 hours of playing MGSV I got another bluescreen, this time it was kmode_exception_not_handled. So yeah, the only thing left that could be causing these damned blue screens is... I have no idea.

[cerebus23]

Kmode error seems to be centered around faulty hardware, or driver install.

http://www.tomshardware.com/faq/id-1655596/fix-kmode-exception-handled-error-windows.html

http://windowsreport.com/kmode-exception-windows-10/

If you have done overclocking at all it might be wise to do a burn in or stress test and see if it causes the error. Then it might be advisable to reset your clocks, and start over. Maybe try dialing your oc back, or up your voltage a tad to see if it cures it. Some combo.

Otherwise get a driver cleaner, and redo your audio and video drivers making sure to uninstall, run the cleaner to clean out any left over files or registry entries, and do a clean install of those drivers. And if that fails you might just have a hardware component going bad and well that might be harder to track down, but seeming it is around gaming, which puts stress on your video card, ram, psu, cpu start by trying to trouble shoot those.

[Peritum]

Originally posted by cerebus23:

Kmode error seems to be centered around faulty hardware, or driver install.

http://www.tomshardware.com/faq/id-1655596/fix-kmode-exception-handled-error-windows.html

http://windowsreport.com/kmode-exception-windows-10/

If you have done overclocking at all it might be wise to do a burn in or stress test and see if it causes the error. Then it might be advisable to reset your clocks, and start over. Maybe try dialing your oc back, or up your voltage a tad to see if it cures it. Some combo.

Otherwise get a driver cleaner, and redo your audio and video drivers making sure to uninstall, run the cleaner to clean out any left over files or registry entries, and do a clean install of those drivers. And if that fails you might just have a hardware component going bad and well that might be harder to track down, but seeming it is around gaming, which puts stress on your video card, ram, psu, cpu start by trying to trouble shoot those.

Alright, my computer isn't overclocked, and I recently got new ram (My old ram was causing red screens of death, which were tons of fun in their own right). I'll try reinstalling audio and video drivers and I'll get back to you. Thanks for all the help.

[Vayra]

Originally posted by Peritum:

Originally posted by cerebus23:

https://www.google.com/search?newwindow=1&biw=1341&bih=601&q=system+service+exception+blue+screen+fix&oq=SYSTEM_SERVICE_EXCEPTION+bule&gs_l=serp.1.1.0i22i30k1l5.2409239.2412631.0.2416937.6.6.0.0.0.0.490.1285.0j3j1j0j1.5.0....0...1c.1.64.serp..1.4.1075...0.B_-bwsV1zXM

Google helps :P.

There are a number of results for win 7, win 10 etc. See what one fits your situation and good luck.

It's funny, I updated ALL my drivers today and it seemed to have solved the System_Service_Exception problem... except after just 2 hours of playing MGSV I got another bluescreen, this time it was kmode_exception_not_handled. So yeah, the only thing left that could be causing these damned blue screens is... I have no idea.

Basically with most BSOD codes that are not fixed after the 'most obvious' solutions (this includes driver updates, and in case of GPU drivers, even rolling back to a previous, stable one is often a good solution) are tried, it means you've got a serious issue with:

A. your Windows installation (Less likely on W10 than on 7/8/8.1, because auto update)
B. hardware

This stuff won't stop until you fix it. And there are no temporary fixes. Find the root cause, which means: open up your case, clear out dust, and diagnose your hardware. You can do that by removing all hardware from the system except your Windows boot disk and 1 stick of RAM plus your CPU. Boot PC, run and stress it a few hours (play a game, etc.) and if it doesn't BSOD, add another piece of hardware, like the other RAM stick. Repeat until you find what part's doing the voodoo.

Also, it helps to 'read between the lines' when it comes to BSOD stop codes. If you get a lot of memory exceptions, run a memtest and double check RAM + installed applications and OS. If you get a lot of disk access errors, check all drives and especially the SATA cabling (yes, they can break too, had this once myself). And so on. Think logically, and relate error codes to hardware problems and look for them. Above all, whatever you do, do it step by step, and one piece of hardware at a time.

Enjoy...

PS. just noted you bought new RAM... in that case, look at RAM first. Run your system with one stick at a time, swap them around. Windows pagefile will solve any RAM capacity issues for the time being anyway. Buying DOA RAM sticks is not uncommon at all. My first Kingston RAM sticks were blown up inside out of the box... In addition, are the sticks you bought on the supported list for your motherboard? Double check that, and make sure they are two of the exact same sticks (brand, clockspeed, latency)

[Peritum]

Originally posted by Vayra:

Originally posted by Peritum:

It's funny, I updated ALL my drivers today and it seemed to have solved the System_Service_Exception problem... except after just 2 hours of playing MGSV I got another bluescreen, this time it was kmode_exception_not_handled. So yeah, the only thing left that could be causing these damned blue screens is... I have no idea.

Basically with most BSOD codes that are not fixed after the 'most obvious' solutions (this includes driver updates, and in case of GPU drivers, even rolling back to a previous, stable one is often a good solution) are tried, it means you've got a serious issue with:

A. your Windows installation (Less likely on W10 than on 7/8/8.1, because auto update)
B. hardware

This stuff won't stop until you fix it. And there are no temporary fixes. Find the root cause, which means: open up your case, clear out dust, and diagnose your hardware. You can do that by removing all hardware from the system except your Windows boot disk and 1 stick of RAM plus your CPU. Boot PC, run and stress it a few hours (play a game, etc.) and if it doesn't BSOD, add another piece of hardware, like the other RAM stick. Repeat until you find what part's doing the voodoo.

Also, it helps to 'read between the lines' when it comes to BSOD stop codes. If you get a lot of memory exceptions, run a memtest and double check RAM + installed applications and OS. If you get a lot of disk access errors, check all drives and especially the SATA cabling (yes, they can break too, had this once myself). And so on. Think logically, and relate error codes to hardware problems and look for them. Above all, whatever you do, do it step by step, and one piece of hardware at a time.

Enjoy...

PS. just noted you bought new RAM... in that case, look at RAM first. Run your system with one stick at a time, swap them around. Windows pagefile will solve any RAM capacity issues for the time being anyway. Buying DOA RAM sticks is not uncommon at all. My first Kingston RAM sticks were blown up inside out of the box... In addition, are the sticks you bought on the supported list for your motherboard? Double check that, and make sure they are two of the exact same sticks (brand, clockspeed, latency)

Thanks for all the advice! It'll be a while until I find the time to take apart my computer, but in the mean time I'll keep that in mind. I'll get back to you (that is if I remember of course) If I manage to make any progress. Thanks again!