BSOD Errors

The dump files are spread out - and this usually indicates a hardware problem.
As such, please do these tests:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

Also, please update this older driver as it's known to cause BSOD's: ASACPI.sys Thu Aug 12 22:52:52 2004
It belongs to the Asus ATK0110 ACPI Utility (and can also be found in their PCProbe and AISuite utilities).

Please post back if the BSOD's continue (after running the diagnostics) and we'll run some tests.

Here's a summary of the BSOD's:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sun Jan 17 20:18:37.846 2010 (GMT-5)
System Uptime: 0 days 12:33:51.347
BugCheck 1000008E, {c0000005, 828df888, 8e613b60, 0}
Probably caused by : memory_corruption ( nt!MiGetNextNode+20 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Wow.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 12:40:48.457 2010 (GMT-5)
System Uptime: 0 days 0:23:14.455
BugCheck A, {ffffffe8, 2, 1, 828bcbbd}
Probably caused by : usbaudio.sys ( usbaudio!USBCaptureProcessPin+dc )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 12:46:53.596 2010 (GMT-5)
System Uptime: 0 days 0:00:19.593
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Tue Jan 19 14:25:54.632 2010 (GMT-5)
System Uptime: 0 days 1:35:28.505
BugCheck D1, {34, 2, 0, 8ac4661a}
Probably caused by : ndis.sys ( ndis!ndisQueuedMiniportDpcWorkItem+38 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Thu Jan 21 16:48:33.135 2010 (GMT-5)
System Uptime: 0 days 8:54:03.133
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
BugCheck 1000008E, {c000001d, 8f516d96, 82b31c28, 0}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+538 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

Can we see the latest BSOD's?
Once you upload them, 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

Please ensure that Driver Verifier is turned off.

This is the infamous ASACPI.SYS BSOD.
Please update this driver: ASACPI.sys Thu Aug 12 22:52:52 2004

From post #2 in this topic:

Code:

Also, please update this older driver as it's known to cause BSOD's: ASACPI.sys   Thu Aug 12 22:52:52 2004
It belongs to the Asus ATK0110 ACPI Utility (and can also be found in their PCProbe and AISuite utilities).

Summary of the BSOD:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Mon Jan 25 09:05:52.368 2010 (GMT-5)
System Uptime: 0 days 0:00:15.412
*** ERROR: Module load completed but symbols could not be loaded for ASACPI.sys
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System

Driver appears to have come back and caused a bluescreen following system restore. I have tried multiple times to update the driver but to no avail. It says the driver i downloaded is not compatible with the hardware when I manually try to have it download and says it is fully up to date when I attempt to automatically install the driver update.

Edit: I now cannot find the device in device manager. It seems to have been replaced with an unknown device.