Randon BSOD System_Service_Exception

[garthrs]

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

 

[zigzag3143]

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_view.jsp?wv_type=public_web&docurl=20080710133834EN

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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


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

 

[garthrs]

Thank you. I'll try those out now.

 

[zigzag3143]

Thank you. I'll try those out now.

Good luck and let us know if you need help

 

[garthrs]

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.

 

[zigzag3143]

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

 

[garthrs]

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.

 

[zigzag3143]

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.

 

[garthrs]

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

 

[zigzag3143]

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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


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

 

[garthrs]

I had to manually uninstall the Symantec Antivirus... Very long process. It said some reg keys may remain, but they should not affect anything.

I ran the Memtest a total of 10 times now (All night for two nights). Not a single fault.

I will run the driver verifier again tonight. I'll enable it and run into the ground three or four times. I'll upload the results of that tonight-ish.

Thanks again for all your help and patience.

 

[zigzag3143]

I had to manually uninstall the Symantec Antivirus... Very long process. It said some reg keys may remain, but they should not affect anything.

I ran the Memtest a total of 10 times now (All night for two nights). Not a single fault.

I will run the driver verifier again tonight. I'll enable it and run into the ground three or four times. I'll upload the results of that tonight-ish.

Thanks again for all your help and patience.

Your causes are all over the map. Software, hardware, inconclusive. Please run verifier and these

Then, if the above tests pass, I'd try these free stress tests:

FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90ºC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
If the temperature gets above 105ºC, quit the test - the video card is overheating.
- Click "Quit" to exit

CPU Stress Tests:
- http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=19182&lang=eng
- 7Byte : Hot CPU Tester Pro
- 7Byte : BurnIn64
- CPU Stress test - Overclock.net - Overclocking.net
- Fossil Free Online CPU Load or Stress Test.
- CPU Stability Test description, System Resources Tune-Up. Downloads List By All Time Popularity | PCWorld | PCWorld
- CPU Stress test - Overclock.net - Overclocking.net
- |MG| CPU Stability Test 6.0 Download
- LinX - A simple Linpack interface

Related to wfplwf.sys WFP NDIS 6.20 Lightweight Filter Driver from Microsoft Corporation.

 

[garthrs]

Wow... What would cause this to suddenly start happening?

I'll run these tests. Thanks for all the help.

 

[garthrs]

Ok. I ran verifier and performed:
Furmark 1.9.2 Burn-in Test (Fullscreen 1280 x 720, MSAA 8X, Dynamic Background, Burn-in) for about 10 minutes.
Temp maxed at 74 degrees, but stayed mostly at 73 once it leveled out. It did jump to 77 when I toggle Post -FX

Ran IntelBurnTEst v2.52.

Passed standard test (5 times) results-[12-17-2011]-[174647].log

Passed High test (5 times) results-[12-17-2011]-[175041].log

I have not been able to force a crash... Verifier is enabled... I'll keep forcing the limits. Thanks for the help!

 

[zigzag3143]

Ok. I ran verifier and performed:
Furmark 1.9.2 Burn-in Test (Fullscreen 1280 x 720, MSAA 8X, Dynamic Background, Burn-in) for about 10 minutes.
Temp maxed at 74 degrees, but stayed mostly at 73 once it leveled out. It did jump to 77 when I toggle Post -FX

Ran IntelBurnTEst v2.52.

Passed standard test (5 times) results-[12-17-2011]-[174647].log

Passed High test (5 times) results-[12-17-2011]-[175041].log

I have not been able to force a crash... Verifier is enabled... I'll keep forcing the limits. Thanks for the help!

Good luck and let us know if you need help.

 

[garthrs]

I have been able to force a few faults While Verifier was running.
Work/Life has had me busy, but my son was able to force a few faults while he played Skyrim. I did disable Verifier when I wasn't home.

Man this is getting annoying. Thanks again!

 

[garthrs]

... It has gotten worse...

I will most likely be clean installing Win 7.

 

[garthrs]

Formatted drive and did a clean install of Windows 7
Applied all system updates before I installed a single program.
system crashed 5 more times.
Replaced RAM with known functional RAM.
Still crashing.

I desperately need some help.