Dump file help

[bilbonvidia]

Hi, I am having issue reading the dumpfile after installing the dbugging tool.

"Symbol search path is: %windir%\symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82c42000 PsLoadedModuleList = 0x82d8a810
Debug session time: Wed Jan 2 09:07:58.289 2002 (UTC + 0:00)
System Uptime: 0 days 0:00:35.178
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2"

The sysmbols are installed.

Can someone look at the dump and tell be what it is pointing to? I supect a system file is corrupt but startup repair wont work.

Thnk you

 

[usasma]

Corrupt system files aren't very likely - as Windows System File Checker does a good job of ensuring that they don't get corrupted.

Quite often this type of error is due to a virus infection, so I'd suggest trying a couple of these free, online scans (in case your antivirus has become corrupted): Free Online AntiMalware Scanners

If that doesn't fix things up, then please post this info: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Then please uninstall Daemon Tools/Alcohol 120% (a known cause of BSOD's).
Then use this free tool to remove the offending sptd.sys driver: DuplexSecure - FAQ - Remove 32 bit sptd.sys

Then do this:
OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[FONT=lucida console]
sptd.sys     Sun Oct 11 16:54:02 2009 (4AD245EA)
nvstor32.sys Wed Apr 29 21:52:55 2009 (49F90477)
amdxata.sys  Tue May 19 13:57:35 2009 (4A12F30F)
Rt86win7.sys Thu Feb 26 04:04:22 2009 (49A65B16)
[COLOR=Red]lmimirr.sys  Tue Apr 10 18:32:11 2007 (461C106B)[/COLOR]
[COLOR=Red]AsIO.sys     Mon Dec 17 04:10:20 2007 (47663CFC)[/COLOR]
ASACPI.sys   Wed May 13 07:11:32 2009 (4A0AAAE4)
nvsmu.sys    Fri Apr 24 23:07:19 2009 (49F27E67)
nvlddmkm.sys Thu May 14 16:32:27 2009 (4A0C7FDB)
[/FONT]

http://www.carrona.org/dvrref.html#sptd.sys
http://www.carrona.org/dvrref.html#nvstor32.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#Rt86win7.sys
http://www.carrona.org/dvrref.html#lmimirr.sys
http://www.carrona.org/dvrref.html#AsIO.sys
http://www.carrona.org/dvrref.html#ASACPI.sys
http://www.carrona.org/dvrref.html#nvsmu.sys
http://www.carrona.org/dvrref.html#nvlddmkm.sys

If that doesn't fix things, then 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Debug session time: Wed Jan  2 05:26:29.336 2002 (UTC - 4:00)
System Uptime: 0 days 0:00:25.225
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_C000014F
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
FAILURE_BUCKET_ID:  0xF4_C000014F_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000003 86a06d40 86a06eac 82e290e0
BiosVersion = 0519   
BiosReleaseDate = 04/29/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]