Hi,
I am getting the BSOD's.
It cannot be a hardware fail because in Ubunut the system does not freeze.
Here I upload the minidump files.
The system is a laptop TravelMate 5720.
Is windows 7 32 Bits
- the original installed OS on the system was Vista
- Full Retail
- The laptop is 3 years old
- New OS instalation
Thank You very Much.
The analysis inconclusive you should at least up date these drivers. if the crashes still happen run driver verifier to find the offending driver.
Code:
nscirda.sys 1/19/2008 0:55:24 0x479190cc 0x92ab8000 0x92abf800 0x00007800
VSTCNXT3.SYS 10/15/2008 19:29:13 0x48f68ad9 0x9310e000 0x931c3000 0x000b5000
VSTAZL3.SYS 10/15/2008 19:30:03 0x48f68b0b 0x82544000 0x82581000 0x0003d000
VSTDPV3.SYS 10/15/2008 19:32:04 0x48f68b84 0x9300c000 0x9310e000 0x00102000
netw5v32.sys 3/26/2009 11:10:37 0x49cba8fd 0x9262a000 0x92a3d000 0x00413000
b57nd60x.sys 4/26/2009 6:15:34 0x49f44256 0x8240f000 0x8244b000 0x0003c000
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.
- - The most common drivers are listed on this page: Driver Reference
Driver Reference
- - Driver manufacturer links are on this page:
Drivers and Downloads
Beyond that, please run Verifier with these settings:
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:
Code:
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
Using Driver Verifier to identify issues with Windows drivers for advanced users
Ken J
