BSOD Frequent Errors 0x0000000a and 0x0000000e

[deddex]

Hello,

I am trying to fix a computer for a relative, but cannot seem to figure out the cause of these BSOD's, they are frequent, with the computer running typically for less than 5 minutes before crashing out, once or twice for longer since I've received it. I removed expired versions of norton internet security and another norton program as well as a basic virus scan with malwarebytes. The laptop also passed a single full pass from memtest.

Attached is the seven forums.zip requested.

The computer is a sony vaio laptop running windows 7 home premium 64bit

Thank you for your time.
-Tyler

 

[richc46]

Welcome
The good news is that all your dump reports were consistent. The bad news is that they indicate a driver as the problem. The driver is a Microsoft Driver and is actually not the cause, however. This consistency leads me to believe that it is a driver problem. Use Driver Verfier to help us find out which one.

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/Windows 7 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

 

[deddex]

Thank you for the reply.

I followed your instructions, and the system is crashing before fully loading windows with no associated BSOD, just a black screen and a reboot. I am running the laptop in safe mode, but have been unable to get a BSOD so far in safe mode. Do I need to run verifier from in safe mode, or do the settings transfer between safe mode and the normal mode?

Thank you,
-Tyler

 

[richc46]

Unfortunately Driver Verifier must be in regular mode. It tests the various drivers. In safe mode very few drivers are in use and the others cannot be tested.

 

[richc46]

Not as good as the verifier, but in lieu of that try the clean boot procedure
http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[deddex]

I ran through it as suggested, but even with all of the startup processed disable I had a BSOD. I had a second one after restarting all of the processes. I've attached the sevenforum file as before. Let me know if any more can be learned from this.

Thanks,
-Tyler

 

[richc46]

They continue to hint at a driver. There is nothing that I can do without that driver verifier test. The test will help us determine which driver.
Try to run it in safe mode. If it runs, more evidence of a driver.

 

[deddex]

Run just the PC in safe mode? or the driver verifier?

-Tyler

 

[richc46]

Just run in safe mode. If it runs theres a real good chance that the problem is a driver. Just want to be sure as possible.

 

[deddex]

ok, I have done that already and I haven't seen a crash in safe mode yet. Only in normal mode. Would the driver that is an issue be the reason the computer won't boot when the verifier is used? If so couldn't I use the verifier to select different drivers until it boots successfully to narrow down and identify the problem driver?

-Tyler

 

[richc46]

Yes, you can do it that way. May take a very long time
Did this problem occur after you made a change, new software etc?

 

[deddex]

It is not my pc, I was just told it started doing it. I've never had much luck with BSOD's besides full reinstalls. I was able to run the verifier with one group that BSOD'd just after boot. I am attaching the file, the latest 2 are with the verifier. It looks to my untrained eye to point to sfep.sys. I plan to try to find the newest version and uninstall what is on the machine and replace it with the newest one.

-Tyler

 

[richc46]

Yes, it appears that with the verifier that was the driver singled out.
Productname:Sony Firmware Extension Parser driver for VAIO Series Description:Sony Firmware Extension Parser driver Company:Sony Corporation File size:Various

Try to update the driver
Go to the company website.