BSOD caused by SYSTEM_SERVICE_EXCEPTION ntroskrnl.exe

Anonymous
2015-04-29T20:26:51+00:00

Hello

I'm having a pickle of a problem and I'm at a loss how to fix it.

Firstly, please see the following:

https://www.dropbox.com/s/hmtf7irjcwig4hr/042915-23275-01.zip?dl=0

This is the dump file attributed to my latest BSOD.

For the benefit of building a picture of what the problem is, I attach a further two dump files from BSOD's experienced yesterday and a few weeks back.

https://www.dropbox.com/s/j4pz7tqg7wfz9w7/040115-23415-01.zip?dl=0

https://www.dropbox.com/s/0ovv2igm7tq9yky/042715-23306-01.zip?dl=0

I experience these BSOD only when using FSX (Flight Simulator X) and not always in particularly 'stressy' types of environment (high density areas of scenery etc).  I have searched the internet tirelessly looking for a fix and have undertaken the recommendations I have found including MEMtests, Virus scans (using Windows Security Essentials), System checks via CMD & updated GPU drivers. None of which seem to lead to a problem area.

Bizarrely, these BSOD don't occur every time I use FSX but do seem to rear their ugly head after a prolonged period of computer usage. Is my computer getting tired and rebooting in order to have a rest? A bit tongue in cheek but potentially.

Anyway, I would really appreciate some help from the experts on this issue because I'm at a loss where to go and would love to find a 'cure'.

Many thanks in advance for anyone who can offer some guidance.

Dave Potter

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

59 answers

