BSOD Win 7 Home premium

Hi all,

I have recently bought a sony vaio VPCEB1ME1 with windows 7 home premium and I quite soon started to get the blue screen of death. It can happen on any given moment, but I think it happens most of the time when I am playing music with windows media player. I get a blue screen, although I can spot some text saying there is some kind of problem and that my laptop will reboot to prevent further damage, and it reboots after several seconds The text isn't clear to read, so I have no idea what it says furthermore.

I have enclosed all my dmp files I had until now. I hope you can help me out :)

System information:

Processor: Intel core i3 330m 2.13Ghz
Graphics card: ATI mobility Radeon HD 5650

EDIT: I have also performed a diagnostic test to check my hardware but it did not find any problems.

EDIT2: I have downloaded BlueScreenView and it says my bug check codes are 0x7f and 0x9f and it says that it is (in every case) caused by ntoskrnl.exe

Please let me know if you need any further information.

14 memory dumps occurring from 12 May 2010 to 4 Jun 2010 (~3 weeks)
2 different STOP error codes (11 0x7F; 2 0x9F), with 4 different causes blamed.

You can stop the screen (so you can read it) by following the steps here: http://www.carrona.org/setmini.html (it's the removing of the checkmark in "automatically restart" step)

Info link on STOP 0x7F error
Info link on STOP 0x9F error
Please check the "Usual causes" section in the STOP 0x7F link above.

The three most suspicious causes of the errors (IMO) are:
- the ACPI.sys error
- the 2 networking component errors
- the outdated Sony Firmware Extension Parser driver (SFEP.sys dated 2007)

Please update both your wired (Network section) and wireless networking (Wireless LAN section) drivers from the Sony website: http://esupport.sony.com/US/perl/swu...PCEB1MFX&LOC=3
Also update the Sony Firmware Extension Parser driver (in the System Components section of the above link) - as it has been known to cause BSOD's in Win7.
Please uninstall the current software BEFORE installing the freshly downloaded drivers.

Then, if the BSOD's continue, please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVP

