BSOD SYSTEM_SERVICE_EXCEPTION at startup

Page 1 of 4 123 ... LastLast

  1. Posts : 20
    Windows 7 Professional 64-bit
       #1

    BSOD SYSTEM_SERVICE_EXCEPTION at startup


    This was originally posted here: HELP! - BSOD SYSTEM_SERVICE_EXCEPTION at startup - Microsoft Community


    But, due to not having a reply for almost five days, I decided to move here.


    Sorry in advance for the monster post .



    Here is the original post:


    Running Windows 7 64-bit.



    This happened immediately after restarting Windows to install a Windows update.
    I have also updated by graphics card drivers recently, but I think I restarted after that and it worked just fine. I also updated SimCity, but that shouldn't have done this.

    When I start-up my computer, I get the ASUS logo, then the windows pulsing logo, then this BSOD:

    This stays up until the physical memory is dumped to disk, then it disappears. If I just leave it, it takes me to Windows Repair Mode (or something of similar description). One of the options is letting Windows fix the problem, but the Wizard says it can't fix it. I can try to restore my system to an earlier time (I have an external backup drive), but if fails with this error:



    Backup error:
    0x80070057
    The parameter is incorrect.



    I can log onto Safe Mode as Admin, but not my User account. I cannot restore from there as it says "Windows Protection is currently turned off", and there is no way to turn it back on in Safe Mode.

    After some researching, I thought it may be this bug: Microsoft pulls its August Windows update after users report crashes | PCWorld but due to that being in August and restarting several times since then, and the fix provided by Microsoft not working, it is probably not that (even though it has the same symptoms - exact same BSOD, and only affecting 64-bit OSs).



    If it helps:







    Restarting has same effect.

    Thanks in advance for any helpful replies =)



    EDIT:



    Here is the first crash:

    wikisend.com/download/308448/103114-85082-01.dmp



    And here is the most recent: (EDIT: not any more)


    wikisend.com/download/519752/110614-22058-01.dmp


    And here is some more information:


    The person on the Microsoft forum said it was memory corruption probably due to a driver. He Asked me to run Verifier without the Microsoft drivers. Here is the .dmp from the BSOD straight after that: Wikisend: free file sharing service


    The next step was to run sfc /scannow . That came up clean.



    I ran Memory Diagnostics twice (8 passes each time) but the results didn't turn up in the Event Viewer -> Windows Logs -> System like others say they would, although it was logged twice that Memory Diagnostics had been scheduled to execute immediately. I watched the process at the final pass all the way to 100% and nothing showed up under "Status" on the actual display.



    Running Verifier again with the Microsoft drivers ticked this time; here is the .dmp after BSOD:

    Wikisend: free file sharing service
    I just realised it will expire in 4 days and I can't change it so sorry about that. It's attached to the post as a .zip. This is where support from the poster stopped. I still need help, this problem is unresolved. I use my laptop for important work (as well as gaming lol) and the longer it is out of action the bigger the repercussions.
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Code:
    fffff880`059e45d0  00000000`00000010
    fffff880`059e45d8  00000000`00010286
    fffff880`059e45e0  00000000`0000000c
    fffff880`059e45e8  fffff880`02fe72c0Unable to load image \SystemRoot\system32\DRIVERS\RiftEnabler.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for RiftEnabler.sys
    *** ERROR: Module load completed but symbols could not be loaded for RiftEnabler.sys
     RiftEnabler+0x72c0
    fffff880`059e45f0  fffff880`04b6c8d7 igdkmd64+0xb08d7
    fffff880`059e45f8  fffff880`02fe0000 RiftEnabler
    fffff880`059e4600  fffff880`02ff1378 RiftEnabler+0x1137
    The problem seems to be associated with the Occulus Virtual Display Driver, but I need more information to diagnose the problem better.

    Please follow this:

    1. Download the DM Log Collector application to your desktop by clicking the link below

    DM Log Collector.exe

    2. Run it by double-clicking the icon on your desktop, and follow the prompts.
    3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

      My Computer


  3. Posts : 20
    Windows 7 Professional 64-bit
    Thread Starter
       #3

    Zip file of DM log collector


    I had to do it in Safe Mode.

    File is attached. Thanks for the swift reply! And, judging by your badges, it looks like I've got an expert on board

    I did recently install this driver: VIREio Perception - Free VR 3D Driver for the Oculus Rift but I restarted after that and no problems.

    And even more recently I installed this: [Beta] - Unofficial VR Game Launcher/Manager - By Bilago : oculus

    And, now that I remember, over a month ago I installed the Oculus Rift SDK and runtime, as well as MineCrift, and used the Oculus Rift on this machine.
      My Computer


  4. Posts : 20
    Windows 7 Professional 64-bit
    Thread Starter
       #4

    Just found this forum topic:

    https://forums.oculus.com/viewtopic.php?f=34&t=12342

    Might this be my issue?
      My Computer


  5. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #5

    DrGlick said:
    Just found this forum topic:

    https://forums.oculus.com/viewtopic.php?f=34&t=12342

    Might this be my issue?
    Yes, it may well be, but I notice the system driver is stopped.
    Code:
    riftenabler	Oculus VR Rift Display Mgr	c:\windows\system32\drivers\riftenabler.sys	Kernel Driver	No	System	Stopped	OK	Ignore	No	No
    You might also see if there is an updated driver for your video card that might address the issue:
    Code:
    fffff880`05b9ed70  00000000`00000000
    fffff880`05b9ed78  fffff880`05b9ee40
    fffff880`05b9ed80  fffff880`04fb6c14Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
     igdkmd64+0x4f0c14
    fffff880`05b9ed88  fffff880`04fb6c14 igdkmd64+0x4f0c14
    fffff880`05b9ed90  00000000`00000000
    fffff880`05b9ed98  fffff980`12d6eb50
    fffff880`05b9eda0  00000000`80000000
    Code:
    start             end                 module name
    fffff880`04ac6000 fffff880`04fe3740   igdkmd64 T (no symbols)           
        Loaded symbol image file: igdkmd64.sys
        Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
        Image name: igdkmd64.sys
        Timestamp:        Fri Mar 21 02:10:31 2014 (532B0BEF)
        CheckSum:         0052311A
        ImageSize:        0051D740
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    https://downloadcenter.intel.com/Default.aspx
      My Computer


  6. Posts : 20
    Windows 7 Professional 64-bit
    Thread Starter
       #6

    I downloaded the Intel automatic driver updater, but due to being in Safe Mode and the Installer service not running, I can't. I then tried to manually find my driver, but the latest was from 2013. I think. I'm actually not too sure I was looking for the right thing. What am I looking for , exactly? My CPU is an Intel Core i5-2410M.
    Also, trying to find out exactly what I've got adapter wise through Display -> Screen resolution -> Advanced Settings doesn't work, again because of a service that is not running (there is no information displayed where there should be).
      My Computer


  7. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #7

    Mmmmm.......this is getting tricky. Have you tried running sfc /scannow from an elevated command prompt whilst in Safe Mode? I'm hoping it might fix any errors and then allow you to boot normally. Run it 3 times, one straight after the other.

    1. Click Start
    2. In the search box, type cmd
    3. In the list that appears, right-click on cmd.exe and choose Run as administrator
    4. In the command window that opens, type sfc /scannow and hit enter.

    Report the output that appears in the command window once it finishes.

    The more I read this thread, the more it sounds as if its more than just a plain BSOD, but we'll keep at it till its solved.
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #8

    DrGlick, if the above doesn't work for you, I think the best thing to do is uninstall all the Occulus software completely, then test the system for stability.
      My Computer


  9. Posts : 20
    Windows 7 Professional 64-bit
    Thread Starter
       #9

    I did run an sfc a few days ago, but I'll do it three times like you said and see what happens. Thanks.

    EDIT:

    Found out a different way what graphics adapter I have, its a series 2 3000. There is a driver on the website from 4/10/2014, downloading that. I though I was up to date with drivers; but I didn't even know this even had drivers.
    Last edited by DrGlick; 11 Nov 2014 at 16:21. Reason: Update
      My Computer


  10. Posts : 20
    Windows 7 Professional 64-bit
    Thread Starter
       #10

    I uninstalled the Oculus SDK and runtime, and installed the latest driver for my graphics adapter. Still BSOD.
      My Computer


 
Page 1 of 4 123 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:53.
Find Us