Sort by: Most helpful
  1. Anonymous
    2015-05-18T21:19:26+00:00

    Gerry,

    Updated my drivers as you instructed and we are back to a SYSTEM_SERVICE_EXCEPTION BSOD today. Weirdly, I managed a full day of simming and it was only when I finished and the computer was idle (FSX and 2 support programs were still running), it BSOD. Not during a period of intense computer usage. Was very strange.

    Anyway, here are the usual files for your perusal...

    Dump file https://www.dropbox.com/s/40eow5w6uqin1b2/051815-30420-01.zip?dl=0

    Event viewer Application https://www.dropbox.com/s/as5dwkgoo96ec1m/Event\_Log\_Application.zip?dl=0

    Event viewer system https://www.dropbox.com/s/1asaphx1o9ozgcp/Event\_Log\_System.zip?dl=0

    System information https://www.dropbox.com/s/fssnc0lzpqyv1d9/System\_Information.zip?dl=0

    As always, appreciate any help you can offer.

    Regards

    Dave

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-05-16T13:03:00+00:00

    Dave

    *************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1E, {ffffffffc0000005, fffff800030fda4b, 0, ffffffffffffffff}

    Probably caused by : memory_corruption ( nt!MiMapPageInHyperSpaceWorker+1b )

    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

    BUGCHECK_STR:  0x1E_c0000005

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  fsx.exe

    Comparing the latest dump to the previous crash reveal that the following drivers in the last dump are older than those reported earlier:

    AtihdW76.sys                ATI High Definition Audio Function Driver

    atikmdag.sys                  ATI Radeon Kernel Mode Driver

    atikmpag.sys                  AMD multi-vendor Miniport Driver

    I would update the drivers.

    Please run Driver Verifier –Instructions in link below:

    http://answers.microsoft.com/en-us/windows/wiki/windows\_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    Please upload any resulting dump files to your One Drive and post a link as they occur.

    Please restart your computer, allow 30 minutes for the system to run before uploading further information so that the impact of making changes can become apparent.

    Please provide an updated copy of your System Information file. Type System Information in the Search Box above the start Button and press the ENTER key (alternative is Select Start, All Programs, Accessories, System Tools, System Information). Select File, Export and give the file a name noting where it is located. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here. Reports in normal mode preferred. Please say if the report has been obtained in safe mode. The request for a copy of this file is additional to answering the question about make and model.

    Please upload and share with everyone fresh copies of your System and Application logs from your Event Viewer to your One Drive and post a link here. You can remove any earlier copies of the logs from your OneDrive.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-05-16T11:59:12+00:00

    Gerry

    Good to know that I don't have to worry about the first error.  WSE seems to be working fine, it runs with no errors and scans so I think I can disregard the other warning too.

    HOWEVER! My thoughts that I had fixed the issue have just been thrown out of the window. New BSOD today but this time with a different error.  Please find dump file at the following link for your perusal.

    https://www.dropbox.com/s/96xzp0xweejyyh3/051615-21481-01.zip?dl=0

    If you could take a look and see what you can decipher I'd be grateful.

    Regards

    Dave

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-05-16T04:59:48+00:00

    Dave

    I can see no problems in the logs that require attention.

    You can run your computer without the Catalyst Control Center. Removal has no adverse effect and can be beneficial as it releases resources for other tasks.

    Log Name:      System

    Source:        Microsoft-Windows-Kernel-PnP

    Date:          15/05/2015 19:34:36

    Event ID:      219

    Level:         Warning

    Description:

    The driver \Driver\WUDFRd failed to load for the device USB\VID_413C&PID_2101&MI_01\6&31180a4f&0&0001.

    This warning relates to your USB Dell® SmartCard Reader Keyboard. In most cases Event 219 warnings can be safely ignored. They are believed to occur because the device is being recognised by the system before the related software and drivers have loaded. When the software and drivers load, perhaps milliseconds later, the device works as it should. Most users are unaware that there was a brief moment when the device was not functioning. You are only aware of it because of the creation of the Event 219 report.

    Is there a problem with Microsoft Security Essentials? Please clarify. The last error report is timed at 19:14:25 on 12 May 2015. The problem appears to have gone away.

    Log Name:      System

    Source:        Microsoft Antimalware

    Date:          12/05/2015 19:14:25

    Event ID:      2001

    Level:         Error

    Description:

    Microsoft Antimalware has encountered an error trying to update signatures.

     New Signature Version:

     Previous Signature Version: 1.197.2126.0

     Update Source: Microsoft Update Server

     Update Stage: Download

     Source Path: http://www.microsoft.com

     Signature Type: AntiVirus

     Update Type: Full

     User: NT AUTHORITY\SYSTEM

     Current Engine Version:

     Previous Engine Version: 1.1.11602.0

     Error code: 0x80240016

     Error description: An unexpected problem occurred while checking for updates. For information on installing or troubleshooting updates, see Help and Support.

    Updated definitions have been downloaded and installed on 13 and 15 May.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2015-05-15T19:20:52+00:00

    Gerry

    I think you were right about my temperatures. I ran a check on Speccy and the were stable well within the limits of the card.

    HOWEVER! I think I may well have found the cause of my BSOD's.  A few months ago I watched a tutorial online on how to improve performance of FSX.  This included the download and installation of AMD Catalyst Control Centre.  I did this and performed the tweaks as suggested.  Without my knowledge (I probably missed it during the installation), this program must have also installed a program called Raptr which is an AMD program designed for optimising games/streaming and updating drivers.

    Previously, when looking for a fix for BSOD's, I read a post which stated I should uninstall my graphics card, reboot and allow Windows to install the driver it wants for the Graphics Card. I did this and my BSOD's stopped for a few weeks before becoming an issue again.  I believe what was happening was Raptr was running sporadically to update drivers and I must have missed this.  On Tuesday it came to me as a brain wave to uninstall both AMD CCC & Raptr.  I completed a 9 hour session on Wednesday with no BSOD and my simulator actually ran smoother.

    I'll do some more testing over the weekend but I am optimistic.  I have included a latest system information file and Event viewer log for your perusal.  The only items outstanding on the event view is something relating to Microsoft Security Essentials and according to internet browsing, is a pain in the backside to rectify.  Similarly with the WUDFRD.sys driver, this is an error with a USB but I'm not sure how to eradicate this problem from my computer.

    https://www.dropbox.com/s/as5dwkgoo96ec1m/Event\_Log\_Application.zip?dl=0

    https://www.dropbox.com/s/1asaphx1o9ozgcp/Event\_Log\_System.zip?dl=0

    https://www.dropbox.com/s/gq8t1962ve5c8c4/System\_Information.txt?dl=0

    Thank you for your continued support, I fear without it I would've eventually have given up and put up with the problem.  Fingers crossed I may have found the cure...

    Regards

    Dave

    Was this answer helpful?

    0 comments No comments