BSOD Toshiba U500 Satellite Win 7 - 32

[Akhenat0n]

Hi all,

I ve been told rather advised to join this forum in order to require help for my BSOD problem. Firstly, I honestly wasnt expecting that amount of people suffering exactly the same problem with Win 7 !!! That was really freaked me out and I do really hope some of you guys can be able to provide some solid info....

I recently bought this laptop which is brand new and my first time to experiencing with blue screen problem with it.

I copied, zipped and attached it as you can see the "DMP.FILE" for anyone whom may or may not be able to give me an advice for this particular problem.

Thx in advance and your help will be highly appreciated.

 

[usasma]

Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following (this will not affect the analysis of the current files - but it may help later files that are acquired):
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

So, let's try this the old-fashioned way.....

This is a STOP 0xF4 error that blames ntkrnlpa.exe as at fault. This isn't the case - as a problem of this sort would cause many more problems than you're currently suffering from.

The most likely issue, IMO, is either a "hacked" OS - or a malware infection. If this is the case, then repairs of any sort are unlikely to work effectively.

If this isn't the case, then you try running 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: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD:

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Debug session time: Tue Mar 23 19:30:41.142 2010 (GMT-4)
System Uptime: 0 days 4:57:11.311
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
BUGCHECK_STR:  0xF4