Windows 7: Random BSOD 0x0000003b system_service_exception

Cuthalion · 04 Dec 2011

Hey guys and thanks for reading. Running Windows 7 64 bit

Recently I've been dealing with the BSOD 0x03b system service exception, I've already ran memtest through 4 passes and 0 errors. Already using Microsoft security essentials.

Now, to clarify, I used to get BSOD's a lot more often, 0x1e, 0x03b, and some others I can't recall, since I've updated drivers, taken everything out of the computer, cleaned it real well, and placed everything back in. Now I only get the 0x03b.

It also used to only occur while playing games, Rift, and BF3 were the most common. Now it typically occurs while just surfing the internet. I ran windows 7 upgrade advisor and it said that microsoft .NET Framework 1.1 isn't compatible with Windows 7, however after web searching I've found that, that doesn't have much to do with it, most likely.

I've read that this is commonly a video card issue, and was wondering if there was any quick way to see if thats what it is?

System is around 6-7 months old.

zigzag3143 · 04 Dec 2011

Quote: Originally Posted by Cuthalion

Hey guys and thanks for reading. Running Windows 7 64 bit

Recently I've been dealing with the BSOD 0x03b system service exception, I've already ran memtest through 4 passes and 0 errors. Already using Microsoft security essentials.

Now, to clarify, I used to get BSOD's a lot more often, 0x1e, 0x03b, and some others I can't recall, since I've updated drivers, taken everything out of the computer, cleaned it real well, and placed everything back in. Now I only get the 0x03b.

It also used to only occur while playing games, Rift, and BF3 were the most common. Now it typically occurs while just surfing the internet. I ran windows 7 upgrade advisor and it said that microsoft .NET Framework 1.1 isn't compatible with Windows 7, however after web searching I've found that, that doesn't have much to do with it, most likely.

I've read that this is commonly a video card issue, and was wondering if there was any quick way to see if thats what it is?

System is around 6-7 months old.

36 of 50 were caused by a memory exception (probably a driver). Please run these two tests to verify your ram, and find the offending driver.

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

1-Memtest.

Quote:

*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

Code:

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