Summary of the BSOD's:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jun  4 07:03:42.479 2010 (GMT-4)
System Uptime: 0 days 0:24:34.071
BugCheck 7F, {8, 80050031, 6f8, fffff800030a0e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed Jun  2 11:54:42.486 2010 (GMT-4)
System Uptime: 0 days 6:39:37.078
BugCheck 7F, {8, 80050031, 6f8, fffff80003041e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 12:21:22.670 2010 (GMT-4)
System Uptime: 0 days 3:54:12.263
BugCheck 9F, {3, fffffa80043b4060, fffff80000b9c518, fffffa80042489d0}
Probably caused by : ACPI.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun May 30 08:26:11.605 2010 (GMT-4)
System Uptime: 0 days 1:07:02.723
BugCheck 7F, {8, 80050031, 6f8, fffff80003039e60}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 12:04:57.100 2010 (GMT-4)
System Uptime: 0 days 0:04:38.318
BugCheck 7F, {8, 80050031, 6f8, fffff80003094e60}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 11:59:18.681 2010 (GMT-4)
System Uptime: 0 days 1:20:32.273
BugCheck 7F, {8, 80050031, 6f8, fffff80003043e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 10:38:15.811 2010 (GMT-4)
System Uptime: 0 days 1:21:54.403
BugCheck 7F, {8, 80050031, 6f8, fffff80003091e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 28 09:15:43.227 2010 (GMT-4)
System Uptime: 0 days 3:46:32.445
BugCheck 7F, {8, 80050031, 6f8, fffff80003057e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Tue May 18 10:51:13.198 2010 (GMT-4)
System Uptime: 0 days 3:13:10.790
BugCheck 7F, {8, 80050031, 6f8, fffff80003055e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Mon May 17 12:53:10.884 2010 (GMT-4)
System Uptime: 0 days 7:40:35.476
BugCheck 7F, {8, 80050031, 6f8, fffff80003047e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri May 14 07:40:35.826 2010 (GMT-4)
System Uptime: 0 days 1:07:15.418
BugCheck 7F, {8, 80050031, 6f8, fffff80003087e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 13 08:27:37.043 2010 (GMT-4)
System Uptime: 0 days 3:19:53.635
BugCheck 1000009F, {4, 258, fffffa800357a040, fffff80000b9c510}
Probably caused by : ndis.sys ( ndis! ?? ::LNCPHCLB::`string'+4fcb )
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu May 13 05:07:11.226 2010 (GMT-4)
System Uptime: 0 days 12:15:06.443
BugCheck 7F, {8, 80050031, 6f8, fffff80002e45e58}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 16:51:05.267 2010 (GMT-4)
System Uptime: 0 days 10:22:13.859
BugCheck 9F, {3, fffffa80042f9a20, fffff80004399518, fffffa8007c3c260}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : yk62x64.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System

Multi-Language installer for your Marvell Yukon LAN card: Marvell: Download Drivers

I would either use the English version of the Driver at the North American website, or I'd contact Sony Europe for a Windows 7 64 bit compatible version of the driver for the Marvell® Atheros® AR9285 Wireless Network Adapter Driver

I don't speak hardly any Dutch, but it appears that you've visited an update page rather than the original driver page.

You may want to contact this website: SchoonePC hulp bij computerproblemen: installeren en optimaliseren van Windows. for assistance in Dutch. I've had many conversations with the owner and he's very good.

OK, we presume that the BSOD is caused by a driver problem because it's the most common cause. Also, different STOP error codes can be more or less likely to be a driver problem - so that affects our judgment on what the cause is. Other possible causes are hardware problems (either broken hardware or incompatible hardware/software). If these aren't the issue, then that only leaves Windows as the problem (very unlikely).

So, presuming that it is a driver issue....
If the driver was working correctly, there wouldn't be a problem.
So, we presume that the driver is corrupted in some way. So, replacing the driver with an identical driver can fix things.

But first, we try to get a newer driver. This is because there may be problem fixes that were made in the newer version. If there isn't a newer version, then we have to be sure that we remove the driver BEFORE installing the freshly downloaded version - just in case the installer skips over that file because the dates are the same. That way we're sure an uncorrupted version of the driver is installed (and the corrupted version has been removed).

Now, let's get into the language versions of a driver. IMO most language versions only address the stuff that's displayed - but I'm not a driver writer so I don't know for sure. But, making that assumption, I'd feel safe in installing (for example) a Japanese language version of a driver if I couldn't find an English version. I'd also make backups to the system and the registry "just in case" things didn't work.

FYI - I currently have a Japanese software driver on my system for a program that does screen manipulation. I can't read a word of the interface, but I can use it because I've experimented with it and know the controls by memorization.

This dump file summary blames the Marvell Yukon adapter on your system:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 16:51:05.267 2010 (GMT-4)
System Uptime: 0 days 10:22:13.859
BugCheck 9F, {3, fffffa80042f9a20, fffff80004399518, fffffa8007c3c260}
*** WARNING: Unable to verify timestamp for yk62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for yk62x64.sys
Probably caused by : yk62x64.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System

So, presuming that it's a driver problem, and that the Marvell Yukon driver is one of those responsible (because there are other causes listed in the other dump files) I suggest that you update your Marvell Yukon network controller. If the presumptions are right, then this will help to fix your system. I found the multi-language version because you expressed a concern about using the American versions.

The Sony Extension Firmware Parser error is one that sticks with me. This is because I wracked my brains over this at work for several days - until I forced the issue using Driver Verifier (and that's why I requested that you use it). This is just a suspicion on my part - it's not as firm a diagnosis as the networking drivers - but when the presence of the driver is combined with the ACPI.sys error - I tend to wonder about it.

FWIW - if we don't work on this last item, it won't hurt things. In the worst case, we'll fix everything else and will still have a problem - so then we can come back to the Sony Firmware Extension Parser if we need to.

Lastly, each device has a Hardware ID number. And, AFAIK, none of these numbers reflects a difference in languages (read the short blurb on "Driver Search Theory" at this link of mine: Drivers and Downloads ) So I identify devices using those numbers (when I can't find anything else) - and use them along with my Driver Search Theory to locate suitable drivers.

I always recommend that you backup the system and the registry (System Restore is an easy way to do this) just in case something goes wrong.

PS - please don't forget to run Driver Verifier.

Did you mean to say that your Marvell Yukon device is turned OFF?
A device can be off - but the driver can still be loaded in memory.
And, if the driver is loaded in memory, then it can influence things.

In this case, we presume that the Marvell Yukon driver caused the crash - because that's what the debugger told us. But even if it didn't directly cause the crash, we do know that it was involved in the memory stack right around the time that the crash occurred - so it's likely that it had some impact on the crash.

Finally, this is just one of several memory dumps. So this may be a significant problem - or it may just be something that distracts us from the actual cause. The only way to find this out is to treat each error as if it's the real thing.