The computer has rebooted from a bugcheck

Zip up the dump file (that'll make it smaller), then upload it to a free, file-hosting service and post the link here.

Follow the instructions at this link to set your system to make Minidumps in the C:\Windows\Minidump directory: Set MiniDump

Information on the STOP 0x9F error (the info that you posted): BSOD Index

To proceed further (while awaiting the analysis of the large memory dump file, 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:

Code:

Delete these registry keys (verified in Win7 and Vista only):
        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

I'm still running the dump file, but it looks like it blames ATSwpWDF.sys - a component of your Swipe Fingerprint Sensor USB Driver by AuthenTec, Inc.

Please go to the support/downloads website for the manufacturer of your computer and download the latest version of the driver package for your Swipe Fingerprint Sensor.
- Then uninstall the current drivers through Control Panel...Programs...Uninstall a program
- Then install the freshly downloaded driver and monitor for further BSOD's

Also, please remove or update these older drivers that were loaded at the time of the crash. 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 OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those 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 manufacturer links are on this page: http://www.carrona.org/drvrdown.html

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

Code:

agrsm64.sys  Mon Nov 10 10:01:35 2008 - Agere Systems Soft Modem - http://www.carrona.org/dvrref.html#agrsm64.sys
alusbser.sys Wed Jan 23 04:09:27 2008 - no information available for this driver

Please locate the alusbser.sys driver (most likely in the C:\Windows\System32\driver folder), right click on it, select Properties, then select the Details tab. Please let us know what it says for File Description, Product Name, and any other info that you think may help to identify it.

Summary of the BSOD:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 06:38:38.026 2010 (GMT-4)
System Uptime: 0 days 0:56:15.133
BugCheck 9F, {3, fffffa8004c06440, fffff80000b9c518, fffffa8001fd2610}
*** ERROR: Module load completed but symbols could not be loaded for ATSwpWDF.sys
Probably caused by : ATSwpWDF.sys
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System

Do you have any cell phone software installed on your system? The Qualcomm stuff is usually something like an Air Card/WWAN device. I've also seen these devices embedded in Sony and Lenovo laptops. Unfortunately, I'm not able to locate any specifics about it on the Qualcomm website.

Do you have either? If so, can we get the make and model of it?

Thanks for the info!
I'm glad that things are working out.

I did find this link: A-LINK Europe -- 3G Turbo USB adapter 7.2MB/5.7MB (up)
It states that there are 2 firmware upgrades - and one involves Win7 compatibility.
Beyond that, I"m still looking....

If you could provide this info it might help us find the manufacturer of the chipset in the modem (for newer drivers):

Obtaining Hardware ID's to help Identify Hardware
- Go to Start and type in "devmgmt.msc" (without the quotes) and press Enter
- Expand the Network Adapters category by clicking on the + sign to the left of it
- Right click on the network adapter (if there's more than one, do this for all of them) and select Properties.
- Then select the Details tab.
- In the dropdown box, select "Hardware IDs" - and match the info to one of the following descriptions:
- - If the Hardware IDs description contains VEN_ and DEV_, then let us know the 4 characters immediately after the VEN_ and the 4 characters immediately after the DEV_
this is a PCI device and we'll look up the information at http://www.pcidatabase.com
- - If the Hardware IDs description contains VID_ and PID_, then let us know the 4 characters immediately after the VID_ and the 4 characters immediately after the PID_
this is a USB device and we'll look up the information at http://www.linux-usb.org/usb.ids
If you don't have those items in the Hardware IDs description, copy down the entire string of the first entry and include that with your next post.

Thanks, but neither of them is the A-Link device.

It's probably something like:
USB\VID_1E0E&PID_7002 - this is the Qualcomm USB ID number associated with the firmware upgrade for the A-Link modem.

If nothing distinctive comes up (the Qualcomm numbers aren't useful to us), then you'll have to contact A-Link for updated drivers.