Blue screen (please analyze dmp file)

[nontan]

Please kindly help to analyze of problem dmp file?
I find problem as boot by i have 2 dmp file
link of dmp file, i cannot understand its

013010-26145-01.dmp
013010-26613-01.dmp


thank you very much

 

[seekermeister]

I'm posting a link to a similar thread that I just responded to. It may be of more help than someone directly answering your question:

http://www.sevenforums.com/crashes-debugging/59619-win7-bsod-help-needed.html

 

[usasma]

The dump files point to pool corruption (an issue with memory - either the contents of memory or the hardware) and ndis.sys - a component of Windows networking.

So, we'll have to address both errors. First, try this:
- download the latest copies of your networking drivers (both wired and wireless if so equipped).
- uninstall the currently installed networking drivers
- install the freshly downloaded drivers and monitor for further BSOD's.

Also, please remove these older drivers that were loaded at the time of the crash (some of them relate to your networking drivers also). Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall/remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- some driver links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

ISODrv64.sys Fri Nov 02 23:21:18 2007 - ISO CD-ROM Device Driver                              - ISODrive                               - EZB Systems, Inc
urvpnv64.sys Thu Dec 13 15:13:53 2007 - see comments below this box
iaStor.sys   Thu Dec 04 15:47:09 2008 - Intel storage drivers
virtualnet.sys Wed Dec 10 22:52:00 2008 - DVB Fast modem NIC driver                              - SDMC DVB PCI                               - SDMC                              [U][B]OR[/B] ShrewSoft Virtual Network Adapter[/U]                              [U][B]OR[/B][/U] NetworkManager: SCPlugin

For urvpnv64.sys:
- search your computer for it. Once located, right click, select Properties, then select Details and let us know what it says.
- then upload the file to Jotti's malware scan for a virus scan. Let us know the results.

At this point it's time to wait for the next BSOD. If it occurs, zip it up and upload/attach it to your next post. Then follow the next set of directions to start working on the pool corruption.

To address the pool corruption, 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: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD's here:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 30 00:22:22.222 2010 (GMT-5)
System Uptime: 0 days 0:00:46.142
BugCheck C5, {1000000df, 2, 0, fffff800031ecf8c}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 30 00:20:54.732 2010 (GMT-5)
System Uptime: 0 days 0:00:39.652
BugCheck 50, {fffff8800b9ac000, 1, fffff880016fb066, 0}
Probably caused by : ndis.sys ( ndis!memcpy+d6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  ncprwsnt.exe

 

[nontan]

Thank you so much for suggestion, i will try follow by solution you proposed and i will inform results later