Randon BSOD System_Service_Exception

Page 1 of 2 12 LastLast

  1. Posts : 47
    Windows Home Premium 64bit
       #1

    Randon BSOD System_Service_Exception


    I am getting the BSOD S_S_E and I'm not sure why. From what I've read it seems to usually be a memory issue or a VGA driver. I have ran the Mem Diag with zero results and ensured that my video crad driver was up to date. I could not get perfmon / report to run. "The parameter is incorrect." is the error I get.

    I have attached the .zip file and would appreciate any assistance I could get.

    Thanks for the help!

    garthrs
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    garthrs said:
    I am getting the BSOD S_S_E and I'm not sure why. From what I've read it seems to usually be a memory issue or a VGA driver. I have ran the Mem Diag with zero results and ensured that my video crad driver was up to date. I could not get perfmon / report to run. "The parameter is incorrect." is the error I get.

    I have attached the .zip file and would appreciate any assistance I could get.

    Thanks for the help!

    garthrs
    Two issues

    1- Your Symantec.

    I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
    http://us.norton.com/support/kb/web_...080710133834EN

    Microsoft Security Essentials - Free Antivirus for Windows

    2- Memory corruption

    These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable


    Further Reading
    Using Driver Verifier to identify issues with Windows drivers for advanced users


      My Computer


  3. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #3

    Thank you. I'll try those out now.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    garthrs said:
    Thank you. I'll try those out now.
    Good luck and let us know if you need help
      My Computer


  5. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #5

    Quick question: the Verifier got its BSOD... now what? Is there a file I'm supposed to have? A report to read? It only asked me if I wanted to submit the data. The additional info was two links to ULA and a C:/Windows/MEMORY.DMP link... since I can't open .DMP files i figured I should ask what to do now.
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    garthrs said:
    Quick question: the Verifier got its BSOD... now what? Is there a file I'm supposed to have? A report to read? It only asked me if I wanted to submit the data. The additional info was two links to ULA and a C:/Windows/MEMORY.DMP link... since I can't open .DMP files i figured I should ask what to do now.
    Upload the DMP files as usual
      My Computer


  7. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #7

    Lol! Thank you for your patience with me as I stumble through this.

    Ok. Final Results:

    Symantec removed

    Memtest passed 6 times 0 Errors

    Driver verifier forced 2 crashes I think, definitely one. Sorry, they all run together.

    Re-package .dmps and uploaded to post.

    Thanks for all the help so far.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    garthrs said:
    Lol! Thank you for your patience with me as I stumble through this.

    Ok. Final Results:

    Symantec removed No it is not

    Memtest passed 6 times 0 Errors

    Driver verifier forced 2 crashes I think, definitely one. Sorry, they all run together. None of these were driver verifier enabled

    Re-package .dmps and uploaded to post.

    Thanks for all the help so far.

    Still memory corruption. Symantec still installed.
    Last edited by zigzag3143; 29 Feb 2012 at 00:41.
      My Computer


  9. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #9

    I'll make sure Symantec is removed. Will that stop the memory corruption?
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    garthrs said:
    I'll make sure Symantec is removed. Will that stop the memory corruption?
    It may or may not. You can run these two tests after you take Symantec off.


    These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

    If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!



    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5 or 6 passes.

    Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.

    If a known good stick fails in a motherboard slot it is probably the slot.

    RAM - Test with Memtest86+



    2-Driver verifier

    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable


    Further Reading
    Using Driver Verifier to identify issues with Windows drivers for advanced users
      My Computer


 
Page 1 of 2 12 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 13:51.
Find Us